Sub 37 LFO sync issues and non-responsive panel

Everything Sub.
Post Reply
angalths
Posts: 2
Joined: Sat Mar 11, 2017 2:04 am

Sub 37 LFO sync issues and non-responsive panel

Post by angalths » Thu Mar 16, 2017 8:51 pm

Hey all!

I just got a Sub 37 a week ago, and have run into some serious issues. I'm trying to determine if mine is broken, or if I'm just doing it wrong.

The issues:
1. The panel can become non-responsive, and freeze the instrument for a couple minutes, or until I power cycle it. This seems to occur more when I have an LFO synced to midi. The front panel will completely freeze as shown in the videos. One time, while frozen, I pressed the Save button which caused the small display to go haywire - also in the videos.

2. A midi synced LFO will double trigger on some days, but works perfectly on other days! The midi synced LFO became an issue in the last few days. I'm using a patch that worked fine about 5 days ago, and I've added a recording of each to the dropbox linked above. In general I feel like the processor has something going on in the background causing it to misfire for the LFOs.

The evidence:
Videos of the panel freezing, as well as the LFO sync issue.
https://www.dropbox.com/sh/nglnui8877upt3y/AADb1SYX47-B3Aunb0GwFRVAa?dl=0

So far I've tried...
I've talked to Moog tech support yesterday. They suggested it may be a midi feedback issue, and suggested I disable sending and receiving programs changes, so I've tried that.

I've also tried using the midi din port instead of USB. Specifically, I had the midi in port as the only port used, and did not have the midi out or USB ports hooked up. I was still able to recreate both issues above.

I'm using Ableton, and tend to use the Sub 37 Editor for loading and saving patches if that matters. I appreciate any help I can get!

jimo
Posts: 1
Joined: Fri Mar 31, 2017 11:02 am

Re: Sub 37 LFO sync issues and non-responsive panel

Post by jimo » Fri Mar 31, 2017 11:41 am

I have a very similar issue. Sub 37 about a month old. Using Cakewalk Sonar. It seems when I start Sonar it is making the 37 "freeze" and have no sound (and most buttons frozen). Sonar is sending some MIDI info that is causing this. I as well called Moog and they suggested the same thing - which didn't solve the problem either. Doing a reinitialize of the Sub 37 temporarily fixes the problem but will happen again if I open up a new project. Super irritating and would love to figure out what is going on. -Jim

User avatar
LuthierMark
Posts: 20
Joined: Sun Jan 29, 2017 6:42 pm

Re: Sub 37 LFO sync issues and non-responsive panel

Post by LuthierMark » Sat Apr 01, 2017 7:16 am

This sounds like a MIDI loop, which happens when your Sub 37 sends MIDI data to your DAW, and your DAW sends this back to all your MIDI devices.

The usual setup when using a DAW with an external keyboard synth like the Sub 37 is to set the synth to something called "Local off".

In the Sub 37 you achieve this by going into the Global menu and scrolling to "Local control" and turning everything to "Off". You can also do this in the editor on the "Setup" page, switching all buttons in the "Local control" pane to "Off".
Last edited by LuthierMark on Sat Apr 01, 2017 3:45 pm, edited 1 time in total.
"The thing is, to put a motor in yourself" fz

Moog Sub 37 1.2.0, Nord Modular Rack, Novation KSr,
Emagic Unitor8, Focusrite Saffire Pro40,
Logic Pro X 10.3, MacBook Pro Retina 11.2, macOS 10.12.3

User avatar
Bald Eagle
Posts: 349
Joined: Wed May 22, 2013 11:25 am
Location: Long Island, NY

Re: Sub 37 LFO sync issues and non-responsive panel

Post by Bald Eagle » Sat Apr 01, 2017 12:19 pm

jimo wrote:I have a very similar issue. Sub 37 about a month old. Using Cakewalk Sonar. It seems when I start Sonar it is making the 37 "freeze" and have no sound (and most buttons frozen). Sonar is sending some MIDI info that is causing this. I as well called Moog and they suggested the same thing - which didn't solve the problem either. Doing a reinitialize of the Sub 37 temporarily fixes the problem but will happen again if I open up a new project. Super irritating and would love to figure out what is going on. -Jim

The same thing happens with me. None of my other synths have this problem. I would consider this to be a Sub 37 bug.

Post Reply