| > John, I did some extensive testing with the PhISEM opcodes last night.
> My csound version was built from the dev branch on Aug 16th, and
> appears to have the fixes for a few other bugs I had tested/reported
> (ftgenonce, pset, flooper2). I'm not sure if your changes to phisem
> opcodes were included in this build or not, but I still figured my
> findings could be useful.
> I still see a lot of unexpected behavior with the phisem opcodes.
> Some of these might be intended behavior, but I don't think so. If
> anything I reported here is working as intended, please let me know so
> I can change my instruments and tests. I tried to to test all
> parameters on all phisem opcodes that I could find listed in the
> manual and document it as best as I could.
sorry not to respond earlier but I was engaged elsewhere. Just
getting back to your report -- which is daunting....
Would you be so kind as to send me your test csd files? It would give
be a head start in attacking them, and would be a great hep to me.
Kindly send offlist to this address, or at least a selection so I can
get back to this code, as it is 14 years since I looked closely.
> Opcodes tested: bamboo, cabasa, crunch, dripwater, guiro, sandpaper,
> sekere, sleighbells, stix, tambourine. Let me know if I missed any.
that is complete
What does "values off by scale of 32768:" mean?
I will start with the example you sent (guiro)
==John ffitch
|