des99

It doesn't need to look different for every update, it just needs to get better. They haven't changed how Logic looks or works, so that stuff will be essentially the same. The marketing images will be accurate, Apple don't mess up with that stuff.

I was literally watching the live event when I saw David's post... I'm more interested in Logic 11 than iPads, so it's paused half way through and has been for a while now... 😉

I think most of us look at the big shiny things and go, "Oh, OK, cool I guess" but we're often more interested in the minutiae of the update notes... 😉 Don't be quick to judge, there's often a lot more improvements than the tent pole marketing upgrade features.

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...