Preface: I’m very happy with the new 4.1.0 update and I don’t mean to be one of those guys
With the introduction of Device Presets, it would be really cool if some of those Device Presets could be referenced within our Normal Presets.
for example: if presets 1A , 2B , 3A all used a specific Amp device preset. When that Device preset was updated and saved, all the presets using that specific device preset would update to those settings. (Very similar to Palletes, or presets on a lighting console)
it could be achieved by a Global Device Preset toggle next to the Device Preset in the selection list and whenever updated it would change that device preset in all presets it is used in.
This feature would be super powerful for editing entire set lists of presets. For example if you wanted more gain on all Lead patches in a setlist, you just push up the gain on a Global Device Preset and the gain is pushed up on all presets and scenes using that global device preset.
Or you want to change your cab IR on 14 presets, just update the global device preset used in those presets and it’s changed on all 14 presets.
Strong support for this, and I’d like to push the idea one level up.
Global Device Presets solve the single block case. What I keep hitting is the whole preset case. My setlist has families of near identical presets: a master with clean, crunch, lead and two solo scenes, then daughters that are the same rig with one or two blocks different, for example a solo doubled with a pitch shift instead of a fuzz, or a Poly Capo for Eb tuning. When I swap the amp or rebalance the scene levels in the master, I have to repeat it by hand in every daughter, even though the difference between them is only ever two or three blocks.
What I’d like:
Mark a preset as a parent and create daughters from it. A daughter inherits everything by default: chain, device settings, scene bypass states and scene levels. Any block or parameter edited in a daughter becomes a local override and stops inheriting, with a marker on the grid so you can see at a glance what is local and what is inherited. An option to release an override back to inherited, and an option to flatten a daughter into a fully independent preset. On upload to Cortex Cloud or export, daughters resolve to static, self contained presets, so nothing shared depends on a parent the recipient does not have.
Scene levels matter as much as device settings here. Rebalancing a setlist is the job that eats the most time, and it is the one thing block-level linking will not fix.
Two things to make it safe live: a clear indicator that a preset is a daughter, and a confirmation listing which presets will change before a parent edit is committed.
