des99

Um... Yeah, scr*w that guy! ☺️

No, *future* fisherking is running LP11.

Thanks - I'll do what I'm doing then, keeping the h2ps for the internal patch browser, and having aupreset copies for Logic. 👍 Now we just need Logic's preset browser to get good... *tap fingers*

Yeah I know. It's not the end of the world - it is what it is for now - we can always go again next year, or do a different poll later on. It was really to get a flavour of where we are now, anyway...

Honestly, I thought I'd get more than four days before having to deal with this, but there you go! 😁 I've added an LP11 option now.

Keyboard Maestro Yes, so I saved myself about a thousand clicks converting all the presets, stuff I've download, and commercial soundbanks I have... 😉 I put them in a separate "Logic Library" folder which I access in Logic's browser, and deleted all the h2p files from those copies, and left the regular h2p's for browsing in Zebra if I want (I'm not sure whether there's any downside between the formats in use). I always know where they go... for me, ~/Library/Audio/Presets, always. You mean root and user - yes, this is a standard Mac feature, and it exists for good reasons - you should know why macOS does this, if you don't already. Sure, you can put what you want in those folders. You'll only see the relevant files given the context anyway. Sure. Everyone has different ideas of how to implement presets, whether to include their own browsers, file formats and a whole bunch of other implementation decisions - it's why plugin presets are a mess generally, and a big part of the reason for this thread to attempt to standardise preset access to some degree. 👍

No wonder David's been busy recently... he's got more chapters to add to the book... 😉

Yes, no change, but it's never reliably opened *all* 5.x or 6.x songs anyway, but 7.x projects are reliable to open. It can *sometimes* open 5.x or 6.x songs but it depends on things that I've never been able to reliably determine.

Let's all thank the Apple brass for not mentioning the "subsr*****" word in this announcement...

Well, if you need more channels than 16, you need more ports. With Notator, you could have up to 7 I believe (four with Log3 and another three with Export). Cubase also had MIDI port expanders, and then later, multiport MIDI interfaces were a thing - I've had an 8 port emagic AMT8 for over twenty years now too... The MIDI spec just describes what happens over a MIDI cable (effectively, one port). It doesn't say anything about having multiple ports, nor does that affect the spec in any way.

Future des99 responds: "Clearly my Logic poll was the trigger for launching a new version... and you're welcome! 😉 "

Yep, I've done this too. I use KM so I just select a folder, and press a key, and KM selects the presets and converts to native format, which is waaaayyy faster than doing them the way I have to for other plugins...

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.