Hi
Just recently been having issues running my SP with Cubase 7
Simply pushing midi to it from Cubase makes it freeze and last night had to reinstall the firmware
Then it will play ok for like 2-3 mins then freeze again
Its definately bad data coming from my daw but I cant work it out
Any clues guys ?
I’m not sure if this is applicable or not - and I don’t use Cubase - but Amos mentioned in another thread that the Little Phattys have issues with MTC - MIDI Time Code. (this thread: http://forum.moogmusic.com/viewtopic.php?f=7&t=17857&p=118010&hilit=MIDI+time+code#p118010)
I’m using an Akai MPK25 as my controller for my Slim Phatty, and as my master clock source for my Dark Time sequencer, MoogerFoogers, etc.
I was getting some weird results with my SP - reduced volume levels, hung notes, issues transferring patch sets with the stand-alone Editor etc., especially when or after using the MPK transport controls to start/stop my sequencer and drum apps. It turns out that the default transport setting of the MPK uses a combination of MMC (MIDI machine control) and MIDI clock. After I saw the comment from Amos about MTC, I changed my transport settings on the MPK to send MIDI clock only, then did another factory reset on the SP. Since I did that, I have had NO issues with my SP, even after using the Editor to change patch sets several times.
It might be worth looking at your Cubase settings and see if it is sending MTC or MMC. If so try, setting that to MIDI clock only, then do a factory reset on your SP before you try controlling with Cubase.
Might help… 
Thanks Stuka
Appreciate the suggestions
You might just have something there
Cheers
No problem -
I’ll be interested in seeing if that makes a difference for you or not!
I was pleasantly surprised by the (apparent) impact it made with my Slim phatty!
It seems completetly unrelated, but my copy of the editor was practically unusable until I changed the MPD’s clock format and performed another (the last of several) factory reset on my SP.
Never would have figured a clock sync source could have that much of an impact!! 
Randy
Hi Randy
Hit the nail on the head !
Problem solved
Thank you very much
BTW you mentioned using the editor
Is it worth the outlay ?
Chris
Cool - glad it solved the problem!! 
As far as the Editor goes ~
Now that I got it working, yep, I like it!
Keep in mind that mine is the stand-alone SoundTower editor that Moog sells, not the plugin, but that’s all I really wanted - just a way to backup and experiment with a bunch of different patch sets.
Works great - but still a bit overpriced, IMHO 
BTW -
You can upload the SYSEX Phatty banks (available for free download on the Moog site) to the SP using a SYSEX program, then convert, tweak, and save them as presets and banks using the editor.
Cool stuff… 
Hey Randy
Appreciate all your help here
Yes I will invest in the editor putting aside the inflated price
Still not as inflated as the 64bit version of the VST editor for the korg kronos $200…OMG !
The 32 bit VST comes standard …useless to me
OK so there are other sound banks on the moog website you can load into the SP ?
Will check them out.
Cheers
Chris
Compared to the Korg editor, I guess the price on the Moog Phatty editor isn’t so bad after all!!
The SYSEX banks on the site are actually listed for the Little Phatty, but work fine for me on the Slim.
Should be enough to keep us busy for a day or two! 