Bug#1035387: csound: Regression from Bullseye: K opcodes not initialized at init time
Package: csound
Version: 1:6.18.1+dfsg-1
Tags: fixed-upstream, upstream
See https://github.com/csound/csound/issues/1707
I'd like to NMU a fix once things settle down on the upstream side and
I'd like to file an unblock request (or a stable update request if
this misses the bookworm release).
I'm not a member of the multimedia team, but I am familiar with the csound packaging.
Are you okay with me doing an NMU and submitting a merge request on salsa once we settle on a fix on the upstream github issue?
You can declare an opcode something like
opcode inittest,K,0
According o the docs, the output parameter is copied both at k-time
and at i-time. It turns out in csound 6.14 (bullseye) it's always
copied at i-time even if declared as 'k' not 'K'. But that in 6.18
it's only copied as k-time. If you are using the opcode as a state
machine, triggering reinits, etc, that can totally break your
orchestra.
Reply to: