sunbrother

Agreed. Keeping my Mac Pro 6,1 actually helped speed up my new Studio in a subtle way: I manage my Dropbox on that computer. No longer will I get a System Overload out of nowhere, look up at my task bar, and see Dropbox stuck syncing a single file that never changed.

Did you ever encounter this on Sonoma or only Ventura? Curious since PlugSearch 4 came out and looks great!

E-core usage is primarily for operations as far as I can tell, so a video of someone, say, looping a cycle in Logic while editing regions would show it even more. That’s where I saw it the most and was happy to see they weren’t being “unused” as people tend to say. plus they seem to be preferred by a lot of other apps. So if another app does something on a schedule it doesn’t give you a system overload.

I have seen many operations in the DAW use those, just not real time DSP... Can we say with certainty that other hosts are using them for real time DSP tasks? In that video he's comparing it to REAPER and Cubase- I didn't see him test it without pre-rendering FX disabled, pre-buffering disabled, or ASIO Guard disabled. Logic doesn't have any of those features...

What version are you using? When everything is working the way it should, I've found Logic is as able to work with as little round trip latency as other DAWs, which at a 32 (or sometimes 64) sample buffer is good enough for guitar amp sims, even with a musician who is very sensitive to latency. This is excluding intermittent and weird situations I've run into where the same projects would have less latency when loaded in 10.7.9 than 10.8.

I do it that way with the Slip tool all the time. Flex is powerful and capable but also can be a big headache in some situations, so if I can just slip, nudge, and crossfade regions like this I do. Improving the approach how? Do you mean to make it faster? Using Slice at Transient Markers can make this a little faster with some kinds of instruments/playing styles, but it's not always necessary either.

The main difference is that you're using a Take Folder and Take Folders don't automatically add to the Comp when you extend their left side like that. Nor can you crossfade Take Folders. You can open the Take Folder and Swipe the beginning of the active Take to the left, but that still may leave an audible click between the Folders. One good way to accomplish this would be to Flatten the Take Folders without merging so you can still move things around. To do this, left click the Comp indicator, which in your case is the "B" next to "GTR Interlude: Comp C" and click Flatten. Be aware that this will get rid of the Take Folder. Personally, I would prefer turning all the Take Folders on that track to Track Alternatives at this point for this exact reason. It preserves all your Comps and Takes while allowing you to move, expand, and crossfade individual regions on the Active Track Alternative.

828es via USB, not using AVB. The second interface is a MOTU 4pre via Firewire. In the greater scheme of things, I think the greater theme of this thread might just be CoreAudio having issues occasionally and not really signaling to the user with how to fix it... which is indicated by many of our "fixes" involving restarting and toggling. Just a hunch.

Just another data point on this- I don't know if it's related but this started happening to me shortly after I transitioned to using an Aggregate Interface. When it happens, it occurs in every single project I've tried loading. And for clarification on my particular issue, when this happens all the individual channel meters in the mixer display no audio even when I am playing back. I'm talking about simple playback of a mix, not monitoring or anything like that. No activity on any of the meters in Logic's mixer. My Aggregate Interface is only used by Logic. The system uses one of my interfaces, same for system sound effects. Either way, it occurs in Logic regardless of the interface I select. Even in a new project with a single Apple Loop. It does not occur if I use the Mac Studio Speakers but I can't really get any work done like that so that's only helpful in an informational sense. The only way I have found to fix it is to reboot all my interfaces. Perhaps the order I boot them in is a factor, I haven't tested extensively outside of how to fix it. Maybe in my particular case it's more of a Core Audio issue and Logic is just showing me the symptoms.

I'm sorry, I forgot to mention that (when I ran into issues like this) turning off Smart Tempo only helped in newly imported audio or new projects. From my last project, it seems once they were analyzed by "Smart Tempo" then I had to undo it by re-importing the audio on a new track. There's a command or two for performing Flex Analysis again or making the audio into a new region but they didn't seem to work either. This might not be your issue but it sounds familiar to a last project where it kept calculating the audio I recorded at tempos like 120.11 or adding a bunch of redundant orange flex markers I couldn't delete when there was tempo automation.

Gracias. En Logic 10.7.5 Apple agregó la función muy útil "Smart Tempo". Creo que deberías apagarlo primero. No sé si ese es el problema, pero a veces "Smart Tempo" puede complicar algunas operaciones de Flex. Quizás esta captura puede ayudar:

As someone who had things working well in Monterey on my Mac Pro but had to upgrade to my M1 Studio Ultra due to other reasons- I do get where you’re coming from. After ruling out two peripherals that caused stability issues with macOS Ventura and Logic (a dock and a hard drive), the remaining problems were finally just various bugs in Logic and various unstable M1 Native versions of plugins. Peripherals aren’t going to cause Flex issues but if you’re experiencing crashes, panics, and beach balls (except beach balls while saving, that’s a Logic M1 Native bug) don’t skip this troubleshooting step… Many here may disagree but I personally found that, on macOS Ventura, Logic and nearly all the plugins I rely on are much more stable in Rosetta mode. You can tick a box in File Info to enable this. There are a handful of bugs that are only in native M1 Logic, but most of all I find that if an Intel build of a third party plugin was working to my satisfaction on Monterey, now it works well here too. The system is still miles more capable than my Mac Pro even with an emulator. The only weird thing is plugin validation works better in Native Logic so I had to enable Rosetta after installing all my plugins. I don’t make too extensive use of Flex so I’m not sure what bug you’re encountering when you say it’s going out of sync. What version of Logic were you running before you upgraded computers? Just curious what your reference point is.

Normalizing adds gain to an audio file/region to reach a specific amplitude. This would allow you to see whether or not anything is actually changing. If "Logic Pro automatically adjusts the volume level of Apple Loops so they play back at the optimum level when previewed in the Loop Browser or added to a project" then there would be no "loss of audio information," it might just be quieter or louder. This would only sound different until you brought them to the same volume. Normalizing the loop before and after will allow you to confirm this. To normalize in Logic Pro, in the Audio File Editor menu bar, choose Functions > Normalize (or press Control-N).

Normalize the loop before and after. Are they different after that?

A better way to do this would be to render the tracks to audio. That would get rid of the first issue. For the second issue, I'd consider utilizing the Live Loops mode. You can drag the rendered audio into there and trigger them as needed. When set up correctly, you can move from major to minor on a beat and prevent pops. Also, it may be unrelated now but when setting up Logic for performances, meta events can be very helpful https://support.apple.com/guide/logicpro/meta-events-lgcp2158b34e/mac