MACKIE CONTROL V1.02

UliMors wrote on 4/23/2004, 3:33 AM
Hi ,

as you know, the Mackie Control Universal supports three modes:
(selectable by pressing CH1 + CH2 "SELECT" while powering up)

a) MACKIE CONTROL
b) LOGIC CONTROL
c) HUI

I tried to run my mackie control (V1.02) with the demo of VV5.
VV5 "sees" the midiinterface, connections are working (CUBASE SX works fine with it), but VV5 does not recognize the MC.

My MC runs in "MACKIE CONTROL" mode.

Is the demo restricted? Is it necessary to switch the MC to "HUI MODE" (thats the only difference between a MACKIE CONTROL and a MACKIE CONTROL UNIVERSAL)?

Any help appreciated.

ULI

Comments

pwppch wrote on 4/23/2004, 6:37 AM
We communicate in the native Mackie Control protocol. We don't support the HUI or Logic Control Mode.

We have not tested against the v1.02 firmware as this was not available to us from Mackie. Therefore we only officially support Version 2.0 and higher of the firmware.

The demo is not restricted. If the correct MIDI ports are enabled in Vegas and the Mackie is correctly connected, Vegas will discover the Mackie and automatically configure it.

Note that you must also enable external control once it is configured. This is done from the Options menu in Vegas.

Things to check:

- Are you MIDI ports enabled? Note you must Apply these changes before attempting to add the Mackie.

- When you open the External control prefs page in Vegas, what does the status of the Mackie device added indicate?

- When you open the Mackie configuration dialog, and press the scan, does is the Mackie discovered? You will also notice that the Mackie LCD display indicates the channel mapping while in configuration mode. This indicates that the Mackie and Vegas are communicating.


Peter

UliMors wrote on 4/24/2004, 1:43 AM
a) yes , I even enabled ALL ports (2 x 8) and tested MTC out as well - this works fine. Also, while scanning I can see short activities on all Midi Outs. Midi Out is working fine with all other software - so I guess its not the Interface nor the cables.

b) "no mackie devices detected" - double clicking and "scan" does not lead to a different result.

c) no. there are short activities on MIDI OUTS while scanning, but MC does not respond.

Since I am working as Tec Engineer for Mackie Designs (LOUD Inc) in Germany & Benelux I will try to get in contact with Ken Berger to see if there are any changes made to MC mode in V1.02 to V2.x
Unfortunately I dont have an upgrade kit here at the moment (V1.x to V2.x needs an eprom upgrade) - but I´ll get one.

If you like to get in direct contact with me , I am also communication with Guido Harding and his folks (Soundservice Berlin - distr. SONY).

See reputation www.mackie.com/de

you can contact my by produktinformation@mackie.com

Regards

ULi Mors
Arnar wrote on 4/24/2004, 5:10 AM
Interesting , can you help me get my hand on the eprom upgrade :)
UliMors wrote on 4/24/2004, 7:54 AM
have a call at Mackie , Woodinville/Seattle and ask for parts dpeartment. I think the V2.x update eprom costs a small amount, see also

http://my.mackie.com/forms/reserve_mcupgrade.asp

but I guess a call by phone is worth a lot more than sending a mail order.

ULI
PipelineAudio wrote on 4/24/2004, 11:14 AM
See if you can see the control in generic mode first instead of using the mackie driver. Many times my MCU will not be seen by vegas as an MCU but it can be seen as generic
UliMors wrote on 4/25/2004, 8:57 AM
generic is working fine - but I guess no user would neglect things like track names and full exchange of parameter values etc.

Also some generic functions will not work on the Mackie Control since some controller values are not send by standard midi controller data but native ones - its hard to interprete that in a "generic" way.

ULI
PipelineAudio wrote on 4/25/2004, 11:33 AM
just trying to establish you were seeing the same thing I am. Many times vegas will see the mackie controller just fine. Just not as a mackie controller