-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Eq rack2 #364
Eq rack2 #364
Conversation
… are changed, do ramping in the next process() call
… for a specific Channel
m_deckEffectSelectorsSetup = true; // prevents a recursive call | ||
QList<QPair<QString, QString> > availableEQEffectNames; | ||
if (CheckBoxHideEffects->isChecked()) { | ||
m_pConfig->set(ConfigKey(CONFIG_KEY, "AdvancedView"), QString("no")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No config changes should be made until Apply is pressed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original behavior of this preference pane is that we instantly change everything.
I might remember that this was result from a discussion we head. should we change that?
Hm, if you're referring to the filter knobs I don't think that is served by this PR -- is it? The filter knob use case is more for a "quick effect" concept we've talked about which has a single superknob and an effect selector. That way the users filter sweep knob could change into a bitcrusher if they want to change it on the fly. |
I realize -- and sorry for turning this PR into a complaint-fest :). The change this PR makes is nice since it enables users to change their EQs in a more general fashion (and in the future maybe use an EQ plugin of their own). I think we're more discussing the usability implications of per-deck EQ choices and the proposal you put forward of having the number of knobs change dynamically and support for swapping out the EQ with a different type of effect. I see how a super advanced user might benefit -- and there's no reason to not let them in their own skin -- but our default skins need to be easy to use and easy to explain to users. |
All comments issued. |
Conflicts: src/effects/effectsmanager.h
Ok -- looks good. Cleanups can wait till master :). |
This is an updated version on Nicus EQ Rack Branch.
It enables the full power of the effect back-end for the EQ Knobs as well.
You can select which EQ should work on which deck and you can load any other effect to the EQ Slots.
Next steps to merge: