soundog

The above turns out to be the best "fix" for those of us who want to use our audio interface as our studio's output device. Create an aggregate device for recording your guitar tracks with Helix. You can switch it back to "normal" when doing your microphone tracking. I just got a new Stomp to use for recording some tracks in Logic Pro and was using it (audio in) with an Apollo Twin (audio out). I was having the exact same 2—3 second guitar delay mentioned by the OP after recording for awhile. Maddening. Creating an aggregate device fixed the problem. So either solution (aggregate or using Helix as your audio out monitor) will do the trick.

Holy Mackerel! Talk about plug-in and just play. I just received my Iridium pedal (a Christmas present to myself for being relatively good). This thing is over the top good! Yeah, I'm playing it some with the HFX, but I like it enuf with just the built in IRs and a pinch of the room reverb. Holy Mackerel!

Thanks all. My basement has several pieces of musical hardware that was abandoned by software; its just something to be aware of when investing in stuff. At least the Variax still plays! In reality, one can't assume any manufacturer will continue to support old products via software updates — they gotta prioritize resources. That said, I do have an old Mac that I think I'll hang onto for running "old" but essential 32-bit apps such as Workbench. And I wonder if someone might create a utility app that will run 32-bit apps under the 64-bit OS?

I bought a Variax 700 Acoustic in 2010. One of the main reasons to buy a Variax is for the custom tone-shaping available via the Workbench software. Unfortunately, Line 6 hasn't updated the necessary Workbench software to keep up with computer operating system evolution. I managed to mess around with Java versions, etc, to keep it going over the past several years, but the OSX move to Catalina seems to have broken everything. And with it, my trusty Variax. Ten years is a short life span for a guitar! Yeah, I can still plug it in and play it, but the custom tone-shaping feature is poooooft. I also own a Variax Standard, which uses the newer Workbench HD. But one could logically predict that the HD software will be abandoned within ten years, just like for the earlier Variax models. The 10-year life span for custom tone modeling is something to keep in mind if you are considering buying a new Variax.

The Beat Bars looks nice and I'm sure it would play nicely with Helix. Expensive though. If your on a budget, you can use a expression pedal like a Yamaha FC7 ($45) or M-Audio EX-P ($30). They work just dandy.

Hmmmm. It's easy to overdrive bass in the digital domain. Its possible your metering is not detecting (or reacting to) your really low frequencies. Experiment with dialing down the input on the Steinberg further and see if that helps. You can also play around with a high pass filter (70 Hz or thereabouts) and/or light compression before Native. Also (of course) try turning your amp gain down (and the master volume up to compensate).

@dawiodjoopkk12 — what sayest thou? Are you bona fide? A bot? A devil? Enlighten us!

Wow, datacommando — I see what you mean! Very weird. I just read his other posts. I wonder if those little links at the bottoms of his posts (different in each post, and hidden by using small, light-colored fonts) give him some kind of cash flow? Like 0.00001 cent per post. So now he's some rich kid living in a mansion at the edge of the sea somewhere ... laughing at us and drinking Mai Tai's. If so, I feel used.

You gotta admit it made you want to click on it.

Right on! Everyone having this problem should open a ticket and provide info to tech support. Doing so will help prioritize the alarm, and maybe lead to a solution. Squeaky wheel gets the grease. As someone who enjoys using Helix Native (with Mojave and Logic Pro 10.4.7), I sure wish Line 6 would find a fix for y'all.

It's true!

A Klon is to a reverb as an amoeba is to a sperm whale. Where can I get this on a T-shirt in a men's medium?

If it shows up in the plug=in manager as Enabled, than you should be able to use it: Create an audio track. In the track channel strip (main window or mixer window), click the Audio FX button, and use the pull down menu to find Audio Units > Line 6 > Helix Native. Select Helix Native and it should appear as a plug in in your audio track channel.

Excellent info, @goldballoon ..... thanks for adding it!

Sure its subjective. But you gotta trust your ears! Also, see this thread:

Hmmmm. That's not normal behavior, and certainly annoying! The trial version does "phone home" (requiring a log-in to your Line 6 account) but an authorized/purchased copy of Helix Native should not do this, and you should be able to use it unhindered. Try a reinstall, or contact Line 6 and open a support ticket. The other possibility is .... did you recently upgrade Logic to version 10.5? It has had some problems with various plug-ins, especially when running under Catalina.

Then you've got a seriously big problem.

This is a weird thread, but I'll chime anyway. I play on a lot of sunlit stages. I find direct sun is the worst, and if you are in a shadow you can see the LEDs good enough. So ... if you build a thin plywood (even cardboard or art board will work) three sided box fitted to surround the sides and back of the Helix (leaving a slot for cords in the back, you can then fit the top with shade cloth that will cover just enough so you can still access the pedals, etc. The box should be high enough to need cast shadows cast on the LEDs. If the sun is behind you, you can fashion a high shade block behind you and the Helix. You have to think in terms of a sun block between the sun and your pedals. High noon is the biggest challenge, but that's where shade cloth can help.

