Logic no longer plays 44.1k project w/ interface at 48k on M1-based system

For years now, I have been able to work with both newer projects at 48k sample rate and older ones still at 44.1k on my interface running at 48k. That still works on my Intel-based iMac, as of very recently, that is no longer working on my M1-based MacBook Pro.


On the MacBook Pro, now, when I open a 44.1k project and play it, it starts playing back too fast and at too high of a pitch (which obviously makes sense if) playing back at 48k w/ no rate conversion and then displays an “Error while trying to synchronize Audio and MIDI” dialog with a message of “Sample Rate 48,000 recognized. Check conflict between Logic Pro and external device.”


Well, the rates /are/ different. That was just never a problem before. It is still not a problem when working on my Intel-based iMac, also using an interface running at 48k (I have confirmed this is actually true).


both systems are running MacOS Monterey 12.6.8 and Logic Pro 10.7.9.


Has something changed in that MacOS update or Logic update that could cause this new behavior only on systems running Apple Silicon? Is there some way to recover the ability to work on a project at a different sample rate than the interface as I have previously been able to do?

Posted on Aug 6, 2023 7:30 PM

Reply
Question marked as Top-ranking reply

Posted on Aug 10, 2023 10:53 PM

So, I do seem to have figured out what’s going on with this and how to work around it.


In the past, Logic seems to have honored the currently set sample rate of the interface, but now it changes the interface to use the same sample rate as the project if possible.


Since the MOTU UltraLite AVB offers the 44.1k rate as an option over USB, Logic switches it to that, but the interface cannot actually operate at 44.1k while connected to the other computer over AVB and continues to communicate at 48k over USB in spite of the 44.1k setting.


I can get around this by disconnecting from whichever computer is not actively using the interface at the time and then restarting the interface.


There are other scenarios in which this would not be a workaround such as when using one AVB-capable interface connected to another over.


it would be helpful if there was some way to tell Logic to follow its old behavior and not try to change the sample rate of the interface.

Similar questions

3 replies
Question marked as Top-ranking reply

Aug 10, 2023 10:53 PM in response to stevecjor

So, I do seem to have figured out what’s going on with this and how to work around it.


In the past, Logic seems to have honored the currently set sample rate of the interface, but now it changes the interface to use the same sample rate as the project if possible.


Since the MOTU UltraLite AVB offers the 44.1k rate as an option over USB, Logic switches it to that, but the interface cannot actually operate at 44.1k while connected to the other computer over AVB and continues to communicate at 48k over USB in spite of the 44.1k setting.


I can get around this by disconnecting from whichever computer is not actively using the interface at the time and then restarting the interface.


There are other scenarios in which this would not be a workaround such as when using one AVB-capable interface connected to another over.


it would be helpful if there was some way to tell Logic to follow its old behavior and not try to change the sample rate of the interface.

Aug 7, 2023 3:57 AM in response to stevecjor

stevecjor wrote:
(...) For years now, I have been able to work with both newer projects at 48k sample rate and older ones still at 44.1k on my interface running at 48k. (...)

This is quite unlikely. It would require an automatic sample rate conversion, which is possible, but it's more likely that your sound card has automatically adjusted to the project's sample rate. And it's possible that your sound card needs an update to communicate properly with the new M1 chip.

Some old sound cards will need to be manually changed to match the project's sample rate.

What kind of sound card are you using?

Aug 8, 2023 12:54 AM in response to yoyoBen

I am using a MOTU UltraLite AVB. I am using it in a setup where I work on the Intel iMac, connecting to it over AVB (Ethernet) and my wife works in another place in the room, connecting to it over USB. We are rarely actively using the interface ar the same time, but it is quite often connected to both.


Since AVB only works at multiples of 48k, I have it set to 48k, so I know for certain it is operating at that rate for the Intel, and all evidence suggests that in that case, it must run and does run at 48k for the USB as well.


Now, I’m wondering whether Logic on the MacBook Pro simply believes that it can change the bit rate to 44.1k since it does support that rate as a general capability even though not when used as we are using it?


Whatever is different now seems like it must have changed with either the latest Logic update or the latest Logic update, though I obviously might have guessed wrong about it having anything to do with Intel bs M1.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Logic no longer plays 44.1k project w/ interface at 48k on M1-based system

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.