Helix Talk

[SwirlyMaple]

In pre-3.60 versions, the attack time on the Deluxe Comp was being limited at the low end of the control, so the time displayed did not match the actual attack time for VERY fast attack settings. We addressed this in 3.60 so the time displayed always matched the actual attack time. As some of you pointed out, this could result in distortion in situations where you had the attack time set below this artificial limit. For 3.70, we took some time to reassess this and find a happy-medium at these extremely fast settings to reduce the distortion while still allowing much faster attack than pre-3.60 versions.

Thanks for the info and welcome to TGF! Always great to see Line 6 peeps here.

 

[pipelineaudio]

When you say “everyone denied” did you mean “the one that dk_ace and a few others immediately confirmed?” You weren’t exactly alone on that one it impacted everyone that used very short attack times…

D

It definitely wasn't "immediately" first we had to run the week or so of denial gauntlet, RTFM, Google is your friend, "learn what a compressor does" etc

 

[SwirlyMaple]

It definitely wasn't "immediately" first we had to run the week or so of denial gauntlet, RTFM, Google is your friend, "learn what a compressor does" etc

Well, here's the thread... people can draw their own conclusions I suppose!

Helix 3.60 update, Deluxe Comp distortion?

I am getting pretty major distortion coming from the Deluxe Comp after the 3.6 update. I havent gone back to earlier on my floor, but switching native between 3.5 and 3.6 the issue shows up on 3.6 and goes away on 3.5. Anyone know if its the comp itself or maybe there's something else changed...

thegearforum.com

 

[pipelineaudio]

Well, here's the thread... people can draw their own conclusions I suppose!

Helix 3.60 update, Deluxe Comp distortion?

I am getting pretty major distortion coming from the Deluxe Comp after the 3.6 update. I havent gone back to earlier on my floor, but switching native between 3.5 and 3.6 the issue shows up on 3.6 and goes away on 3.5. Anyone know if its the comp itself or maybe there's something else changed...

thegearforum.com

People were actually pretty cool here. The thread on TGF was compounded by whatever else weird bugs my particular helix kept getting where it was corrupting presets. The TGP thread was nothing like this at all.

I’m crossing my fingers that whatever damn possession was corrupting my floor presets is gone for 3.7 and so far so good but that’s a whole nother can of worms.

 

[SwirlyMaple]

People were actually pretty cool here. The thread on TGF was compounded by whatever else weird bugs my particular helix kept getting where it was corrupting presets. The TGP thread was nothing like this at all.

I’m crossing my fingers that whatever damn possession was corrupting my floor presets is gone for 3.7 and so far so good but that’s a whole nother can of worms.

Did you ever figure out what the deal was with your Helix, or swap it for another? I tested the heck out of those preset corruptions you were seeing and could never replicate it. Almost seemed like a memory issue or something on your hardware. Genuinely curious.

 

[pipelineaudio]

Did you ever figure out what the deal was with your Helix, or swap it for another? I tested the heck out of those preset corruptions you were seeing and could never replicate it. Almost seemed like a memory issue or something on your hardware. Genuinely curious.

I was able to borrow an LT but any time I transferred the files out, it was just like when pasting the presets here or in helix native, the corruption was already there and I couldn’t get the LT to corrupt the files itself. When I saved, the illegal values were still there if you looked at it in a text editor. I think you may have been the one who originally saw the invalid characters in some of the preset values

So far so good on 3.7

 

[SwirlyMaple]

I was able to borrow an LT but any time I transferred the files out, it was just like when pasting the presets here or in helix native, the corruption was already there and I couldn’t get the LT to corrupt the files itself. When I saved, the illegal values were still there if you looked at it in a text editor. I think you may have been the one who originally saw the invalid characters in some of the preset values

So far so good on 3.7

Weird! Well, I'm glad to hear it seems to be working now. Hopefully whatever it was is gone for good!

 

[James Freeman]

 

[James Freeman]

NDSP +120dB at 100Hz, very real.

That's a LOT of talk, just skip to the parts he's playing.

 

[James Freeman]

Gotta say though, Silverface Bassman in the Bass category is one of the worst decisions Line 6 has ever made.

 

[zib]

Gotta say though, Silverface Bassman in the Bass category is one of the worst decisions Line 6 has ever made.

@James Freeman what do you prefer ? "Yes but...no" or "why not ?"
Just a joke, do not feed the troll.

 

[Lysander]

Now, that's a statement.

Gotta say though, Silverface Bassman in the Bass category is one of the worst decisions Line 6 has ever made.

Yeah. Don't know if "worst decision" applies but... is anyone actually using Bassmans to play bass these days?

 

[kartikg3]

Gotta say though, Silverface Bassman in the Bass category is one of the worst decisions Line 6 has ever made.

Yeah. Don't know if "worst decision" applies but... is anyone actually using Bassmans to play bass these days?

Maybe it's Line 6's way of nudging guitarists to try the bass amp models for the guitar, because some of these have magic controls?

 

[dronerstone]

It would be awesome to have an app for Android (or iOS), solely to build presets.

- doesn't need to process audio
- compatibility modes like in Native
- factor in the 'favorites' feature
- export/import capabilities

Shouldn't be too difficult to pull off, I guess.

Drool over presets on your way home from work.

Every time I think about this, I'm fairly certain geeks like us would love it.

 

[ragingplatypi]

Maybe it's Line 6's way of nudging guitarists to try the bass amp models for the guitar, because some of these have magic controls?

That was my thinking. An easy, and interesting, fix would be to just have the same model available in both the guitar and bass sections.

 

[Humberd]

So I downloaded the 3.7 update and it said successfully complete
But it seems all the stock presets that I've tried are very fizzy and harsh sounding?
Any help would be appreciated. Don

 

[Sleezy E]

So I downloaded the 3.7 update and it said successfully complete
But it seems all the stock presets that I've tried are very fizzy and harsh sounding?
Any help would be appreciated. Don

Did you do a reset per the instructions?

 

[Humberd]

I'm pretty sure I was following the instructions, can I start over and reinstall 3.7 ? I had 3.6 on there to start with

 

[Mooselake]

I'm pretty sure I was following the instructions, can I start over and reinstall 3.7 ? I had 3.6 on there to start with

I think if you:

-Do a full backup the way you have it now
-Do a factory reset
-Save off the two factory setlists
-Reload you new backup
-Reload the two factory setlists you saved off on top of factory 1 and 2 respectively

You'll get to where you want to be. That's more or less how I do it after an update. There may be a more efficient way.

 

[Foxmeister]

There may be a more efficient way.

There is!

When you restore your backup, you simply deselect the factory set lists.