MCU for audio only?

drbam wrote on 7/26/2006, 5:18 PM
I've been thinking about getting a controller and since the MCU appears to be the most reliable unit with Vegas, I thought this may be the way to go. However, I was looking at the Vegas overlay on the Mackie site and it looks like about half of the functions on the overlay apply to video. Of course this makes sense given the direction Vegas has taken. But as an audio only Vegas user, I don't want to spend $1000 on something that looks as much like a video controller as it does audio. It seems to me it'd be like keeping all the video windows visable in Vegas while doing audio only – confusing and full of needless clutter to say the least. So my questions are, am I missing something here? how do you audio only users find working with the MCU? Are there other templates or other ways of working with it that makes it totally viable as an audio controller for Vegas? I don't want to spend another dime on features I don't need nor want - especially as it relates to Vegas.

Thanks!

Comments

pwppch wrote on 7/26/2006, 7:17 PM
Half? Not really. Don't see how you concluded this by looking at the overlay. It clearly indicates that buttons that have dual purpose depending on whether the surface is in audio or video mode. (Like th Shift key functionality is also indicated.)

There are very few Video mode specific functions for the MCU. Where the MCU/Mixer model mapped between audio and video, we exposed them.

If you never touch the "Video" mode button on the MCU, the MCU is 99% audio. There is only one Video centric button that is mapped in audio mode : Show/Hide Video Preview window.

When in Audio mode, all of the faders, knobs, track buttons, and Control functions work on the audio aspect/features of Vegas.

Simple answer: MCU was implemented with Audio in mind first.

Peter
drbam wrote on 7/26/2006, 8:11 PM
Thanks Peter. Obviously I mis-understood the overlay terminology, jargon, whatever. I looked at virtually every other overlay, and Vegas's was the only one that did not appear intuitive to me (most likely because of the dual-purpose buttons, regardless of whether they're clearly marked). Most all of the other overlays used terminology that immediate felt familiar. The weird irony is that I only use Vegas, SF & Acid, and am not familiar with any of the others apps that have MCU overlays. At any rate, thanks again for clarifying it.
pwppch wrote on 7/27/2006, 7:45 AM
What is not familar?
Can you provide examples?

What terminology on the template did you not understand?

Pan, Output, Input, Inserts, Setting, Track, Bus, Mixer, Plugins, Automation, Bypass FX, Metronome, Surround, Downmix, DIM, Marker, Region, Loop, Mark-in, Mark-Out, RTZ, Pre/Post, Pan mode, Undo/Redo, Input Monitor, Meters, TimeFormat, Automation Mode, etc, etc.

The only Video specific terms on the template are:

Compositing, Motion Blur, and Fade To Color.

While some of the terms/labels are Vegas specific - Regions, Event Trim - I can't imagine them not being understood by an audio centric user.

Please, I'd like some input and comparisons between those MCU templates that you felt were clear in their terminology.

Thanks,
Peter

drbam wrote on 7/27/2006, 10:46 AM
Peter:

I really don't wish to get into a debate about this. These terms: "Compositing, Motion Blur, and Fade To Color" most likely jumped out at me like some flashing neon lights because I still feel resentful about how Vegas audio users were pretty much abandoned in order to pursue the video market. Right, wrong or indifferent, that's the way many of us feel and you of all people are keenly aware of it. In handsight, I see that I overreacted to the MCU overlay thing because it pushed a sore spot. Its clearly my issue and I apologize if I was inappropriate or offended anyone with my comments. Thanks again for clarifying the MCU question for me – I'll probably choose it when I'm ready to get into a controller.

Peace,

drbam
pwppch wrote on 7/27/2006, 6:27 PM
Not looking for a debate - really. There is absolutely no need to appologize. You said/asked nothing wrong in my book. (Even if you are just venting frustration, there is nothing wrong with that.)

Just wanted to know what specifically was confusing you. I just want to make sure that I wasn't missing something when I designed the layout for the template and the mappings on the MCU.

I am very aware of how you and others feel.

Vegas is as Vegas does.

Peter