district78

I looked at the Activity Monitor to see what was happening when the rainbow wheel popped up. I saw that cfprefsd was using a lot of CPU. Then I did a fs_usage command to see what files were being used by that daemon. I could see that the computer was access the Logic Pro prefs file over and over (way more than on another computer that isn't experiencing this issue). I feel like it's a permissions issue, but I have no idea if that's the case or how to address it.

Recently upgraded an 2017 iMac Pro to Ventura from Catalina and now when I crossfade 2 audio files Logic hangs for over 5 seconds. I can adjust crossfade boundaries but as soon as I create a new crossfade things slow down. I have identified that it has something to do with the cprefsd daemon updating the logic preferences file when I create a fade. I tried trashing the Logic prefs file (which didn't work), but not sure if there are other preference files that I may want to trash. Would appreciate any ideas anyone has. Let me know if you need any more info. Thanks!

No tempo events. On the same machine with 10.6.2 it doesn't happen. Was happening with 10.7.2 to 10.7.4. The only workaround I have is to constantly reapply project tempo to region.

I can't upload a video because the file is too big but I can reproduce pretty much 100%. I'm starting with an m4a file and dragging in to the project. Then analyzing in smart tempo editor. I can recreate this issue with the scissors or just adjusting the boundaries of the audio. Here's what it looks like before and after a slice.

Since updating my machine from Catalina and 10.6.3 to Monterey and 10.7.4 I'm finding Flex audio to be super buggy. Splitting a region that is in flex and follow with scissors causes the first half of the region to fall out of time and resizing a region causes all kinds of craziness. Is anyone else experiencing this? Any solid workarounds? Here's an example of what I'm seeing: 1. Drag an audio file of your favorite song in to logic. 2. Double click the region 3. Click Smart Tempo and Analyze 4. Edit->Apply project tempo to region and downbeat 5. Split the region on various bars and the regions change size and the audio goes out of time.

Thanks for your replies. It's a bummer that no one else is able to reproduce it, but I assume a lot of people haven't experienced this because we are doing music editing and remixing so we are importing audio from m4a or mp3. From your replies I played a little bit with exporting the tempo to the audio file and resetting the flex edits. While those things didn't solve the problem, I did see the behavior change. I'm thinking it has something to do with how logic is handling flex markers and/or the tempo of the audio file. I'm able to reproduce this issue on every computer I have and very easily. If you drag an m4a in to your logic project. Set the tempo, then enable flex time on the track. Speed the song up by 10 BPM or more and then use scissors or marquee to split the audio. You may have to try a couple different edit points as sometimes it's fine, but depending on where you slice it, the end of the first half will get stretched out. I'd be happy to make a video to show the problem if anyone can point me to info on how to do that. Thanks, Spencer

Has anyone had any good experiences or developed any useful workflows when dealing with all the new flextime bugs aka behaviors? I fully expected the 10.3.1 release to fix the issue of regions resizing themselves when splitting with scissors, but it is still there and I have not figured out any reasonable way to deal with it. Maybe I need to rethink what I expect of flexing, but it used to work marginally well before 10.3 and now it's just broken. Here are some highlights of problems I'm experiencing, I'd love to see if anyone can help. One caveat, we do a lot of projects where we import master audio files in to an existing project and use flex time to adjust their tempo. 1. Splitting flexed region causes left region to change tempo. 2. option dragging bottom right corner while in flex view now loops region. You now have to press option once you've started dragging the edge of the region. 3. Sometimes can't extend a flex marker past the edge of a region. 4. when moving a flextime marker past other existing flex markers, all audio in region stretches out of time. 5. Extending the region boundaries reveals audio that is totally out of time. (This has always been that way) Thanks, Spencer

We're having problems with fades as well. using the fade tool hotkey (CTRL-SHIFT), when creating a fade for the first time it doesn't always create a fade. Also, resizing a fade doesn't work properly when you redraw it with the mouse. We're dealing a lot with flexed audio. I thought it might have to do with the fact that that hot key now brings up a different tool when not over a region. Also, when a fade exists, the resize fade tool just changes the shape of the fade instead of adjusting the fade boundary.

I'm also having this issue with flexed audio. I'm on El Cap and it is a pretty major problem for us. Across the board dealing with flexed audio is really difficult in this 10.3 release. Do you have tempo events in your project? thought it might have something to do with that.

I think I'm having the same issue, but toggling catch playhead only seems to work while playing. Once I stop playback it turns itself back on. Is it possible that my preferences are corrupted or is that how it's supposed to work?

I'm seeing a weird behavior when dragging and dropping an m4a in to my arrangement window. There's an audible stutter at the beginning of the file that actually exists in the AIFF that's being generated. LPX 10.0.6. The image attached shows the top track which the audio was brought in via File->import and the lower track is brought in via drag and drop. Is anyone else experiencing this?

I'm seeing this as well. But it's low on the list of weird stuff since moving to LPX since it's just a little annoying.

Have you checked out varispeed? It may sound okay on the material you're working with. Also, there's the time and pitch machine in the sample editor if you want to change the tempo of each file individually (however, the editing in the sample editor is DESTRUCTIVE so you should make a backup of your audio file before using the time and pitch machine. In my opinion, if you can power through getting the transients detected in the sample editor, slicing will sound the way you want it to.

You can try creating a new project and importing all the tracks from the corrupted project from the browser. Also, you can try running Logic in 64 bit if you aren't doing that. It may be an issue with one of the 3rd party plugs and moving them into the 32bit bridge sometimes helps.

Type "Dominator" in the library. It should get you most of the way there.