Piplodocus
Well-Known Member
My amp (Diezel Hagen) is MIDI controlled and has 4 channels + solo volume boost. I wanted to avoid using loads of patches cuz I use this amp with other things and don't want to overwrite for those saved programs. So I've saved programs 101-104 in the amp as these 4 modes and 105-108 as the same + solo boost. So if I have 50 presets in my rig, I can just use reuse those same 8. Traditionally with my old MM LT I then I use the PBC PC messages section to choose which of those I want in each patch. Simple.
I've now considered for the sake of programming patches easily, it might make more sense to turn all the patches PBC PC sends to the amp off in all presets, and program 8 buttons on an "Amp page" for each of those 8 variations (and stuff them all in an exclusive "Amp channel" group with "all off" disallowed). I've actually done it with 4 buttons for the 4 amp channels with the solo of each on the 4 hold functions.
The upside is I can then program a preset's amp channel and if solo boost is on just by setting the channel in the PBC's "amp page" and saving my IAs for that preset. I can easily set it with button state in the preset tab of the editor, or on the pedal itself and quickly save the change (and I can easily see what it's on from the amp page on the PBC). Seems a no-brainer compared to having to use the PC change selector for the amp in the PBC menu or on the editor.
But any downsides of making my amp PC changes with IA buttons that send state on preset change? I can't think of any, but are there any pitfalls I've not thought of because it sends some stuff before those if they're IAs or something?
I guess you don't want to do this with something like Timeline presets, because it might set some IA buttons before others (like send CCs, then send new PCs with IA PCs after), but can't think of one from the amp. I guess that begs the question what order does it send IA buttons in (e.g. Song presets (if a new song) -> Set any local page -> All preset PCs (in order of device?) -> Expr override assignments -> IA buttons (in order of page or order of device or something else))? So would IA buttons be last so any IA button saved states will override patch changes/expression assignments/pages if they also control them? And buttons states saved in higher pages could overrule button states set in lower pages (although largely you'd use IA link to avoid that)? Or does it work out all things it needs to do first, then sends them all out in device and CC number order?
So yeah, in short, any pitfalls you can think of, and are there general rules what order everything is sent in on preset changes?
(Was thinking of doing this with my Empress Tremolo 2 and Meris Enzo as well since they don't have many presets, and have Trem patch and Enzo patch pages too with PC IA buttons in their own exclusive groups. So on preset change I'd have amp, trem and synth PCs sent with IA button saved states, and CB Brothers, Timeline and BigSky set with the preset PCs)
I've now considered for the sake of programming patches easily, it might make more sense to turn all the patches PBC PC sends to the amp off in all presets, and program 8 buttons on an "Amp page" for each of those 8 variations (and stuff them all in an exclusive "Amp channel" group with "all off" disallowed). I've actually done it with 4 buttons for the 4 amp channels with the solo of each on the 4 hold functions.
The upside is I can then program a preset's amp channel and if solo boost is on just by setting the channel in the PBC's "amp page" and saving my IAs for that preset. I can easily set it with button state in the preset tab of the editor, or on the pedal itself and quickly save the change (and I can easily see what it's on from the amp page on the PBC). Seems a no-brainer compared to having to use the PC change selector for the amp in the PBC menu or on the editor.
But any downsides of making my amp PC changes with IA buttons that send state on preset change? I can't think of any, but are there any pitfalls I've not thought of because it sends some stuff before those if they're IAs or something?
I guess you don't want to do this with something like Timeline presets, because it might set some IA buttons before others (like send CCs, then send new PCs with IA PCs after), but can't think of one from the amp. I guess that begs the question what order does it send IA buttons in (e.g. Song presets (if a new song) -> Set any local page -> All preset PCs (in order of device?) -> Expr override assignments -> IA buttons (in order of page or order of device or something else))? So would IA buttons be last so any IA button saved states will override patch changes/expression assignments/pages if they also control them? And buttons states saved in higher pages could overrule button states set in lower pages (although largely you'd use IA link to avoid that)? Or does it work out all things it needs to do first, then sends them all out in device and CC number order?
So yeah, in short, any pitfalls you can think of, and are there general rules what order everything is sent in on preset changes?
(Was thinking of doing this with my Empress Tremolo 2 and Meris Enzo as well since they don't have many presets, and have Trem patch and Enzo patch pages too with PC IA buttons in their own exclusive groups. So on preset change I'd have amp, trem and synth PCs sent with IA button saved states, and CB Brothers, Timeline and BigSky set with the preset PCs)