beadsynt segmentation violation

[csound-plugins]

beadsynt segmentation violation

[gesellkammer]

With the github actions tests I can confirm that this is now fixed

[gesellkammer]

Thanks for the report. I can confirm the same crash on linux. I will investigate it as soon as I can

[gesellkammer]

Could you try the latest build?

https://github.com/csound-plugins/csound-plugins/releases/tag/latest

Just place the beosc.dll into your plugins64 folder

[enchilada404]

Ok, with the new build there is some sound output... but it sounds like it has been "frequency-time-stretched", and then it ends in csound command: Segmentation violation again.

[enchilada404]

I just tried v1.15.0 and the Development Build, but there's no change in behavior here. Sound is warped and then back to csound command: Segmentation violation.

Also, when I check versions with risset, it still lists versions 1.14.1 of all plugins.

[enchilada404]

Here's just to let you know that v1.17.0 from Apr 20 is still giving the same result.
I think that the loristrck/beadsynt combination is pretty unique, and it would be nice to have it working again.
Let me know if I can help in any way.

[gesellkammer]

Could you try the latest Develoment build?

[enchilada404]

Sorry to say, both the latest development build and 1.18.0 also fails with the same segmentation violation here on win 10. Sound has some phase issues and plays back at wrong speed and pitch.

[gesellkammer]

I can confirm that it is building and running correctly in windows latest (this corresponds to windows server 2022) with last released csound 6.18. This renders cleanly without any errors.

…

On 29.05.23 15:24, enchilada404 ***@***.***> wrote: Sorry to say, both the *latest development build* and *1.18.0* also fails with the same segmentation violation here on win 10. Sound has some phase issues and plays back at wrong speed and pitch. — Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAT3NFASQJF4M2BJJVJGPLXISPQVANCNFSM6AAAAAAWCZCQ7M>. You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[gesellkammer]

I can confirm that it is building and running correctly in windows latest (this corresponds to windows server 2022) with last released csound 6.18. This renders cleanly without any errors.

[enchilada404]

For me it will render to file (non-realtime) without reporting any errors.
However, it sounds like this (the default "fox" example):

testt.mp4

...and realtime gives me segmentation violation on both win 10 & 11, with sound being identical with above non-realtime output.

[gesellkammer]

This is how the example is supposed to sound, see the csd regarding speed and filtering. Regarding segmentation fault with realtime, that I cannot confirm.

[enchilada404]

oops my mistake. I thought I was using my version that just plays the sound unmodified, sorry.
Still getting segmentation fault though when playing beadsynt.csd example 🤔
Otherwise it seems to work fine.

[gesellkammer]

If it renders to file but not to dac then your segmentation fault has probably little to do with the opcode itself. From the point of view of the opcode there is no difference.

[enchilada404]

It renders to dac, and now it sounds correct.
Segmentation violation comes after Csound is finished.