Songs too fast after upgrade
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Songs too fast after upgrade
I just upgraded to Leopard OX 10.5 and when I opened up a song I was working on in Digital Performer 6.02 the song is now much faster. There is clearly a problem with the word clock sync. I am using a Tascam D24, a Focusrite ISA430 and an RME Fireface 400.
I haven't changed anything other than Leopard 10.5, so maybe it's just something I need to correct in the Mac or in DP. Anyone have any ideas why an upgrade to leopard would mess up the word clock sync of my system? Otherwise, anyone have any suggestions of what works best as the master clock device and I'll just try re-wiring everything (ugh ...)
Thanks for your help
- Marc
I haven't changed anything other than Leopard 10.5, so maybe it's just something I need to correct in the Mac or in DP. Anyone have any ideas why an upgrade to leopard would mess up the word clock sync of my system? Otherwise, anyone have any suggestions of what works best as the master clock device and I'll just try re-wiring everything (ugh ...)
Thanks for your help
- Marc
My karma ran over my dogma
Re: Songs too fast after upgrade
Did the sample rate get changed inadvertently?
MacPro5,1 2012, six core 2 x 3.06, 10.12.5, Digital Performer 9.13, 40 gb ram, 828mkIII, 2408 mkII, MTP AV, Logic Pro X 10.3.1, Studio One v 3.2, Pro Tools 12.7.1
Re: Songs too fast after upgrade
billf wrote:Did the sample rate get changed inadvertently?
agreed.you are probably at 48 instead of 44.1
2012 Mac Pro 3.46GHz 12 core 96 gig,Mojave, DP11.01,Logic 10.51, RME UCX,Great River ME-1NV,a few microphones,UAD2, Komplete 12U,U-he,Omni & way too many VI's,Synths & FX galore!, Mimic Pro w/ SD3,Focal Twin 6 monitors, Shunyata...........
- James Steele
- Site Administrator
- Posts: 22791
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: San Diego, CA - U.S.A.
- Contact:
Re: Songs too fast after upgrade
Marc-- follow up? I really don't like to see a spate of posts with a problem where the original poster never comes back to clarify if they found a solution or not. This leaves mounds and mounds of open ended posts that can give the impression that no solution was found. If you do find a solution, please *give back* to the board and report what it was rather than not post again until next time you have an issue. Thanks.maswot wrote:I just upgraded to Leopard OX 10.5 and when I opened up a song I was working on in Digital Performer 6.02 the song is now much faster. There is clearly a problem with the word clock sync. I am using a Tascam D24, a Focusrite ISA430 and an RME Fireface 400.
I haven't changed anything other than Leopard 10.5, so maybe it's just something I need to correct in the Mac or in DP. Anyone have any ideas why an upgrade to leopard would mess up the word clock sync of my system? Otherwise, anyone have any suggestions of what works best as the master clock device and I'll just try re-wiring everything (ugh ...)
Thanks for your help
- Marc
JamesSteeleProject.com | Facebook | Instagram | Twitter
Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
Re: Songs too fast after upgrade
Hi James,
I live in Europe so there is a time difference -- I was sleeping when the previous posts were being filed. It's now morning here, so this is the first I can reply with a follow up. (And believe me, I really appreciate the help! So I hope no one thinks I was being rude.)
To answer the questions above, I recorded the original audio files in DP at 44.1, but I can see that the RME and the Tascam are both now slaved to 48, and the Focusrite, which I always thought was the master, seems to be the problem. I am now going to check the cabling to confirm which machine is actually the master clock. In any case, the cabling hasn't been changed in years, so I'm still confused why the upgrade would change the sample rate.
Is there something within the Mac OS that would change something? It's probably just a selection I need to make somewhere, no?
-- Marc
I live in Europe so there is a time difference -- I was sleeping when the previous posts were being filed. It's now morning here, so this is the first I can reply with a follow up. (And believe me, I really appreciate the help! So I hope no one thinks I was being rude.)
To answer the questions above, I recorded the original audio files in DP at 44.1, but I can see that the RME and the Tascam are both now slaved to 48, and the Focusrite, which I always thought was the master, seems to be the problem. I am now going to check the cabling to confirm which machine is actually the master clock. In any case, the cabling hasn't been changed in years, so I'm still confused why the upgrade would change the sample rate.
Is there something within the Mac OS that would change something? It's probably just a selection I need to make somewhere, no?
-- Marc
My karma ran over my dogma
- James Steele
- Site Administrator
- Posts: 22791
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: San Diego, CA - U.S.A.
- Contact:
Re: Songs too fast after upgrade
My apologies. I should look more closely at the message timestamps!maswot wrote:Hi James,
I live in Europe so there is a time difference -- I was sleeping when the previous posts were being filed. It's now morning here, so this is the first I can reply with a follow up. (And believe me, I really appreciate the help! So I hope no one thinks I was being rude.)
JamesSteeleProject.com | Facebook | Instagram | Twitter
Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
Mac Studio M1 Max, 64GB/2TB, macOS Sequoia 15.5 Public Beta 2, DP 11.34, MOTU 828es, MOTU 24Ai, MOTU MIDI Express XT, UAD-2 TB3 Satellite OCTO, Console 1 Mk2, Avid S3, NI Komplete Kontrol S88 Mk2, Red Type B, Millennia HV-3C, Warm Audio WA-2A, AudioScape 76F, Dean guitars, Marshall amps, etc., etc.!
Re: Songs too fast after upgrade
No worries. I really appreciate the quick response!
Here's where things stand. This started out being an issue of PLAY crashing DP, so I upgraded to Leopard. Then the upgrade to Leopard somehow affected the word clock.
I found the glitch in the word clock, which turned out to be the Tascam D-24 mixer not recognizing the external sync source, which in this case was an ADAT lightpipe from the RME Fireface 400 (which should be the Master clock source). So my RME Fireface was the master UNTIL I turned on the Tascam, when suddenly it automatically switched to Slave mode, and the Tascam showed that it had NO external sync source. The Tascam manual might as well be written in Aramaic because it's impossible to figure out something as simple as how to enter the sync source, so I simply unplugged the lightpipe. This put the RME back into Master Clock mode. However, it took about five or so minutes before the Tascam woke up to the fact that it was not getting a clock signal and a screen popped up asking me to select the sync source. I plugged back in the lightpipe, confirmed ADAT as the source in the dialog box that had just popped up, and sure enough the Tascam synced. I then set the Focusrite back to slave, which got rid of the digital jitter. Everything is now synced at 44.1, as before, and I thought I was done.
But you fix one problem and another pops up. I tried to test recording audio via SPDIF and, sure enough, the audio monitor detects no signal in DP.
This, however, should be something that someone here must have encountered before. Any ideas what is causing this latest problem? (The RME drivers have been updated, so that's not the problem). What other reasons could be blocking SPDF from being recognized in DP?
-- Marc
PS. The initial problem, DP crashing with PLAY, was not fixed by moving to Leopard. But perhaps when I fix this latest problem, maybe the other problem will be resolved.
Here's where things stand. This started out being an issue of PLAY crashing DP, so I upgraded to Leopard. Then the upgrade to Leopard somehow affected the word clock.
I found the glitch in the word clock, which turned out to be the Tascam D-24 mixer not recognizing the external sync source, which in this case was an ADAT lightpipe from the RME Fireface 400 (which should be the Master clock source). So my RME Fireface was the master UNTIL I turned on the Tascam, when suddenly it automatically switched to Slave mode, and the Tascam showed that it had NO external sync source. The Tascam manual might as well be written in Aramaic because it's impossible to figure out something as simple as how to enter the sync source, so I simply unplugged the lightpipe. This put the RME back into Master Clock mode. However, it took about five or so minutes before the Tascam woke up to the fact that it was not getting a clock signal and a screen popped up asking me to select the sync source. I plugged back in the lightpipe, confirmed ADAT as the source in the dialog box that had just popped up, and sure enough the Tascam synced. I then set the Focusrite back to slave, which got rid of the digital jitter. Everything is now synced at 44.1, as before, and I thought I was done.
But you fix one problem and another pops up. I tried to test recording audio via SPDIF and, sure enough, the audio monitor detects no signal in DP.
This, however, should be something that someone here must have encountered before. Any ideas what is causing this latest problem? (The RME drivers have been updated, so that's not the problem). What other reasons could be blocking SPDF from being recognized in DP?
-- Marc
PS. The initial problem, DP crashing with PLAY, was not fixed by moving to Leopard. But perhaps when I fix this latest problem, maybe the other problem will be resolved.
My karma ran over my dogma