sunbrother

Yes, most of the time that’s how it works. But a significant portion of the time it will crash during this process. The only reason I mentioned “respective computers” etc was to emphasize that I’ve seen this problem many times over the years on different computers. It varies. Either 1) while sitting there looking at the list of tracks in the Files Browser, 2) after attempting to Add tracks/buses, or 3) if I try to use the Tempo information of the imported tracks. In this current case it crashes after I click Add and then confirm in the dialog to use the Tempo Information. I’ll try doing it without Core Audio since I have a recent test case in mind. I guess I’m assuming the import feature has never crashed for you either since David said he’s never seen it crash?

All of the projects I'm discussing opened as expected in those computers' respective versions of Logic. On my current computer, the projects I've experienced this with all open as expected. Side note, I remember from some beta testing of a plug-in host that a frequent cause of third party plugin crashes are related to them trying to (as far as I understand) do GUI related operations at the wrong time. Even if I assume all the times where the Files Browser would close prematurely are due to things like that, why would it be so hit and miss to simply import Content using the respective check box? That shouldn't involve plug-ins at all, right? I have a current project that exhibits this behavior. If I select to use Tempo Information after importing the Content, Logic crashes 100% of the time.

All four computers I’ve owned over the last few years were formatted APFS.

I might just do that. I'm having a hard time believing it's just project corruption. That would mean throughout the years most of the projects I've tried to import from were corrupted. Is it really that easy for projects to be corrupted?

Is it just me or is importing from other Projects in the "All Files" Browser just plain crash prone? I came back to using Logic about four years ago and in that whole time period spanning Mojave to Ventura on three separate machines I've found that this feature seems to crash more than any other. Usually I'm importing a few tracks straight into an empty project and only ticking the Content box. Occasionally I'm trying to import a full set of tracks with all their inserts. Whatever I'm doing, there always seems to be something that makes it crash. This time it would crash only if I chose to import the Tempo data. Maybe 1/3 of the time the Files Browser will just close as I'm deciding what content to import from within the project before throwing a crash report. I remember this happened on my old computers too, lest someone thinks it's something related to a specific internal or external drive. I'm willing to believe that 3rd party plugins can crash an import (I remember this being a potential issue in any DAW that had this feature) but why does it so frequently crash when I'm just importing the Content? Anyone else have a similar experience?

What about the file lengths? Are any of them unexpectedly small, such as 40 KB?

This happens when Logic accidentally truncates an audio file. Usually if you go to your Audio Files folder within the Project folder or package the affected audio files will be much smaller than they should be or sometimes have a very recent modification date. If you find a backup of those files and replace them the regions will go back to normal and the error will disappear. Even though I’ve only seen this problem twice, I’ve started backing up my Audio Files folder after recording sessions to counteract this problem. There’s a whole inconclusive thread about this issue here but the only takeaway so far is: nobody knows what causes it, it can happen on very basic setups, and backing up the Audio Files folder helps.

Me too, but so far it seems to occur in all of the last projects I've done. If I leave Plugin Latency Compensation set to "All" then about 25% of the time I record Logic will have gotten into a state where it will print a significant delay to my recorded tracks. At least I assume it's Logic since using a different Plugin Latency Compensation setting fixes it/prevents it. It may be a Core Audio issue that Logic is simply interacting with and then showing the symptoms of. Software monitoring is off and low latency mode off. I don't think low latency mode impacts this in my case as I did a lot of recording in one project it and didn't have low latency mode engaged but left Plugin Latency Compensation at "Audio and Software Instruments". The problem never showed up.

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.