I keep getting this message and I don't know how to resolve it.
"Error while trying to synchronize audio and midi. Sample Rate 42,367 recognized. check conflict between Logic Pro X and external device
"Error while trying to synchronize audio and midi. Sample Rate 42,367 recognized. check conflict between Logic Pro X and external device
That is the only time I see this message. It may happen more for me since I have audio hardware clocked outside of my Mac. If my audio hardware is clocked to 44.1kHz and the project I load is 48kHz, this is the message I see. I have to manually change my clock, or change the setting on the project. I see this message about a dozen times a day :(
I can see if your interface follows the Logic project setting that you would not see this message.
Another thing the OP can check is to see if his hardware interface is set to External clocking with no external clock present (i.e., is it clock sync'd).
What interface are you using?
That is the only time I see this message. It may happen more for me since I have audio hardware clocked outside of my Mac. If my audio hardware is clocked to 44.1kHz and the project I load is 48kHz, this is the message I see. I have to manually change my clock, or change the setting on the project. I see this message about a dozen times a day :(
I can see if your interface follows the Logic project setting that you would not see this message.
Another thing the OP can check is to see if his hardware interface is set to External clocking with no external clock present (i.e., is it clock sync'd).
What interface are you using?
Check to be sure your audio interface clock is set to internal...
In the UA Console app, what is the status of the sample rate and clock settings (lower left corner of the window)?
You will see this message if your project's audio sample rate is not the same as the sample rate your hardware is using.
Go into Logic -> File -> Project Settings -> Audio... and check the Sample Rate there.
It should be set to match your hardware.
Ah, OK, you have actual external hardware - OK. However, this message also pops up (very regularly) with users who have no external hardware. I think your case is the first ever in which the message actually was true in the sense that there is actual external hardware involved. My bad.
And what is the project sample rate in File -> Project Settings -> Audio?
Also, is the Apollo set as your audio interface in Logic Preferences?
If the project is 44.1kHz along with the device, it should be syncing up...
Thanks for that reply. I confess I'm a novice and have no idea where to find the audio interface clock. Could you point me in the right direction?
I'm connected to the U.niversal Audio Apollo Twin. I use it for vocals, guitars and bass plugged into the high input slot
You will see this message if your project's audio sample rate is not the same as the sample rate your hardware is using.
Go into Logic -> File -> Project Settings -> Audio... and check the Sample Rate there.
It should be set to match your hardware.
Nope. That is rarely the case when you get this message (never, really - in the over ten years I've been on this site this never once this was the case, and this has been asked thousands of times - just search this site for "error while trying to synchronize" or "error synchronize")
What happens is that Logic (or better: a software instrument (Alchemy may do this, for instance)) cannot "keep up" with the playback speed, and it drops samples - the number in the error message is ALWAYS lower than whatever the set samplerate of the project is. It is in fact a variation on the "system overload" message. Your synth patch is too much for your CPU.
There are some remedies:
Project sample rate is 44.1, Apollo is the interface in Logic
and yes the problem seems to be fixed I've played the project through a few times and the message has disappeared.
Thank you very much for sticking with me and answering the questions. I now know more about sample rates, internal clocks and preference settings.
44.1 kHz Internal clock
I keep getting this message and I don't know how to resolve it.