Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not depend on control inputs in XX_activate #3

Open
NerdyProjects opened this issue Mar 24, 2014 · 2 comments
Open

Do not depend on control inputs in XX_activate #3

NerdyProjects opened this issue Mar 24, 2014 · 2 comments

Comments

@NerdyProjects
Copy link

LADSPA API does encourage but not enforce connecting control inputs before the activate call. This leads to undefined behaviour or even segmentation faults (use of uninitialised memory) when using most of these plugins in an ALSA chain.

Fix is possible by a small fix in alsa (call activate as late as possible) but the real issue lies here...

@swh
Copy link
Owner

swh commented Mar 25, 2014

Right, this is an issue as sometimes plugins have a choice between having non-optimal behaviour, or breaking the timing restrictions.

As LADSPA is pretty much obsolete I'm not really inclined to fix, but would accept patches that fixed the issue.

@NerdyProjects
Copy link
Author

Thanks for your answer. I am in the process of getting the mentioned alsa fix upstream, that's enough for me. So sorry, no patches from my side :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants