![]() So if you don't have live tracks with high demands, track playback may be a better choice. With the Playback and Live Tracks option, the system may be a bit more stressed. If the computer has enough cores and there are no other DSP demands on the computer, each live channel strip can be processed by a different core. The Playback and Live Tracks setting distributes the load across multiple threads when a track stack is selected that contains multiple software instrument channel strips, or when more than one audio track is being recorded. When a track stack is selected for live input, or when multiple audio tracks are recorded, all of the DSP required for the input is processed by one processing thread-and thus by one available core on the computer. The Playback setting reproduces the behavior of earlier versions of Logic. You can use multithreading to affect how Logic distributes the DSP load when a software instrument track stack is selected for live input or when multiple audio tracks are enabled for recording. before it was only PlaybackĬhanging the multithreading setting has produced the most noticeable difference!įurther information about the multithreading function: (maybe helpful for the problem solution) Processing Buffer: Small, before it was Large Processing threads: Automatic (Recommended), before it was 10 (8 high performance cores) It runs smoother with the following Logic Pro X audio settings: It seems to be triggered more easily on bigger sessions. It is very different to a normal cpu-overload. And it keeps playing back that small loop until i stop it. I have a screenrecording i could send to you if that would help to understand the behaviour. In my case it keeps repeating a very small part of the session, like a mini-loop. I don't think it is related to cpu usage in the conventional way because in that case playback would just stop (or playing distorted audio sometimes). I also made A/B comparison tests with several logic sessions testing both interfaces one after the other on the same session. I tested some logic sessions with stock plugins only with the same 'stuttering/looping' with the UC. I do have a few plugins that require rosetta, that does not seem to cause any problems even with native ARM Logic. Logic runs fine natively with the other interface. ![]() ![]() Maybe you have some plug-ins that require Rosetta? We dfo have new M1 systems and do a lot of load tests with Loigic, and have not seen it 'stuttering' unless it is overloaded from plug-ins.Īlso you did not tell us what driver you use - the old 3.27 or the newer 4.04? Logic has been ported long ago and runs natrive without Rosetta. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |