![]() ![]() But this is cumbersome and could be much improved. So it’s still necessary to scroll down to the “VST Instruments” folder and find the corresponding audio output for the MIDI track, of which there are very many (and AFAIK Cubase can't select the output track automatically for you).Ī workaround is to move each and every VST Instrument output out of the “VST Instruments” folder, place it below its MIDI track and use Cubase 8’s “hide others” option in the new visibility menu. However, when set up in the above manner, it’s impossible to edit the automation for the audio output from within the MIDI channel (and MIDI automation doesn’t address the same functions, of course). In my case this works wonders when it comes to workflow, especially when you have a large number of tracks in your template. You can also rename the output to match the MIDI track name which is very useful. ![]() I switched to Cubase from Logic for two reasons, Expression Maps and the possibility to see, in the Inspector of any MIDI track, the corresponding audio fader and sends/inserts without having to go to the mixer or dig up audio channels. VEP Instance 1 MIDI Channel 1 -> Virtual Instrument in VEP with Output 1-2Ĭubase MIDI track has Output 1-2 selected in the Fader section of its Inspector The Cubase template has MIDI tracks set up accordingly, one per VEP instrument.Ĭubase MIDI track -> VEP Instance 1 on MIDI Channel 1 The Instrument Rack in Cubase holds a couple of VEP plugin interfaces which connect to VEP and have many outputs enabled (around 80 per instance). ![]() I work almost exclusively with Vienna Ensemble Pro, which holds a very large virtual instruments template. "Now that with Cubase Pro 8 the line is blurring between Instrument Tracks and the Instrument Rack, I’d like to add a suggestion with the hope that a developer at Steinberg might actually read this. Lots of Cubase/Nuendo users must run into this problem is my guessĭid anybody find a solution for this or is this dealt with in Cubase 9 ? I found article below on the Steinberg forum
0 Comments
Leave a Reply. |