guiro was missing the adjustment for 0dbfs; fixed in git. Not seen what is wrong with cabasa or crunch though. Quoting jpff@cs.bath.ac.uk: > Sounds like a bug; will look > ==John ff > > Quoting Kevin Welsh : > >> It appears as if the PhISEM opcodes (guiro, cabasa, crunch, etc) never >> got some parameters scaled properly when things were converted to work >> with 0db scaling. >> >> The doc page suggest a value 0-1, however even relatively small values >> create a runaway condition. But if you use a range of 0-(1/32767) the >> opcodes appear to work as intended. >> >> Can anyone confirm if this is a permanent intended change, or is this >> a bug in the behavior that will eventually be fixed? >> >> >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> To unsubscribe, send email sympa@lists.bath.ac.uk with body >> "unsubscribe csound" > > > > > > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body > "unsubscribe csound"