pilottes

I upgraded the editor to 1.12 last weekend in the hope this bug would be fixed but no luck. During the last FW upgrade from 1.06.05 to 1.10 I noticed afterward that my patched were getting changed. I did a global reset and all but no use. So now I'm stuck with an environment I can't properly backup or I can try FW 1.12 in the hope of fixing this but live with the Tempo bug. It's simple to check If someone could create a pacth where one footswitch is assigned to two blocks. On active, the other inactive. You save it with the light ring OFF. You export and reimport and the footswitch's ring is now turned ON by default. You have to cycle through the different blocks by touching the footswitches (as usual) to stop on an unactivated block and resaving in this state to get the ring light OFF by default. Sounds easy, yes it is. But multiply by X time for a X footswithes and Y times for Y patches you reimport and it makes an upgrade to the next FW a real pain in the neck.

It sounds beter for single note than for chords.

Any sighting of flying unicorns?

I happened to see Gilmore's double effect rack !! OMG 8-[

I have to say up front that I have no idea how many ressources are involved in a project like Helix. How many people, how issues are escalated, etc. I do get the impression that it is with great pain and difficulty that decisions are made and that it all take a lot of time. It's a bit unfortunate but it looks like its the way thing work when everything is scaled X times. We can only hope the right decisions are made not the get a better product but to get the best product. As for the number of assignments to a footswitch you could have left that decision to the user. In a sense, thuser that find 3 assignments and more will limit himself to 3 and less. Every body would find its own magic number. Deciding 8 is kind of arbitrary.

I don't want to get into a long debate about Ideascale but Ideascale is sort of not the perfect forum for some items. Number 8 was a UX decision and corrective actions should remain in your hands and not depends on votes. Ideascale would be more for additional models and such don't you think? You would skip over a some great ideas because it doesn't show up on Ideascale?

Had my Helix for 3 months now. Still loving it. I brushed quite a few time with the limit of 8 assignments to a footswitch. Just a quick example. Defined a SOLO footswitch Raise the Level, Mid and high on an EQ, Change the Gain and Ch level on the AMP. Change the Reverb parameters, activated a ducked delay, deactivat a base delay. What about wanting to change Comp and added Distortion pedal.... You get quickly to and above the limit. If this limit is hardcode ADIOS thwe scene thing. Why a limit? I would double it to 16 at least. Not a complain, an observation.

I've tried different approach and the only one that works for me is by simply using the pickup selector on the guitar period. If I try to involve a foot in addition to the pickup switch I screw up half of the time. I use a stereo cable, say piezo on guitar input and mag connected to return 3. I keep Path A and path B separated. You have to change leftmost input on path B to Return 3. This way you can have acoustic on path A with th Taylor IR mentionned above and the Studio pre-amp and path B for mag pickup works. For my acoustic/electric patch I used 2 amps on the path B so I can cover clean fender or distorted amps. I created the patch for Jethro Tull's Aqualung. Works for me. So many possibilities.

Hum... doesn't sound like a priority at all... may be I overinterpret ...

The trails! Absolutely right! It explains everything. Thanks!

I noticed that some noise from my tube amp was making it back to Helix (4CM hookup) even if the FX Loop block was disabled. To fix this I had to assign the return level parameter to flip between 0db and -60db, So beware if you have noisy devices in loops....

Of course. This is an evidence. We should'nt have to vote for that type of addition. L6 should pick and choose the clever ideas after evaluating effort to implement vs payback. Ideascale should be mostly reseved for additionnal models, amps, effects. Period. L6 should prioritize great ideas when they see it even if it comes for only one person. I'm a bit dissillusion about the whole expectation business from FW update but hey it's also Monday morning.

Looking back in the early days of HELIX they did come out with a new FW update, 2 or 3 times, with as little as 1 week before a FW bug fix release. You can check the history of releases.

Thanks D_I your input is apprieciated.

If we just stick to facts and what we all heard in the last few months. From knowledgeable sources it was mentionned that after years of work they had to make the call and put it out there. By itself it explains the rought edges and the few features we are missing. Think about the lad who needs to sync MIDI BPM or the complex effect control with on/off thresholds and all. Not insignificant functionnality. They do market it as the central peice of gear to control your rig, right. As far as I know it's not deep enough to control my JVM the way I would like, but we all have different gears... Once the most importants missing tricks are implemented for the majority of people "that you are targeting" it would be alright to call it a day and start working for a few years on the next best thing called HELIX II.

Bummer! It's my first Line 6 product. I don't know about the customs but I'm more excited than a kid on Xmas Eve. I love the Helix. A decent FW update and I would remain forever in a silent bliss.

I know I shouldn't but I'm dying here!

I think its time to give some more functionalities, bugs fixes, MIDI features and the like. Lets turn the page on the editor for a while and get some improvement on a key issues. Scenes, latency, etc. which will go a long way into briinging more fans.... Than the icing would be eventualy to add more amps and rare effects, But, thats me.

Don't have an answer unfortunatly. There's quite a few parameters that I don't know what it's supposed to do. A few blocks have the Headroom parameter...? That's why we need a better description in the manual. Hopefully they will update it for the next major FW since we seem to be stuck in the past with rev B documentation

I think the TS210 should be perfect for what I want to do. I got to try a Berhinger PA with 15" last night couldn't get rid of the bass. So, smaller the better AND it will fit easily in a small car. Great one more item to add on the TO BUY list.

Interesting. I was seriously considering the EV ZLX12P because of the price and the long history in audio. I 've been battling boominess for ages and can't take it anymore that why I want to buy powered monitors. Since they don't have TS2 on the floor around here it would help if you could find out if he has the 10" or 12".. Thanks again

I looked them up and I noticed they now have a TS2 series now with a bit more power and migth replace the TS1 series since they don't seem to be more expansive.

That,s what I was afraid of. It's as good a reason as any to buy more stuff. Thanks D_I

Is it possible to toggle between one and the other by assigning a footwitch other the the Toe Switch. Let say I assign the amp gain parameter to vary smootly with the position of EXP 1. To switch from EXP 2 (volume) to EXP 1 I would have to press the expression pedal toe switch to toggle to EXP 1 but maxing out the volume in doing so. I want to move this ability to switch to a normal footswitch FS-1-5 or FS 7-11. ...

Sounds like you know what you're doing. The loadbox was the obvious goto device but 0.1 W is not much to warm your coffee mug. Good thinking!