No products in the cart.
I’m new here so if this has been covered already plz excuse ;-))
I get this weird thing where Logic 11.2.2 pops up a window saying something about ‘Extra Midi Inputs’, it’s just annoying and I have to close this notification window before Logic will open.
For def I only get this message on projects which have an instance of SD3 instantiated.
Issue has been bugging me a long time, I’ve slowly managed to narrow it down to one factor: the presence of SD3.
Has anyone else experienced this and if so, does anyone know the fix?
You are concerned over the wrong thing in this case. This is not an issue as it is Logic doing its proper job by reporting any changes to CoreMIDI. Superior Drummer add new MIDI channels when loaded. Logic is acknowledging those channels.
You should be more concerned if those notifications stop happening.
jord
Fair enough, Jordan, thanks for your input. But since I don’t see Logic reporting new midi channels with any other of my 1000+ plugs (Omnisphere, Falcon, Addictive Drums etc) I have to ask myself – and the board – ‘Why is SD3 unique in this annoying manner?’
Frankly I don’t want to be notified in this way, it’s a pain tbh.
Why can’t Toontrack set up the AU SD3 so that it just invisibly creates these extra channels but does not have to get in my face and tell me every time like some hyperdiligent rubberneck?
Of course you’re right that I should be worried if the channels were not created for some obscure reason and then, yes, then I would wanna be notified of this, definitely.
The answer is quite simple: your other instruments don’t provide MIDI output channels to CoreMIDI for Logic. Superior Drummer provides MIDI output capabilities into Logic. This feature is hardly annoying and is doing it in standard CoreMIDI fashion. Logic sees it no differently than turning a MIDI piece of hardware off and on. Logic is simply reporting the changes and is hardly something to be annoyed about
Again this is not Superior Drummer but Logic doing its job.
you can always check the system preferences to see if you can disable Logic’s notifications. However, don’t blame Logic when things are going wrong and you aren’t notified as you should be
jord
1
Thanked by: Scott EshlemanYou are most probably more technically knowledgeable than I am but as far as I know Omnisphere, for instance, provides midi output capabilities in Logic Pro.
If it truly did, CoreMIDI, and Logic subsequently would acknowledge it. I think you’re confusing multi-out with MIDI out as far as Omnisphere goes.
jord
You would probably know better than I but here’s what an AI overview says re Omni offering core audio and midi functions… I know AI can be wrong tho
Yes, Omnisphere provides core audio and MIDI functionality through its standalone application and as a plugin within a Digital Audio Workstation (DAW). It allows for both audio and MIDI output, enabling users to integrate it into their music production workflows
AI also tells you how many rocks you should eat on a daily basis for a balanced diet.
Try quoting directly from the reference manual for a real answer. BTW, I’m looking at it right now.
jord
1
Thanked by: Scott EshlemanHehe, obviously I never read manuals (if I can possibly help it)
I’m sure you’re right about Omni, and it’s good to know at least that neither Logic or SD3 are misfunctioning.
But I still feel the rightness of my original point, ie I can see the validity of a notification telling me that midi channels or connections have not been set up correctly but I cannot see the point of a message which tells me with tiresome regularity about something which is totally fine, which needs no adjustment or looking into, a notification which interrupts – ten times a day – the smooth loading of Logic.
You explain this as ‘Logic doing its work properly’. Once again you’re right I’m sure, but I’m gonna raise this in a Logic forum and see what the experts say over there.
Cheerz for your input.
Hehe, obviously I never read manuals (if I can possibly help it)
As if this needed posting? 😉
but that’s too bad because he would probably understand this whole process better if you did.
But I still feel the rightness of my original point
it’s more your misunderstanding in your original post as well as the following.
I can see the validity of a notification telling me that midi channels or connections have not been set up correctly
firstly, that would not be a notification. if something went wrong, you would get an alert in which you a dialogue box would appear in the center of the screen and disrupting your entire process. This also emphasizes your lack of understanding on how CoreMIDI works as well as publish and subscribe methodology.
notifications are used for signaling changes in configuration. This is exactly what Superior Drummer is doing. it is specifically registering a new MIDI device with CoreMIDI. CoreMIDI is a dynamic framework, which allows you to add and remove devices on the fly. it also takes advantage of the agnostic nature of MIDI. in other words CoreMIDI is like, honey badger: it don’t care who is registering a new device. It sees Superior Drummer no different than it would see eDrums. CoreMIDI also allows any application to subscribe to it, so that any changes in the configuration will be automatically reported to the application. In this case, Logic is doing just that: subscribing to CoreMIDI and is getting a change. It is doing its part by reporting the change to the user through a non-intrusive notification. This is the correct behavior. If I were to turn off my keyboard, I would expect that Logic would tell me that I lost my MIDI device. Once I turn my keyboard back on, I would expect Logic to recognize that and tell me as well. Superior Drummer is a software instrument as well as a MIDI device. The behavior is correct, in how it is being handled.
but I cannot see the point of a message which tells me with tiresome regularity about something which is totally fine, which needs no adjustment or looking into, a notification which interrupts – ten times a day – the smooth loading of Logic.
It is changing the MIDI configuration map. This is a real change to MIDI routing and logic is doing its job properly by reporting this change. However you are incorrect in that it is interrupting logic’s operation. It is not interrupting the flow of logic. In fact, you can do everything you are doing while these notifications are happening. in fact the only time you will be interrupted is if you add a new CoreAudio device. Reason being is because that actually would have to cause Logic to reload where changes in CoreMIDI do not.
there’s nothing unusual going on between Superior Drummer and Logic. The fact that you are annoyed with such a normal and rather expected operation is, honestly, a little weird.
jord
No products in the cart.