codamedia

Backup any custom presets you made.... Try a complete RESET of the Stomp and see what happens....

Buy how are you currently connecting to them to hear your music. Are they connected to the computer? To an audio interface? Or do you just plug an ipod directly into them?

3.0 is not released, and nobody hear will know all these answers. Well... there might be a beta tester or two here, but they are probably under NDA's (non disclosure agreements) and can't discuss specifics on the forum. If you are making suggestion to Line 6.... the forums are the wrong place for that. Feature requests should be submitted to their Ideascale page. line6.ideascale.com

Those sounds are not far removed from a JCM 800. Try the amps noted above, but also try the 2204 & 2204 Mod. For the lead sound... add a wah.. and push the gain just a little more. Surprisingly, those tones don't have as much gain as you might think they do, but they are really refined... and that starts with mic choice/position & post production. ^^^ this ^^^ Flokianni.... if you are not aware of how mics and positions effect the tone, be prepared for a learning curve. It's a critical part of what you are hearing. After the cabinet try adding the LA Studio Comp & some ambient reverb (not too much) to smooth out the edges (eg: refine the tone). If you use dual cabinet, make sure you insert the "stereo" models for these.

On older BOSS multi effects (circa the SE-70), the "natural overdrive" is said to be a drive that "simulates the tone of an over driven tube amp" which is actually pretty vague. Later variations (ME Series) suggest it is just a simulation of the SD-1 overdrive (that's not an effect I would call linear)... and now BOSS uses that term to describe the OD-3 overdrive. There we have it.... three different variations of the BOSS term "Natural Overdrive". Long story short, we need to know which unit you owned to know what you are referring to :)

So the million dollar question is... "what did you tweak when it occurred"? (it may be a single event, it may be a series of events) You may not know (or remember) right now, but take note of it when it happens again. Then do a restore to normal, and try to repeat that same problem!

Why does the Linux machine get an NI interface while having its latency compared to a Windows machine with a "built in" interface? FYI.... I don't have any issues with latency on my aging Windows 10 i5 machine.... but of course, I do not use a budget "built in" interface.

How are you normally using these "studio" monitors for everything else? Most people run their studio monitors from a mixer or interface... and would just plug the helix into one of those rather than directly to the speakers.

What exactly does the global settings say the volume control is assigned to? Which outputs are you connected to? Note: If it's headphones, there are even more global settings to check to make sure the volume will work with it.

I'm the one that suggested the "tilt" as a way to "simulate" moving a mic from the center to the edge of a speaker. I just insert the block and dial back the "tilt" setting.... I don't touch the default frequency which I believe is set to 1k. I'm not saying you shouldn't change it, I'm just saying I've had no need to change it :)

Is this the chart @phil_m? based on that... I am going to edit my suggestion above.... it seems to operate differently than I was expecting...

Try turning off the touch sensitive switches... Global Settings > Footswitches > Touch Select > Set that to OFF Now check to see if the problem still exists..... FWIW... I always turn off the touch feature unless I am programming and require them.

Important distinction.... it doesn't actually add brightness, it just isn't removing it the way a cable does :) EDITED: I have changed my suggestion based on the Cable Tone Chart that is mentioned later in this thread.... Try this.... Insert the "low and high cut" EQ in the first slot. Leave the low at 0 Set the frequency of the "High Cut" to match the desired length based on the chart shown a couple posts down. (EG: To simulate a 20' cable, set the high cut to approximately 6K) There is also a High Cut included in the parametric EQ.... but IMO that would be overkill for this job.

This has been my experience as well... and I am only 2 years in :)

Just to be clear, I am in full agreement with your posts, suggestions and opinions. You are providing a wealth of knowledge for those that might not be aware of what needs to be done, GREAT JOB! While your opening post is providing a "book of information", I was merely trying to expand on "one chapter", and how someone might work around it with the stock Helix cabinets. By getting that "cab/mic/position (tilt)" right, a lot of corrective EQ and filters can be minimized later. Note I say minimized, not necessarily eliminated :)

IMO... it's totally different, more subtle and natural sounding.... just like moving a microphone position. Your not removing frequencies as much as repositioning them... if that makes sense. In theory... it rolls off highs while increasing lows (when shifting the tilt toward the dark settings) .... this is very similar to what a mic picks up when moving it from the center of a speaker to the edge. You can adjust where the tilt frequency is... but to be honest, I just leave everything set to the default and roll the tilt toward the dark for this application. All I can really suggest is "try it"! Simply insert the tilt after the cabinet, and roll back the tilt settings to see how it responds. It's been a game changer for me... and has allowed me to start using the cabs instead of IR's, but that's just my opinion.

