I have a D8B but have never been entirely comfortable with its HUI implementation. For many reasons, I'm actually looking to get rid of the D8B and replace it with something smaller anyway. When working with Vegas, I prefer Mackie Control. Re M-Audio, I look forward to hearing how it interfaces with Vegas. but remember that M is now owned by DigiDesin, which is owned by Avid. Digi is aggressively pushing/pricing their "ProTools M-Powered" application for M-Audio products, and their past history (Digi & Avid) suggests that they may intentionally cripple their products for use with rival applications.

First indications are nothing short of wonderful!

I got the projectmix I/O hooked up after supper tonight and fumbled around for about an hour (Documentation is horrible). I followed the steps verbatim and finally figured that I needed a firmware upgrade. The M-audio control panel software is somewhat misleading on the about page. It stated a firmware version later than the latest available for download????? After a M-audio reboot I noticed that the firmware version appears on the screen when you turn on the thing. It was older than the one on the web site so I flashed it. This added 3 additional modes, Sonar, Digital Performer and Live mode(can't wait to play with that one). I also have sonar 4 producer edition so I decided to give that one a go.

Vegas loves it! Open a new edl, faders snap to attention with one master fader. Add a new audio track and boom, it is reflected on the desk. Name the track and the track name is in M-audio screen! Transport controls work including the job wheel.

I have only scratched the surface with this thing but so far I have only hit one snag on the controller side. I haven't figured out how to get automation to work. When you enable volume envelope, the M-audio fader does not controll the envelope. When automation is off, the m-audio fader does control the track fader. I'll experiment with this later.

The audio side is nothing to sneeze about either! It sounds fantastic. I have not had a chance to test the lightpipe and spdif ins/outs but the 8 analog inputs are very pleasing. Very warm and smooth sounding.

More to come.

JAB

Well after some more testing, I have still not found the M-audio key combination to put it in automation mode. I tried every variation of shift/alt buttons but came up empty.

Sonar mode using sonar 4 producer version is even worse. Very few buttons mapped to sonar.

I have a ticket in with M-audio but do not expect to get much help. I would think that if a company is targeting the masses, you would want your product as easy to use with as many software packages as possible. The M-audio projectmix I/O appears to have all of the capabilities, they are just not setup for each software package. I would think that M-audio r&d would have people writing firmware updates to make it easy for us guys who just want to plug the thing in and use it. I guess I'm going to have to figure out how to map the buttons myself. Not something I'm looking forward to, I'd rather concentrate on editing and mixing and not get bogged down with the technical stuff.

JAB

Making a little more progress. Got Sonar working. Now as soon as I get the automation mode going in vegas I will rest...maybe not.

MarkWWW has been a big help in another thread too.

I think my over all opinion of the projectmix is good now that I have a little more understanding of how it works. It would have been nice to have a little better supporting documentation from M-Audio. I think they assume if you are buying it, you know a little bit about how to make it interface with your software. I knew absolutely nothing about control surfaces before this purchase and the learning curve without documentation is steep.

Thanks to the wonderful folks on this forum, I will be functional soon.

JAB

Finally!!!

I found the correct mode. As it turns out, a firmware upgrade adds several Mackie Control preset modes for different software. At first glance, Vegas will work (sort of) with all of them but there are minor differences in all of them. Sonar mode (was hoping this would work because I also use Sonar) did not have a button/shift/alt combination at all that yielded the necessary "D5" note on note off that vegas wants to see for automation mode. I started going through the other mackie control presets on the projectmix one by one and testing every combination of buttons (with a midi monitor open) until I found a preset that had a "D5" in it.

Voila, the Logic setting had it mapped to a convenient button (sel in) and vegas automation is now fully functional.

Final Conclusion:

Great piece of gear for the budget minded user. Bit of a headache with trial and error. Some conclusive documentation on this would have saved me a few panic attacks.

Thanks to MarkWWW for putting me on the "D5" thing. Which brings up another question. How do you know what midi notes vegas uses for the different functions? Is there a map listed somewhere?

Thanks,
JAB

I've never found an explicit map for this When I was working out the equivalent problem for the BCF2000 I did it by bringing together the information from a couple of different places.

First, I needed the Vegas overlay for the MCU, available here. Then I needed information on what MIDI data was transmitted by the MCU and the most helpful source I could find for that was here. Putting those two together allows you to draw up a map of what MIDI data is expected by Vegas when being controlled by a MCU.

And when you put this together with the infrormation you have about what MIDI data your controller can be configured to send (ideally from the documentation the manufacturer provides, but more likely because you have spent an hour or so working it out using a MIDI monitor because the manufacturer didn't bother to supply it) you can draw up a map to suit your controller.

Mark

The combination of Sony Vegas and the M-Audio Project Mic I/O could be killer - BUT! ( There's alwways a but! ) There is a problem with initializing the automation. Does anyone have an answer that might help us all out?
In Sonar, the faders fly, the buttons respond - all is well. Unfortunatly Sonar isn't as fast or versitile as Vegas ( in my opinion ) and none of the last zillion projects I've put together were done in Sonar so getting a little help from a Mackie Control / midi person would be fantastic! I see that there's a little help here for those who understand and can configure midi, but for those of us who can't - still lost as to how to make the automation work in Vegas!?!?

Maybe a step by step walk through? Please!!!!

Just a note; I'd strongly reccomend Vegas users explore the M-Audio Project Mix - Once this little automation glitch is addressed, your workflow will will speed up considerably.

I suspect that the answer you require is contained in one of the posts by JAB above.

There are a lot more buttons on a real MCU than there are on the ProjectMix so (I beleive) the ProjectMix cannot emulate all of the functions of the MCU at once. Instead it implements a variety of modes each of which emulate a subset of the functions of the MCU, each subset being intended for use with a particular application and implementing the most common buttons, etc, used by that application. There isn't a mode intended for use with Vegas, so you will have to choose the one that is the nearest match to the set of buttons you would like to have implemented for use in Vegas, in particular you need to use one that implements the button that toggles the automation mode in Vegas.

According to JAB, the one to use is the mode intended for use with Logic - you should find that when using this mode the button labelled "sel in" will toggle Vegas's automation mode on and off.

Mark

First, Thanks Markwww - it always sounds corny, but thanks.

Now, on to something that might help others.

I am not a midi guy, but I've been working in DAWs from the beginning, really, the real, honest beginning. So when I finally found some web info about an audio interface AND a surface control – I had to check it out. I looked and poked around, Checked for negative feedback blah, blah, blah… Know what? The M-Audio Project Mix I/O looked promising. Especially for me since most of my work is recorded in fancy places with receptionists and real coffeee. I bring everything back on a protable hard drive. Then I play.

So I bought one. In fact, one of the first ones. Then I had a fucking heart attack!

No, really I did. How crazy is THAT!!!!

So when I could play again (I make my living working with voices) I tried to hook up the new toy. Nope. Tech support – nope. The net – nope. Something about firewire????

Nope. Turns out the unit was... a dud. Hmmmm….

Arranged toi get a new one (Great support from my dealer – Tom Lee in Vancouver, BC)

So now it at least it talks/works with my PC. A bit. Mostly.

But.

There’s always a but.

But the automaton won’t work. No way – no how. So after days of work on the net, a LONG call to tech support, a client waiting, work NEEDING to be done and I’m thinking of re-loading the old system I get some help here. How great is that – again, thanks. But truth be told, it was really intuitive luck that satisfied the situation. So here: For those of you like me, looking for the simple “Make it work” solution ( ‘cause Vegas and the I/O are great together! ) Do this:

Open the I/O in ‘Logic’ mode.

For Automation:

Select the ‘Automation Write’ box within the channel icons (over on the left – same place you’d re-name a channel)

And here’s the rub - use the “Sel In “ button on the I/O to toggle your automation on and off!

…and it works!


I just finished a project – 21 tracks, three languages, a ton of SFX and music and probably saved 3 hours over having to mouse around. So cool -So thanks Markwww, that one last time – ‘cause we all need that one Guru that’s just that few steps further along than we are.


Hope this helps,
Rob
Wordnoise

I thought I would add a note to this very useful thread. I have found that my system sometimes will not respond even when following all of the above tips and suggestions. I work on a dual core laptop and sometimes when I have returned to my home studio with the laptop and connect everything, the projectmix automation will not work. I scratch my head and re-read this post to make sure I have not forgotten something. Then out of desperation, I power cycle the projectmix while the computer is on. I know, I know, M-audio says "never" do this but it fixes the problem. This has happened to me more than once and after a power cycle, I can then boot vegas, hit "sel in" and everyone is happy.

JAB