Thanks for the detail on the Totalmix RockinRog.  I confirm your observations using a 'trial by firewire' method to discover the magic.

Totalmix on my Mac is not always activated by Alphatrack when the 'Deactivate MIDI in background' is selected and a return is made to Totalmix from Logic 8.  However, I can't be sure if that isn't an issue with Totalmix. 

Not being able to quickly select individual channels in Totalmix I have shelved Alphatrack's use until a Totalmix driver materialises.

Now if only there was an Alphatrack 'User's MIDI Macro Editor' acting as translator/remapper to outgoing MIDI messages from the individual AlphaTrack hardware controls to peripherals based on the 'Mackie Control' protocol.

Another reassuring detailed response to questions I've raised so far.

Thanks for that answer, it has helped clarify why your 'plug-in' driver is required for specific softwares and highlights reasons for good communication within the industry as well as with MIDI messaging.

Is the Mackie Control Universal (MCU) protocol standardised ?

I note that RME Fireface Totalmix software declared MCU compatible has similar issues to that of Melodyne Studio when trying to interface with Alphatrack hardware. There is limited success at coordinating buttons of the Alphatrack hardware with software controls using the any of the provided drivers.

It is pleasing and interesting to note that Logic 8 functions extremely well with Alphatrack with obvious good understanding and cooperation between the Logic 8 protocols and those of Alphatrack hardware.  (With lots of midnight oil obviously burnt to ensure the success of said software and hardware combination.)   Logic 8 has MCU and Logic Control protocols built into the software.  The latter Logic Control an offshoot of the original Mackie protocol I am led to believe.

Celemony's Melodyne Studio and RME's Totalmix softwares declare that they are Mackie Control compatible yet do not respond to Alphatrack hardware without dedicated drivers that translate Alphatrack hardware controller actions into the appropriate Mackie Control data.

In the light of all the effort coordinating Logic with the MCU/LC  protocol why won't Alphatrack's Logic, Live (MCU), Final Cut Pro (MCU) and Soundtrack Pro (MCU)  drive any Mackie Control compatible interface ?

Is MCU standardised and a recognised documented protocol ? 
Is the MCU protocol being 'defaced' by different software manufacturers ? 

Assuming that MCU has standardised calling procedures as well as  observing that considerable effort has already been applied to the MCU and Logic 8/Alphatrack exercise:
   Wouldn't a generic editor capable of mapping all the Alphatrack permutation of buttons to appropriate intended MCU parameters be a solution for all current and future MCU compatible softwares ?

Melodyne has options for Generic Controller, Mackie Control, Logic Control and Radikal SAC Control in the MIDI remote Control preferences section. 

Using Alphatrack hardware there is limited control of the Audio Mixer in Melodyne Studio 3.2.2.2 on my PowerPC Mac with OS X(10.4.11) and using the AlphaTrack's Manager option of 'Soundtrack Pro (MCU)'  and selecting Mackie Control as Melodyne's MIDI Remote Control  preference. 

Further selection of Mackie Control as the desired controller and the 'Frontier Design Alphatrack' driver chosen within Melodyne's MIDI in and out port options ensures communication.

A Melodyne Studio arrangement containing 8 tracks can be controlled using AT's :
   Fader,
   Track (previous & next buttons),
   Flip (for Master fader),
   Pan (right encoder knob),
   Record,
   Mute,
   Solo,
All these AT controls work as expected on the Melodyne Studio 'Mixer' so that Track names, Fader position, Pan position, Mute, Solo and Record status are updated on the Alphatrack LCD and interact with Melodyne's Mixer window.   

   Transport buttons partially work, FFWD and REW are the exception.
   Ribbon Controller has control over scrubbing the track backwards and
   forwards in the 'Arrange' window.
   Left and Centre encoders provide '<-Tr-> and <--> symbols on the 
   LCD but have no apparent observable influence on Melodyne.

Function keys F1 through F8 can be user programmed and selected within Melodyne Studio.

Unfortunately The Alphatrack FFWD and REW buttons have no apparent function and using the Alphatrack Shift key sometimes contributes to a lack of sync so that Alphatrack provides a blank LCD display, this behavior is not one where a causal pattern has yet been identified.

One way of resyncing Alphatrack with Melodyne without closing or losing edited material is to deactivate and then reselect the Alphatrack driver in Melodyne's Mackie Control setup.

I have noted issues occur if using more than 8 Melodyne tracks.    In particular cycling from track 1 through to track 16 in a 16 track Mixer window loops back to track 9 when advancing using the Track next button. No amount of 'Track previous' actions rectify this behaviour.

Other track selection issues using the 'Soundtrack Pro' template relate to Melodyne's "Arrange" window not being mirrored in Melodyne's "Mixer" window and vice versa which is contrary to that of the actions with Mute, Solo, and Record buttons. 

Considering the above, until a reliable Alphatrack/Melodyne driver is created the Melodyne software can be controlled in a restrictive manner provided that syncing tracks between the 'Arrange' window and the 'Mixer' is not critical to your method of working.

Now if only a generic MCU editor could be created between Alphatrack hardware and the software host. (See next post.)

Solved it... the install procedure is successful if logging into my Mac as root user.   File permissions are obvious targets that I had overlooked when downloading as user.    Maybe a cautionary note to future Mac users may be useful.

My lesson... don't be too impetus and excited by a new toy, think before activating digits on the keyboard.


Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/frontierdesign/frontierdesign.com/forums/include/parser.php on line 738

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/frontierdesign/frontierdesign.com/forums/include/parser.php on line 738

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/frontierdesign/frontierdesign.com/forums/include/parser.php on line 738

After following the install instructions contained with the hardware I have downloaded the latest Alphatrack Macintosh Installer v1.3 from the sites Support/Download site i.e.

http://frontierdesign.com/download/driv … _1_3_0.zip

and expanded it to the desktop on a Mac dual G5 Mac OS X 10.4.11.

On expansion and use the Alphatrack Remover package performs as intended but the Alphatrack Installer does not install any Alphatrack files in the intended Mac locations.  There is no Alphatrack icon displayed in the Status bar and the files are nowhere to be found in the intended System, Library and Application directories.  In consequence the Alphatrack hardware is not recognised when connected by USB.

The Alphatrack Install package only has a 28KB size which appears suspect and on closer inspection five Alphatrack packages other than the Installer and Remover are contained (hidden) within the expanded Alphatrack Installer package.   These five packages relate to the Assistants, Driver, Icon, Manager and MIDI files that need to be extracted and stored in the relevant locations in the OS. These 5 files appear not to be expanded to their intended file locations when the Alphatrack Installer is activated.

Restoring Alphatrack software v1.1 from the CD restores functionality of the Alphatrack hardware.

Any advice, tips or directions to resolve these issues would be appreciated with this latest v1.3 OS X driver software.