talwilkins

Yeah, I really can't understand the personal attacks either. There's no call for such a thing just because you don't agree. And it doesn't answer any questions you are raising. It's really sad the world is more and more like this. People just don't repsect ech other's point of view and thinik the solution is to bash the person in stead of trying to enlighten them, preferably keeping the option open that their own point of view may need an update. So we learn.

Actually I think the first reason you should be there is for the music and yes, of course the audiance needs a great experience. That means, IMHO, first of all the musicians need orgasmic sound and emmersive experience so they can perform at their absolute best. Then the soundguy needs to make it the best experience possible for the audience. So in the end both the musicians and the audience need to get the best sound possible.

Cool!

Sure, benefit of the doubt is always a good thing. Innocent until proven guilty, right? The age and accompanying ignorance would be the only acceptable excuse though (IMHO) . :D

It's not about being a dumb move, it's pathetic. What's to gain?

Actually the Helix App has the manual under the help menu, right where it's suppost to be in Windows software

What's the giant bug sitting on your expression pedal? :unsure:

I think you should look at it like FLAC and WAV, it's lossless compression. Interestingly IR's are in WAV format so for all we know Line6 actually used FLAC compression :P (probably not)

I thought about that but I haven't been doing anything different. In fact I haven't really been doing anything with the cabs except for High and Low Cut. It's on my to do list to check out the possibilities there but haven't done it yet.

Thanks for all your tips! It hasn't really given an answer but it seems I'm the only one experiencing this issue (if you can call an improvement an issue). I will definitely do some more experimentation with input impedance somewhere in the future! Up to now I just set it to 1M because it seemed to sound the best and haven't looked back. Time to look back!

No, I'm using a regular guitar. I do have a Variax but havn't tried it with 2.01 yet.

No, it's not the impedance, I changed that back to 1M. Also the Imepdance doesn't change the sound that dramatically to my ear. I used to do a high cut to around 5Khz on all cabs, otherwise the tone would be kind of terrible. Now they sound fine without the high cut. I don't really understand.

O.k. Let's then just agree to disagree! I do see your point of view now and agree to a point. It's all academic anyway, we absolutely agree it's not the way it should be now and wether it should be considered a bug or not clearly is more an opinion than hard science. For the record, I have been working in sofware developement and other IT area's as well. It was fun having the discussion though, I like to have a respectfull discussion and winning the argument is not my goal. Learning is! B)

No it didn't. At least not in practical use. "Before" snapshots...If I had a preset with a crunch and a lead amp sound set up on one preset using footswitch control and the wah pedal acted EXACTLY like I expected it too. Like a "real" wah pedal would. I could push the toe switch and have wah whenever I wanted it. Switch back and forth between amps and the wah was still on unless I turned it off (within a single preset). And if I switched presets the wah would be "off" when I came back to the previous preset. It still does exactly that! as long as you do it the same way. You can't say it behaves differently than before when you're actually doing something you couldn't even do before. It's like saying: The accelerator doesn't act the same as before after installing an auto pilot. Before the installment the speed would go all the way down when i took my foot off the pedal. Now, when the auto pilot is engaged the speed will stay constant at the set point. It's a bug! Now...with the ultra-cool snapshots (I LOVE them by the way)....I have 8 different sounds set up using 3 different amps all on one preset. And if I use the wah on a lead it does NOT stay on until I turn it off when switching from one snapshot to another. It acts completely different than it did before. Yes, you have the auto pilot engaged! if you want it to act exactly as before don't use the snapshots (auto pilot). At least, that's how it is right now. That doesn't mean in this case it couldn't be made possible to behave the way you want it to while using snapshots. I would certainly like that option. That's kind of the point that all of us are making about it. It doesn't "act" like any wah pedal on Earth lol Well that could be because there are no other Wah pedals on earth that are actually digital replica's placed in the Helix's current snapshot system. The Helixes Wah pedals behave exactly like the should in the current snapshot system. We just want the option to make the snapshot system to behave differently in order for us to use the Wah's the way we like to while using snapshots. You see, they don't need to change anything to the wah's so saying they don't behave as expected is not correct. I't like saying: Hey, my mouse is not working as it used to after changing the settings to left handed. Now the left mouse button produced a context menu. It's a bug, we need to change the way the mouse behaves. No, you need to change the setting to right handed if you want it to behave the way you're used to. This is why I am simply not going to be using the wah until LIne 6 has a chance to address that problem. I never use a volume pedal (I enjoy creating different tones with the volume control of the guitar itself)...so for now my expression pedal is useless for me. But I do want to say: The snapshots are GREAT! Made the Helix so much more useable. The wah will get fixed and then all will be great! Yes, I believe the issue will be addressed (sure hope so anyways). In the meantime do yourself a favor and use the cheesy workaround, then the expression pedal does exactly what you want. Sorry again for my anal behavior :huh:

