The Beringher XTouch work quite well with Vegas and is not too expensive. Otherwise you have the Mackie MCU Pro that work with Vegas since a long time.

I was wondering if any of you guys have tried this LogicKeyboard, pre-programmed specifically for Vegas Pro.

@KeyplayerG - No I haven’t.

Frankly, I am amazed at how difficult it is to find a "VEGAS CONTROLLER!" It seems to me that pretty much every other Video Program has one. FCP & Media Composer work on Eucon.

@KeyplayerG - Difficult? Sure. However Vegas started life as a DAW and since then, and making it appealing, I guess, to as many people as possible, it’s always had Mackie Emulation. I can’t speak for “pretty much every other Video Program has one.” However, I feel your frustration. Bespoke Hardware hasn’t been high on the VP philosophy. But I’ve made a solution which is getting me there.

I desperately need a controller for Vegas BECAUSE I'm not a Video Editor. I'm a Media Composer.

Yup, it’s tough.

But I can't even get Vegas to see the controller even through the generic MIDI protocol. 😠 

I’m using Mackie Emulation with my PreSonus FaderPro8. Do try that. I’ve got a multi track project using 6 tracks and 4 Busses with SFx Envelopes, Pan and Volume. I can Write, Latch etc.

I’m giving you all this feedback to reassure you by what I’m getting so that they just to see if there are other ways you could possibly make better links.

It depends very much on what you want the hardware controller to do in Vegas. Certainly the Artist Series should work OK for controlling audio within Vegas since it is Mackie protocol compliant. What else you can get it to do depends on how much time you are prepared to customise what it does in Vegas.

 

I’m using Mackie Emulation with my PreSonus FaderPro8. Do try that. I’ve got a multi track project using 6 tracks and 4 Busses with SFx Envelopes, Pan and Volume. I can Write, Latch etc.

I’m giving you all this feedback to reassure you by what I’m getting so that they just to see if there are other ways you could possibly make better links.

Hi Grazie, I'm still working through figuring out exactly what I can and can't do with my Behringer X-Touch One with MCU control within Vegas.

I was curious with your experience with the FP8 if you discovered if any event editing features could be assigned.

More specifically my most common keyboard shortcut editing functions I would love to assign to buttons on the MCU.

S=Split

NUM 4/6= Nudge Event left/Right

NUM 8/2= Move Event up/down track

I was curious with your experience with the FP8 if you discovered if any event editing features could be assigned.

@Rednroll - Hi there! I just crawled all over the MCU Drop down lists of options. Edits? Nada, zilch. Have you looked yourself?

More specifically my most common keyboard shortcut editing functions I would love to assign to buttons on the MCU.

Yeah, but no. I don't see anything that would or could be. There ARE unassigned options, but how would I do anything with 'em, this is well above my pay-grade.

S=Split

NUM 4/6= Nudge Event left/Right

NUM 8/2= Move Event up/down track

For these I could assign to my CSP and be done.

Thanks, that was what I kind of figured as well.

I just got a BT numeric keypad but I'm sending it back. It doesn't seem to be responding quick enough to button presses. So I'm currently looking into other options. What would be kind of cool was that if I could use a small tablet as a keyboard. That way I could arrange buttons and label them as I wished. I'm going to look into that, to see if there's any software which would provide that type of functionality.

Edit:

Here looks like there may be some solutions.

https://windowsreport.com/use-android-pc-keyboard-usb/

I currently have some Win8.1 6in and 8in screen tablets, I'm currently not using. I'm thinking it would be cool if I could put them to use by making them a dedicated configurable keyboard to remotely control my laptop which has Vegas installed on it.

It depends very much on what you want the hardware controller to do in Vegas. Certainly the Artist Series should work OK for controlling audio within Vegas since it is Mackie protocol compliant. What else you can get it to do depends on how much time you are prepared to customise what it does in Vegas.

"SHOULD" is absolutely the operative word here. The reality is that it doesn't. There is no discernible "handshake" between the 2, not one "single sign of life" at all! I've gone over the instructions, connections, cables, etc. dozens of times and it SHOULD work, however limited. But it doesn't. Whereas I've seen tutorial videos for Artist Series with FCP and it works instantly just like my DAW!

As for what I want it to do, that's simple. I just want the most basic "meat and Potatoes" kind of functions: Import/Export, Copy/Paste, Activate Text, Range Selection, Render (Audio &/or Video), Open in Trimmer, Zoom....literally the most basic stuff. I don't need plug-in mapping or any upper level audio stuff because all of that is being taken care of in Nuendo.

But, as I said, My Artist Series hardware is a "paper weight" with Vegas. 😒😕😠

