Community Forums Archive

Go Back

Subject:does acid 6.0b work with the yamaha 01v96
Posted by: ozzborn
Date:8/18/2006 4:25:28 AM

i am upgrading my studio and i am trying to make these 2 work together but i need help.
thanx in advace

Subject:RE: does acid 6.0b work with the yamaha 01v96
Reply by: pwppch
Date:8/18/2006 10:38:06 AM

I assume you want to use the 01v96 as a control surface in ACID.

If the 01v96 is like most of the other Yamaha mixers, it uses sysex in general to send control information. If the 01v96 uses MIDI Machine Control you can set up the generic surface control device to use this for transport msgs.

If the 01v96 has a HUI or Mackie Control mode - or a simple MIDI msg mode - then you can set it up to map faders and other functions using the generic surface control in ACID. Note that ACID will not feed back fader pos to the 01v96.

Peter

Subject:RE: does acid 6.0b work with the yamaha 01v96
Reply by: ozzborn
Date:8/18/2006 4:45:32 PM

the 01v96 has hui or mackie control emulation.

it has templates for protools , cubase , and nuendo.
it also has user templates.
if that m audio device works hassle free, how come the yamaha wont

thanx in advance

Subject:RE: does acid 6.0b work with the yamaha 01v96
Reply by: pwppch
Date:8/18/2006 8:05:49 PM

If it emulates the Mackie Control, then it should work with ACID's Mackie Control driver.

From my reading, this device supports the HUI protocol, not the Mackie Protocol. The HUI and MCU protocols are different and not interchangable.

Did Yamaha update the firmware? Do you have a pointer to any docs that describe the units Mackie Control support? That may help me to trouble shoot this for you.

Peter

Subject:RE: does acid 6.0b work with the yamaha 01v96
Date:9/19/2006 12:25:22 PM

I have tried this with Vegas but from what I could see there was no MIDI activity out from Vegas in either Generic or Mackie Emulation modes when adjusting automation levels.

This looked like a bad sign since I didn't want to just see the trim faders.

Peter, is the MCU MIDI spec published anywhere? It would be useful to see what your codes Vegas & ACID are expecting & generating.

Subject:RE: does acid 6.0b work with the yamaha 01v96
Reply by: Ben 
Date:9/19/2006 5:08:03 PM

I too have been trying for a while to get this working (with Vegas but same principle). I was also confused when looking at the MIDI information that Vegas was sending out, as when in automation mode it didn't seem to be sending anything relavant pertaining to the fader movements.

Peter, it would be great if you could give us an idea of what's going on here - are we missing something?

Thanks

Ben

Subject:RE: does acid 6.0b work with the yamaha 01v96
Reply by: pwppch
Date:9/19/2006 9:24:04 PM

Not sure what you really want to know...

For the MCU, Vegas and ACID send out the automation levels for vol, pan, and mute when the MCU is in Automation mode.

When the MCU is in trim mode, it sends the MIDI message for the vol/pan/mute - and other track level stuff - when you interact dynamically with the ACID/Vegas GUI.

I don't know what you are monitoring, but if Vegas didn't send out the MIDI msgs when when the MCU was in Automation mode, then the faders/pots/leds of the MCU would not track what Vegas is doing.

Note that the MCU automation mode is independent of the individual track automation modes. The MCU automation mode tells the MCU to listen to all envelopes for Vol/pan/mute - as well as sends and FX params depending on what the assign state of the MCU is.

Note also that if a track/bus is in automation off mode, then this essentially by passes the envelope data and no data will get sent to the MCU.

The MCU MIDI spec is not available as an open doc. You have to contact Mackie to get a copy of it. It is under NDA.

Peter



Subject:RE: does acid 6.0b work with the yamaha 01v96
Reply by: pwppch
Date:9/19/2006 9:31:26 PM

The Generic Driver will never send MIDI data out when you interact with Vegas/ACID. It is not set up to send MIDI data, only recieve it. (The prefs/config page for the Generic control in Vegas shows a MIDI output port assignment, but this is ignored.)

The MCU driver MUST send MIDI data back to the MCU to control the faders/pots/leds/LCDs of the surface. Depending on what mode the MCU is in - Automation or Trim - you will get data sent out depending on what you are doing.

If you are moving a volume envelope point where the cursor is and the MCU is in Automation mode, then you will see the fader on the MCU move, and the appropriate MIDI msg generated to do this.

If you move the fader on a track in ACID/Vegas you will see the fader move on the MCU regardless depending on the automation mode of the MCU as well. If the ACID/Vegas track is in "trim" mode and the MCU is in automation mode, then you will not see the MCU fader move and no MIDI msgs will be sent. If you move the fader on a track and the track is showing the automation faders, then when the MCU is in automation mode you will see the fader on the MCU move and MIDI msgs will be sent out.

No, the MCU MIDI spec is not published. You have to contact Mackie to obtain it under NDA.

Peter




Subject:RE: does acid 6.0b work with the yamaha 01v96
Reply by: MarkWWWW
Date:9/20/2006 5:11:49 AM

As Peter says, Mackie don't seem to want to publish the spec of the MCU MIDI implementation to humble users.

But you should be able to find the information you need here at a site where a MCU user has mapped it all out for us. Combining this information with the Vegas Overlay available from here you should be able to work out what MIDI messages are being sent or expected.

Mark

Subject:RE: does acid 6.0b work with the yamaha 01v96
Reply by: drew_
Date:9/20/2006 5:50:26 AM

Thanks for that - I don't have access to an MCU - just the old faithful 01V96 with which I am trying to interface.

I couldn't work out why MCU emulation mode wasn't sending automation data and hadn't realised it depended on a mode switch being set on the MCU.

Also I had been thrown by seeing the "MIDI Output" field in the Generic mode since, not surprisingly, I had imagined there was some code behind the ComboBox!!

Go Back