As long as you’re using the Toolkit templates for Dorico and Cubase, then the complicated Network MIDI is likely already working – that’s the good news. But, sometimes the signal path can breakdown within Cubase (due to every person’s computer being a bit different). So, check that the VE Pro rack instrument in Cubase is connected to a VE Pro instance… here’s how:
In Cubase, expand the folder called “Rack Instruments”, then expand the subfolder “CT_PPC_BS” and select the rack instrument’s “CT_PPC_BS” track.
Open the left zone inspector and click the “Edit Instrument” button to view the VE Pro rack instrument window. Then you should see this:
You’ll want to confirm that you see the same thing as the above screenshot (the VE Pro rack instrument is connected to a VE Pro instance called “CT_PPC_BS”). Is this what you see? If not, do you have the Network Orchestra VE Pro template loaded and does it contain an instance called “CT_PPC_BS”?
Software Crashing or Writing Phantom Notes?
Double check your Dorico Preferences to make sure that the Bome MIDI ports are disabled as inputs. In the Preferences > Play section look for a subsection titled “MIDI Input Devices”. In there you’ll see a bunch of checkboxes representing the ports in Bome. All the Bome instrument ports (both Src and Dest) must be unchecked. Otherwise, MIDI goes out of Dorico, back into Dorico and can really slow down your computer or even force the software to crash.
TXL Configuration or Cursors Not Syncing?
In Dorico, after opening the Network Orchestra template, open the TXL plugin window and check that the MTC messages are routed to a MIDI port that accessible to both Dorico and Cubase. This is how MIDI Timecode (MTC) is sent between the softwares and is required for Cubase to sync its cursor/playhead to Dorico.
On my Mac, I’ve created a port in the IAC driver using the built-in Audio MIDI Setup application. The port is called “TXL” and this is what my TXL port setup looks like (and I recommend it for you, too).
In Cubase’s Transport > Project Synchronization Setup dialog, change “Timecode Source” on the “Sources” tab to “MIDI Timecode”. This should add a new setting to the window called “MIDI Input” under a heading “MIDI Timecode Settings”. In that dropdown box, you need to choose the same MIDI Port that was chosen in the TXL window. This tells Cubase where to listen for MTC.
Testing (When Do You Know It’s Working)?
Write some notes in Dorico and play them back, so that you can see what’s happening in Cubase. (I use the cycle/loop playback feature in Dorico to make it play the same bar of music over and over while I troubleshoot).
While the notes are looping on playback, switch to your Cubase window and look at the MIDI track for the instrument that is playing in Dorico (e.g. Piano). Do you see the level/indicator on the MIDI track in Cubase showing that a MIDI signal is being recieved (even if you don’t hear the right sound, this is the first question to answer)?
Make sure the Cubase track is monitor enabled and look for the level meter on the MIDI track to indicate MIDI input is being received.
You can also add a “MIDI Monitor” MIDI Insert to the Piano track and see if it indicates MIDI input on the track. To do this, open the left zone inspector in Cubase with the Piano track selected and open the MIDI Inserts section, then add a MIDI Monitor insert and see if there are messages in the window while Dorico is ‘playing’. What do you see?
Misc. Tips
Windows and Mac both have built-in firewalls that can break network MIDI communication that needs to occur between Dorico and Cubase (via Bome). Check your firewall settings for your computer. I have my Mac firewall turned off, but if you choose to use a firewall then be aware that Bome may need certain ports configured in order for MIDI to flow properly.