In that case I would go for something designed for controlling Vegas ie. the Contour Shuttle Pro. They are a fraction of the cost of any of the Avid Artist series and will easily allow you to do what you want for just a 'pocket money' price. 😉 if you really want to use your Artist controllers then you will have to move over to some compatible video NLE software I'm afraid.

@Rednroll - Hi there! I just crawled all over the MCU Drop down lists of options. Edits? Nada, zilch. Have you looked yourself.

@Grazie

Hi Grazie,

I'm continuing to dig through all the Vegas MCU button assignment mappings. Just an FYI, I did find an event editing function, just in case you're interested and haven't found it yet.

MCU command button assignment CLICK=EVENT TRIM in Vegas. Pressing that button will cause the cursor to jump to the next event edge and highlight the edge red to indicate you are in EVENT TRIM mode. Then you can trim the event edge by 1 Frame using the the JOG/SHUTTLE wheel. If you turn the ZOOM button on, it will then trim the event edge by 1 Pixel, which is zoom dependent trimming. While the CLICK/EVENT TRIM button is on, you can then use the RIGHT/LEFT cursor buttons to jump to the next event edge to do further trimming.

I've got a pretty good Excel sheet going now with most of the MCU button assignments, and their Vegas mappings along with the SHIFT, ALT, and CTRL modifier function assignments. I haven't completed it yet, but have spent quite a few hours working through it.

For the time being, If interested see EVENT TRIM on pages 501-503 in VP16 manual.

@Rednroll - ooo... That sounds interesting: CLICK=EVENT TRIM : Where did you see it in amongst all the MCU Dropdowns? I treble looked at the Transport, etc etc but could find that.

Trackview.EventTrimMode.ToggleEventTrimMode perhaps?

Maybe this can help you. I did printed it to use it as an overlay when I had a Mackie Control

@Grazie

Here's what I've been doing.

I look at the Vegas Overlay that goes over the top of the original Mackie Universal Controller as @Adi-W posted.

I then compare that to the original Mackie Universal Controller labels, where in this case EVENT TRIM=CLICK button.

I then look at my Behringer X-Touch ONE to confirm if it also has a CLICK button and confirm that button is assigned to MCU command CLICK .

In the event if I run into an MCU available command which is not already assigned to a button on my X-Touch ONE, I then look at this list of assignable button MCU commands and assign it to a button.

I then dig into the Vegas 16 Pro owner's manual to further figure out how the command is suppose to work, which in this case is the EVENT TRIM button.

Then I test it out and confirm if it works that way.

Pretty simple huh? ;) This isn't what you've been doing with your Fader Port 8 when configuring it for MCU operation mode with Vegas?

As I mentioned, as I'm going through this entire process, I've been creating an Excel sheet with all this cross reference mapping information, so that when I'm done I'll have a quick reference sheet.

This is what it looks like for this particular CLICK=EVENT TRIM button.

Pretty simple huh? ;)

@Rednroll - Yeah, right... Well done you, well done 👍.

This isn't what you've been doing with your Fader Port 8 when configuring it for MCU operation mode with Vegas?

Nope. Once I’d worked out the connectivity, no mean feet for me, the FP8 just worked, I didn’t need to do any further assigning.

Pretty simple huh? ;)

@Rednroll - Yeah, right... Well done you, well done 👍.

This isn't what you've been doing with your Fader Port 8 when configuring it for MCU operation mode with Vegas?

Nope. Once I’d worked out the connectivity, no mean feet for me, the FP8 just worked, I didn’t need to do any further assigning.

Yep your FP8 likely just worked since I believe it is natively supported by Vegas and Vegas will automatically re-assign the buttons on the FP8 for you when you select "PreSonus Faderport Driver" as your available device so that it matches up with the Vegas overlay for the FP8.

Where with the X-Touch ONE it also just worked but, I have to select the Emulated MCU driver since native support doesn't yet exist in Vegas and then I have to manually configure some of the buttons on my X-Touch ONE to get the functionality I wanted. Doing this could be useful for you as well, since you're just using the button assignments as the developers considered were most important to you. There's also quite a few modifier button combos where if you haven't gone through the manual, they're not exactly obvious since they're not labeled on the overlay. For example pressing the SHIFT+ALT button on controller causes buttons to control different functions in Vegas similar to keyboard short-cut combo button presses.

I found the 2 commands in the pic below to be pretty important for using an MCU controller with Vegas. Where since they weren't currently assigned to buttons on my controller, I was lacking these control functions. Vegas likely does this re-assignment mapping for you with the FP8 when you select the FP driver in Vegas. Your FP8 doesn't have a "Global" button and that's the part that Vegas does for you. Vegas assigns one of the buttons on the FP8 to the "Global" MCU command, and then you put the Vegas overlay on your FP8 which is then labeled "VIDEO".

I had to assign a button to MCU commands on my controller to GLOBAL and READ/OFF to get the VIDEO and AUTOMATION control capabilities.