Helix Native, how to save Setlists/Presets with each DAW Project and Tracks

[Crunch71]

 

If I, for example, create a preset and I name it Preset1, and then create all the blocks I want with their settings in Preset1. I see that that in my DAW, if I use that same Preset1 for multiple tracks, the settings for each block are saved with each track, which is great. If I change the name of Preset1 to Preset2 in one track, all the tracks using Preset1 are then using the same slot now named Preset2. Not a big deal.

 

If, however, I load an entirely different and new Preset from disk in the same slot as Preset1 I see that it overwrites Preset1 for all DAW projects/tracks using Preset1 with the new Preset!

 

Is the standard procedure then to always make sure I save that Setlist with its Presets and load it into Native for that particular DAW Project to use that Setlist with its Presets? I should not change the name of that Preset slot or load a new Preset into that slot in other Projects/Tracks? I have to somehow remember what Setlist is used on each Project/Track?

 

I would have thought that Setlists/Presets are totally saved in each DAW project, and it would not matter what I do to a Setlist/Presets in other Projects/Tracks? I am using Cubase 13.

 

 

Hope I am explaining this well enough. Sorry if it's been asked before.
 

 

 

Thanks!!!

 

[DunedinDragon]

I think what makes this feel odd to you is that the idea of a preset is confined to Helix Native, not to the DAW or the project, and that's consistent behavior across ALL Helix products.  In fact it's pretty much consistent with the vast majority of plugins.  This simply mirrors the behavior across all Helix products and allows Helix Native to behave consistently with all other Helix units and be a part of the Helix eco system.

 

But the fact is this behavior is consistent with most plugins used in the DAW world, it's just handled differently.  Most plugins provide for users to create their own presets outside of the manufacturers presets and they're referenced by the name the user gives it.  If you change the behaviors but not the name, those behaviors will change for all projects that use that named preset.  This is because plugins have no inherent knowledge regarding what DAW projects they're used in.  If you create a new preset under a new name that will only be used in each DAW project that uses that new renamed preset.

[Crunch71]

On 4/3/2024 at 4:54 AM, DunedinDragon said:

...This is because plugins have no inherent knowledge regarding what DAW projects they're used in.  If you create a new preset under a new name that will only be used in each DAW project that uses that new renamed preset.

 

I think the thing that is different with Native compared to other plug-ins is that Native allows you to export and import entire Setlists of Presets thus allowing you to remove all the presets that are currently being used by a DAW project. That is perhaps not standard among plugins and something that allows Native to be used live and be similar to other HX products. 

It seems the answer is, as you say, "create a new preset under a new name that will only be used in each DAW project that uses that new renamed preset." 
Also, to leave the current Setlists loaded and not import new ones unless you really need to. There are hundreds of Preset slots avaiailbe within the multiple setlists that can be loaded at one time with Native. I don't see myself having to load entirely new multiple setlists at any time soon.

Thanks a lot for the taking the time to reply and help out man!

[DunedinDragon]

On 4/3/2024 at 11:32 AM, Crunch71 said:

 

It seems the answer is, as you say, "create a new preset under a new name that will only be used in each DAW project that uses that new renamed preset." 
Also, to leave the current Setlists loaded and not import new ones unless you really need to. There are hundreds of Preset slots avaiailbe within the multiple setlists that can be loaded at one time with Native. I don't see myself having to load entirely new multiple setlists at any time soon.

And that's why the Native scheme works so well.  I and many others use a preset per song in order to customize the sound to the specific song.  Even in doing so I only ever need to have a single setlist loaded because it more than accommodates that type of workflow.  That is unique in the world of plugins generally and quite useful in a practical sense for me.

[craiganderton]

Also remember that the DAW saves a "snapshot" of your settings, regardless of the setlist. For example, I have only three main setlists when using Native. One is my multiband guitar stuff, one is everything except guitars (vocals, drums, bass, keys, strings, etc.), and one is the presets included with my book. So, I call up an appropriate preset, tweak the settings, but don't bother to save the preset because the DAW will save the tweaks as part of the song when I save it. 

 

When I re-open the song, the DAW will show the name of the preset I loaded originally, but it will retain all the tweaks I made while working on the song.