phil_m

They posted an announcement about on the top of the forums last week: http://line6.com/support/forum-86/announcement-90-forumknowledge-base-not-loading/ This is what Frank said about it over on TGP: https://www.thegearpage.net/board/index.php?posts/26002744 We have some pretty major infrastructure issues at the moment due to a separate infrastructure upgrade a few weeks ago. The fix is not an easy one and we will be bringing everything down for about half a day at some point in the next week to try and resolve this. We apologize....this is kicking our butts.

I believe they’ve seriously considered that at some point... But people do expect them, still. They are helpful in the sense that people can get some ideas in regard to preset construction at least.

"Any point" was a month ago...

You want a current doubler, not a voltage doubler...Hoping that was just a typo, because sending 18V to the HXFX may actually damage it. If it is indeed a current doubler, what else do have powered by the Zuma?

1) Not sure about that one... Could be related to what you have on in your signal chain, I suppose. 2) If you go to Global Settings>Preferences and set Tempo Pitch to "Transparent", you should hear that. 3) Hmm... You should be able to set the value of any parameter assigned to a controlled per snapshot. Unless you're saying you're expecting the toggle state of the footswitch to be remembered per snapshot. That won't. Real-time controllers exist outside of the snapshots. You can however select a specific level value to be saved with each snapshot. 4) I have to think about this some more... Unfortunately, I'm just about to run out the door...

https://www.amazon.com/gp/aw/d/B01N812NKL/ref=mp_s_a_1_3?ie=UTF8&qid=1520536749&sr=8-3&pi=AC_SX236_SY340_QL65&keywords=2.1mm+to+2.5mm+adapter

You shouldn't need a driver to pair the AMPLIFi with your PC. Note that the only thing you can do via Bluetooth and your PC is stream audio through the AMPLIFi. It may be that Windows needs updated BT audio drivers or something like that, but that would be a Microsoft issue, not a Line 6 issue.

I'm using the small... It fits like a glove with the G70 transmitter. It almost seems like it was made just for it it fits so well.

Line 6 welcomes suggestions and feedback, it's just that if you just post a thread here, it mostly like won't be seen. The best way to make sure they see it is to post it on IdeaScale: https://line6.ideascale.com/

If you're worried about tone suck with it, I would just use one of the Helix's sends to send a signal to an external tuner rather than put it in the audio path. There's actually "Tuner Out" parameter on the Tuner page that allows to select the sends as an output to an outboard tuner if you want to do it that way. That way you wouldn't have to insert a Send block in all your presets.

I confirmed the CC Toggle values weren't being sent with snapshots in 2.53 as well, and I emailed Dom from Line 6 about it (the lead QA tester). He confirmed that they have this logged, so they are aware of it. I imagine they're planning to address in the next update.

I don't get this sort of feeling at all with the Helix... I find most of the amps to be really sensitive to the input volume and pickups. I actually kind of think it's a little easier to get a wide range of tones from the Helix models than real amp in the sense that for many amps to get in that sweet spot of responsiveness, you'd have to have them quite loud. I recorded this a few months ago when this topic came up. This was all done on the same preset, same snapshot. The only thing changing is my pick attack and the pickup position. I don't believe I even moved the guitar volume knob for this clip. https://soundcloud.com/phil-miller-20/jtm45-pick-attack

What DAW are you using? I have never had this issue, and, really, your DAW should be automatically compensating for any sort of latency of this nature.

No, that's not how it's supposed to work... Only the tap switch should be blinking.

If I had to guess, I would say it’s probably something like a ribbon cable that wasn’t quite connected properly and finally came loose enough to cause weirdness.

I got one of these for all my transmitters... https://www.amazon.com/gp/product/B000P4D8G4/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 Before I had the pouches, I did have the clip come off a couple times. It was kind of my fault, though, as I forgot I had the guitar plugged in still while trying to take it off. I've never had it come off under just normal use. I still like using the pouches and keeping the transmitters on my strap a lot better, though.

Seems like a pretty clear hardware issue... I'd ask for a replacement.

There was a small number of LTs that left the factory with a defective pedal assembly. It sounds like yours is one of those. Apparently, they have 10 metal fabrication machines at the factory, and one had some sort of issue where it was creating these parts incorrectly sporadically. Open up a support ticket, and Line 6 will send you a replacement.

You have to hit that button that says "Authorize This Computer".

I think the thought process is that if someone was going to plug an external expression pedal in the EXP2, they would be more likely to use that pedal as a volume pedal and use EXP1 as the wah because it has the toe switch.

They're having some infrastructure issues... They are aware of it, and are looking to fix it.

If your not hearing the time-based effects in the Mesa's loop, it sounds like perhaps its loop isn't turned on... Assuming all the cables are connected correctly, I don't know what else it could be, really, because the amp is actually passing signal otherwise.

Well, where are you doing your range tests? I guess my only recommendation would be to test it more than just one environment if at all possible. There could be something causing interference with the G75 somewhere that's not affecting the G30 in that particular space.

Sounds like you need to turn direct monitoring off for your interface.

You don't need to download the .hxf file to install the update. You just need to run Line 6 Updater (make sure HX Edit is closed before starting it), and follow the prompts to send the update.