You can use any layout you want, then customize only the switches you want to be different per preset.I like to setup my FC12 so “most“ things are in the same place. If I could design a layout and set it to per preset I would only have to make a couple changes instead of using the Per Preset layout on every preset and building it from scratch.
Use Overrides instead of Placeholders.I like to setup my FC12 so “most“ things are in the same place. If I could design a layout and set it to per preset I would only have to make a couple changes instead of using the Per Preset layout on every preset and building it from scratch.
One of the factory layouts...What's a per-preset layout?
It has only placeholders.One of the factory layouts...
That’s a layout though. The way it’s written it sounds like a feature. ¯\(ツ)/¯One of the factory layouts...
I know...It has only placeholders.
Well, the OP references "per preset" twice.That’s a layout though. The way it’s written it sounds like a feature. ¯\(ツ)/¯
I know you know that, I was trying to help the OP understand why it might not be best for his intended purpose, as I understood it.I know...
Wouldn't it be more intuitive and faster to just make the layouts either Per Preset or Global? Using overrides is just another way to accomplish what I am already doing with the Per Preset layout on EVERY preset...Use Overrides instead of Placeholders.
So like if you click a new preset, your unit automatically loads a specific layout for that preset?Wouldn't it be more intuitive and faster to just make the layouts either Per Preset or Global? Using overrides is just another way to accomplish what I am already doing with the Per Preset layout on EVERY preset...
Per preset layouts would take a lot of memory no?Wouldn't it be more intuitive and faster to just make the layouts either Per Preset or Global? Using overrides is just another way to accomplish what I am already doing with the Per Preset layout on EVERY preset...
Maybe - depends on your personal use case... but there are only 9 layouts... I don't think we're getting more.Wouldn't it be more intuitive and faster to just make the layouts either Per Preset or Global? Using overrides is just another way to accomplish what I am already doing with the Per Preset layout on EVERY preset...
YesSo like if you click a new preset, your unit automatically loads a specific layout for that preset?
Hmm, I haven’t delved into the overrides feature much. Just used it once to create a momentary switch for a flanger block. Other than the manual is there a good explanation to how these work? Maybe a video?Maybe - depends on your personal use case... but there are only 9 layouts... I don't think we're getting more.
Per-preset overrides aren't exactly the same as the per preset layout as they can be assigned to any switch on any layout.
Right now I’m using a per preset layout for each preset. I don’t think it adds any cpu usage to the preset.Per preset layouts would take a lot of memory no?
I'm sure there's probably a video or two out there, but I'm a "manual guy" so that was all I needed..Hmm, I haven’t delved into the overrides feature much. Just used it once to create a momentary switch for a flanger block. Other than the manual is there a good explanation to how these work? Maybe a video?
Layouts are global. Those layouts take storage on the unit. You are asking for layouts to be per-preset, so now you need 512 times as much storage.Right now I’m using a per preset layout for each preset. I don’t think it adds any cpu usage to the preset.
Right now I’m using a per preset layout for each preset. I don’t think it adds any cpu usage to the preset.