Dude! I’ve been struggling with this problem, even opened up the ticket with line 6 tech-support. Went back-and-forth with them for a few weeks and then I saw your video. You were way more helpful. Thank you. L6 said they might address it in the next firmware update
that would be awesome if they were able to address it from their end, but unfortunately, most other units behave similarly. Midi clock is a specific message. Luckily, this fix seems to be working really well after testing it and utilizing it over 100 gigs
@@kevinsingssongs your fix did the trick. Thanks again! I have a CME midi router/filter. Never thought to look for the stop command in the settings because only the Helix was affected. None of the other devices receiving the clock. You the man!!
@robhenning8537 I didn't know that unit would also provide this option. That's much cheaper than the midi hub unit I think it is safe to finally put this issue to rest 🙌 best of luck with your build out
Pretty sure this was/is a “helix” issue, being reverted back to the clock internal of the device.. my iPad receives a clock then if I stop the clock it stays at the tempo that was last set (still “stopping” transport controls play,stop) If you ran ipad (or cpu) in your set up you could use that as the middle man instead of your added device (running the same midi filters). Glad you got it worked out!!! 🎉🎉🎉 happy looping buddy!!
That very same problem i have since a long time. I have it also with the Stomp, the Stomp xl in combination with the RC600 or the RC 500. Here i saw the first time a solution for that annoying problem. I love the delay's on the Stomp. But stopping a track for a break the delay is out of sync and ok when starting the track again is not nice. Well done! Thanks
This is a great fix for the issue I'm having too... I have the 600 sending clock to a Roland J6... The all start is really annoying as I don't always want to trigger the sequencer with my loops. This looks like it will fix my problem by filtering out that message. The looper seems to be able to filter out all start/stop messages coming IN, but not sending them OUT which is frustrating.
interesting, I've never tried running midi in, maybe they will fix it someday. Getting a lot of feedback from other people saying this is not an issue issue for them.
@@kevinsingssongs it makes sense to me that the looper is the master... That's the way most loopers work for sure. I haven't tried it as the master either (I've only just plugged it in to a sequencer to see if the tempo would work with it, which it did) but don't know if changing up my whole set up is gonna fix my synth start issue lol
@@kevinsingssongs Yeah, it seems to be very buggy and they bugs range widely depending on the hardware you're combining with it. I have another issue with the same J6 synth - the 'hold' function turns off randomly. No idea what triggers it to do this. And the delay on the synth also goes haywire when syncing with the RC-600. I'm gonna have to tinker to see what it is that is causing these things. Might also ask Roland to help as well.
Fantastic problem-solving, Kevin! I see you have a MorningStar MC6. I have MorningStar controllers too, and Boss RC500 & 600. If you are still responding to comments, I would love to hear why you didn’t just use Morningstar’s software editor to alter the command/filter? Why use an additional midi filter box to solve this problem? Thx again🙌🙌🙌
I was not aware of this feature inside the MorningStar to be honest I ended up purchasing the Midihub for another solution, along with sending midi to multiple devices
@@kevinsingssongs thx Kevin! I don’t know if MorningStar can filter this, but it’s a problem I’m about to have to solve and now I’ve got two options to do it. Appreciating your solution!
One way around is to have the click track running in the background keeping the clock, and only turning it off at the loop end. Which also means you must loop to click track. That is the trick to keep all devices in sync if you have drum machines etc. A muted rhythm track...
Just thinking aloud, but what if you sacrificed a loop to always play. You’d also have to sacrifice all start/stop functionality too. You could then use a separate midi switcher along with assign functions in the rc600 to send to get all start/stop functions back.
Dude! I’ve been struggling with this problem, even opened up the ticket with line 6 tech-support. Went back-and-forth with them for a few weeks and then I saw your video. You were way more helpful. Thank you.
L6 said they might address it in the next firmware update
that would be awesome if they were able to address it from their end, but unfortunately, most other units behave similarly. Midi clock is a specific message.
Luckily, this fix seems to be working really well after testing it and utilizing it over 100 gigs
@@kevinsingssongs your fix did the trick. Thanks again! I have a CME midi router/filter. Never thought to look for the stop command in the settings because only the Helix was affected. None of the other devices receiving the clock.
You the man!!
@robhenning8537 I didn't know that unit would also provide this option. That's much cheaper than the midi hub unit
I think it is safe to finally put this issue to rest 🙌 best of luck with your build out
Pretty sure this was/is a “helix” issue, being reverted back to the clock internal of the device.. my iPad receives a clock then if I stop the clock it stays at the tempo that was last set (still “stopping” transport controls play,stop)
If you ran ipad (or cpu) in your set up you could use that as the middle man instead of your added device (running the same midi filters).
Glad you got it worked out!!! 🎉🎉🎉 happy looping buddy!!
i had this issue with synthesizers and akai mpc units too, saw peeps posting in groups and forums with similar issues
That very same problem i have since a long time. I have it also with the Stomp, the Stomp xl in combination with the RC600 or the RC 500. Here i saw the first time a solution for that annoying problem. I love the delay's on the Stomp. But stopping a track for a break the delay is out of sync and ok when starting the track again is not nice.
Well done! Thanks
it's integral for my new setup, i just posted a rundown of it
This is a great fix for the issue I'm having too... I have the 600 sending clock to a Roland J6... The all start is really annoying as I don't always want to trigger the sequencer with my loops.
This looks like it will fix my problem by filtering out that message.
The looper seems to be able to filter out all start/stop messages coming IN, but not sending them OUT which is frustrating.
interesting, I've never tried running midi in, maybe they will fix it someday. Getting a lot of feedback from other people saying this is not an issue issue for them.
@@kevinsingssongs it makes sense to me that the looper is the master... That's the way most loopers work for sure. I haven't tried it as the master either (I've only just plugged it in to a sequencer to see if the tempo would work with it, which it did) but don't know if changing up my whole set up is gonna fix my synth start issue lol
@@kevinsingssongs Yeah, it seems to be very buggy and they bugs range widely depending on the hardware you're combining with it. I have another issue with the same J6 synth - the 'hold' function turns off randomly. No idea what triggers it to do this. And the delay on the synth also goes haywire when syncing with the RC-600. I'm gonna have to tinker to see what it is that is causing these things. Might also ask Roland to help as well.
Fantastic problem-solving, Kevin! I see you have a MorningStar MC6. I have MorningStar controllers too, and Boss RC500 & 600. If you are still responding to comments, I would love to hear why you didn’t just use Morningstar’s software editor to alter the command/filter? Why use an additional midi filter box to solve this problem? Thx again🙌🙌🙌
I was not aware of this feature inside the MorningStar to be honest
I ended up purchasing the Midihub for another solution, along with sending midi to multiple devices
@@kevinsingssongs thx Kevin! I don’t know if MorningStar can filter this, but it’s a problem I’m about to have to solve and now I’ve got two options to do it. Appreciating your solution!
@@Firstinversion899hey did you get the Morningstar to filter?? Having the same issues!
One way around is to have the click track running in the background keeping the clock, and only turning it off at the loop end. Which also means you must loop to click track. That is the trick to keep all devices in sync if you have drum machines etc. A muted rhythm track...
Just thinking aloud, but what if you sacrificed a loop to always play. You’d also have to sacrifice all start/stop functionality too. You could then use a separate midi switcher along with assign functions in the rc600 to send to get all start/stop functions back.
how do you route your mixer?
If you have already told about that in a video, could you tell which one?
I have an in-depth description of my paddle board on another video, but I simply run the output from the RC 600 into one channel
ok thanks i just have to find that video@@kevinsingssongs
It seems to me that the Helix is the issue.
Is there not an option on the Helix to no revert to internal clock?
unfortunately not, this happens with every midi unit i have plugged in, synths, pedal, mpc workstations, etc