littleeden

@soundog and @DunedinDragon Many thanks to both of you for your suggestions and help.  Everything seems to be working fine now, but I'll certainly check out the kit that you both suggested, as I think I need to move to a more stable solution.

The midi monitor was the obvious place to start really, and I'm feeling a bit daft that I didn't think of it myself, but it just goes to show that sometimes all you need is another person to look at the problem, and this is, of course, the great strength of these forums.  Cheers guys, hope you're getting back to gigging now.

7 hours ago, soundog said:

Have you used a MIDI monitor (snoize.com) to see what Logic is actually sending to your Helix? (Or you can connect an iPhone running a MIDI monitor in place of your Helix to see what is being sent.) This way you can be certain where the problem is arising. Helix may not be misbehaving, it may be doing what it is told. Test this first, and let us know....

As suggested, I have run a midi monitor (snoize), and confirmed that Logic is sending the same, correct pc's every time I start play back, regardless of the order of songs I select to play, but that the Helix is reacting to them differently if I don't follow the order that I've laid out my songs in Logic.  This seems very odd to me.

EDIT:

I went back to the midi monitor a second time and noticed that when I selected a new song out of order, Logic sent two midi commands very close together, the first instructing Helix to switch to the patch for the song before, and the second telling it to switch to the correct patch.  Presumably because of the proximity of these two, Helix was not seeing the second command.

I'm now in the process of ensuring that there is at least a beat or two separation between the beginning of a song and the occurrence of the midi command to select the patch for the that song.  So far, this seems to be working.  Thanks for your help - I wouldn't have seen this without the midi monitor.

4 hours ago, soundog said:

Have you used a MIDI monitor (snoize.com) to see what Logic is actually sending to your Helix? (Or you can connect an iPhone running a MIDI monitor in place of your Helix to see what is being sent.) This way you can be certain where the problem is arising. Helix may not be misbehaving, it may be doing what it is told. Test this first, and let us know....

Thanks Soundog - I'll give it a go and report back.

1 hour ago, DunedinDragon said:

I use a very similar stage automation system.  I currently use a Morningstar MC8 MIDI controller to manage things now, but originally i did it all through the Helix.  The big difference in my approach from yours is the selection of the preset and the starting of the song are two distinct and individually controlled MIDI operations that I control.  In fact, those are the ONLY things I actually control, Ableton takes care of all the other MIDI interactions in the course of playing the song.  I think because of this my setup runs perfectly regardless of which song/preset I choose.

As I remember when I used the Helix for those interactions I used the command center and used an instant command so that when I changed presets on the Helix it sent the MIDI command to Ableton about which track to use so they were sync'd up (preset and session track).  I then used a separate stomp button to send the appropriate CC command to Ableton to start playing.  One of the key reasons I switched to the MC8 is the Helix instant commands would sometimes get out of sync if I had more than one instant commands and wasn't careful about how I defined them and saved them.  Also it was very clumsy to have multiple MIDI commands defined behind a single button interaction.  Moving to an external, dedicated MIDI controller gave me a MUCH more robust, trouble free system with a greater range of MIDI options which was really necessary once I wanted to incorporate automation of other elements in the performance such as a BeatBuddy drums and stage lighting and so forth.

In my current system with the MC8 I still have two independent physical actions I physically execute for selecting the song, and starting the song.  When I select the song's bank on the MC8 it selects the appropriate preset on the Helix, and selects the appropriate BeatBuddy drum song, and so forth.  That allows me to visually see that everything is sync'd up.  When I then press the Start function on the MC8 it starts the playback of the appropriate Ableton track, and sends the start command also to the BeatBuddy as well as any other startup interactions in need to take at the beginning of a song.  From there, the Ableton track controls all other interactions throughout the song by sending a single MIDI command through the MC8 which may then incorporate several MIDI interactions in one button press.  So, for example, when the backing track reaches the point where the song goes into a bridge, Ableton has a single MIDI command it sends to the MC8 to fire off the Bridge preset which then might change the Helix preset, do a fill on the BeatBuddy and change the lighting controller.

I can't specifically tell you what might be occurring in your case other than to tell you that I had all sorts of anomalous behaviours that plagued me trying to use the Helix as my MIDI controller which were all easily solved by using a full featured MIDI controller rather than the limited and sometimes arcane methods used on the Helix.

Thanks Dragon - I should have mentioned that the way I have Logic set up is that my backing tracks for each song, together with the midi track, are contained in a folder.  To select a new song, I simply use the down arrow key on my Mac to scroll to the next folder (or I select the folder using the cursor).  I have the transport set to 'play selected region', so simply hitting the space bar starts playback.  Within a half a beat or so of the count-in playback starting, I have placed the relevant midi command to be sent to the Helix to select the patch and snapshot required for the start of the song.  

