roadtosalvation Posted March 13 Share Posted March 13 Hey all, I didn't see any post that covers a potential bug I've found yet so posting here. I am using Helix Native 3.71 on Windows 11. My PC is decently high-end, 32gb RAM, 7900x CPU, etc. I've confirmed this occurs in both Cubase Pro 13 and FL Studio 21.2.2. Fresh installs of everything. UMC404HD interface. Helix Native works fine once added to a channel initially, and even after switching through a few different presets, but eventually after switching through many presets (30+) it stops outputting any audio. The plugin still does show the input levels are present (see pics), but even if you disable all the effects or switch presets, once it enters this broken state it will no longer output any audio. If you restart the DAW or delete the plugin from the channel and re-add it then it works fine with any preset again. In FL Studio, it actually makes a quick buzzing sound at the moment it breaks. When this occurs, other instances of Native on other channels don't cease functioning. This feels like it might be a memory leak within the plugin; resources are being allocated when switching between presets but never released, so eventually it presents an OOM exception in Native. It seems to happen faster when switching between more intensive presets (ie: DEVIN TOWNSEND). However, I don't see any increase in memory usage in the Task Manager when this happens. Does anyone know why this is occurring and how to resolve it? Is it possible to file a bug report? Would any other information could help debug this? Greatly appreciate any insight, thanks. Quote Link to comment Share on other sites More sharing options...
VincentSchrover Posted March 15 Share Posted March 15 Hi to everyone. I can confirm this. I have the same experience. On one Laptop with Windows 10 it worked fine. After the update to Windows 11 it loses the output connection after several preset changes. Daw is Reaper. It looks exactly like your screenshots. On my brand new second laptop wich came with Windows 11 Helix Native behaves the same. After several preset changes it goes silent. After restarting Reaper all behaves normal again. Quote Link to comment Share on other sites More sharing options...
glasser Posted March 17 Share Posted March 17 Same thing happens to me with Reaper. Windows 10 with AXE I/O interface. Quote Link to comment Share on other sites More sharing options...
Pitmairen Posted March 26 Share Posted March 26 I have the same problem. I'm using Windows 11 Pro. Helix Native works fine for a few minutes, then suddenly the output stops. It is the same in both Reaper and Ableton live. I have to restart Helix Native to get it working again. Quote Link to comment Share on other sites More sharing options...
rg652ahm Posted March 26 Share Posted March 26 Verified in Cubase 13, Bitwig and Cantible VST host on windows11 Quote Link to comment Share on other sites More sharing options...
moqshjdf Posted March 27 Share Posted March 27 I have the exact same issue, this time on Logic Pro. Apparently this is an OS-insensitive bug. Quote Link to comment Share on other sites More sharing options...
eaglepass Posted March 31 Share Posted March 31 I can confirm a similar problem behaviour in Studio One Pro 6.5.2 on Windows 10. Quote Link to comment Share on other sites More sharing options...
dandy12 Posted April 12 Share Posted April 12 I have exact same issue in multiple DAWs - Cubase 11, Reaper - Windows 10. I have tried multiple interfaces BOSS GT-001 and SSL 2+. After playing around in Helix Native for some time, audio output suddenly stops. The only way to get it working is to unmount the plugin on track and reload which is annoying. Same happens in Reaper. Though I see main output track as "Track Muted" when this happens in Reaper. Can this be because switching from one preset to other sometimes suddenly cause a noise peak, causing the DAWs to mute the sound output to prevent ear damage. Quote Link to comment Share on other sites More sharing options...
fujgol Posted April 14 Share Posted April 14 Processed audio from Helix Native does not register using Reaper Quote Link to comment Share on other sites More sharing options...
dandy12 Posted April 20 Share Posted April 20 Hey is there any update on this? This is really frustrating and blocking because all tweaks has to be done again. Quote Link to comment Share on other sites More sharing options...
wn6134 Posted April 23 Share Posted April 23 Reaper 7.15. MacOS 14.4.1. The same. Quote Link to comment Share on other sites More sharing options...
Nandolino Posted July 4 Share Posted July 4 Same here. Logic 10.8.1 on MacBook MacOS Sonoma. It's an annoying Plugin issue. Line 6, please solve this problem. Quote Link to comment Share on other sites More sharing options...
datacommando Posted July 4 Share Posted July 4 On 7/4/2024 at 9:41 AM, Nandolino said: Same here. Logic 10.8.1 on MacBook MacOS Sonoma. It's an annoying Plugin issue. Line 6, please solve this problem. Hi, This is a peer to peer user forum. There are no Line 6 staff here and only very occasionally do they visit these forums, especially on 4th July - (See the “sticky comment” in the black banner stripe at the top of this page entitled “Welcome to the Line 6 forums”). If you have issues that nobody here can help with then raise a ticket with Customer Support. Hope this helps makes sense. 1 Quote Link to comment Share on other sites More sharing options...
dooz911 Posted September 29 Share Posted September 29 Hey everyone... I have the same thing going on in Reaper 7.22 on MacOS 15 but it is really random after switching presets. This did not happen in Studio One but could be coincidence. Did everyone file an issue at line 6 support? If not, please do. The more reports come in the more serious is it taken. Best, Daniel 1 Quote Link to comment Share on other sites More sharing options...
dandy12 Posted Wednesday at 09:08 PM Share Posted Wednesday at 09:08 PM On 9/29/2024 at 10:31 PM, dooz911 said: Hey everyone... I have the same thing going on in Reaper 7.22 on MacOS 15 but it is really random after switching presets. This did not happen in Studio One but could be coincidence. Did everyone file an issue at line 6 support? If not, please do. The more reports come in the more serious is it taken. Best, Daniel I have talked to support about this annoying issue. There seems to be problem with Simple Pitch blocks. I have tested my self and the presets that cause this issue have Simple Pitch blocks in common. If you edit the preset and remove the pitch blocks, it works. They said they are aware and working on it. Though I have experienced it with presets that don’t have pitch blocks as well. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.