I was wondering. When I open a new project and select via the project assistance the Yamaha MOTIFXS8 with VST editor I noticed that the VST connection inputs are set to:

MOTIFXSAD port MOTIFXS8 13 and 14. Why is that?

When I have some midi data on midi track on track 01 and I want to record that as audio using the XS8 tone generator the audio track expect audio to MOTIFXS8 13 and 14 because that is set in the VST connections routing.

THis means I have to set the voice output in the XS8 to m13&m14;.

When I do that I am able to record the midi track 01 as audio to m13&m14;.

Am I right or am I wrong. What do I not understand here?

Jan

I was wondering. When I open a new project and select via the project assistance the Yamaha MOTIFXS8 with VST editor I noticed that the VST connection inputs are set to:

MOTIFXSAD port MOTIFXS8 13 and 14.

When I have some midi data on midi track on track 01 and I want to record that as audio using the XS8 tone generator the audio track expect audio to MOTIFXS8 13 and 14 because that is set in the VST connections routing.

THis means I have to set the voice output in the XS8 to m13&m14;.

When I do that I am able to record the midi track 01 as audio to m13&m14;.

Am I right or am I wrong. What do I not understand here?

When you select a template via the project assistant, you inherit the setting for that particular template. You should not use this template unless it serves your particular purpose.

The template tries to make assumptions about how you are going to setup to record. I am a big believer in learning how to make the assignments yourself. Then if you find that you always set up a certain way, then SAVE your setup a project assistant starting point… You do so by going to FILE and “Save As Template”

In the template you have selected: Motif XS8 with VST Editor
The OUTPUT SELECT parameters are changed so that PART 1 is going to the main LR output
PART 2 is routed to m1/2
PART 3 is routed to m3/4
Etc…
PART 7 is routed to m11/12
And the A/D INPUT is routed to m13/14

Now it would be a wild guess as to what you would need to route where. I’ve done lots of recording with the XS and XF and have never ever used this particular arrangement. The OUTPUT SELECT parameter is what changes here and is a decision I make based on the music and the project.

Any PART assigned to L/R will go through the SYSTEM EFFECTs and the main left/right outputs
Any PART assigned to a mLAN output will be removed from the SYSTEM EFFECTs and the main L/R outputs and travel a discreet route to DAW.

See screen shot 1 for the OUTPUT SELECT setting of the template you selected
See the second screen shot for the OUTPUT assignment of the Audio Parts.

The thing you are missing - if you are missing anything at all is - YOU can (and SHOULD) change the OUTPUT SELECT parameter to suit what YOU want to do. If you want to send PART 1 to m1/2 simply change the setting. You can do it on the EDITOR, you can do it in the Motif XS - either place it is the same OUTPUT SELECT parameter. The TEMPLATE only makes it easy if it is exactly what YOU want to do. If not, CHANGE IT!

Click thumbnail to see full-size image

Bad Mister,

Thanks. I agree. Most of the times I do make my own routing setup, but I just stumbled to that project assistance screen and opened a new project with it and tried it out and saw those VST connections setting.

I was just wondering about that MOTIFXS AD setting to 13/14.

Remains one question:

when I change the output select in the MOTIF VST Editor of a particular track and I did not change that voice output also in the MOTIFXS8. Audio of that midi track will not be recorded on a Cubase audio track armed with that changed voice output as input via output select in the VST editor.

I have to change that particular voice output in the XS8 as well.

Or do I misunderstand this procedure?

Thanks in advance for your answer.

Jan

Bad Mister,

It seems to work now, although I am not sure why it does now and not yesterday.? Maybe it has something to do that I changed the direction on the setup screen into MOTIFXS to PC, instead of PC to MOTIFXS, although I am not sure that was the problem.