OFS

Yup, makes sense. Thanks for your help!

Hey des99, thanks for your help. It got me to solve the problem. So, the thing is, I have the habit of deleting the VST2 versions of the plugins when the installer doesn’t allow me to choose which formats I want to install. When you suggested the problem is related to the installation I re-installed one of the plugins, kept the VST2 file, and let Logic perform the validation which now worked. It also started working in Studio One, which showed the KORG plugins with no GUI, even when I dragged the VST3 version. Admittedly, I should be more careful about deleting the VST2 files, but it never caused me trouble before, and I would never thought that deleting VSTx files could affect the AU versions, since in my mind they were separate code. I conclude from this, that the AU and VST3 versions of the KORG plugins are nothing more than wrappers for the VST2 version and they don’t even contain the VST2 code inside their files - they require the presence of the VST2 file to run. Interesting stuff… Anyway, thanks for your help, you got me on the right track!

Hello, Is anyone having trouble using the KORG Collection 4 plugin synths in Logic? I recently purchased the latest version and installed the latest version of all included plugins and some of the plugins fail the AU validation in Logic Pro. I've also tried re-scanning and it didn't work. The following is a list of the plugins that don't work: - LegacyCell - M1 - MS-20 - MonoPoly - Polysix - Wavestation The rest of the plugins in KORG Collection 4 work fine. I've tried re-installing the full suite and got the same results. Can you help me resolve this issue? Thanks, Miguel Barrosa

Fully agree with everything and I’d add that the UI itself for naming the buses must be updated - it should be possible and easy to change the order of the buses. That radio-button thing doesn’t make any sense for that purpose.

Hello. Sorry to revive an old thread, but I’m attempting to come back to use Logic more regularly after spending 2 years with Studio One and getting frustrated with its quirks. However, I’m just being reminded of Logic’s own quirks, and not being able to store the I/O setup per session is one of my pet peeves. I think it makes no sense at all to have it being a global setting, especially if one likes to keep the bus naming clean as the naming, inevitably changes over time as you add/remove stuff from templates. Plus hardware changes, same computer used in different places, etc. There’s a reason Pro Tools has this nailed. @David Nahmani if you have some contact with the development team (I don’t know if you do) and if you agree that this should be changed (and have the time and patience), maybe you can make the suggestion. Saving multiple preference files is a clear hack and shouldn’t have to be done. This is one of those things that I feel that it’s been this way for so long, that it’s forgotten and won’t ever change, unfortunately…

The fact that no one replied to this thread shows that, unfortunately, not many people seem interested in what you’re talking about. I’m with you 100%, this drives me nuts. I think I/O labels should be saved with the session file so that when later down the line you change your labels, old sessions don’t get messed up with a send to a “Delay” that now is a “Reverb”. I think Pro Tools has this nailed, the IO labelling section is very complete. At the very least they could change the stupid IO setup window (I HATE that dialog…) and make the lines draggable up and down so you can add a new reverb or something to an upper slot without having to copy and paste EVERY SINGLE LINE below the position you want to insert one line down!

Hello, I can’t install the latest Logic version because I’m still in Catalina, but I’d assume that they didn’t change anything. To be clear, the script I made was never required, I just felt that it made the drummer patterns sound closer to the original when going through SD3, especially regarding the hi-hat. Some people seem to agree with me, others don’t as you can read here: https://www.toontrack.com/forums/topic/logic-drummer-to-superior-drummer-3-midi-mapping/

Hi David, thanks for your help, once again. I must set aside time to really understand the MacOS Audio/MIDI Studio so I don't fear it anymore...

Hi Dewdman42, I have a sort of primal fear about the Audio MIDI setup in MacOS. Not as much as with the Logic Environment but pretty close... Anyway, thanks for your advice, between these three choices I think I can get it done.

David, you’re the man! It’s amazing how you always seem to know how to solve the most obscure problems. Thanks! Also thanks to Venk Ivanov, your solution seems easier although it costs money. I’ll check the plugin, if it’s not too expensive I may buy it.

Hello everyone, I'm using a Scripter plugin with some MIDI note transformations in order to better map Logic's Drummer sounds to an external drum plugin (Superior Drummer 3). I'd like to know a way to make a new MIDI track that is the result of the original MIDI track plus the transformations made by the Scripter plugin, sort of like a "MIDI bounce" including the Scripter plugin changes. Anyone know how I can do this? Thanks! Miguel Barrosa

Ok David, thanks! Anyone else ever had this happen, or is it just a weird thing on my sessions?

Thanks David. This never happened to you, then?

Hi David, thanks for the reply. I've attached the project, I'm curious to see if it happens to you on your system. I've already reported this thing to Apple twice, but so far the issue remains, even in 10.6. Maybe if you tell them they'll listen VCA Selection Bug.zip

This one also happens to me and it drives me mental! And not only with aux channels, sometimes software instrument tracks. Every new update I pray they fix this but, no, never...