External Control

ChrisBo wrote on 7/13/2005, 3:12 PM
I'm finally figuring out external control on my friend's Vegas 5 rig. he has a Yamaha O1v96v2 (2.04 to be exact) You would think SOMEONE would have more information on this. After reading in this forum, I'm resigned to the fact that I need to map the board myself, the problem is that I'm having trouble understanding what the Vegas patch program is describing. Once it's done, I'm happy to post it, but I'm looking for help with definitions. Using GM control on the Yamaha, I can get it to control the "Trim" in Vegas, but when I turn automation on, the Yamaha's faders moves are no longer recognized. I haven't even tried to manipulate more than that yet. Any ideas of where to find more info on terminology? Does Version 6 do any better?

Comments

TielBr wrote on 7/16/2005, 11:13 PM
I responded with how to map the board yourself at first,... but then after reading again, I'm thinking you're asking something else alltogether.

I use the Mackie MCU, so there's probaly a few differences, but I can confirm/clairify that the MCU has an "automation Mode" button, that when pressed, switches the entire board, faders and all, to your automation settings. (which, if un modified previously will be all 0db.) If you set the automation control in vegas to one of the "write" settings. (latch or touch) The next time you play back the track, Vegas will record your control movements, and will repeat them automaticaly on subsequant playbacks. If it's on "read", then it will do nothing. Also, if you turn off automation, the board returns to the standard edit mode. When you play back now, your edits still take place, but they are not visually apparant on the board.

Is this even remotely what you are asking...?
PipelineAudio wrote on 7/17/2005, 4:39 PM
It wont do you too much good mapping the board yourself, as vegas doesnt seem to send midi info back to the control surface, so changes made in vegas will not be reflected on your controller.

Yamaha is aware of the need for MCU emulation, but it sure wouldnt hurt if you told them that too. The more users we can get onboard the better
ChrisBo wrote on 7/18/2005, 9:40 AM
That's all helpful to know, but not really what I'm asking. The issue for me is that Vegas will read fader moves for 'trim" (non-autiomation mode) until I put Vegas into autiomation mode, then Vegas will not respond to fader moves, and as a result I cannot record automation.
PipelineAudio wrote on 7/18/2005, 10:34 AM
on the channels to record automation, click "show automation controls"

and you will be set
bakerja wrote on 1/12/2006, 7:47 AM
I am having this problem also with a new M-audio projectmix I/O.

Doing what pipelineAudio suggests does not make the M-audio control the faders in automation mode. It in fact takes the fader control away from the M-audio. Automation can still be accomplished with the mouse, but the goal is to mix on the m-audio.

I only hooked the thing up last night and am sure that I am missing something, but if anyone out there has any experience with mackie control and automation, specifically the m-audio desk, it would be greatly appreciated.

Thanks,
JAB
pwppch wrote on 1/12/2006, 2:58 PM
You need to define a key/button on your surface to switch to automation control for the surface.

I assume you are using the Generic Control driver:

From the configuration page, set the "View function group" to

Assign

You will note:
Toggle Automation Mode
Automation Mode On
Automation Mode Off

Assign EITHER the Toggle or each of on/off functions.

What this does is then tell the surface driver to send Automation msgs vs trim msgs.

For those that use a device that emulates a Mackie MCU, determine what button the emulated device uses to map to the MCU Automation On button. Use this then to toggle the surface into and out of automation mode.

Peter


bakerja wrote on 1/13/2006, 6:18 AM
Thanks Peter,

This will help. I will dive into it.

JAB