des99

My suggestion was to upload a test project. When you went into more detail regarding your import crashing, I just said does it do the same thing with core audio disabled to rule out plugin crashes. I didn’t know Logics behaviour in this regard, that’s all.

Yep, but in this case, the error that’s displayed is somewhat misleading, especially as you can have projects loaded, with audio objects, with core audio disabled…

? It really doesn't. Yes, a MIDI port (just like a MIDI cable) *always* handles up to 16 channels. That's part of the MIDI specification. If you want to pass multiple sets of 16 MIDI channels to a single device or application, that's why you use multiple ports (for instance, my XV-5080, which can handle 32 MIDI channels, has two (real) MIDI ports on it). All that's happening there is Kontakt is receiving MIDI from the host - the same old 16 incoming MIDI channels. You can see that Kontakt (as a feature) supports other input ports, but these are "not available" in your screenshot because they are not a thing in this context. If you run Kontakt in standalone mode, then Kontakt is responsible for MIDI I/O, and it can receive MIDI from multiple devices/ports (up to four, by the looks, which it labels - arbitrarily - as A through D) - so in it's MIDI Settings, you can enable multiple MIDI ports, and so have, for instance, one keyboard playing one loading Kontakt instrument, and a different keyboard, coming in on a different MIDI port, playing another loaded instrument. But it's just a Kontakt label - you're basically using it's MIDI settings to say 'Hey, treat the MIDI port from my audio interface as "A", and the MIDI port from my USB keyboard as "B"', and can just route accordingly inside Kontakt (as you can't otherwise label those A/B/C/D ports as "Audio interface" and "MIDI keyboard" or something more descriptive). None of that has anything to do with the MIDI specification, it's simply a Kontakt feature of handling multiple MIDI ports in standalone mode. it's also irrelevant in Logic, which handles all the MIDI I/O when Kontakt is running as a plugin (which is why there is no MIDI Settings menu in this context), has a 16 channel bottleneck, and why only the default set of 16 channels (which in this context, Kontakt arbitrarily calls "A") is available, and the multiple port feature is not available. All instruments in Logic on a track receive one MIDI ports' worth of data, 16 channels. Logic does have more multi-port MIDI routing options these days though, they finally eliminated the painful MIDI sequencer bottleneck in the environment (but kinda bypassing it) but all the above is still true - it just gives more flexibility in MIDI routing in the main window.

I don't know what this "MIDI Port A" you are referring to is? Is this a port that your MIDI interface creates on your system? There is no "MIDI Port A" on a Mac unless an application, or MIDI device driver, creates one, but I have no idea what's on your system. Perhaps if you can do a screenshot of what you are referring to that might give some clues as to what you're referring to..?

Can confirm this here. I think that's a bug in how this is handled for sure.

Yes, if you sent to the IAC bus, those events will come back into Logic. Correct - it's just regular incoming MIDI data, which Logic will handle in the usual ways. A virtual MIDI port is simply a virtual MIDI "cable" that can route the regular 16 channels of MIDI between applications. The Mac comes with the IAC bus which can be used for this by default, but macOS apps can create their own MIDI ports as required.

Try trashing your AudioUnit cache file. You can try quitting Logic and running "killall -9 AudioComponentRegistrar" then restarting Logic. Do the plugins show up in another host - say, the free HostingAU, or show up in PlugInfo (or again in terminal, with "auval -l")..? Are the plugins supported on your new computer/macOS version? if you reinstall one of the ones that doesn't work, does it work now?

Then your plugin is required to output MIDI from itself. As we mentioned above, Logic doesn't support this. You'll need to output to a virtual MIDI port directly, bring that back into Logic, handle the routing from there - if that's something that can work for your application.

You might need to reinstall and/or reauthorise the ones that aren't working.

Remember, AU plugins in Logic can't *output* MIDI back to Logic - it's simply not supported. The *track* itself will output MIDI to an instrument plugin (or any other environment object), but it won't go any further. You'd have to output the track to an environment object, and distribute it on from there, but this doesn't include any MIDI outputs from plugins. If that's what you want to do (again, I have no idea what your plugin does), but if your plugin needs to output MIDI, then you'll need to directly output to the MIDI IAC bus (ie, to the MIDI port directly), and have it then come back into Logic.

How familiar are you with Logic's Environment? I don't know what your plugin does or how it functions, but you can distribute MIDI to environment objects using the Environment (every track in Logic has an environment object assigned to it). You can also send MIDI out of Logic and back in using the IAC bus, which has helped for certain workflows too.

I meant to mention - in the past, one of the things that prevents being able to save out plugin patches as presets was not being able to "pick up" the patch name, in order to name the saved patch with the same name. For plugins that don't have a way of doing this, I've resorted to a range of workarounds depending on the plugin, but one of the benefits of moving to a more modern macOS version on Apple silicon is being able to leverage the built-in technologies. Now, using Keyboard Maestro's "OCR Area" command, set to use Apple's built-in macOS text recognition engine instead of the old KM one (the Apple engine is really good, especially for something as predictable as a UI-rendered font), you can literally on the fly OCR the plugin display of patch names on screen to a variable in order to pick up otherwise unretrievable names. This means even plugins that were impractical to do before are now fairly straightforward. 👍 This is but one of the many challenges and problems I've had to workaround over the years of doing this. One pet annoyance is what Tal-Pha does (but it's not the only one) - you can't simply step through the patches using the next patch button in order to save the patches out per bank one-by-one, because as soon as you save a preset, the synth's internal state is reset and the synth always goes back to patch 1... grr...

No, a "crash" is a specific thing in computers. Ok, that's likely you are overloading a core with the plugins you are running. In other words, the plugins on a channel are requiring more CPU to process than one core can manage. You can narrow it down to see which particular plugins are doing this, but likely it's because they are not optimised correctly for Apple silicon.

I don't see how far apart they are matters - Command-clicking a track will add it to a selection. Scroll to the next track, Command-click it to add it to your track selection. Or you can select one track, scroll, and then Shift-click to select all tracks up to the selected track. What version of Logic are you on?

IR files don't show up in those menus - plugin settings are what show up in the menus. Loading an IR is a different procedure to loading a Space Designer preset. Import your IR to SD, set the plugin settings as you wish, and then save the plugin preset as required. Now you just reload that preset from the menus when you want to use it. You have to do this for all IR's you want to save quick access to, if you don't want to always load them manually from the IR's files. There was a utility that would do this automatically I think, but I ended up scripting it with Keyboard Maestro for a while, until I got tired to not being able to quickly access downloaded IR libraries (as SD is a bit tedious/clunky auditioning IR's), and instead moved to LiquidSonic's Reverberate 3, which handles IR libraries much more comfortably...