-
Notifications
You must be signed in to change notification settings - Fork 4
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
Spectrograph gets very slow after a while #51
Comments
In the video, were you using the LV2 / VST2 build of the program? Wolf Spectrum is probably slowing down the UI update loop because the rendering code is not very optimized. At least, it seems like Wolf Spectrum is slowing down Surge's UI. Also, the spectrogram appears to be scrolling slower when you are tweaking Surge's parameters. |
Yes, I've used the LV2 plug-in via Carla. |
@unfa I can reproduce the slowness (at least, to a certain extent):
This causes Wolf Spectrum to scroll very slowly. The performance improves as soon as I stop playing with the slider. I suppose Surge is slowing down the UI update loop. Also, just hovering the sliders with the mouse appear to slow down Wolf Spectrum a little bit. As a workaround for this kind of issues, you can use the standalone JACK version of Wolf Spectrum instead of the plugin version. That way, the spectrogram should scroll more smoothly. But then, perhaps your CPU simply had trouble keeping up during the filming? If so, I would try to optimize Wolf Spectrum for lower CPU usage, to see if it helps... |
CC @baconpaul, any thoughts? Do you think this might have something to do with surge-synthesizer/surge#4347? |
Maybe |
@baconpaul I was running the official 1.9 binary during my tests. Anyway, I'll take another look at this issue before the next release of Wolf Spectrum. |
right well that one has the leak fixed. i'm really not sure what causes that ardour x usage in surge. We do know that the alpha of our next version (where we replatform to juce) doesn't show the same problem. |
Look at how slow Wolf Spectrum gets after 20 minute of non-stop use:
https://youtu.be/C92wFP0CG7c?t=1739
Could this be some problem with non-freed image memory or something?
The text was updated successfully, but these errors were encountered: