Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Editing multiple presets at one time (rig mode?)


Sjaltenb
 Share

Recommended Posts

Hello,

 

I am wondering if this is possible:

 

Let’s say I have 20 different songs that each require snapshots within for different song parts.
 

I’ve been building a template preset with every conceivable pedal needed and then copying that 20 times, and then editing as needed for the different songs and their parts within (snapshots).

 

For years, my issue has been that I’d I decide to change an amp setting, or swap out an IR, I have to do that on all 20 presets. 
 

It seems like there needs to be a “rig” mode that allows universal editing of the rig (amp settings, pedals, etc.) that would allow for this. 
 

I know that I can copy/paste and I know there are global/favorites but that’s not really what I’m looking for. 
 

At minimum I would think the amp settings could be tied to a universal - or you could have pedal settings that tie back to a universal controller (meaning within the preset and pedal you say - tie to pedal setting A and then you can edit “A” and it changes for all presets.

 

thoughts / suggestions?

Link to comment
Share on other sites

In a way that's somewhat the idea behind being able to save favorites if you could simply modify your favorite and it would automatically endure across all instances of that favorite wherever it might be used, but that's not how it works.  You could submit this to IdeaScale and, if described properly, might be popularly supported.  Under the current architecture of the Helix I'm not sure how practical it would be.

 

What you're really describing is the concept of inheritance in which a change to a favorite would endure across multiple instances of use of that "favorite" in all presets.  But in the current architecture all presets are standalone and static.  Also there's the case in which a preset is not stored in the Helix itself, but stored in a backup or on the hard drive as a copy of the preset.  This would undoubtedly add significantly to the load time of a preset which I'm not sure I'd be willing to endure.  That's just one possible implication but there are many more I can think of.  On the surface it's a great idea.  I'm just not sure whether it's worth it to make it work seamlessly in the current way presets are handled.

 

Maybe the next version of the Helix could incorporate a more comprehensive flexibility within presets to allow such things rather than trying to retro-fit the concept to the current architecture.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...