Leaderboard

Figured it out. I had to monkey around with the output settings on the kemper. Turns out I dont need and effects loop block on every kemper rig thankfully. Next step is midi integration....

Yes, it's one bug, but it is very detrimental to performances. It makes every bank change worrisome, as I still cannot determine the root cause of the issue. Thus, when performing, I never know if the Helix will suddenly get stuck in the wrong mode. If so, I am required to manually reset back from Snapshot mode (or restart the Helix) on stage, causing me to drop out of the performance while fixing the issue.

I'm having the same issue getting stuck in preset mode. I'm on 2.82 also. This is a problem when I have to hard boot the Helix mid set. I use my Helix for a LOT of gigs. I need this fixed ASAP. Please!

I also use Studio One, but it's version 4, which has been optimized quite a bit compared to V3. Plug-ins like Helix require a lot of CPU; with all due respect to PreSonus, who include some very fine plug-ins with Studio One, their amp plug-in is not on the same level as Helix. Fortunately, Studio One has a couple different ways to do what's called "track freeze" in other programs, so after recording a track, you can bounce it to processed audio, and save CPU. You can also preserve the pre-bounced state in case you need to revert, and edit the plug-in later. Unfortunately for guitar players, a fact of life is that lower latencies - which give the most comfortable playing "feel" - stress out the CPU the most. Amp sims like AmpliTube, Waves G|T|R, and Guitar Rig can select "lower resolution" modes while tracking, and then when mixing, you can increase the resolution because you can also increase the latency while mixing - you won't notice the change in feel compared to playing. Consider using some of the lower-latency amps in Helix when tracking, then going for the heavy-duty ones when mixing. As to the spiking, that could be something else, and you just hadn't noticed it because it didn't matter until there was something else draining the CPU. Not sure which platform you're using, but for Windows, Latencymon (which is free) will show what's drawing CPU power. For many people, just turning off the wi-fi made a significant improvement in performance. I also found some "HD Audio" drivers that graphics cards install can give a really big performance hit, because they prioritize video over audio. Some will even basically stop your hard drive if needed, so they include a big audio buffer. Disable any unused audio drivers (but note that when there are updates to Windows, you may need to dig in and disable again - they're often turned back on as a "favor" to you). Finally, I've had some mysterious "all of a sudden the program starts crackling" issues when using multiple Helices. Saving the project, closing Studio One, and reopening solved the problem for at least the next several hours, providing I wasn't trying to do a zillion other things on the computer. Good luck! You'll find the same issue with other CPU-intensive plug-ins. You might want to become friends with Studio One's internal performance monitor, which shows CPU drain for plug-ins and what they contribute to increased latency. It can be quite revealing about what's dragging down a project.

If you want to go straight into the front of a clean amp, and use Helix as a digital pedalboard, see this post. Using Helix into the effects return or power amp input of your amp lets you add Helix amp models (but no Cab model) and have effects before or after the amp - your guitar amp is only used to provide the power and speakers, Helix does everything else. Using Helix with 4CM allows you to position the amp's preamp in a Helix block position, allowing you to include effects before and after the amp's preamp. Whether this is useful or not depends a lot on you amp's preamp. It may overlap with functionality you can get nearly as well in Helix already.

I really like this guy's simplified explanation: http://line6.com/support/topic/16164-irs-vs-cabs/?do=findComment&comment=120284 I'm biased, though. :-)