I know that I knew this at one time, but we all get stuck in certain ways of doing things. Your explanations are so good that it triggers new inspiration for a different way to accomplish a task. Thank you for these.
Thank you Anthony. It's been some time since I used Cubase regularly and although much of this information is revision for me, your approach is very helpful and easy to follow. You've put a lot of effort into these and it's really appreciated. Warm regards from Sydney - Dav
Great quality Anthony, everything well explained. One of the best who informs about Cubase. (As good as Dom and Chris ;-). More people should follow you. Thnx!!
Excellent information, thank you for sharing your knowledge my friend. Learned again a few new things, also good to refresh memory. You explain so clearly Anthony, so easy to understand. I love that piece of music. It's available to download for free from public domain. I played the piece on piano, not fluent yet, though.
Anthony, your way of thinking and explaining things so that the people can understand them, is amazing. Keep on having the same attitude and doing the same type of content. In the ocean of terrible and skilless youtubers who mislead the people into watching their nonsense videos, your channel is a treasure. Do you know if it is possible to connect 3 X MOTU Midi Express XT USB (8 MIDI outputs and 8 MIDI inputs) midi interfaces (48 midi ports with 768 midi channels in total) directly to a PC/DAW (directly means in paralell, not in series)? I use Cubase 11 Pro. Will Cubase Pro be able to see and process all those midi ports and channels? I would like to be able to simultaneously and directly connect (via MIDI DIN 5-pin cables) up to 24 synths/groove boxes, etc to my DAW. No midi thru / daisy chaining between devices to avoid the complex midi-related problems many people encounter (the audio and/or the midi data of different devices arive in Cubase at different times, etc). If the PC and Cubase Pro will allow it, I bet this would work flawlesly and every midi device will have its own port, its own 16 midi channels, its own dedicated midi track in my Cubase template, and it will be available at all times - a perfect setup for relaxing and being creative. This type of connection will also allow Cubase and any of the midi devices to become the master clock (provided the respective device has that ability) and to control any or all the other devices at the same time. This can be done very easy just by selecting the midi output of the source-device in the midi input dialog of the destination-device track/tracks inside Cubase. To further avoid the midi-related problems I was talking about earlier, I will keep all the devices connected to the PC through MIDI DIN 5-pin cables only. In the case of the devices that have both "audio through usb" and "midi through usb", if I would like to connect them to the PC through usb (for "audio through usb" - I doubt that) I would disconnect the "midi through usb" connection inside Cubase. What do you think about that? A bit cheaper option would be to buy just 1 MOTU Midi Express XT USB midi interface (8 MIDI inputs and 8 MIDI outputs), and on the way from the midi interface to the midi devices to put a midi splitter/thru box (like the "Kenton MIDI thru 25" - 1 midi input and 25 midi outputs), and on the way back, from the midi devices to the midi interface to put 3 X 8to1 mergers (like the Kenton merge 8). But as I understand (please correct me if I'm wrong), those splitters and mergers do not retain the ports and their channels' information - they merge all ports and all their channels into 1 port with 1 channel, it copies it and it sends it to all the midi devices and, on the way back, to all the midi interface's ports that the mergers connect to. And that will ruin all the dexterity - no more 1 track-1port-1midi device-16 channels. Please correct me where I am wrong. P.S. - I didn't started to build my new studio yet. At the moment I have less than 16 devices and 2 X Motu midi interfaces would do it. I'm just thinking that in the future I will exceed 16 units and I will have to buy the 3rd midi interface. So it would be better to start with what gives me the possibility to expand when needed. I do not want to risk by mixing models or brands in the future. If you know of a better solution, I would appreciate if you would share it. Thank you in advantage and I'm wishing you a wonderful day!
Thanks very much for your kind message, and many apologies for the delay in my reply. Cubase should be able to easily handle any number of MIDI devices that you connect to it. Unfortunately I'm not the best person to give you advice on that topic, since my MIDI setup is actually fairly simple, and I try to restrict my comments to those from personal experience. I suggest you re-post your question on the Cubase forum - hopefully someone with a setup similar to the one your describe can comment: forums.steinberg.net/c/cubase/6
@OneManAndHisSongs Hi, Anthony. Thanks for the reply! I just talked to Kenton UK, the company that makes the midi thru and midi merger boxes. The solution is simpler than I thought. I misunderstood something. The outputs ports of the above-mentioned 2 boxes (Kenton midi thru 12 and Kenton merge 8) retain all the information that comes through their midi input ports. In the case of the "midi thru 12" box, the exact input info is multiplied 12 times and sent through EACH of the 12 output ports to 12 different devices which can use any or all the 16 channels that come from the midi interface to the "midi thru 12" input port. The "Kenton midi merge 8" merges 8 ports that come from 8 midi devices and all their channels and data, into a single port with 16 (? - I forgot to ask) channels which can be connected to one of the Motu midi express xt midi interface. As this midi interface has 8 midi input ports and 8 midi output ports, it can drive up to 128 midi devices. So, there is no need to buy 3 midi interfaces in the case I presented above. For a 24 midi devices setup, only 1 X Motu Express xt, 2 X Kenton midi thru 12 and 3 X Kenton merge 8 are needed. The Kenton only makes midi thru 12 and midi thru 25 boxes. No midi thru 16. So, in the case of midi thru 12 box, 4 midi channels are extra and can only be assigned to the already connected 12 devices (because there is no physical connection to connect 4 more midi devices). In the case of midi thru 25, you can connect up to 25 midi devices, but use only 16 channels (as there are only 16 channels per port). Using this setup and the same brand and length of cables, leaves no place for midi and audio misalignment, other than that of the midi devices processing the midi info in different ways :)))
Thanks you very much for your tutorial. Basic? it's possible, but fundamental for many persons. For mi , it's genial explanation. Good and beautiful theme for th example Midi. Musicals salutations😊😉
Thanks you! Yes, I deliberately wanted to start with the basics since if you don't understand these terms everything else can seem very confusing. Hope you enjoy the rest of the series :)
anyone having issues with the way the new cubase 12 midi ad controller function in the lower project window is either not recognizing or some midi ports are missing when trying to add a new device.
Hi, on my midi keyboard the pads are set on input channel 10, the keys on ch 1, but in Cubase I can t route or even have the option to select separate input midi channels. I want to play 2instruments track at the same time so the pads for some drum loops and the keys for some synths, the only way I have found is the midi input transformer, but only on pro version, not elements. I can t understand why this isn t mede more simply by Steinberg
That sounds odd. I can only imagine it's a function of the version of Cubase you're running, but it seems such an intrinsic requirement I'm very surprised.
Hey Anthony thanks for this. I'm trying to do something different and couldn't quite get it from the video: I'd like to use my external hardware keyboard to input the midi notes, but then I would like to send the midi notes back to my keyboard and use the sounds of the keyboard itself rather than a VST. So, midi notes trigger "live" keyboard sound. Any ideas?
I don't have a keyboard with onboard sounds, so I'm not really the one to help, but I think you need to activate MIDI Thru (in the Preferences/MIDI page), then output the MIDI to your keyboard using its dedicated MIDI Port. You might be better asking someone who uses that feature though: the Cubase forum is generally pretty good for general questions: forums.steinberg.net/c/cubase/6
I can’t get my behringer TD-3 to trigger and play with Cubase… Tried everything, every Midi setting I can think of, no joy. For some reason I just won’t start it. It will on the other hand send midi notes to a track but that not what I want…. It works perfectly fine in Akai Studio 2 DAW though but it’s just a long way round of doing things.
Did you try posting a request for help on the Cubase forums? They're hit & miss, but sometimes someone will have exactly the answer you're looking for. forums.steinberg.net/c/cubase/6
Sir, had an issue. I have two Midi connected to cubase and one of those have a faulty pitch bend. So I use other keyboard for pitch and other stuff. I was wondering how can I disable cubase to read Pitch bend signals from the faulty midi and keep the pitch bend signal in from oth3r midi I could do this in studio one. But not in cubase. Newly switched
Thank you for you amazing videos Is there anyway to invert a Midi signal in Cubase? i assign some buttons to do something but when I press those buttons and they light up..... Cubase receives it as an Off signal, and when they turn it off, Cubase take it as an On signal
You're welcome, thanks for the feedback! It's not Cubase that's doing that - it's your device. If you have a look at Episode 4 in this series (ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-8C-n_Xmatic.html) you can see examples of me configuring my NI Komplete & NI Maschine devices to transmit the correct messages to Cubase to achieve the effect I'm after. Somewhere in your device's management software you'll have the option (hopefully!) to invert the states of the commands it's transmitting.
Hi Anthony, I'm having an issue with Komplete Kontrol when used as a plugin on Cubase and I was wondering if you know the answer to my question. When selectin an instrument channel that has Komplete Kontrol loaded on it as a as plugin on Cubase, my hardware keyboard (S88 MK2) is displaying the "Midi" screen instead of the "Plug-In" screen and there's nothing I can press on the hardware instrument to change that and start browsing sounds. Instead, I need to open the software plugin on Cubase and click on the little keyboard icon to make it connect to my hardware S88 properly, show the "Plug-In" screen, and let me browse the library from the hardware keyboard. I'm suspecting it has something to do with the Midi information not being sent from Cubase to my hardware keyboard. Do you know how I can configure things so that my hardware keyboard automatically connects to the right instance of Komplete Kontrol when I select the channel that the plugin is loaded on? I know this is possible because it used to function exactly that way in the past before it suddenly stopped doing it one day.
I'm afraid I'm not the person to ask, since I actually allow my Komplete to enter MIDI mode, preferring to control everything from within Cubase. You might have more luck posting your question in (both?) the Cubase and NI forums - hopefully someone on either side of the fence knows the answer.
on the NI s mk2 range plugin is for nks compatible and midi for standard midicc. So in Komplete Kontrol everything is a plugin not midi but when your out of Kontrol then a vst is a midi. If your in Kontrol you use browser for Kontakt and your other nks compliant instruments should show up? It should never leave plugin unless your browsing your available instruments? If this is not the case KK is broken so I would start it in standalone and see after a rescan it should fix the problem. I guess you can switch out of nks mode into midicc by pressing the midi button but why would you when KK is your loader? So in answer to your issue, KK is the issue if this happens on all instruments, reinstall it
