eriksan007

Thanks but there does not appear to be a global snapshot setting page in Helix Native. With regards to “saving the snapshot”, I assume it’s just a matter of selecting the snapshot and turning off the wah, and saving the preset to library? I have tried that.

I have the guide, but it’s not helpful in this case. I know how to configure bypass assignments and controller assignments. The issue is that certain blocks don’t remember their bypass states between snapshots. Updated youtube video. (I’m not sure how this applies: “Helix and HX devices' exported presets include a global Snapshot Control option where hardware controller assigned parameters can also be enabled or disabled for control via Snapshots. Helix Native does not offer this option but will preserve the presets' hardware settings upon import and export.”)

Thanks and yes, the check mark is next to “Snapshot Bypass”. Unfortunately, it did not work. In snapshot 2 I turn off wah, save to library, then go to snapshot 1, then back to snapshot 2 and the wah is on again! Min film - Medel.mov

Why is it that some blocks do not come back to their set bypass state, after toggling from and back to that snapshot? For example, as in the attached video, in snapshot 1 I turn off wah, go to snapshot 2, then back to 1 and the wah is on. The wah is set to “Snapshot Bypass”. Min film.mp4

Ok, I figured out a way to bug report for Helix Native, just select "No Product" in the Ticket creation section. Then there will be a Helix Native option.

To do that, drag the following block down.

I’ve seen that there are split and join blocks, but I can’t find them anywhere.

I consider notes valuable as well.

If you have a laptop, it could be due to faulty battery.

Looking to buy a second hand/used license of Helix Native.

I'm still experiencing this issue on 20190929.

I've run into a similar issue in my thread.

I've run into this issue as well in Cubase and Reaper, see my thread for the problem description, but no solution yet.

Update I resolved the issue, which was due to a faulty battery on the Macbook Pro which didn’t hold any charge, once replaced, Helix Native runs smoothly. -------------------- Cubase At 1024 sample buffer size and one instance of the plugin, the CPU usage is at about 80% and audio drops out slightly. Two instances, or other plugins, lead to serious dropouts. Reaper At 1024 buffer size and one instance of the plugin, the CPU at about 30 % load and it works unless I do something CPU intensive. Two instances makes use of 60% and the audio only plays well for a few seconds before starting to drop out. Versions Helix Native 1.81 demo, Cubase Pro 10.0.40, Reaper 5.983/64, Mac OS 10.14.6 (8GB RAM), RME Fireface 400 via thunderbolt adapter with firmware version 3.36 and Totalmix 1.60. My computer. Do I have anything unusual taking up CPU?

I'm having a similar issue in Cubase Pro 10.0.40, Mac OS 10.14.6. See my thread.