Preset to Impulse Response correlation broken in Helix Native 1.93

[richardwhite2009]

I welcomed with anticipation the new method of Helix linking its IRs to Presets with what appears to be the IR name (vs the index number in the list of IRs).

 

My understanding of how this is supposed to work, is that once you have specified which IR a preset is based on, the preset is supposed to be smart enough to "find" that preset based on name -- in the list of IRs.  I think this is supposed to provide the user the flexibility to rearrange the IRs without worrying about having to re-link the presets to new IR index numbers.  I did some testing, and for the most part it, this feature SEEMED to work on my laptop. If you moved an IR, re-clicking on the preset would re-link to the IR in its new location.. I also found that if you deleted an IR, re-clicking the preset would produce an error message.   I found however that on a number of occasions that if an IR was deleted, an error message was NOT presented when you re-selected the preset.  What happened in this case was that the preset definition had been updated automatically to point to IR number 127 which was empty. In both cases, the name of the preset was lost. (It would have been more useful if this name had been displayed in the error message saying it could not find this IR).

 

In addition, after spending THREE HOURS fixing my presets so they pointed to the proper IRs (they had gotten mixed up in the upgrade)... I created a bundle of my patches as well as some setlists, and then happily went to my second computer, fully expecting that I could just copy in my IRs to Helix Native, and then import my bundle or the setlists -- and then the preset references to the IRs would all sort themselves out...

 

Nope.  This did not work.

 

Only about a half of the references to IRs were resolved, even though all my IRs were all copied into Helix Native first.

 

Could anyone please confirm:

- has anyone else experienced this bug?

- am I doing something wrong: do the IR references not get copied into the bundles and setlists?  Do I need to manually export and import each single preset in order to preserve the IR reference?   (I certainly hope not!  That would be way to much work).

 

If someone from Line6 is reading this, could you please reply and comment on how this new feature (to co-ordinate presets and the IRs they reference) is SUPPOSED to work?

 

Thanks for your help.

 

Richard.

[HonestOpinion]

On 8/3/2020 at 5:43 PM, richardwhite2009 said:

I welcomed with anticipation the new method of Helix linking its IRs to Presets with what appears to be the IR name (vs the index number in the list of IRs).

 

My understanding of how this is supposed to work, is that once you have specified which IR a preset is based on, the preset is supposed to be smart enough to "find" that preset based on name -- in the list of IRs.  I think this is supposed to provide the user the flexibility to rearrange the IRs without worrying about having to re-link the presets to new IR index numbers.  I did some testing, and for the most part it, this feature SEEMED to work on my laptop. If you moved an IR, re-clicking on the preset would re-link to the IR in its new location.. I also found that if you deleted an IR, re-clicking the preset would produce an error message.   I found however that on a number of occasions that if an IR was deleted, an error message was NOT presented when you re-selected the preset.  What happened in this case was that the preset definition had been updated automatically to point to IR number 127 which was empty. In both cases, the name of the preset was lost. (It would have been more useful if this name had been displayed in the error message saying it could not find this IR).

 

In addition, after spending THREE HOURS fixing my presets so they pointed to the proper IRs (they had gotten mixed up in the upgrade)... I created a bundle of my patches as well as some setlists, and then happily went to my second computer, fully expecting that I could just copy in my IRs to Helix Native, and then import my bundle or the setlists -- and then the preset references to the IRs would all sort themselves out...

 

Nope.  This did not work.

 

Only about a half of the references to IRs were resolved, even though all my IRs were all copied into Helix Native first.

 

Could anyone please confirm:

- has anyone else experienced this bug?

- am I doing something wrong: do the IR references not get copied into the bundles and setlists?  Do I need to manually export and import each single preset in order to preserve the IR reference?   (I certainly hope not!  That would be way to much work).

 

If someone from Line6 is reading this, could you please reply and comment on how this new feature (to co-ordinate presets and the IRs they reference) is SUPPOSED to work?

 

Thanks for your help.

 

Richard.

 

Sorry I have not confirmed your bug. If this is confirmed you should open up a ticket with Line6 so it can get resolved.

 

Just wanted to comment that I am grateful for the title of your post. Call me oblivious but I had not been aware that there was a 1.93 version of Native. I thought that 1.92 was the latest(due to the out of synch naming correlation between HX Edit 2.92 and Native 1.92) . Appears there is a new 1.93 version with bugfixes so I downloaded and installed it. Thanks!