Logic 10.7.4 Monterey M1 pro crashing on Patch track stack such as Producer Drumkits

[icalone]

Logic 10.7.4 Monterey M1 pro is crashing on Patch with multi-timbral aux tracks such as Producer Drumkits.  When I load a producer kit from the library on a fresh "new" Logic project, and then I start selecting any of the internal aux tracks of the individual drum sounds, Logic immediately crashes.  This also happens on multi-output (and multi-timbral) instruments such as Omnisphere and other plugins setup like a producer kit as a track stack

Other non-track stack patches play fine it seems.

Brand new Macbook Pro M1 pro with fresh installs all around on Logic and plugins. 

[David Nahmani]

Try to create a new user account on your Mac and see if you can reproduce that issue in the new account? 

[icalone]

David,  After working on this a bit I've realized that the problem is running deeper than just Producer Kits-Multi Output Patches.  After testing further, now I realize that other patches are also crashing Logic (never ending spinning wheel). And that even opening the Library on audio tracks is crashing Logic most of the time.  So I feel this is possibly a more general Logic Library issue.  So... on my old 2016 MBP, awhile ago I moved the Logic factory Library to an external drive to save space.  That external drive also had my Kontakt Libraries, etc. When I set up my new M1 machine with Logic, I naturally now have been using that external drive with the new machine.  Now, on the newer M1 machine when I installed Logic, I believed I pointed Logic's factory content to be installed to the local harddrive (and not the external).  So, maybe there is something going on now that Logic on the M1 is also seeing/indexing what's on the external drive and it's causing the crashes. Currently I'm moving Logic's Factory content folders off that external drive and we'll see what happens.

Edited May 21, 2022 by icalone
typo

[icalone]

I moved the Apple and Logic Library folders from the external drive. On the M1, I also re-downloaded and re-installed the Logic content to its local harddrive.  Started Logic (without any peripherals or HD's attached) and still, I am experiencing the same crashing going with the same library procedures.  My M1 was set up by my IT dept. and they have the admin/system level access, so I don't feel comfortable (until I can talk with them on Monday) about creating another User account to test it.  Is there any other file such as a .plist file or similar that I could try deleting?  I already tried resetting preferences in Logic's menu.  thanks!

 

Edited May 21, 2022 by icalone

[icalone]

Ok so I think I may have figured it out (for now).  In my user channel strip folder on the M1 computer, I had some aliases in there to other channel strip folders  (Bus --> Audio, Audio --> Bus, etc..)  I had originally set these up in my old computer, and then when I was setting up the M1, just copied these folders over  to the M1 computer like you would normally do.  So, I deleted all the alias folders and everything seems to be working now.  Then I went back in to the M1's channel strip folder and tried to create some new fresh aliases in the same way.  I put an alias of the Bus folder into the Track folder, and this worked.  But, when I put an alias of the Track folder into the Bus folder, Logic crashes when I access the Library from an Aux/Bus track in Logic.  Not sure why this is.  It seemed to work on my older intel Mac (10.5.1 and Mojave)

Understand what I'm trying to do here?  The reason I do this is, since bus/aux and audio tracks have the same plugin structure (it seems), when I create say an audio track plugin flow that I like and I want to save it to the library, I may at times want to have that same plugin setup to be on an Aux/bus track as well.  This is the reason for the aliases.