For what its worth, Helix preset files (.hlx files) follow the open standard JSON "JavaScript Object Notation." There's plenty of documentation re JASON online, and free or paid JSON editors available. I used to use one on the Mac called JSON Wizard to bulk edit Helix files. You can decipher the parameters in a preset jason file, but its not for the weak-hearted, and you may need to sign some sort of deal with the devil to get adept at deciphering things. Some Helix users have attempted writing parsers for .hlx files; look around on the forum and you might find something. Just to show you what you could be getting into with reading .hlx files, here is the front part of a preset, as read into a free online JSON Editor (there are lots of them, but I used jsoneditoronline.org): {"data":{"device_version":43122688,"tone":{"variax":{"@variax_str3tuning":0,"@variax_str2level":1,"@variax_str4tuning":0,"@variax_str2tuning":0,"@variax_str1level":1,"@variax_str5level":1,"@variax_model":0,"@model":"@variax","@variax_str3level":1,"@variax_volumeknob":-0.1,"@variax_str4level":1,"@variax_str6level":1,"@variax_str5tuning":0,"@variax_customtuning":true,"@variax_lockctrls":0,"@variax_toneknob":-0.1,"@variax_str1tuning":0,"@variax_magmode":true,"@variax_str6tuning":0},"dsp1":{"split":{"bypass":false,"@position":3,"BalanceB":0.5,"@enabled":true,"BalanceA":0.5,"@model":"HD2_AppDSPFlowSplitY","@no_snapshot_bypass":false},"block2":{"@path":0,"@type":0,"@stereo":false,"@position":2,"@no_snapshot_bypass":false,"Gain":2,"@enabled":false,"@model":"HD2_VolPanGain"},"outputA":{"@output":5,"@model":"HD2_AppDSPFlowOutput","gain":0,"pan":0.5},"block4":{"@no_snapshot_bypass":false,"Speed":0.02199996,"SyncSelect1":6,"Feedback":0.28,"@position":4,"@stereo":true,"TempoSync1":true,"@type":7,"Mix":0.22,"@model":"HD2_DelayModChorusEcho","HighCut":9540,"Level":0,"ModulationMode":1,"Depth":0.49,"@path":0,"@trails":false,"Scale":0.75,"Time":0.538,"@enabled":false,"LowCut":155,"Spread":1},"inputA":{"decay":0.5,"noiseGate":false,"@model":"HD2_AppDSPFlow1Input","@input":0,"threshold":-48},"block8":{"@model":"HD2_Chorus","Mix":0.5,"Tone":0.5,"Predelay":0.3199999,"Level":0,"WaveShape":2,"@no_snapshot_bypass":false,"SyncSelect1":6,"Speed":0.3199999,"@type":0,"@stereo":tru etc...... If you read through this gibberish, you’ll be able to find the block # used, and what it is. So for the above, Block 4 is category: Delay, and the effect is the Mod/Chorus Echo. The parameters used for Mod/Chorus echo are: Time, Feedback, Low Cut, High Cut, Mix, Level, Speed, Depth, Modulation Mode, and Trails. Reading through the gibberish, you can figure out what the parameters are. I didn’t take the time to do a direct compare of the JSON file and the preset parameter settings to figure everything out exactly, but most of the parameters are obvious. It wouldn’t take long to decipher the rest and get good at it. For this example: Time: 0.538 (not sure how this translates to ms in the block, but do some math; the parameter range is 0—8s. Double check to determine.) Feedback: 28% Low Cut: 155 Hz High Cut: 9.54 KHz Mix: 22% Level: 0.0 dB Speed: 0.02199 (again, double check to see how this parameter relates actual preset; range of actual parameter is 0—10. I’m guessing this is 2.2) Depth: 49% Mod Mode: check to see if 1 = off, chorus, or vibrato Trails: Off Like I say, its devil’s work. Somebody should write a good interpreter or parser and give it away to the world. I can’t because I’ve got to go clean my deck.

Necrophilia is a treatable condition.

When you say "muddy" it makes me think that you may be overdriving the signal chain. Try turning things down (interface input volume, Helix input level) and also dialing down the bass and drive on amps. Another thing to experiment with is putting an EQ plug-in before Helix and see what adjusting low-mids and low-end does....

Very smart idea! Happy looping...

Wise words, @cruiseon2. I was reading up on swapping pickups in my Standard, but your post was the tipping point for me. Gonna Let it Be.

Haven't tried it, but should be fine to use either Send or 1/4" LT out into your looper, then the looper into your XR18. You can route the looper within Helix so it is post or pre Helix effects.