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

roadtosalvation

Members
  • Posts

    2
  • Joined

  • Last visited

roadtosalvation's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. 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. UMC404HD interface.Fresh installs of everything. I've made a thread on Reddit showing users with different hardware set-ups (Mac) and different DAWs having the same issue however: 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. I've also gotten this just randomly too- without switching through a bunch of presets. ie: Just changing 1 preset after loading a project can cause this to occur. 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? Would any other information could help debug this? I went to the bug report page but Helix Native did not appear as a valid product that I could register, and thus I could not report a bug against it. Greatly appreciate any insight, thanks.
  2. 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.
×
×
  • Create New...