PeterHamm

I saw something similar to this in a beta build of an older firmware. It might be a corrupt preset. First. Try saving to another slot and then back. You MIGHT have to delete the EQ block and put it back in, but try that first.

Sorry, still not a huge fan. I know that some broadcast folks use them, but there's a reason you never see them on the shelf in a Music store. I think they probably have a harshness inherent in them. I do find that my open back DT990s (Beyer) sound fantastic with Helix, and any closed back headphones are only good for when I have to have no bleed because I'm tracking vocals.

No offense, but "Koss" may be your problem. Not surprised they might sound harsh. The headphone amp in Helix might be a little much for them.

Did you try a different browser, or clearing your cache? Since this isn't a widely reported issue, it might be something going on there.

This is a global issue, but the global setting you need to change is not in globals, instead it is the first dial when you page to the Variax input block. Can't remember the name of it. but you change that and you are golden across all your patches.

POD Go has something called "Kinky Boost" which is an EP Booster.

It still seems, to me, like this new Boss processor will be really awesome for a lot of guitar players.

well, there is another reason this wouldn't work. It would be WAY too easy to hit the wrong pedal and mute your whole sound during a song. That would not fly during a live performance at all.

Variax doesn't have the kind of functionality required to make that happen. It only sends audio from the guitar to the Helix, even over VDI.

Except... it's functionally impossible because that footswitch is shared with the tap tempo function.

Actually, I just thought about it. Trails on an FX return is functionally impossible anyway. That's why it's not there. Think it through.

If there is a send somewhere that feeds that device, just turn on/off the send instead?

YES! ...not to mention the fact that the product is continuously improved and updated. If you got one in the early days, as I did, you are looking at MAJOR changes, and new features and models that (at least in my case) are enabling me to make music now I couldn't when it first came out. Honestly those folks who don't understand that humans are part of the cost of great stuff are just annoying though. They are the same people who think all software should be free so they justify pirating it.

NECRO THREAD ALERT!

Yeah, but you open the preset, go to the block, and select "default" and wham. I think actually automatically changing every single instance of Cosmos Delay in every single one of my presets, or something like that, would be 99% useless tbh.

I think it's coming in 3.0 "Favorites" or some such. Also, I think at the basic level, you'll be able to set your own default settings for all blocks.

Check your sample rate settings in your DAW as well as in your Helix Floor Global settings. Make sure they match.

I find the tap tempo light to work fine, always have.

well, the gulf between usability on the two platforms is far from what it was just a decade or so ago, but yeah. I still find Windows 10 so annoying to configure and use that my "test" laptop I have here never gets turned on.

I am more than a regular on all the forums. I see WAY more issues with Windows computers and HX products than Mac. I don't know that there is actually that many issues with Catalina, tbh. I certainly had no issues with it with either Native 1.8 or 1.9, through all the betas as well.

Suggestion: stop trying to figure out the tap tempo thing, guys. It's a known issue, and they are literally fixing it as I type this.

I did in 2.82, but I have not in 2.90, and I have specifically designed presets that change the tone control from snapshot to snapshot.

You probably want to post this in the bug reports discussion, tho.

I would definitely try re-loading first.

check globals. Also, turn the unit off and back on again 2 or 3 times (let it fully boot up). I've heard stuff like this happening only on the first few boots. Again... did not see this in my testing, sorry.