Bug#916047: csound: regression in String handling

package: csound version: 1:6.12.2~dfsg-1 severity: important justification: Regression over stretch with insidious and hard-to-diagnose consequences I noticed that my orchestras were failing on several sound files after upgrading to buster, and tracked it down to some cases of filenames being

Bug#916066: csound regression: zir opcode appears entirely broken; hangs instrument

package: csound version: 1:6.12.2~dfsg-1 I was experiencing strange failures with orchestras with csound 6.12 and eventually I've tracked it down to the zir opcode to read a value from zk-space at i-time. It's fairly basic: the zir.csd from the csound examples fails to print out anything in the

Bug#924260: NMUDIFF for csound 1:6.12.2~dfsg-3.1

index 84a4831..72a6859 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +csound (1:6.12.2~dfsg-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix diskgrain, syncgrain and syncloop when sample rate of sample +differs from orchestra, Closes: #924260 + + -- Sam

Bug#924260: Csound: regression in diskgrain stretch->buster when file sr != orchestra sr

package: csound severity: important justification: Stretch regression with no work around without code changes version: 1:6.12.2~dfsg-3 tags: patch, fixed-upstream, upstream Hi. In https://github.com/csound/csound/issues/1119 I reported an issue. In stretch, if you want to deal with a file that

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).