I am slaving Sonar to an external DP24.  To get this to work, I set the clock source as MMC.  Works fine until I use the transport controls on sonar and then MMC is broken.  I go into clock source to find it has been reverted to "audio".
 
Can someone explain this behavior, or is it a bug?

Aren't you supposed to use the transport controls on your master device?

Hi Teal,
 
In order for MIDI Machine Control to activate the DP24, MIDI connections must be made (MIDI i/o to an interface). Make sure it is set to MMC slave in the MIDI remote control menu. If you have a device ID set to something other than "All" make sure that device ID matches Sonar's MMC device ID setting in Preferences - Project - MIDI. (If you do not have other devices connected that respond to MMC, just use the "All" setting on the DP24 for the MMC slave ID.)
 
In Sonar, open Preferences - Audio - Sync and Caching (Advanced) and set to "Full Chase Lock", "Do not Switch Clock Source, but Start if in SMPTE/MTC mode", and "Maintain Current Clock source and wait for timecode." In Preferences - Project - Clock set it to SMPTE/MTC (or in the Control Bar Sync module). 
 
With these settings, Sonar should send out MMC command to start to the DP24 at the now time's current location. The DP24 should then send out MTC and start Sonar's transport. 
 
I suspect you have "Switch Current Clock source and Start Playback" set in Preferences - Audio - Sync and Caching (Advanced). This automatically switches the clock to an Audio sync when pressing play in Sonar. 

Daniel,
Thank you very much!  But I actually want to slave Sonar to the DP24.  It is working for the most part; I can use the DP24 transport controls and sonar will follow the transport.  It even works with looping set in the dp24.
 
I will try your settings but I don't believe the dp24 can act as slave.  The desired setup is to use SONAR as a midi workstation appended to the portastudio.  Instrument outputs will be set individually in SONAR and routed to inputs in the DP24, thus I will have hardware and fader control over the mix.  Programming and midi handled in sonar.  Essentially using the DAW as a glorified drum machine.
 
The plan is/was to set up a template in the DAW with Kontakt, Maschine, and EZDrummer each with their own stereo pairs routed out to inputs on the DP-24.  All of the analog tracking would be handled in the dp-24, and I would be using the dp-24 transport and faders for the mix.   Kinda retro, I suppose, but I have my reasons.

I have sometimes used Sonar with my Tascam 2488 and midi MTC - Midi Sync.
 
I usually use it to expand my track count while taping a concert. For me, it works best to just use SPIDF to sync the clocks - skipping the midi sync. I usually set the Tascam 2488 as slave to my RME device. It works pretty well. I think sampling is tighter this way then with Midi Sync.
 
For me, I just start both devices... record a snare hit that I use to light up the tracks after importing the data to Sonar from the Tascam... and let it roll.
 
This is a very cheap way to take my track count to 16 without even using the ADAT input on the RME.
 
Edit: Haha - just looked - DP24 is just the new version of my old Tascam 2488

gswitz
I have sometimes used Sonar with my Tascam 2488 and midi MTC - Midi Sync.
 
I usually use it to expand my track count while taping a concert. For me, it works best to just use SPIDF to sync the clocks - skipping the midi sync. I usually set the Tascam 2488 as slave to my RME device. It works pretty well. I think sampling is tighter this way then with Midi Sync.
 
For me, I just start both devices... record a snare hit that I use to light up the tracks after importing the data to Sonar from the Tascam... and let it roll.
 
This is a very cheap way to take my track count to 16 without even using the ADAT input on the RME.
 
Edit: Haha - just looked - DP24 is just the new version of my old Tascam 2488

 
Unfortunately, they did not give it any digital I/O!  On a positive note, it sounds better than it has a right to with whatever cheap ADCs they are using.  But instruments interface directly with the UFX before being sent to the DP-24, so that may have something to do with the quality.

Teal 
Unfortunately, they did not give it any digital I/O!  

Well I'll be! They stole your SPIDF plugs! Bastards!! ha!
 
Oh well.
 
Guess Midi Sync it is then.

Back in like 2005 or so, I did successfully make the Tascam 2488 the Midi Sync Slave of Cakewalk. I was also able to control the faders in the device from Sonar, so I could write fader automation. In the 2488 it had like, jump/catch settings for the faders. The faders were not motorized so it was a bit confusing.
 
Also, I was able to use it as a control surface for Sonar. So, I could plug it in via midi and move the sliders on the interface to write automation in Cakewalk.
 
I pretty much never used it this way. I'm too lazy.
 
I picked up a AlphaTrack single track device as an external controller which is nice and small - with a motorized fader.
 
I also got a touch screen which works better than any controller I've used.

BTW, you're smart to know you have to clock sync the devices or you'll get crazy distortion when you bring all the tracks together. You're on the right track. I don't see a way to sync the devices short of Midi.

Not meaning to spam you... I remember having to hit Play+Record on the Tascam to set it 'wait' mode to listen for Midi MMC messages from Sonar. If I didn't do this, it wouldn't suddenly start recording. Tracks have to be armed and you have to put it in Play+Record. It doesn't start recording until it gets the message at which point it suddenly jumps to the point in time that matches the Sonar Project. There is a lag for it to start. (seconds).