cruisinon2

I heard that excessive use of Helix Native gives you hairy palms...

99.97% of the time it's nothing more than confirmation bias. Lifelong tube snobs will inevitably conclude that the results are infinitely better with a tube preamp in front of everything, because they've been worshiping at that altar since day one, and they desperately want it to be the "truth"... so before they've ever played a note and tested it out, they already "know" what the results are gonna be. Quitting smoking is easier than forsaking the Gospel According to Tubes... trust me, I've done both...;) But when push comes to shove, I'd bet money that you couldn't tell the difference in a blind taste test... with the exception of the handful of true "golden eared" producers/engineers out there in the world, most of us couldn't...and that includes me.

Who'd you think he was?...;)

Post this in the Helix forum, otherwise you'll be waiting until 2 years after the second coming for anybody to see it.

There's no fix. The old transmitters' battery life was intentionally neutered by a firmware update for liability reasons... if you really want a deep dive into why, there are a thousand other threads on here that go through it all in gory detail. If you want it to work as advertised, you need the new G10TII transmitter. Reports from the wild seem to indicate that these will get you pretty close to the advertised battery life, much like the original transmitters prior to the ridiculous firmware update saga. The base unit will still work just fine with the new transmitters. You can try opening a service ticket and see if they'll replace the transmitter, but since you're not the original owner I'm guessing you don't have a sales receipt... what they'll tell you is anybody's guess. You might be stuck paying for it... only one way to find out.

Oh that's never going away. Thank a lawyer...;)

Last week I had a sandwich that sucked... life's rough. ;)

No.... but keep the faith, my man. ;) Regardless, in here your request will go 173% unnoticed by anyone who can actually do anything about it...feature requests have to go in IdeaScale.

And with the inherent latency that many Bluetooth devices have, you don't want to go that route anyway. It's fine for passive music listening, but when playing an instrument in real time, no bueno...

I especially like the new "feature", that requires me to switch to "desktop view" in order to access the login button, which (for me at least) is now absent on every mobile device and browser I've tried. Nothing like extra grunt work to brighten your day, lol...

It's not. For those of us who've been hanging around this forum for a long while, the one thing that has become crystal clear over the last dozen-ish years that the JTV's have been around, is that some folks have this problem, and others don't. You either get a good one, or you don't... We could argue all day long about why this issue plagues some instruments and not others, but frankly I don't think there is a single, universal explanation. As with most things in life there are likely multiple contributing factors...nothing exists in a vacuum. And the more tech-dependent something gets, the more things can go wrong. The more complicated the plumbing, the easier it is to clog the drain... Regardless, mine works just fine, and has for 9 years now... and I have the same firmware as everybody else. So if it were purely a software problem, we'd all be suffering from it, L6 would not have a single happy JTV customer, and this product would have gone the way of the dodo looooong ago. Either way, no matter what the cause(s) may be, nothing is getting fixed via firmware updates at this point... there hasn't been an update of any significance in many moons, since ~ 2014, or so. This is no longer a developing platform.

Just for my own morbid curiosity, which holiday(s) are we talking about? I can destroy a set of non-coated strings in less than a week.... can't wait till Christmas to change 'em out. ;)

Somebody just finished reading "How To Win Friends and Influence People"...

I have no idea what "getting asked for a token" means... but what I do know is that nobody who might be able to answer your question will see this in here. Post it in the Amplifi forum.

You could preview stuff until you're blue in the face, and there's still absolutely zero guarantee that it would sound anything like what you heard when you actually get your hands on it... for precisely the reasons listed above. There are simply too many variables. And having only one common denominator (the patch) is woefully insufficient to yield anything that approaches tonal continuity from one user to the next. With my first modeler, I downloaded hundreds of patches from Customtone in a futile attempt to find anything useful. Never ended up using a single one of them. No amount of "previewing" would have changed that outcome, no matter how glorious they might have sounded in someone else's posted sound clip. Customtone is a nice concept, but in the end it is nothing more than a marketing gimmick, and almost entirely useless in real-world applications.

Two words: $hitty platform.

Stay with me, because this one is a bit of a curve ball...but if you want a Marshall sound, I'd start with one of the Marshall amp models. ;)

It's obviously a hardware problem, so it's unlikely that there's anything you'll be able to do about it yourself. If there are no qualified repair places for you to take it, then I'm afraid you're going shopping....

Only that it's an 12-ish year old product at this point, for which there have been no updates of any significance since 2014 or so. Stand by for someone to chime in with "there have been more recent updates than that!"... and while technically true, they've only been minor bug fixes, and the addressing of compatibility issues with Workbench for the Standards, which were introduced later. In terms of modeled sounds or functionality, there's been nothing genuinely new in Variax Land for nearly 8 years (an eternity in today's techno-world), so the current versions are clearly no longer being developed. Smart money says that the next iteration, whatever it may be, is probably not far off... exactly when is anybody's guess, of course.

It's like buying headphones... you'll either love or hate whatever you get... unless you can try them first, you kinda have to cross your fingers and hope for the best. Just make sure that the wire is replaceable... that'll be what eventually craps out. The earpieces themselves should last forever as long as you don't knock them around too much.

5 lb ankle weights....

You can't find it because it doesn't exist... you asked for a way to make the same change(s) to a whole bunch of existing patches... making the same change to everything simultaneously would be the definition a "global edit". But unfortunately there is no way to do what you're asking. It is what it is...

Nope... can't make the same global edit across multiple existing patches simultaneously.

They could issue a green one for St. Patty's Day, and call it the Gaelix...

You'll have to be a bit more specific... what exactly happens? "It blocks itself" doesn't convey much...