No products in the cart.
Bear-Faced Cow
Participant
Topics Started: 30
Replies Created: 3014
Has Thanked: 266
Been Thanked: 1071
I’m not sure what you’re getting at here. I drag grooves into Logic all the time without issue. In this case, are you using the standard default mapping when playing the grooves?
it might provide a bit more insight if you post your Superior Drummer project.
jord
mappings are one way and are for reading whatever MIDI instrument data into Superior Drummer. Exporting MIDI from Superior Drummer is always in its own format.
If you want to export from Superior Drummer into Logic without affecting the original MIDI track, create a new track for the same instrument and drag your MIDI there.
jord
What Scott said… don’t use follow host when exporting using either the tempo map or setting the tempo markers. Follow host in this case would be useful for real time bouncing into your DAW.
jord
Again, are you setting the tempo markers within the Tracker? Tempo issues will result from not ensuring that your downbeats are aligned.
jord
To start, the tracker, and any drum replacement for that matter, is only as good as the audio that you are feeding it. I don’t see any indication of the type of audio and the quality that you are using.
As far as time and hits, did you set the tempo markers for each bar as well as the threshold for each instrument?
jord
Picture’s worth a thousand words.
This is not disruptive in any way. I am able to work this Superior Drummer and load my desired library/preset while this notification is showing. Same goes if I turn off any of my MIDI controllers.
This is disruptive.
If you are getting anything different, then either you are using an ancient version of either Logic/Mac OS in which it is on you and not ToonTrack. Or you have something poorly configured in your OS which is again on you.
jord
1
Thanked by: Scott EshlemanHehe, 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
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 EshlemanIf 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
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 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
It is not poorly named. Rescanning your grooves for its information is the process in which it restores the MIDI database.
jord
No products in the cart.