I tried looking on the forum for an answer to this question but to no avail.
When I start the sequence in my DAW (Anvil Studio) my Sub Phatty’s LFO (which is set to midi sync) goes too fast initially (LFO speed light flashing and modulating off the planet) and then settles down after a few beats to the midi synced setting.
It appears it’s taking a few beats to sync to the master clock? (Which during this time the Sub Phatty is modulating like crazy making the first few beats unusable)
I have tried my DSI Tempest as the master clock also and because the clock runs all the time on Tempest (as opposed to start/stop clocks on the DAW) it syncs beautifully with no issue!
I’ve also connected my Novation Impulse controller direct into the midi in of the Moog and the LFO syncs immediately also.
My Boomstar SEM and Prophet 08 do not have an issue with clock from the DAW.
It appears to be an issue between the Sub Phatty not liking the start of the clock pulses from the DAW??
Have any other users experienced this and if so what suggestions would you recommend?
I have upgraded previously to the latest V2 firmware on the Sub Phatty.
That isn’t the latest release though. The zip on the website has a name that suggests it contains 2.1.3, but actually contains 2.0.3. If you search the forums however, you can find releases up to 2.1.6 I believe. (I’m running the latest beta myself.) Maybe links to those were also mailed to registered users. I have no idea why Moog are so bad at linking to the latest versions of their firmware and software on their website. It’s quite annoying, frankly.
I have installed V2.1.12 (Beta) firmware so will be seeing how this goes and hopefully be able to give some feedback in the Beta test group.
It did not change the issue I was having with the LFO LED flashing off the planet for a few beats when the DAW initially sends clock but for the meantime I am going to use my Tempest as the master clock and work on this a bit later.
Actually it is a little similar on the DSI forum’s where recent Beta’s are available for instruments there but not on the main website.
Anyway, I guess just involves a little digging but I understand your point!
I don’t think it’s a bad thing that beta’s aren’t publicly available on the website, but it doesn’t make sense to me to not have the latest release public release up there.