hblobl

Well, back to the original problem ... I have a workaround so far, which really removes the performance (CPU load) issue. I did: 1. I unplugged all midi devices 2. I deleted all devices in Control Surface Setup window - even the original instances. 3. I deleted all assignments in the Controller Assignments window 4. I turned off “New -> Automatic - Installation” 5. I did “Control Surfaces -> Bypass All Control Surfaces” 6. Rebooting and Restarting Logic After that, the CPU load issue has been gone, even when I attach my midi devices again and configure everything new from scratch. Even the tedious automatic installation of duplicate midi controllers on every Logic start is gone now - that has been in 10.6.1 already (but without performance degradation). And ... yes ! ... I got feedback from Apple support, asking me details and for diagnostics ! I wrote a PDF to summarise the details for Apple. If somebody got the same specific problem, I can share it ... well, just don't know how to do it right now.

Well, back to the original problem ... I have a workaround so far, which really removes the performance (CPU load) issue. I did: 1. I unplugged all midi devices 2. I deleted all devices in Control Surface Setup window - even the original instances. 3. I deleted all assignments in the Controller Assignments window 4. I turned off “New -> Automatic - Installation” 5. I did “Control Surfaces -> Bypass All Control Surfaces” 6. Rebooting and Restarting Logic After that, the CPU load issue has been gone, even when I attach my midi devices again and configure everything new from scratch. Even the tedious automatic installation of duplicate midi controllers on every Logic start is gone now - that has been in 10.6.1 already (but without performance degradation). And ... yes ! ... I got feedback from Apple support, asking me details and for diagnostics ! I wrote a PDF to summarise the details for Apple. If somebody got the same specific problem, I can share it ... well, just don't know how to do it right now.

Thanks for the replies so far. This problem is getting attention at the Apple Communities ("10.6.2 the worst update ever") ... it seems the midi control surfaces software is broken somehow. One workaround recommended is, to switch them off (Logic Pro -> Control Surfaces -> Bypass all Control Surfaces), if you can live without control surfaces (haven't tried that yet). Another to upgrade to MacOS Big Sur. According to one comment, the problem is gone there). This is not viable for me, since Boss Tone Studio doesn't work with Big Sur ( . Or back to 10.6.1, which is not that perfect. The real solution of course would be, if Apple fixes the problem ASAP !

After updating Logic from 10.6.1 to 10.6.2, it is incredibly slow, the GUI is next to being unusable. I didn't change anything other than the upgrade. ... yes, there is enough disk space. CPU load is like mad and the machine is getting very very hot. Did anybody else experience anything similar ?

Yes, that helps of course, since it ignores the tempo information in the file. Well, I think I found it: After clearing the Tempo List and "Remove original recording tempo" you have to "Update File Information" in the Audio File Editor. So it should be possible this way to write modified tempo information to the file. The purpose of the "Remove original recording tempo" alone is unclear .. well anyway, seems I have a solution now. Thanks you for that instant replies ... very good support community. .. waiting for your book on 10.6.x ... Oliver

... see attachment screen print. Did another Test: 1. Clearing Tempo list (1.1.1.1 tempo does not clear) 2. Again "Remove original recording tempo" 3. Closing the project, closing Logic 4. Starting Logic again 5. New project with tempo "ADAPT" and audio region "Flex & Follow" off 6. Dragging the file into an audio track 7. Tempo list immediately there again ... so it has to be in the file ....

Ohh , we crossed or messages .. ...just edited mine meanwhile .. Tempo information is still in the file, because - after clearing track and tempo list in Logic - when I drag the file again into the track, the tempo list is immediately there again without Logic analyzing it (Flex & Follow : off).

David, Thank you for that quick answer ! ... besides the clock icon I still cannot remove the tempo information from the file ... ? Tempo information is still in the file, because - after clearing track and tempo list in Logic - when I drag the file again into the track, the tempo list is immediately there again without Logic analyzing it (Flex & Follow : off).

Inge, are you using Logic 10.6 ? Perhaps it helps to set "Flex & follow" to "off" in the header of new tracks which should not adapt tempo changes before you import. I am currently too at that point and I am not 100% sure.

Hi, I've got a .wav file, which I see in the project audio screen. It is unlocked und the small watch icon tells me, it got tempo information embedded. Apple states in its support pages for Logic 10.6: (see attachment). Well, that's wrong. There is no "Remove Tempo Information from Audio file" but "Remove original recording tempo". I assume, that's what it is meant. Anyway, if I do this, the clock icon is still with the file and obviously nothing has been removed. I see with finder, that the file has changed, but when I (after clearing everything in Logic) import it again (in ADAPT mode), there is the tempo list again. I can't find a way to remove the tempo from the file. What is my misconception ? Please help. Thanks for any help, Oliver