SaschaFranck

Fwiw, one thing which you may want to keep in mind as well: In case you're using pretty hot leveled patches and add whatever USB audio stream from your sequencer, YT or whatever, you might run into clipping on your output converters. Unfortunately, the new output meter doesn't display a mix of these signals but the level of the patch only. Anyway, in a digital environment, it's likely the best idea to deal with levels rather conservatively, i.e. not running them all too hot. Usually, for all sorts of monitoring purposes, there's more than enough options to pull the levels up in case that's needed - without adding all that much noise floor. Personally, I rather have a tiny bit more noise (in case that even happens) than digital clipping.

Fwiw, mine is sitting there at -5.0dB and I'm usually getting a decent balance between, say, backing tracks from YT and my Helix patches, so I think your patches must be pretty loud. Possibly a good idea to check with some factory patches as I think they serve well as "role models" for proper patch leveling.

Go to the global settings, Ins/Outs, first page, rightmost entry should say "USB In 1/2 trim". Adjust to your likings.

You could adress this issue the other way around by increasing the volume of your USB return (which is what YT is using). Then turn down the master volume. I would however suggest to check your preset volumes at one point in time (maybe it's exactly the right time now that nobody's gigging anyway...), because usually, with the USB return level untouched, YT videos should be pretty loud in comparison to any "average" leveled Helix patch. At least that's what things are like over here.

You might as well try the offline update through the Line 6 updater. To me it seems as sometimes the Line 6 server doesn't work all too shiny, so it might be an idea to take it out of the equation. The Line 6 updater allows for an offline update (the flash updaters are available as separate downloads) whereas HX Edit doesn't.

To join the choire: Thanks from me as well!

Which firmware version?

Yeah well - to quote Digital Igloo from the update instructions: Maybe the interwebs were too polite so far...

I could post a video proving that statement wrong. The LED is always flashing a tad slower compared to the delay repeats (at 1/4, of course).

Well, I'm not saying it's accurate enough to use it as a metronome replacement (which won't work anyway for most people, regarless whether it's coming from a metronome app or the Helix), but it's defenitely accurate enough to give you a good start up tempo (should you need to count in based on the tempo programmed in the Helix) or information about delay taps. I have measured things a bit and the LED is always flashing slower than the actual tempo, but at, say, 100BPM, the first 4 beats are sufficiently accurate. And as it doesn't serve any other than "informational" purposes, this is just fine in my book. Ok, I never exactly needed it anyway, but I could imagine it to be helpful to check whether the Helix has registered my taps properly.

Hm, just out of interest, I crosschecked and it seemed to be fairly accurate. Thing is, for whatever (psychological?) reaons, I find it incredibly tough to play along with the flashing. Happened to me before when trying to use my smartphone metronome just in optical mode. Maybe that's also why one tends to think it's off time.

Yeah, I have never seen it working in time at all (but I only bought a Helix at FW revision 2.8). That's why I simply switched it off in the global settings.

With an almost empty Helix, the process seems to be a *lot* faster (I exported everything before the update and cleared all my setlists and IR slots), so to me it seems there's not much Line 6 could do about it, unless they can speed up the patch/IR loading process. Anyway, even if it takes an hour, I don't think that's a lot, given you only do these kinda things once or twice a year. And fwiw, a "monster machine" very likely won't help to speed the process up at all.

Yeah, and each time someone posts in this very thread here, it's going to look more prominent. But well, it was just an observation, nothing more, nothing less. Everybody I asked to really check the tap tempo thing had to admit it wasn't working correctly. Well, of course, you didn't - but apparently you also didn't feel like having to check carefully.

Because people may miss 2.91 is the actual FW version (and it pretty much seems like). Well, it seems to be a random thing. The tap tempo bug wasn't.

In settings > audio > general, is "Software Monitoring" checked? In that case, when you record enable a track in Logic, (R of the channel appears in solid red), the channel fader needs to be dragged down because otherwise you'll also listen through software monitoring - shouldn't exactly sound better, though, but then, it might as well result in a thickening doubler effect. Otherwise, I'm using Logic as well, Helix as an interface, no issues that would be similar to what you describe.

Did you update to 2.91 already? (and fwiw, this thread should be closed...)

Build your own presets so you are the one to decide when they sound good. Every bit as you'd do with an analog setup. Then proceed from there.

I can confirm the huge output meter delay (and lack of any metering for the compressors) on path 2 once the Helix is switched on for a while. Rebooting so far seems to to fix it, haven't measured when the symptoms start showing up.

Could perhaps be the server being slow-ish. Maybe Line 6 should provide an easy way for an offline update. Download the file, open it via HX Edits updater functionality and go ahead.

I'm actually quite used to just tapping twice, mainly because most devices don't calculate average values (ok, the Boss things I used for a long time do) but also because I hate it in a live context. I actually don't exactly know why because I'm tapping quarters almost all the time, but it seems to be really distracting in case you have to hit a switch as well.

Ah, ok, thanks again. So it might make sense to stop tapping at all and restart when the first taps were off.

Hey, many thanks for your experiment, silverhead! Know what? As we discussed this in the bug thread yesterday, I wanted to do some more elaborated tests just today, as the 2.9 issues seem to be fixed (in fact, they are). I was even planning to start a new thread with the results - but to my amazement, you've beat me at it, so cheers! And it's pretty interesting that you can actually perform so many taps - that should result in pretty good averaged values for live playing (in case you find a spot to tap so often, rather looking like a stork or so). Now, the only relevant question remaining might be: In case you did some badly timed taps at first and don't want to bother with 10 more, how long does it take the tap tempo function to forget these first taps in case you don't touch the switch at all anymore? Yeah, pretty much a rather academic question, but in case of very slow tempos, it might be quicker to stop tapping (in case you were off) and start out fresh instead of proceeding with 10 more taps.

This isn't true, they're indexed by waveform. You can check that for yourself (or ask through your Line 6 channels). Load and select an IR, save patch, remove IR, rename original IR, reload it, reload the patch -> the patch will now load the renamed IR. I think it'd be better if both waveform and name were checked (I have several IRs for testing purposes that I only rename to something more meaningful once I decide that they're keepers). And as far as exporting and reimporting patches requiring IRs goes, there's still plenty of room for improvement as you still have to keep track of things manually. For instance, the error message that is now showing up could as well tell you which IR is required and ask you to locate it on your computer (offering a search function in addition), just the way software samplers do it. A raw error message isn't of much help.

I would defenitely open a support ticket - IMO this looks as if it is related to your unit (as it already happened with 2.82) rather than the firmware.