3rd-Party DSP Plugins: Incorrect Initial Values
Posted: 04 Jun 2013 19:45
Good evening Bernd,
I know I’m a few hours early, because your official return to duty is only tomorrow. But now that I’m at it for preparing tonight’s show, and I noticed this behaviour again—I always do when firing up my other machine and starting PFOA—I thought I should put this here before I forget about it again.
I already noticed a handful of versions ago—can’t say at what point exactly—that at least some, but definitely not all, third-party DSP plug-ins need to be clicked on once after starting PFOA showing the little window with the value dials in order to work with the correct values they have been set to. Because when showing this value dial window for the first time after program startup, it first shows the default values for a split second, then jumps to showing the values the plug-in has been set to. And I was of the impression one day I purposely took a good listen to it that it’s not purely a display issue, but that those plug-ins really run at default values at first, and only change after having been clicked once.
Some plug-ins I already observed this behaviour with are: the GVST plugins, especially GGate (a noise gate), and GSatMax (gain, saturation, and limiter) from the beta section; and Jeroen Breebart’s Broadcast plug-in from his VST plug-in bundle. I have no way to tell whether it’s the plug-ins’ or PFOA’s fault. Two plug-ins that do not exhibit this behaviour are the GranComp3 and GranComp3 Mono plug-ins from the BuzComp Free series.
I’d be happy if you could have a look into this matter and hopefully find out where the dog lies buried.
Thank you very much in advance and kind regards
Sven
I know I’m a few hours early, because your official return to duty is only tomorrow. But now that I’m at it for preparing tonight’s show, and I noticed this behaviour again—I always do when firing up my other machine and starting PFOA—I thought I should put this here before I forget about it again.
I already noticed a handful of versions ago—can’t say at what point exactly—that at least some, but definitely not all, third-party DSP plug-ins need to be clicked on once after starting PFOA showing the little window with the value dials in order to work with the correct values they have been set to. Because when showing this value dial window for the first time after program startup, it first shows the default values for a split second, then jumps to showing the values the plug-in has been set to. And I was of the impression one day I purposely took a good listen to it that it’s not purely a display issue, but that those plug-ins really run at default values at first, and only change after having been clicked once.
Some plug-ins I already observed this behaviour with are: the GVST plugins, especially GGate (a noise gate), and GSatMax (gain, saturation, and limiter) from the beta section; and Jeroen Breebart’s Broadcast plug-in from his VST plug-in bundle. I have no way to tell whether it’s the plug-ins’ or PFOA’s fault. Two plug-ins that do not exhibit this behaviour are the GranComp3 and GranComp3 Mono plug-ins from the BuzComp Free series.
I’d be happy if you could have a look into this matter and hopefully find out where the dog lies buried.
Thank you very much in advance and kind regards
Sven