However, I think you may have hit on a better way for me to do this.  As I understand, you use an external controller to select the relevant patch on the Helix and at the same time to selectthe relevant song to play back on Ableton.  You then also use that controller to start playback, at which point Ableton starts controlling your Helix (and lights etc) via midi.  Have I got this right?

I use Logic to run backing tracks for solo performances, and have set up PC and CCs to select my Helix patches each time I start a new song, and to switch Helix snapshots in the course of the playback.  It works really well, and on a couple of songs, I've even got it changing the guitar sound, starting loop record, looping and stopping playback all at the same time.  All of which saves me a huge amount of tap-dancing and lets me focus on my performance, which, as a one-man band, is really helpful.

However, there is a serious problem.  It all works fine, time after time, if I play through my songs in the order I've set them up on Logic (which matches the order I've put my patches into in the appropriate set list on the Helix), but if I want to jump around and play the songs in a different order, Helix invariably selects the patch which is numerically before the patch for the song I choose.  

If I then select the song that matches that patch on Logic, the Helix will again select the previous patch.

If I then, further, select the next song on Logic (ie the one I originally wanted), Helix seems to catch up and select the correct patch.

I should add that the patch change message is only sent when I start playback for each new song, not when I select the song.

Now, I'm not a MIDI expert, but it seems to me logically (no pun intended) inconsistent that the Helix should behave this way.  Logic is demonstrably sending the correct PCs to the Helix when I step through the songs in order, so how can it possibly send a different message at any other time?  But then again, why should the Helix treat the PC differently if I jump between songs?

The upshot of all of this is that when I play gigs, I have to stick religiously to the order of songs I've set my Logic backing tracks to, which is not ideal.  Does anyone have any idea what might be going on and more importantly, how to rectify it?

On 4/21/2020 at 6:37 PM, PiFromBRC said:

Thanks guys!  I appreciate the hard work.  Pure kismet that I logged on aboot ten minutes after DI posted this.

 

 

(Insert standard 'what's coming in 3.0 and when' - joke here.)

Stay safe!

On 4/21/2020 at 6:39 PM, chasingMango said:

I had to resist the urge as well =D

:-)

Line6 got in ahead of you - see release notes:  

17 hours ago, danpisacreta said:

My update froze at "rebuilding preset 287". Cycling helix floor had no effect. HX edit (version 2.9) will no longer recognize helix. Tried booting into update mode with no success. Can anyone help with next steps?

I had the same issue (mine froze at 503).  I tried a rebuild preset boot (holding down fs 10 & 11 while switching the unit on) and that didn't work, but it might for you.  Eventually I turned the unit off and left it for a couple of minutes, then when I turned it back on it started rebuilding from 503 and completed.  HX Edit then recognised my unit and showed firmware 2.90.  Are you sure you're leaving the unit for a minute or two before switching back on again?  That's sometimes an issue with some devices.

Otherwise, try a launching in update mode by holding fs 6 & 12 while swiching on (see Helix/Rack/LT/FX/Stomp Reset Procedures and Troubleshooting Tricks in the Knowledge Base). 

SOLVED - 

I tried doing  a reset build reboot (holding FS 10+11), and again it got stuck at preset 503.  I switched off the power, and when I powered it back up, it just started the preset rebuild from preset 504 and completed successfully.  HX Edit recognises the unit and shows firmware 2.90, so hopefully all is now ok.

Hello all - as the title says, I followed the update instructions to the letter, got the firmware successfully updated, but now my LT is stuck at 'rebuilding preset 503'.  I haven't touched anything yet, but it's been about 20 minutes now.  What should I do?  Thanks

As the title says really - does anybody have any tips they've discovered for tweaking some of the model sounds with Workbench to get them closer (to their ears) to the originals, or to create interesting new sounds, like Richie Castellano did with his emulation of Brian May's Red Special?

17 hours ago, cruisinon2 said:

https://www.tremol-no.com/

Looks great - many thanks.

Hi all - does anybody have any recommendations on the best way to block out the trem on the Standard to prevent it from moving?  I never use trems and I want to get my tuning more stable.  Thanks.

On 1/12/2020 at 5:06 PM, codamedia said:

 

 

IMO... the biggest problem is making people understand the power of snapshots.... they are still an enigma to many.  

 

 

 

This, exactly.  I've found them to be an incredibly powerful tool, and I can't think of anything I've wanted to do that I haven't been able to, by using a snapshot.  Incidentally, I also have a patch where I switch from acoustic to hi gain using... you guessed it, and I don't understand why so many people seem to have such a hard time grasping the concept, either.