In fairness to the OP.... he wasn't insisting that Line 6 do this.... he asked if anyone in the community has gotten it to work, which is actually how the Linux community generally rolls.

IMO.... this is the biggest "high cut filter" sound engineers use when micing a guitar cabinet.... live or in the studio. First they make a microphone choice.... but it can even be as simple as the venerable SM-57, just one - about 1" off the speaker Next it's where they place that mic on the cone! The CENTER is bright, the EDGE is dark, and every 1/2" of movement from CENTER to EDGE acts as a high cut filter! Good engineers will not reach for a hi cut filter or an EQ until they have the mic placement the way they want it.... and most often, no further cuts are required once they get that right. Enter the problem with the helix cabs.... they don't allow this critical movement of the mic placement. You can move it back a few inches, but you can't move it over a few inches. They all appear to be mic'ed at the center only. This would explain why people complain of fizz, and feel the need to over compensate with hi cut filters. It is the brightest position. The introduction of the simple TILT EQ in 2.8 has provided a simple and elegant solution for this. Insert it after the cab, and adjust the TILT downward (toward dark) to simulate moving the mic toward the edge of the speaker. IMO, each "-10" is about the same as 1/10 movement toward the edge. FWIW, I set mine around "dark 50".... which is how I would mic a cab in real life... about half way between center and edge.

I can understand this... but I don't believe the Helix AUDIO drivers will cause you any grief. The only time I have seen problems like you describe are when unwanted peripheral drivers build up (disks, printers, scanners, camera's, etc... etc..), never an audio driver. Having an audio driver installed just allows you to "use it if you want to".... when you don't use it, it should stay out of your way. IME... the Helix audio driver stays out of the way!

The tuner is part of global settings... IMO it cannot hurt to take notes (or pictures) of all your global settings, then do a global setting reset. IME, this will reset... Everything under the global setting menu The global EQ settings/state The tuner settings The variax input settings (if you use a Variax)... Most variax settings are retained in each preset, but mixed in with those is one or two global settings that need to be changed... just once. Set all of those manually rather than importing an old set of globals.... it really doesn't take too long. (NOTE: It's always a good idea to backup your entire Helix prior to doing a global setting update, just in case you push the wrong footswtiches during startup. Yes, words of experience - LOL)

Here is something to keep in mind.... When Line 6 releases a Helix 2, it is going to be the new flagship.... not an LT replacement. Since you say "money is an issue", waiting is not likely to provide much satisfaction. What if that release you wait a couple years for ends up being a $3K Helix that has more power, a touch screen and includes profiling (Kemper) as well as modeling? Something like that would not push the price of the Floor or LT down one cent. I'm not trying to be a salesman here, I'm just suggesting that you might want to rethink your approach. Me, I'm going to enjoy my Helix LT each and every day until this happens....

Slightly off topic... but I just want to point out that I have been seeing the same sentence (replace DEBIAN with other distro names) for about 25 years.... yet nothing ever seems to change in market share :)

I agree with everything you are saying here.... newer machine, faster machine, more opportunity for more advanced programming that "at some point" will not run on the 1st generation of Helix devices. That is an inevitable update. Our opinions differ in that I don't expect there to be any dramatic hardware changes. Sure it might look a little different, get a larger screen.... touchscreen, but I don't expect anything earth shattering. You are worried about being left behind if you buy a Helix but you would be happy with a Pod Go if it has a VDI port? The Pod Go is a slick little product, but it's already a compromise compared to an existing Helix. Have you considered an LT? It has way more features than the POD Go, it has the VDI port, and it's about 2/3rd the cost of the Helix floor with the same horsepower and programming under the hood!

Slightly off topic, but where in the world do you live that TOURS are taking place? I've been doing a few gigs here and there, but certainly no tours! FWIW... I have no problems with my LT on tours.... it's not exactly a piece of plastic :)

I just loaded Helix Native along with the hardware compatibility mode for the Stomp.... it automatically loaded up the presets for the Stomp and sure enough, there was "Bloomin' Onion". I'm not sure what to say, but I don't hear any modulation in the high end that is pulling it off key. If I try a bend or any vibrato it gets ugly, but when I play the note cleanly there is nothing artificial that is taking it off pitch. If it is just the highest octave that is getting under your skin, that is the delay in the parallel path. You could just disable that delay, or turn down it's volume a little so it doesn't stand out so much. If anyone else wants to give it a try, I've attached the preset.... completely original (unaltered) FX_Bloomin'Onion.hlx