mySoftware [Updates]

Once you create a user profile on Motifator and update with the appropriate information, the updates shown here will be specific to you.

newProducts [YOK]

rssFeeds [Syndicate]


forumforum
 

Old Motifator threads are available in the Archive.

Viewing topic "BadMister - VST Editor Question if I may….."

     
Posted on: February 17, 2009 @ 12:56 PM
boulez
Total Posts:  669
Joined  02-12-2007
status: Guru

This is a “what is the intended purpose” sort of question and I realise there will be several approaches and applications

Looking at the Cubase screenshot you posted with ‘all outputs activated’

I wonder if you would give a little clarity to what the particular Cubase tracks in this shot are intended to do

I can see (and create here) the MIDI track with 8 instrument tracks and one Group FX (I think) track. How can each instrument track adrress a different voice of the XS and therefore be (as you say) Mutli-Timbral. I instictively want to give each Instrument track a different MIDI channel which would achieve what I am asking but can’t see how to do that.

or .......

Have I got it wrong (as I sense I have) and are the 8 instrument tracks in fact the audio lanes of the MIDI track and do they therefore represent the 8 stereo returns from the XS? If so, why, in the inspector do I see only audio ouput (and not input routing).

This would then raise the question “ How can I set up Cubase such that I have (say) 16 MIDI tracks and have each track play a different voice of the XS with the XS returning the audio to (say) 16 Cubase tracks”? - (in a similar way to having 16 MIDI tracks each with its own instance of Halion each with a different voice)

I realise there is much confusion above but hopefully, you will (with your experise), be able to see what I am finding confusing and then clarify.

We have already spent quite some time so please don;t think we are being ‘lazy’ here :)

B

Thanks.

PS We have the MediaBay integration working but more of your thoughts and tips on that feature would be most welcome.

  [ Ignore ]  

Posted on: February 17, 2009 @ 08:39 PM
Bad_Mister
Avatar
Total Posts:  36620
Joined  07-30-2002
status: Moderator

In general, when you want to use the Motif XS as a multi-timbral tone engine (and it is fair to assume that this will be the most common usage)… you do not want to use an INSTRUMENT TRACK.

An INSTRUMENT TRACK (by Steinberg definition) is for when you are only using the device in question for a stereo output.

INSTRUMENT TRACK ................................................

Restrictions
• MIDI volume and pan cannot be controlled (there is no “MIDI fader” section in the Inspector); instead, the VST Instrument volume and pan are used (via the “Channel” section in the Inspector). This applies also to the respective automation parameters.
_ Due to there being only one volume and pan control for the instrument track, the Mute button will mute the complete track, including the VST Instrument. (As opposed to a MIDI track with an assigned VST Instrument, for which muting the MIDI track still allows you to monitor and record the VST Instrument.)

• Instrument tracks always have one stereo output channel only. This means that VST Instruments that do not provide a stereo output as their first output channel cannot be used with instrument tracks.
• Due to the limit of one output channel, instrument tracks play only the first voice of multi-timbral VST Instruments. If you want to use all voices, you have to set up a MIDI channel in combination with the multi-timbral VST Instrument like in normal VST handling.

Conclusion
• The instrument track is the easiest application of a VST Instrument in a MIDI track. It is well-suited for automation.
• However, the instrument track is unsuited for instrument setups with multi-timbral instruments or for setups with incompatible restrictions, e.g. a MIDI device that never sends on the first channel or only has mono output. In cases like these, use a MIDI track.

.................................................................

So from this explanation, you would only use the Motif XS VST with an INSTRUMENT TRACK when your goal is simply to use Cubase automation on a project and/or you are only using one sound from your Motif XS. Not when you want to use it with a multi-timbral setup. In the coming weeks we will have a tutorial on how to use the INSTRUMENT TRACK - but you are asking about the “ACTIVATE OUTPUTS” Function… Which would be used when you are using the Motif XS multi-timbrally.

Initially, when you go to DEVICES > VST INSTRUMENTS and you select EXTERNAL > MOTIF XS VST… it will ask you if you want to create a MIDI track. A MIDI TRACK is (as I’m sure you know) where you can record MIDI your data, *typically* you create a MIDI Track for each MIDI channel. I say ‘typically’, because you can use a single track if set the MIDI track so that Channel = “ANY”. You only need to DISSOLVE PARTS when you need to edit a mistake… but typically, most users find it useful to create a separate MIDI track for each Channel. You simply need to point the OUTPUT of that MIDI track to “Motif XS VST”.

(I personally have found it more convenient to work with a single MIDI track set to Channel = ANY because it makes navigating the Track view much simpler)

Our tutorial will take you through both methods. The MIDI Tracks are where you record your MIDI Data… the audio lanes are for RETURNING audio (the MIDI track data travels to the tone generator of the Motif XS which outputs audio. The Returning audio can then be processed in Cubase with VST EFFECTS, automation, etc., etc. this returning audio is found in the so called “audio lane”.

When you activate, say, all 8 of the stereo Outputs, it creates 8 audio lanes. How signal gets assigned to those lanes will depend on the what mLAN OUTPUTS you route that signal to…

How you decide to route signal will depend on where and how you wish to process (effect) that data. Routing something to an individual (mLAN Output) takes it out of the System Effects of the XS and isolates it on a stereo bus. But the routing to these OUTPUTS takes place, (most importantly) in the Motif XS.

Keep your MIDI tracks (as the ultimate level of UNDO/REDO) and commit parts to audio using either Motif XS processing, Cubase VST Effects, or both as your project dictates.  The options that this brings to the mix (pun intended) is great. The danger in any explanation is that you might think there is one way to work…

There is not. It is extremely flexible.

You asked transferring MIDI tracks to audio tracks:
The short answer would be in a minimum of two passes. The question does not really include the thinking through to your final product. You do not need or you may not need to transfer each of your MIDI tracks to separate audio tracks. You are thinking very single (or at best, two) dimensionally.

You should be thinking what PARTS from my Motif XS would benefit from processing with external effects (say those you have in Cubase as VST Effects)… what tracks do I simply need to use the current processing available in the Motif XS.

Example: I just finished a Project with the following Motif XS tracks:
Horn section - made from 5 tracks: Trumpet, Alto Sax, Trombone, Bari Sax, and Brass ensemble
Rhythm section - made from 4 tracks: Organ, Bass, Guitar and Drums.

I setup the guitar with several VST EFFECTS and printed it as audio (using Export)… The original MIDI data I dragged into a FOLDER Track labeled MIDI… I now Mute that Folder. My new processed guitar has 2 Insertion Effects from the XS and I assigned a Tube Distortion and Flanger from my arsenal of VST Effects in Cubase.

Instead of thinking in box, where I’m processing everything all at once I concentrate my effects (and my resources) on what I’m doing at the moment.

I only render to individual audio tracks data I need to processes specially. Otherwise the tracks are routed to the L&R;(Main) outputs which have the Motif XS System Effects.

  [ Ignore ]  

Posted on: February 17, 2009 @ 11:12 PM
boulez
Total Posts:  669
Joined  02-12-2007
status: Guru

Thank you very much.

This clarifies much of what was confusing and the real example you gave is very helpful indeed.

Looking forward to the tutorials to come on this item,

Regards,

B

  [ Ignore ]