oscwilde

A test you might like to try is to only run the video on your main screen/Logic video track (or window on the same - primary - screen). Test with the second monitor running (but no video)....i.e. just the desktop on the second screen. If it crashes, physically turn off/disconnect the second monitor and re-test. A further option to try....and this is gonna sound a little counter-intuitive, but can you launch Logic in Rosetta mode and load the problematic project? (I'm assuming your plug-ins work in both native/Intel modes.) While there's a CPU hit with Rosetta, your rig isn't being challenged...but it might be stable. Would be interesting to see if the errors are thrown (anywhere...but particularly at the same spot).

Just make sure "native" monitor resolutions are used seems to be the key thing when running multiple displays with M-series Macs. If the problem crops up again, let us know.

You should consider a pair Doug....then you'd be one of the "cool kids" 😉

This thread solution might be relevant.

The error in the log points to a graphic problem. Have you changed the display configuration in any way - and are you trying to run video on the second monitor?

Sounds like fun. Is there a reason why external MIDI tracks/instruments are used - rather than using a built-in software instrument on student iPads? This simplifies the entire process - bouncing and/or transferring of projects between iPads/the Mac. i.e. students could compose/save a project using Alchemy or Retro Synth, or whatever, and process (and easily bounce) directly on the iPad....or they could do the above and then transfer/open the project on the Mac - as settings/plug-ins, etc. are directly transferrable between the platforms. Similarly, a project started on the Mac can be opened on the iPad - if no third-party plug-ins are used. The primary issue with using the external instrument plug on LP4iPad is that the app is (currently) limited to stereo I/O. In practical terms, using a multi I/O interface is the most (only???) efficient way to use the external instrument plug-in.

Is there a question here? You can insert tuners on channel strips and can bypass them when not needed. There's also a global tuner utility available in the Transport bar.

Kind of a catch-22 with TB interfaces with this sort of I/O...and the cost - if looking at a direct replacement. I don't know the 2626 facilities, but can it be used as a pre - linked to another interface via ADAT? If so, something simpler/less expensive might act as a (reliable) bridge. Really depends on your needs/budget and space/whether or not you want to work like this/add another interface or have an all-in-one solution.

Yes. As @David Nahmani explained the Reason instrument is not installed on your system, but is installed on the school Mac. Yes, you can bounce the Reason parts as audio and save them with the project, for further work on your Mac. Note that the work possible will be limited to audio manipulation/processing/mixing - you won't be able to edit notes etc. in the Piano Roll, like you can with MIDI data.

In essence, your friend needs someone with a current Mac/MacOS version to make the purchase on their machine (say your Mac) - using your friend's Apple ID credentials. The purchase is tied to this Apple ID. Once made, logging in with their Apple ID on "any" Mac (capable of running Logic), will allow them to download the appropriate Logic version for their MacOS. For Monterey this will be Logic 10.7.9. See this thread:

Yep...a good discussion can fix this at the source. Moving (dancing) singers don't realise the impact this has - particularly if new to the recording process - when perfoming in front of a sensitive studio condensor. There's also a "doesn't matter, just fix it in the mix" headspace - given the ability of modern tools to actually do this - but old-school (or just old 😂) engineers/producers lean toward "get the recording right in the first place". Spending 10 minutes with new singers on (studio) mic technique might save you hours later.

OK....then looking thru the crash log, there were a number of specific plug-ins listed...Fabfilter, Izotope, etc. that were used in the project. - it might be one of these....or a particular combo of plug-ins that is not exiting cleanly with Logic Given Melodyne/ARA appear in the log, I'd assume you're running in Rosetta mode? Can you actually work in Native mode or are you reliant on certain plugs/features that don't run on Apple Silicon? Unfortunately, there's no quick way to check for misbehaving plug-ins....as it's a plug-in by plug-in thing (or combo of plug-ins by combo of plug-ins thing). As a Q, did you migrate an install from an older Mac or did you reinstall Logic and all plug-ins, drivers, etc. from scratch on the M3?

Is this set to Standard in the Menu bar?

Skipped over? Are your note edits visible in the Undo History? If so, click on the appropriate edit and it will revert.

Look at the Transport bar. It should be visible there...but if not, customize it to always display Sample rate. You can also check this in the Project Settings. Fair enough...and pretty cool.