sunbrother

I stand corrected since it sounds like that's what Michael was doing. Side note, I really wish they'd clean up the issues with that. Feels kinda cheesy that they just threw up a dialog box many years ago that says "Don't do this, it doesn't work right." I remember the last time I tested dragging from one project to another to see if it worked and I could see Logic place the regions in some seemingly arbitrary place before re-arranging the regions and tracks to reflect where they should be. There's clearly room for improvement.

Thank you very much for digging into that. That's a piece of a Comp. If you right click a Comp it gives you those options. What a Comp from one track is doing in the middle of my Takes for another is beyond me. Whatever bug I ran into, it had to do with Group Editing, Take Folders, and Comps. I recorded these takes in a long pass then turned on an Editing-only Group and comp'ed it. I have the Fade Tool, Marquee Tool, Quick Swipe and Take Editing click zones enabled. I comp'ed this in a single pass, collapsing/uncollapsing the Take Folder and swiping takes. When using Click Zones it can be easy to split with the Marquee tool unintentionally which I Undo. Those are the only commands I would use. I don't usually have a habit of performing Quick Swipe from the Comp Track itself (on a collapsed take folder) but that's a possibility too. Well, that's one of my favorite takes. Perhaps I can copy the tracks, flatten and merge the main set, and unpack the copies for safekeeping. After unpacking, if that Comp region is there, I'll delete the overlapping Comp region that doesn't belong. Thanks again for going through that. It gives me some potential clues for a bug to look out for next time I'm comping a Group. To tie back to the original thought of Import being crash prone, it looks like in this case it's because it's an "integrity check" of sorts where a mistake Logic made earlier won't import.

I’ve seen the OPs issue and I never open more than one project in Logic.

This sounds like a known bug. It’s kind of hard to search this forum but there are a few posts about it. I think it can be caused by a few things. Undoing operations that unpack new tracks is one of them I think. Also I saw a post a while back that speculated that New with Next MIDI Channel can have something to do with it too, perhaps if it’s undone. Ive seen this happen before, luckily only twice.

OK, test away. https://www.dropbox.com/t/3wirsO8XxNkTOGbN Open a new empty project and: 1. open all files browser. 2. select the test project 3. open it in the all files browser 4. select 1 and (1) - (6) 5. click the checkbox for Content 6. Add/Import with the button in the lower right 7. Click Yes for Importing Tempo Information After #7 Logic Pro always crashes for me. Those files were simply recorded in Cycle mode in a few takes, nothing fancy.

If it's not possible what purpose was disabling Core Audio and importing the Content meant to serve? I might be misunderstanding your and @oscwilde's suggested troubleshooting.

Tested this on two computers. One is an M1 Studio with macOS 13.6.1 and one is a M1 Air with 13.6.3. 1. open Logic 2. disable Core Audio in Preferences > Audio 3. Open a new empty project 4. Create a software instrument or audio track. Expected result: it creates a track actual result: An error is given that the user has exceeded 1000 tracks, even though there isn't a single track in the project yet.

Nope, same result. Can't nudge a single note without it forgetting all my Beat Marker edits.

I've noticed something odd when I'm using the Smart Tempo Editor on MIDI (I'm more used to it with Audio). It's probably me being new to it. When I move a single MIDI note in a region that's already been Smart Tempo analyzed and had its Beat Markers edited, all my Beat Marker editing and the Smart Tempo analysis disappears. I used Undo to recover it but I'm wondering how I'm supposed to proceed from here. For reference, I did the following: 1) Recorded piano (MIDI, virtual instrument) and vocal (audio). Did not use click or change tempo. On a test run, Free recording was completely out of sync with what we played so I opted to just leave the tempo at 120 and turn the click off. 2) SMPTE locked the vocal. I'm planning to match the piano MIDI to the vocal first and then see which tempo irregularities I want to keep and which I don't. 3) Analyzed the tempo of the MIDI region containing the piano performance. It's Variable and has some fluctuation to it. Mainly sticks between 122 and 127 bpm, then very gradually goes down to 105 or so during a long outro. 4) Edited the Beat Markers in the Smart Tempo Editor for the MIDI region while in ADAPT mode. 5) Got everything sounding good and the click follows along with the piano player and the vocal by extension. Now here's the rub: I want to move a few notes that were dragging in the piano performance. Quantize works, but if I want to nudge them to be a little "off the grid" that I created with Smart Tempo, all my Smart Tempo edits in the Editor go away and it says I need to Re-Analyze the region. Does that mean I have to be okay with all the Scaling and Moving of the Beat Markers disappearing if I want to Nudge a single note? Or am I doing something wrong and there's some Lock function I'm supposed to use? I guess as long as I created the Tempo curves with Adapt I can say goodbye to the Beat Markers and work relative to the new grid, but it just seems odd to lose all that editing.

Thanks for the suggestion. It's pretty bizarre how all the Convolution reverb plugins I've tried face plant when you try to point them to anything but their built in libraries. Waves IR-1 even makes it difficult to access its own built in library! Shame their IRs are so good (imo of course).

Sounds like buggy behavior... I opened Logic on my other computer (M1 MacBook Air, macOS 13.6.3), disabled Core Audio, created a new empty project and got the same error as soon as I tried to create a single track. No importing necessary. Gotta love finding more buggy behavior when troubleshooting buggy behavior. If someone wants to test importing from a zipped and stripped-down version of the project feel free to PM me.

No. 1. I reduced the song down to 6 tracks and made a new empty project to import into for testing 2. I get that same error in New Empty Projects if I create them with Core Audio disabled. This is regardless of import/export so it's not a corrupt project. No sync. iCloud Drive is enabled but I don't use it in tandem with Logic. My projects are on my internal drive and I don't back them up to the cloud. Projects all stored as folders, not packages. Audio files are set to copy to the project folder or whatever. I have regular Time Machine backups and that's it. Symlinks and aliases... In what way? The only way I use them with Logic is I have aliases to my external drive in the Patches folder, but I barely ever even use the Patches function because of how limited it is. I use symlinks and aliases with other applications like Sononym for cataloging samples but not Logic.

Well, I guess you could call this a rogue track. I guess the difference is when I get a rogue track or whatever I wonder why it's happening. 🙂 I can't even test this. If I disable Core Audio then attempt to import it says "You have added the maximum number of Audio tracks (1000) to your song. Delete one or more Audio tracks before adding another Software Instrument track." If I create a new song it won't even let me add my first track. I get the same error. Does this work for you? I also tested recording audio into a new song from my template, then trying to import that Content into a new song and using the Tempo Information. It worked, so I think it's safe to say my Template is not corrupt at least.

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.