Moog Music Forum

Sometimes the arpeggiator drops out and stops playing notes. It started happening playing in duo mode but now happens with any setting. Doesn't happen when the arp is has latch on, only when playing on the keys.
The arp will stop while i am holding keys down. It takes hitting the keys a few times for it to start playing again.

Anyone else experienced this problem or knows a fix?

thanks

Yes - this has happened a couple times for me too! Seemed like a certain combo of keys at a certain time woud cause it to pause the arp and I would need to hit the keys a few times to start it playing again.

Yeah this happens every now and them with mine too, no big issue for me, but it would be a pain if it was on stage

What if your firmware version when you experienced that, if I may ask?

It happened to me sometimes (version 1.07), but only when the arpeggiator was set to 'ordr'.
Didn't test it with the new firmware yet.

Toine wrote:It happened to me sometimes (version 1.07), but only when the arpeggiator was set to 'ordr'.
Didn't test it with the new firmware yet.

Exactly the same here with 1.07.
With FW1.1 I had no probs so far.

Ah i am on 1.07. It also happens the most when on ordr with me as well.

I'll update the firmware now and report back, thanks!

updating to 1.1 made no difference unfortunately

Me too - latest FW and happens with ordered arp!

I wonder if it is happening for everyone or just a few of us? Shame because the ordered mode is one of the most useful t me :C

I'm experiencing this with firmware rev 1.2. When the Sub 37 is in Sequence mode, duo active, running from an external MIDI clock, the sequencer randomly stops playing when holding down a key. Not a combination of keys, just a single key. The stop point appears random, but happens 5-20 sec after the key is pressed. Once this failure occurs, it will keep happening until the Sub 37 is powered off and back on. Reproducing this error is difficult--it happens intermittently.

This makes using the Sub 37 sequencer/arp onstage absolutely worthless--imagine having a song stop 10 seconds in and having to restart not just the sequence, but the synth as well? Any help or insight from Moog here?

Ok, I've posted here and written Moog support twice. No response from them either here or via email after two weeks. Anyone know what's up?

In the sub 37 editor vst under "setup->midi-settings->clock options" choose "follow spp"
I had also lots of problems with the arp not being in sync to my daw. this fixed it!
I also disabled "phase reset" and switched the Midi out mode to "keys"

Also in Ableton I set the MIDI Output MIDI Clock Sync Delay to -12.5 ms so that the moog receives the trigger notes a little bit earlier so the incoming audio is more in time.

Hope this helps

So, I got to thinking that this could be a sequencer output problem. I had never had any problem with the sequencer dropping out until I did a "Restore Default Global Settings". After that, my sequencer/arpeggiator acted surprisingly wacky. I did a quick test of unplugging USB and trying everything out again and it worked fine. Once I plugged USB back in, it was bad again.

Logic is it's own form of MIDI hell because it's trying to be smart by retransmitting midi messages. Knowing this, when I first set up my Sub 37 I set "In Ports" to USB *ONLY* and "Out Ports" to DIN *ONLY*. I didn't remember that I did this, so I had problems after the reset. Once I switched my ports, all was good.

The reason your sequencer would stop is because it's sending notes out that are getting sent back. The timing of this can be imperfect due to latency. Depending on what's going on it could run forever or stop after 10 seconds.

On a side note, I noticed that when using "Order" for the arpeggiator, it would get the dropouts mainly when Back/Forth is enabled. When it's not, we're all good. Still feels like a bug to me though.

-Rob

I believe disabling local control on the synth should avoid MIDI feedback issues and then it should work without using two separate cables for MIDI.