PierM

Pod Go is able to run a bunch of HX algos, as happen with Helix which can run legacy algos, coming from old L6 devices. This is about algorithms (math) running on different platforms, which looks like they need different patch structure, because - again - platforms are different. Not sure why we are arguing about that, I mean, it's just a fact. Then, if you ask me if L6 did that for market separation purposes, or because was necessary due the different hardware abstraction, I have no idea.

I discovered that the issue is a double click that happens on a single tap travel. This especially happen with "heavy" tapping; as soon as the FS is all down, there there is the first TAP, when FS is released, there is a second TAP. That's why most of the time you get a jump to max tempo. Because two clicks/taps are sent within an extremely short time. Also happens when you hold down to leave the tuner; two taps on release. Dont know if this is an electrical glitch from the switch, or a mechanical problem, engaging the switch multiple times. To avoid that, you need to be very soft on tapping, or use an external switch/control to tap. I could repro this on my Helix Rack Control, an two Helix floor from friends...so looks like it's there in every unit. HX Stomp seems less affected, I guess hardware and mechanics arent 100% the same. Imho this would be fixable code side, introducing a threshold to clean up the tap triggering.

They are not compatible.

I don't have a 212, but I do have two 112+ and a Firehawk 1500, which is stereo. Honestly, with the FH1500, the stereo spread is barely there, unless it's an explicit effect like a ping pong, and you are sitting exactly in the middle of the two speakers. As soon as you move just a little out of the center axis, stereo is gone. Imho, if you want stereo, you need two separate cabs. As for the vocals through the PCs, I'd say they can be pretty boomy in a small room, even with low cuts and EQs... so yeah, I'd keep the Bose.

Sorry I do quote myself :P

And how are you monitoring the Helix? Straight from the Helix, or are you monitoring from the DAW? From what you describe, doesn't sound like an Helix problem. More like a DAW problem, not Helix hardware related.

What's doing the iMac in that context? How are you monitoring the Helix?

Compensate at the output, that's it. Native it's different from other plugins. The dynamic range and the headroom are really wide (and that's why you need to stay low at the input, especially with your interface which has a bit of a narrow dynamic range), and they works better with dynamic impedance circuit at the input (which is what Helix hardware does), which is rare to find on the average audio interface.

Too hot input signal. Native needs an input in between -36 and -12dB (the gray range at the left of Native meter). I'd suggest to set your max input levels to -12. Never above that, even if it's not red. If your signal stay above that area, everything will start sounding distort. Sometimes with native, and some combination of audio interface and pickups, it's better to keep input level on the interface panel, set to the minimum.

Hi. Here you can find 126 pages (along 6 months of blah blah) about the subject, and also few L6 guys posting there. https://www.thegearpage.net/board/index.php?threads/helix-3-1.2197408/ Short answer is; nobody really knows. My only wish is mic offset for cabs, even if I'm not longer using Helix amp modeling, but this could be something pulling me back. :)

Hello. Can you please just f....g stop? Thanks.

You need to press the gain encoder, and then dial the value. This will place a keyframe there, to be stored in the snapshot.

Funny to see in the other thread, about exactly same topic, someone saying exactly the opposite. :)

Yep, what the other guys said. I do keep my pedalboard always in the FX loop of HXStomp (which sits in the same pedalboard), or the big boy Helix Rack. This way I still have the option to bypass those pedals, and move them where I want, per patch. Sometimes I do also keep my HS Stomp, in the Loop of the Rack... that's weird, but fun. :D I think that's the beauty of these toys.

Anyway, afaik the M9 had the same tactile switch, soldered to PCB. Same as Helix, HX etc... Funny is, I remember people complaining about how bad those were lol! What make noise in these systems aren't really the little switches, but friction of springs/metal bits just above the actual switch. Messing around there, imho, is a path to nowhere. Also, this will totally void the warranty (and considering it's a brand new, just released XL, doesn't really sound a smart move). If ain't broke, don't fix it.

Why didnt you buy a regular stomp instead XL, and a controller with swicthes you like? Sigh...

I do have a 2011 (Bought in 2016 as new, from Thomann). Never had a single problem. Played a new one, didnt notice anything different. I dont think new board is doing something the average user could hear or feel. Probably just stuff that makes L6 happier, but not for the sound or for the performance, otherwise we would have seen a marketing lollipop back in 2012. Nice anectode is that, within a collection of +30 guitars (most of them Custom Shop items), this JTV59 is the best companion for my Fishman Tripleplay. Incredible how well the FTP tracks this guitar. Coincidence maybe, maybe not. :)

Helix Stomp has a single Setlist, with 126 presets, subdivided into 42 Banks, with 3 Presets each. This means you can't do what you are asking for, as there is no multiple setlist onboard. Just one. My suggestion is to think per preset, not per setlist. Just do proper backup to avoid losing stuff. Helix Floor/Rack/LT; 1024 presets (8 Setlists * 32 Banks * 4 Presets) Helix Stomp; 126 presets (1 Setlist * 42 Banks * 3 Presets)

My take on this is that Native meters are probably just intended as signal in/out leveling, not for live metering. It's clear there is a much slower response, and a fairly rude quantization. i wouldnt be suprised if they are also affected by buffering. For sure not calling or reading level info straight from DAW.

No. As already explained, you can "remote" the Page <> functions through external FS4 and FS5, to scroll between modes. This will exclude these as Stomp 4 and 5. They will work just as Page/Navigation <> FS prev/next mode. If you want to preserve all FS, from 1 to 5, and avoid the Page nav, you need a MIDI controller, and use that one for snapshots and other stuff.

I do have both, Rack and Stomp. Tone is the same (but DSP is the half, so you cant do same double path things as the Rack), but Rack is still a different beast, for everything but tone. Stomp can be a PITA for patch editing/creation, as well for accessing sub layers of features and commands. I'd say, unless it's a very basic patch, the Edit software is kind of mandatory for Stomp...:)

If I may suggest; for basics like that, google is working great. Then there is Knowledge base, on this same place; https://line6.com/support/page/kb/general-faq/line-6-device-factory-reset-procedures-r435/

If you want a block bypass to not be stored in any snapshot, select that block, press Action button, and set Snapshot Bypass Off.

Yes.

That's a multifunction joystick, with rotation encoding, axis and push. It's a 6 pin, and a single broken solder (cold joint) it's enough to stop one of the functions.