In previous fb2k versions (0.8.3 and before) the DSP settings could be changed and were effective in realtime, for example in the equalizer you could move the sliders and in a short time (depending on your buffer settings) the change was effective.
Now with 0.9.1 when configuring DSP settings unless I press OK and close the conf.window the settings are not effective. Adjusting equalizer this way is very uncomfortable.
Full Version: DSP settings don't work realtime anymore
I've encoutered the same dilemma when porting my Dolby Headphone Wrapper plugin to 0.9.
The truth is that one can code the plugin to react realtime, nothing in fb2k prevents it. However the new official 0.9 DSP tutorial proposes another point of view, with a dialog box where changes can be either accepted or cancelled. Then, changes should apply only when you press OK button.
Once coders get used to the new way of working of 0.9 surely they will upgrade the code to be realtime responsive.
Anyway this is more a Development question rather than a Support one.
The truth is that one can code the plugin to react realtime, nothing in fb2k prevents it. However the new official 0.9 DSP tutorial proposes another point of view, with a dialog box where changes can be either accepted or cancelled. Then, changes should apply only when you press OK button.
Once coders get used to the new way of working of 0.9 surely they will upgrade the code to be realtime responsive.
Anyway this is more a Development question rather than a Support one.
QUOTE(Chungalin @ Apr 27 2006, 06:45 PM) 
Anyway this is more a Development question rather than a Support one.
Hmmm... Development question:
If you have two instances of your DSP - one for playback, another for converting. For which one apply the changes in realtime? How to distinguish which instance is for playback and which instance is for another things?
You cannot identify where a given instance of your DSP is used. You can modify the playback DSP settings that the core uses (see dsp_config_manager), but this should not be done in the configuration launched by dsp_entry::show_config_popup().
The best choice would probably be to add a subclass dsp_entry_v2 of dsp_entry with a new method
I'll point Peter to this topic to see what he thinks about this.
The best choice would probably be to add a subclass dsp_entry_v2 of dsp_entry with a new method
CODE
virtual bool show_config_popup_live(dsp_preset & p_data, HWND p_parent, service_ptr_t<dsp> p_dsp) = 0;
I'll point Peter to this topic to see what he thinks about this.
QUOTE(foosion @ Apr 27 2006, 07:21 PM)
The best choice would probably be to add a subclass dsp_entry_v2 of dsp_entry with a new method
I'll point Peter to this topic to see what he thinks about this.
CODE
virtual bool show_config_popup_live(dsp_preset & p_data, HWND p_parent, service_ptr_t<dsp> p_dsp) = 0;
I'll point Peter to this topic to see what he thinks about this.
That would be great!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.