The Param Map is greyed-out for the VST3 version of Helix Native in PatchWork. I have not experienced any issues with the parameters/host automation with other DAW's/hosts I have used (Reaper, Ableton Live, Gig Performer).
I found an old post from 2018 where someone reported a similar issue with Helix Native VST3 and Axiom. No progress since then?
viewtopic.php?p=7150988#p7150988
Helix Native VST3 parameters not available in PatchWork
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 6336 posts since 8 Sep, 2004 from Paris (France)
Unfortunately no. We have no idea why this happens, and we have not received any answer from Line 6 about this topic. The VST version however does not have any issue.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6336 posts since 8 Sep, 2004 from Paris (France)
Yes that's indeed only the VST3.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6336 posts since 8 Sep, 2004 from Paris (France)
Hi,
I haven't checked this pug-in for a while, but a couple of changes have been made to fix a similar issue with other plug-ins, so it is not unlikely that it has been fixed for this VST3 too (there is more than a single method to expose the parameters in VST3 and we had missed a few of them). Have you tried it with a recent version of PatchWork?
I haven't checked this pug-in for a while, but a couple of changes have been made to fix a similar issue with other plug-ins, so it is not unlikely that it has been fixed for this VST3 too (there is more than a single method to expose the parameters in VST3 and we had missed a few of them). Have you tried it with a recent version of PatchWork?
-
- KVRer
- 6 posts since 27 Sep, 2025
I've tested the last 2.74. It's possible to make a workaround using internal midi automation provided by the Helix native plugin...
..but I've also discovered another significant issue: Helix native is not responding to CC69
The CC 69 is essential for the plugin because it controls the "snapshot" receiving 8 possible values (0 to 7) to change to 8 "snapshots".
I double-check this by testing the plugin outside Patchwork, and also other containers like Unify and Element.
It's a pity, because this makes the helix native almost unusable for live use.
..but I've also discovered another significant issue: Helix native is not responding to CC69
The CC 69 is essential for the plugin because it controls the "snapshot" receiving 8 possible values (0 to 7) to change to 8 "snapshots".
I double-check this by testing the plugin outside Patchwork, and also other containers like Unify and Element.
It's a pity, because this makes the helix native almost unusable for live use.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6336 posts since 8 Sep, 2004 from Paris (France)
I have double checked the plug-in today, and it indeed reports only the " fake" MIDI CC parameters (that are not automatable, so they do not appear in the list, which is expected - they however have MIDI CC 0 to 129, which is unexpected as there are only 128 CCs available...).
I have no idea why tis plug-in does not expose the other parameters that can be seen in some other hosts (I have tried many different things to initialize the VST3 components in various ways, but it still only reports these parameters. It remains a mystery to me!).
Regarding CC69 it actually appears in the list, so it should be supported. Have you checked that it was not used elsewhere?
I have no idea why tis plug-in does not expose the other parameters that can be seen in some other hosts (I have tried many different things to initialize the VST3 components in various ways, but it still only reports these parameters. It remains a mystery to me!).
Regarding CC69 it actually appears in the list, so it should be supported. Have you checked that it was not used elsewhere?
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6336 posts since 8 Sep, 2004 from Paris (France)
I have opened a ticket with Line6, we'll see if they can provide more information about what their plug-in expects to show their parameters!
-
- KVRer
- 6 posts since 27 Sep, 2025
Thank you for your answer. Yes, I checked again, and snapshot is not changing. CC69 is reserved always for snapshot change, and it's not possible to use it in another automation for this plugin. It's really easy to test.Blue Cat Audio wrote: Tue Oct 07, 2025 12:37 pm Regarding CC69 it actually appears in the list, so it should be supported. Have you checked that it was not used elsewhere?
Just sending CC69 in the range [0-7] may change the snapshot number in the range [1-8] as this picture:
You do not have the required permissions to view the files attached to this post.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6336 posts since 8 Sep, 2004 from Paris (France)
The ticket has been forwarded to the dev team @ Line6. We'll hope we'll get some feedback soon.
I guess the whole plug-ins parameters are messed up with the hidden parameters (they should be at the beginning of the parameters list). So the CC# is probably off (if it works).
I guess the whole plug-ins parameters are messed up with the hidden parameters (they should be at the beginning of the parameters list). So the CC# is probably off (if it works).
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6336 posts since 8 Sep, 2004 from Paris (France)
Got an answer from Line6:
"It’s been logged as a bug, but it is unknown as to when it may be addressed."
Maybe you guys can also report the bug to them. From my experience, it is in general faster to get an answer when customers complain rather than other companies...
"It’s been logged as a bug, but it is unknown as to when it may be addressed."
Maybe you guys can also report the bug to them. From my experience, it is in general faster to get an answer when customers complain rather than other companies...