Automation/Control Assign BUG

[Leroy2112]

I updated Native to 3.10 and now have noticed that some of my blocks are missing some of their assignments. For instance I had a expression pedal controlling the delay time on the Cosmos Echo (midi cc4) and a Bypass parameter (midi cc12) working just fine before updating to 3.10. Now the Time parameter is gone and when I add it back it will not save the time parameter, it just disappears when I reload the saved preset! A similar thing is happening with my volume block. In the video you can see that both parameters (bypass & time)are there then after switching back and forth presets the time parameter is gone. 

Any help with this would be greatly appreciated.

Thanks,

Leroy

[silverhead]

I suggest you open a support ticket to report this bug.

[Leroy2112]

@silverhead I did last night. 

[soundog]

I wonder if that is related to this:

 

 

Good to know the bug has been reported. Thanks, @Leroy2112

[superstring]

I am having the same issue with 3.10.  Controller assignments will not save with presets.  It seems to only keep one assignment and delete all of the rest.  I am using Logic as the DAW.  I submitted a support ticket as well.

[superstring]

So far I have not found a rhyme or reason to why some midi CC assignments are deleted as soon as a patch is saved (volume, distortions, amps, modulation, pitch, etc.). I had a theory for a while that it was the first parameter in an effect, but it happens for others as well. 

This is with 3.10 running on Logic Pro as an Audio Unit (AU) plug-in. 

 

 

Things I’ve tried that make no difference and still lose assignments when patch is saved:

 

1. Tried two different midi pedals (including Line6 FBV).

 

2. Tried assigning directly through the drop down CC list rather than by midi learn. 
 

3. Upgraded from Mojave to Catalina. 
 

4. Tried a different computer (this was a clean install as I had never installed Helix Native on it).

 

5. Tried saving Helix presets to the library and directly to a hard drive. 

 

None of that made any difference. Not sure what else I can do. At this point, I’d like to try and go back to 3.01. Does anybody have any experience installing older Helix versions?  Should I uninstall first?

[soundog]

Open a ticket with Line 6 and report the bug. This is a bug affecting lots of people, and it should get high priority.

 

I don't know why you couldn't use an older version, just be sure to save your presets first. Rather than uninstalling you could probably just move your 3.10 AU component out of the Components folder and install 3.01 (Library>Audio>Plug ins>Components). I have not tried this myself, though.

[superstring]

Thanks soundog.  Since part of my troubleshooting involved installing Native on another computer, I'll use that one to test out your method.  At this point I'd rather have the midi assignments than the new features of 3.10 (though of course ideally I would have both).

[superstring]

I tried installing 3.01 by first moving the 3.10 AU out of the components folder, but I get an error when I launch Helix Native: "Failed to connect to DSP engine. (Device has not be initialized properly.

)".  So looks like I might be stuck with the assignment bug until there is an update.  I am very curious why Soundog doesn't seem to be affected when I have tried it on two different computers with the same Hx 3.10, Catalina, Logic Pro and have the bug on both.  I did file a support ticket and will report back if I get a resolution.

[superstring]

Update (solved?): I had an issue reinstalling 3.10 after I tried to downgrade to 3.01.  So I did a search on my computer for everything named "Helix" and dragged it to the trash and reinstalled 3.10 and was careful to only install the AU version (unselected vst and aax versions).  But now in 3.10 the controller assignments are saving!!!  Not sure what the issue was, but for now it seems resolved.  Of course, I need to try and replicate those steps on my other computer to see if I can get it to work there.  I'll have to be more careful there to backup all of my presets first.  Not sure if this will help anyone else since there seems to be an issue on Windows as well as macOS.

[superstring]

I spoke too soon. I can't get that fix (install 3.01 and then 3.10 again) to work on the other computer.  I even did the exact same steps.  The only thing that seems different is the time that it worked, when I first opened up Helix Native inside Logic it made me sign into my line6 account.  So now I'm wondering if that could somehow be related?  If so, is there a way to force Helix back into default state?  I guess I'll keep searching for a solution.  I had actually be planning on spending the week creating midi assignments for Helix Native.  Bad timing on my part I guess...

[Leroy2112]

Still no fix for this, I've been back and forth with Line6 support since MAY! :(

[josehdx]

Is this issue solved? I have used all automation knobs and switches and i can go beyond midi cc 52