I've been experimenting with creating a midi track in Logic to control the patch and snapshot changes on my Helix LT in time with my backing tracks, and I've got a question that I can't seem to find the answer to in any documentation.

When I create a programme change event in Logic to select a patch on the Helix, the patch only selects momentarily before switching back to patch 1B.  I've found a workaround that make the selected patch stick - I have to also create controller change event to select a snapshot (cc69 0-7) - but I don't believe that should be necessary. 

My question is, what have I missed (or is this actually normal behaviour)?

Many thanks in advance.

Swapped out for new without question by Professional Music Technology in Old Street, here in London.  Can’t fault the service from them or Line 6, thanks.  

Edit:  And if anyone's interested, the new one performed faultlessly at last night's gig.  So if anyone gets the same problem, my advice is don't mess about - take it straight back to your dealer.

Ah you’re gonna have fun.  Welcome to the rabbit hole!

12 hours ago, PiFromBRC said:

 

Okay, you precious, delicate, little flower.  I apologize for *suggesting*, and I quote, " it is at least possible that one person is posting from..." .  Does that apology match your desires?  I could get you a warm bagel if that would help.  Pick warmer is up to L6 though.

Yes that’s fine, thank you very much.  I prefer my picks cold, though.

On 2/24/2019 at 8:41 PM, PiFromBRC said:

 

Could be.  I'm still holding out for the heated pick holder.

Yeah, well, I'm still holding out for an apology for your baseless accusation.  Guess we're both gonna be disappointed.  Boo hoo.

Well, according to the response to my ticket (very quick, thanks), it’s a hardware problem that needs a tech to look at it, and I should take it back to where I bought it.  So that’s what I’ll do.

On 2/23/2015 at 7:26 PM, boydtee said:

Thanks for the advice. I'll try it tonight and see if this works.

Did it?

I just posted about the same problem here: 

If I get any joy from the support ticket I opened, I'll post it here as well.

I just bought a G30 and have gigged it twice.  On the first occasion, there were a couple of dropouts, but last night it got really flaky.  Not only did I have multiple dropouts, but on three or four occasions, it stopped working altogether, and I had to switch the transmitter off and back on to get it working again - not what you want to be doing mid-song!  I'd checked the battery status indicators on both the transmitter and the receiver, and both were showing green.

On examining it this morning, I was able to replicate this behaviour by pressing on the battery compartment door.  I tried this because I remember that before at leas two of the crashes, I'd either knocked the unit (backing into a mic stand), or squeezed it (taking it off my strap when changing guitars).  When I did that, I saw that the battery light on the transmitter started plashing purple, and at the same time, the audio light was flashing yellow.  While this was happening, the signal status LEDs on the receiver showed nothing, and the battery status LEDs showed one or two red.

Notwithstanding the battery status indicators I mentioned in my first paragraph, I swapped in a new set of batteries, and was unable to replicate the fault.  Putting the old batteries back in let me get the fault again.  From this, I deduce that:

1. the battery  status lights on both on the transmitter and the receiver do not give a reliable indication
2. when the batteries start getting a little low, somehow the battery door on the transmitter becomes very sensitive to small bumps and pressure, causing the unit to crash

I realise now, of course, I should have swapped in a brand-new set batteries before each gig, but I didn't expect the battery indicators to be so inaccurate, or for the unit to be so sensitive when battery power got a little low.

Does anyone else have any thoughts about this?

Edit: have opened a support ticket, so we'll see what they say.

On 2/22/2019 at 7:15 PM, PiFromBRC said:

Okay...color me conspiratory, but first this guy (who has a registered product) said:

 

 

and then this guy (with no registered products) said:
 

 

which suggests that it is at least possible that one person is posting from two profiles. 

If you're suggesting that I'm that person, then you are wrong - have a look at my profile, and you'll see that I am a registered Helix LT owner.  Please DO NOT make assertions about me that you cannot back up.

You might have wanted to check some of my other posts on this forum as well, then you'd have seen this:

https://line6.com/support/topic/37347-pedalboard-for-helix-floor/?tab=comments#comment-273156

2 hours ago, cruisinon2 said:

Welcome to today's episode of "First World Minor Gripes That Will Be Forgotten By Lunch"...;)

I believe you’ll find that’s true, not only of every discussion on this, or any other music forum, but also probably of every issue associated with the entire western music industry.

I’ll tell you why.  On embarrassingly more than one occasion at gigs, whilst attempting to switch on or off the stomp box I’ve assigned to foot switch 8 (I think), I’ve missed and changed patch.  Too easy to do in the heat of battle.