midi sordino

Does this still happen if you use system settings for audio? Are you using the internal drive or do you also use external drives? If so, how are they formatted?

What are the audio buffer settings? Try with 1024 and see if issue is still there..

No worries. The L2 gain slider adds gain to the signal. As Fab Filter say 'Simply put, it makes your audio louder, while respecting the current maximum output level'. The output level sets the ceiling beyond which the signal will not go. The difference you see with the Logic Loudness meter will depend on where it sits in the chain on the master bus. If it is inserted after the L2 at the very end of the chain on the master bus then it should have the same or a similar integrated LUFS reading, but if it is inserted before the L2 then it will show the loudness before the L2 applies gain to the signal.

It’s because the gain slider on the L2 (far left) is set to +3.3 dB. Easy to miss when you start using the L2. The free YouLean Loudness meter is also a handy tool to double check files, either in a project, or for me, usually after they’ve been bounced / exported.

You’re right, the reading between the L2 and Logic’s meter are out by around 3db. 3.3 db to be precise, as this is the amount of gain you’ve applied on the L2 (gain is on the far left). Easy to miss, as some of the controls aren’t that easy to spot when you start using the L2. The free YouLean Loudness meter is also a handy tool to double check files, either in a project, or for me, usually after they’ve been bounced / exported. Hope this helps.

Looks like this problem has already been solved by David Nahmani. Check the link...

Just noticed that if I group two audio channels, and they are at different volumes, Logic won't accurately track the difference between the faders. Small example: Fader 1 is at -2 db and Fader 2 is at -5 db. If I group the faders and 'volume' is selected, then set Fader 1 to 0 db, Fader 2 will read -3.1 db. I don't think I had this issue in previous version of Logic. Can anyone else confirm?

This is something you need to do, but I don't think it will resolve your CPU spike problem. I'm on a 20-core M1 Ultra Mac Studio with 128 GB of RAM and I'm using the internal drive (4TB). I've given disk full access, have tried multiple audio buffer, multithread, process buffer and Kontakt 7 settings (multiprocessor support off and also on & different preload sizes). Also tried this with internal audio rather than my interface but I'm still getting single thread CPU spikes like yours on certain larger instruments, e.g. Lores. All this was tested in a Logic project with no third party plugins except Kontakt 7 and the same settings as you.

I used Dropbox with LPX for almost ten years without any file corruption. But you had to re-download a project file from the web browser to the desktop (not replace another project file) if you wanted it to open properly. I no longer use Dropbox with LPX. The final straw was recent projects not showing up in Logic. It's a known issue: https://www.dropboxforum.com/t5/Apps-and-Installations/Logic-Pro-X-projects-stored-in-Dropbox-don-t-show-up-in-quot/td-p/645886 Unfortunately there is no current solution. I now use local a local drive to backup my LPX projects and only use the Dropbox backup feature to store a copy of my project in the cloud. Hope this helps.

No worries. You're in native mode by default. To enable Rosetta you get info (cmd + I) on the Logic Pro app icon and tick 'Open using Rosetta'. I have the same preload setting on my Kontakt 7. I've noticed some libraries are more CPU hungry and will give me similar random spikes to yours, e.g. Straylight. I think most Spitfire libraries should be compatible with Apple silicon. On their website only two libraries are incompatible. But I would check the CPU performance with other Spitfire libraries, or similar libraries, and see if the issue still persists. It's possible that it's specific to Kepler (which might be quite CPU hungry). If so then maybe contact Spitfire support to check if it is supported. It's a shame to think that Mac Silicon can be such as hassle and be quite underwhelming in scenarios like this. I miss the ease of using my iMac Pro and never seeing messages like 'An Audio Unit Plug-in reported a problem'. But even though things have settled a bit, it's still something of a transitional phase and we are where we are.

I've also had CPU overload issues with some Kontakt instruments since I migrated from Intel to an M1 Ultra chip. It's annoying because you expect improvements when you 'upgrade' your computer. I spent a long time trying to make sure all my third party plugs are compatible but I'm still not happy with the CPU load on quite basic templates in native mode (or Rosetta). To the OP: There are lots of potential reasons for your CPU spike. Are you in native or Rosetta mode? What's the i/o buffer setting? Also process buffer range and multithreading can have impact on CPU. https://support.apple.com/en-ie/HT203930#:~:text=Process Buffer Range%3A set this,Multithreading setting to optimise performance. Does this issue persist using internal audio rather than your interface? Is your audio interface driver up to date? If in native mode, make sure all plugins in the project are compatible with Apple silicon and OS Ventura (if you're on the new Mac) but also check the CPU on the project with no plugins and just Kontakt 7. Re your second point - There's a slight delay opening plugins on Apple Silicon. It's a known issue. Not aware of any delay when closing Kontakt. Hope some of this helps.

Update - I saved the template without any hidden tracks (there was one hidden track) and the issue disappeared, so it would appear to be a bug. Will report.

Not sure if this is a bug or not. When I open the mixer on a solo piano project template and 'All' is selected, I don't see all the tracks (1). In the first screenshot you can see that the Ribbon Mic channel is missing. If I then switch to 'Tracks' (2) then switch back to 'All' I do see all the tracks (3). Am I missing something? Thanks, M

Great. Thank you very much!

Small but annoying problem. When I open any Logic project template, after a very brief pause, it renames every project ‘Untitled 3’. I've tried renaming 'project alternatives' to the template title. I thought it worked at first but now it's not. Even stock Logic templates are all renamed 'Untitled 3' when opened. I’ve plugged out all peripherals and tried system audio. If I try another user account it renames any template projects ‘Untitled’. But I’d like to remain using my main user account. I reset all settings in LPX but it didn’t work. Am I missing something obvious? Maybe Prefs I can trash that might fix this? Thanks, M LPX: 10.7.9 | OS X version: 13.3.1 | Mac Studio (M1 Ultra) | Interface: RME 802