intense method call in setParameter
-
- KVRer
- 16 posts since 28 Aug, 2011
Hi KVR,
I am trying to make a call to a third-party library in order to change a parameter value using setParameter. The library's "change parameter" method however is quite intensive which I cannot change. I am getting sporadic crashes when changing the vst parameters using the default sliders in Ableton, however, when automating the parameter from a Live clip is is working perfectly and results in full use of the default slider.
I understand setParameter can be called by the audio thread, so is it that the library method maybe take too long to complete? In which case, would setting up some locks help? Considering automation of this parameter is fully working, can I assume that Ableton is not calling setParameter itself but perhaps setParameterNotifyingHost? If this is the case, am I able to make the calls to setParamNotif.... myself for use with the default parameter sliders?
Many thanks!
I am trying to make a call to a third-party library in order to change a parameter value using setParameter. The library's "change parameter" method however is quite intensive which I cannot change. I am getting sporadic crashes when changing the vst parameters using the default sliders in Ableton, however, when automating the parameter from a Live clip is is working perfectly and results in full use of the default slider.
I understand setParameter can be called by the audio thread, so is it that the library method maybe take too long to complete? In which case, would setting up some locks help? Considering automation of this parameter is fully working, can I assume that Ableton is not calling setParameter itself but perhaps setParameterNotifyingHost? If this is the case, am I able to make the calls to setParamNotif.... myself for use with the default parameter sliders?
Many thanks!
-
- KVRer
- Topic Starter
- 16 posts since 28 Aug, 2011
I have just noticed, as long as the Live is playing, the sliders work perfectly with no delays or crashes. The crashes only occur when the sequencer is not running which is rather bizarre. Perhaps I could just put in some control to stop parameter changes when it has stopped?
- KVRian
- 775 posts since 30 Nov, 2008