You do have a point here from the analogy point of view. However in the case of the Helix, it's a software development not hardware like adding the remote afterwards. From the point of view of a new user I see you're point that it would be perceived as a bug but from a development point of view I still think it's not a bug but a not completely developed system. It doesn't need a bug to be fixed but a new function needs to be added in order to make it possible that the Helix behaves as many people expect it to. Mind you what most people expect is not by definition correct or best.

Is is just me or has the sound of the cabs been improved in 2.0(1)? In my experience I really needed to use the High Cut on the cabs before 2.0(1) and set them to between 4Khz and 6Khz. Now if I choose a new cab (or so with cab) it sounds just fine. It actually seems there's not much happening to the sound if I do a high cut on them. Anyone else having the same experience?

Why not an ABS case? I have a Gator case and it's really good. I wouldn't worry if it fell out of a truck (standing still of course).

You're presets would be highly appreciated!

You are truly an exceptional player!

Youre analogy is off imho because you are starting from a situation where everything is built together from the start. In your scenario it would cetainly be a bug because there is no reason for the problem to exist there, with one remote and all the functionality there from the start. The functionality hasn't changed so why would it not work the way you expect it to? In Helix this not the case. functionality has changed. Using the remote analogy, the Helix got another remote added and now has two remote systems. one the standard stomp switches that toggle one ore more blocks on and off. And another that recalls a snapshot bypass state of several blocks and parameters. And you can use them mixed together. As far as I'm concerned there is just some functionality missing like also saving the EXP1/EXP2 state of the pedal with a snapshot. Still not a bug. Do you also feel the fact that having one switch controlling more than one block can mess up with snapshots is also a bug?

The fact that people people were surprised about the behaviour coils also mean thay don't fully grasp haw the Helix functions. I, for one was not surprised by the behavoiour although I was a bit surprised Line6 hadn't caught it and provided a solution yet. But hey, thats the way these things often work. they are human, so no biggy. Yes, people telling you to do a 9+10 reset didn't get the issue, I agree there. Analogy (attempt anyway): You buy a TV set. It has a volume button. Works just as you expect. Next you get your tv signal throuh internet with a special receiver, that has it's own remote with volume button. One nite befor you turn off the tv you turn the volume all the way down on your internet receiver. The next day you turn the tv on and find the volume is all the way down but you forgot that it's muted on the internet receiver and try to get the volume up with the TV remote. Doesn't work!! Is this a bug? or is it the expected behaviour? Would it be great if the system worked differently so it wouldn't matter which remote you use? Yes, but it's not a bug imho. With Helix in the current configuration, you need to turn off the Wah before switching to another snapshot (if you don't have an external pedal connected to EXP2 or my goofy solution). That's the way the sysem works now. Is that ideal? Far from it, but it's not a bug. In fact I'm sure the configuration also makes some things possible that some people would miss if they treated it as a bug and took this behaviour out. That's why I think the answer is in giving us options to change the configuration so it works the way we want it to now bur also leave the possibility to leave just as is for other scenario's.

Actually when I encountered the issue I though: "Damn that's irritating but yeah, that was to be expected. I hope they found a way to deal with this" The I went to the forum to start a thread on it but found that someone beat me to it and the goofy workaround was suggested by someone. Then I thought: "Great, a workaround for the time being Until Line6 six comes up with an elegant solution" So yeah I think I understood the issue but didn't find it unexpected (damn, I'm being anal again :rolleyes: Sorry)

That would indeed be true if the behaviour was unexpected. Here this is not the case. The Helix behaved in this exact way before snapshots. They introduced snapshots and in combination with this new feature the existing behaviour can be undesirable to some (maybe most). This behaviour was not unexpected. It's like the fact that you can get into trouble with your snapshots if you have more blocks assigned to one switch. Line6 caught that one and put a warning in the release notes. or was it the manual, I don't remember. It's a result of things getting more complicated when certain features are added. Is it a problem that needs to be fixed? YES ​​Sorry for ranting on about such an unimportant issue: "Should it be called a bug or not?". I'm a bit anal when it comes to this kind of thing :unsure:

Not a bug. It's a problem that surfaced when adding new features (snapshots) on top of the old. A worst it's something in the workflow that needs to be ironed out. There is no faulty programming involved. it's a design problem not a bug.

I don't see Phil_m really defending the situation or making it out to be difficult to fix. All he's saying is that it's not a bug, which it really isn't. There's no code going haywire or doing unexpected things. What this is though is missing functionality which does make the snapshot's a little problematic to use with Wah. I wouldn't call a car without GPS being a bug, right? I'm sure Line6 will resolve this. Either make my workaround an option in the software (it really is goofy but it works). Or save the state of the pedal (EXP1 or EXP2) in the snapshot. That way it will switch back to the desired state whe going to another snapshot.