Allow the footswitch assignment to be included in user defaults. That way, any time you select a user default version of a device/block/model, it could already be assigned to your preferred footswitch (or no footswitch at all).
If I get you right, this would first mean to implement a user default section for blocks, right?
1 Like
Yes! As far as I know âdefaultsâ currently only exist for expression pedal assignments. I am thinking maybe that a feature request for user defaults already exists. If so, I would just incorporate footswitch assignments into it (if it isnât already there). May have missed this in a pre-existing feature request.
Update: Was just checking out the âSet parameters as defaultâ setting in various blocks such as âBrit Bluesâ overdrive. If you use it on a blockâs parameter, it sets a new default for that parameter that persists across snapshots and presets, or even if you restart the QC without saving the preset. Weird, unless I missed it, I donât think this is documented in the CorOs 2.0 manual, which only describes defaults when a parameter is assigned to an expression pedal. The quoted text below was the only reference I could find from the manual regarding âSet parameters as defaultâ. It would appear that the full capabilities of this setting are not documented. This feature is more powerful than I thought. Unless I missed something.
From the Quad Cortex User Manual 2.0:
âThe EXP inputs assigned to a device block can be remembered by
using the âSet parameters as defaultsâ option after assigning an
expression pedal to a parameter.
The parameter position and the toe-switch polarity are not
remembered while saving Presets. The current parameter position
and toe-switch state are maintained while loading presets.
When a parameter is assigned to an expression pedal, the Scene
data is also ignored for that parameterâ
1 Like
Just to muddy the waters further, try this.
- Set the âToneâ = â2.0â on the âBrit Bluesâ model, and click âSet parameters as defaultâ.
- Now set 'Tone = 9.0.
- Now click âReset to defaultsâ.
You would expect the âToneâ parameter to return to the factory defaults for the âBrit Bluesâ model. But it doesnât. It returns to 'Tone = â2.0â - the user default you set in the first step. I havenât located a way to reset to the factory default parameters for a block. This is not at all the way I expected the QCâs current user default implementation to work, nor do I think it is documented.
Bizarre not to have a way to reset models to their factory parameter defaults. What am I missing here? Is there a way to restore the factory defaults? If there isnât one, I intend to exercise caution setting custom user defaults as I donât see a way to restore them to factory unless you have them written down or saved at the default settings in another preset.
Donât know whether this is a feature or a bug. If it is a âfeatureâ I believe Neural very much needs to add a âReset to Factory defaultsâ option, in addition to the current âReset to defaultsâ.
I think this is exactly how it is expected to work. But like you said, there is no option for a factory default restore. This should be added.
Btw , a much better way of doing this would be to allow the user to save multiple âUser presetâ of each virtual device, instead of having only the âSet Parameters as Defaultâ. The ârealâ default would be the factory one, but once you add a block onto the grid, there should be a way to choose one of our âuser defaultsâ âŚ
4 Likes
Absolutely! My preference would be to allow multiple user âfavoritesâ for custom variations of blocks as well as allowing a user default for blocks you always set the same way. No matter what they end up developing though it seems like being able to get back to a factory default is ground zero and should always be an option.
Funny, I started this feature request just to add footswitch defaults on a per block basis but it turns out that the defaults implementation is so strange right now that the whole kit and kaboodle needs to be assessed.
1 Like
+1 to both of your comments. Need to re-assess my votes! 
1 Like
Iâm voting for this because Iâm getting tired of unassigning blocks (especially always-on stuff like EQ and IR) as I add them to the grid.
I donât need the QC deciding for me what footswitch they should be assigned toâI want the default to be no assignment at all.
3 Likes
Yup, currently it just generates totally unnecessary editing every time a preset is created. Defaulting to no assignment is probably the way to go. At the very least it should be an option. As it stands now the default assignments just generate reassign/unassign busywork.
It looks like the whole framework for how both parameter and footswitch defaults are being handled on the QC needs to be overhauled.
1 Like
The best system would be :
- By default a block shouldnât have any footswitch assigned.
- Any block should have the ability to have multiple user-defined âconfigurationsâ (in addition to the âFactory configurationâ that would be read-only, in case we want to restore the initial default)
- The User-Defined configurations should store the whole block settings, including the Footswitch assignement.
This way, when we put a block onto the grid, it would not have any footswitch assigned, but we could easily select one user-defined configuration.
It would be really nice, and doesnât seems to hard to implement ! (of course, new blocks, or new variations of existing blocks - like the recently enhanced SLO Amp - would not have the same âuser configurationsâ as their âlegacyâ counterpart, they should be considered as totally new block.)
Perhaps we should create a new Feature Request (or merge an existing one ?) for this âuser configurations for blocksâ proposal ? (I purposely avoided the word âpresetâ and used âconfigurationâ instead, in order to not add any confusion !)
Clarification: the user-configuration should store a âsnapshotâ of the current block configuration, but not the fact that a parameter is Scene-bound (âabcdâ state) as this information is Preset-specific.
1 Like