(10 replies, posted in AlphaTrack:User Forum)

Does the message only appear when the AlphaTrack is connected? Do you have the latest drivers installed for you other devices?



(3 replies, posted in Dakota:User Forum)

Sorry, not currently. They do pop up on ebay or craigslist from time to time.



(3 replies, posted in TranzPort:User Forum)

Hello Sotagear,

we'll have to take a look at it but I don't recall there being a tool to change that in the SDK. Currently it is set to follow Steinberg's own commands.

I'll add it to the wishlist though.



(3 replies, posted in Dakota:User Forum)

Hello Teddy,

Sorry no. You can have a Dakota and a Wavecenter, but not 2 of each. The computer can't identify them separately.



(1 replies, posted in AlphaTrack:User Forum)

Hello Seb,

Sorry, there isn't an easy way of reprogramming the AlphaTrack in Logic. However if you are familiar with using the Logic Controller Assignments panel you are welcome to take a shot at it. Unfortunately the Controller Assignments is a bit intimidating for most folks.

If you try and end up wishing you were back to the original settings just go to Logic/Preferences/Control Surfaces and select "Rebuild Defaults".

Good Luck,



(3 replies, posted in AlphaTrack:User Forum)

In Cubase and Nuendo AlphaTrack can select Inputs, Tracks, or Output busses on your Mixer by pressing Shift and turning the middle encoder. This works regardless of what encoder mode is currently selected.

Note - AT works only with Mixer 1

Hope that helps.



(3 replies, posted in AlphaTrack:User Forum)

Hello fabio,

With what software?  AlphaTrack can control the Master fader in many apps but they are all different. Check out the individual user app user guides on our website downloads page.




(4 replies, posted in AlphaTrack:User Forum)

Haven't tried C5 here yet but we don't expect any issues. Steinberg hasn't notified us of any major changes that would affect us and we haven't heard of any problems in the field yet.



(1 replies, posted in TranzPort:User Forum)

Visit our downloads page to get it.




(4 replies, posted in AlphaTrack:User Forum)

We have just posted version 1.0.6 of the AlphaTrack Plug-In for Cubase and Nuendo. This fixes the long-standing issue of delays when using Solo, Mute, or Rec Arm buttons.  You will also find a copy for all you 64-bit Windows users.

Visit our  downloads page.




(8 replies, posted in AlphaTrack:User Forum)

Is there any chance that either of you don't have the latest AlphaTrackCN plug-in file installed? You should be using at least v1.04.

Also, we expect to be posting another update to that plug-in with the next couple days to fix a few unrelated issues. So keep an eye out for v1.06 to appear too.



(10 replies, posted in AlphaTrack:User Forum)

Hello duncanmusic,

While I can't say for sure what might be causing this, it is not normal behavior. Here is a list of things you can try. Any one of them might solve the problem but you should try them in this order.

1. Confirm that you have only 1 copy of the AlphaTrack.bundle file on your computer, and it is located inside the Logic/Show Package Contents/Contents/MIDI Device Plug-ins folder.
2. Repair Permissions on the your entire computer.
3. Select Logic/Preferences/Control Surfaces/Rebuild Defaults.
4. Logic Preferences/Midi/Reset All MIDI Ports
5. Go to Logic/Preferences/Control Surfaces/Setup. Highlight the AlphaTrack icon and delete it. Then close and relaunch Logic.

If none of these seem to help then please tell us more about your system and any other MIDI devices you may have installed.


Yes, it has been a while. And not to make excuses but we have had sooooo many programs to work on. Anyhow, this IS being done right now and you can expect to see an update posted within a few days.

Best to all,



(7 replies, posted in AlphaTrack:User Forum)

Hi Brian,

I'm afraid that this really sounds like a faulty unit, although I must admit, I have never heard of this problem before. 

We can set up an RMA if you would like to send it in to be checked out. If so call 603-448-6283 x107 and speak to Brian. He'll get you set up.
If MIDI-Ox shows the symptom then you know it has nothing to do with Cubase. And unless there is some mystery filter going on with the computer I can't imaging what else it could be.



(3 replies, posted in TranzPort:User Forum)

Hello brithedark,

I guess the best answer I can give you is that Pro Tools users are easily our biggest 'group' of buyers. And while I should leave it to actual paying customers like yourself the chime in here, we have had very good response to both TranzPort and AlphaTrack. We have basic PT7/8 versions of LE and M-Powered here and not a ton of 3rd party plug-ins to beat on, but nor have we heard of problems from the field regarding HD or other support. I encourage you to surf the DUC forums as well for user comments there.

To the best of our knowledge, with the exception of a few minor feature changes, Digidesign has not altered their HUI support since PT5. We occasionally have reports of someone getting the "Can't communicate......" message but ultimately find that the user just updated their computer or PT version and simply forgot that they needed to reset their PT controller preferences as well. No plague of 'mystery' disconnects that we are aware of.

Hopefully some realtime users out  there will add their own 2 cents worth here too and give you their perspective.



Hello Bob,

Well unfortunately not directly. Microsoft has flat out refused to support 3rd party external control of WMP. See: http://social.msdn.microsoft.com/forums … e1a2947e3/

That being said, you can use Bome's MIDI Translator as an intermediary and convert all of TranzPort MIDI commands to emulate keystrokes. I think Bome's has even done a downloadable patch just for TranzPort and WMP on their site.



(5 replies, posted in AlphaTrack:User Forum)

Yes, unfortunately there are just so many variables in this area that every company has gone off and done their own thing.

Another thing that we are beginning to see  more often with some apps is MIDI 'Learn' mode. They have a built in command set that the user can pair up to any controllers MIDI I/O. This can also work well for both parties. The key is for the app to also provide feedback to the controller for display, LED's and fader motor, to the same address.



(4 replies, posted in TranzPort:User Forum)

Hello rtorstick,

Yes, apparently in the process of reconstructing our website after our recent server meltdown, the 64-bit  Cubase plug-in wasn't replaced. If you email support@frontierdesign.com we'll gladly send it directly to you. In the meantime we'll see about getting it put back up on the downloads page.



(10 replies, posted in TranzPort:User Forum)

Hello fclef, Craig, and all

just to briefly answer the question as to why we haven't released a driver fix for this 'bug'. It is not that we have turned a blind eye to the issue. If it were a simple driver tweak we would certainly have done it long ago. Unfortunately the solution appears more complicated than that. Also, this problem is not consistent with all machines. Some, like an XPC machine in my office, do not exhibit the problem at all.

We are still looking into it and hopefully we will find a suitable solution. Windows 7 is still a ways from being useful to 3rd party developers. Microsoft has a nasty habit of changing their audio/MIDI interfaces in the 11th hour as was seen with Vista. This caused a major disruption for many hardware manufacturers that they won't be anxious to repeat.

We'll keep looking at it and post any new progress as soon as we can.




(5 replies, posted in AlphaTrack:User Forum)

Hi Tony,

Actually this is a very good question. And one that throws a lot of folks because at first glance the answer seems so obvious. We get asked all of the time how come we don't just add a generic Mackie Control mode. Unfortunately it is actually much more complicated than it may appear. There really is no such thing. Here's the condensed version of why that is.

First, yes, the Mackie Control protocol is a 'standardized' set of commands. This is true for HUI, and Logic Control as well. That command set reflects all of the communication required to send and receive data to ALL of the faders, buttons, knobs, LEDs, displays, etc, on an actual MCU. Including modifier keys to increase the functionality of the entire unit and this gets to be a long list.

Now for the problem. Each different software app may, and in fact does, use those controls however they best see fit. This means that while there is a standard set of messages, there is no standard to how they are applied. This is also why Mackie offers a number of overlays for the MCU depending on what software you are using. For example, the "Read Automation" button in Pro Tools is the "Click" button in Digital Performer, is the "New Audio Track" button in SONAR, etc. With a few exceptions, like Play and Stop, there is just no common pattern. This gets further complicated when you figure in the modifier keys.

Now to add another curve ball. Remember, the AT doesn't have anywhere near the number of faders, buttons, etc that an actual MCU has. Which ones do we choose? We can't replicate everything. And because every app rearranges the commands we can't even be sure to have a few of them right unless we write a specific driver mode for every single application. Ouch! That's a lot of research and coding for us, and also a big part of the reason why we freely publish the AT's MIDI spec.

Many applications have chosen to write their own command set for AT, or TranzPort, right into their programs. It's much easier for them because they already know the command set that they can support and all of the best user 'tricks' that they can show off. Since we can't be an expert on >30 DAW apps it is much harder for us and invariably results in a flood of user requests to change this feature or that because they aren't the best ways to do something. Or we missed some great feature altogether that is unique to that program.

So while we have done a few very basic ones, you can see that it is actually a much bigger challenge than it seems at first. This is also why we happily send units to companies who would like to add support for our products. And if I am not mistaken, we did send an AT to the Melodyne folks a while back.

Did I say this was going to be the condensed version? Oops.



(4 replies, posted in AlphaTrack:User Forum)

Very odd. Although I'm not sure, its beginning to sound like maybe there is a physical problem with that unit. If you purchased it at a local shop can you bring your laptop there to compare your AT with another one? A hassle I know, but also a good way to be sure its cured.

You could also load up MIDI Monitor on your computer and monitor the incoming MIDI data. That might also show whether or not it is sending incorrect sporadic messages.



(4 replies, posted in AlphaTrack:User Forum)

Hello themash,

What DAW software are you using it with? Is there existing automation on the selected track? Also, make sure you have chacked for any driver/plug-in updates on our website.

The fader should be quite responsive both to touch and existing automation. Is there any chance you have your computer's AC cord ground lifted? This can sometimes cause AC noise to get into the touch sensing circuit and cause the fader to mis-behave.

Give us any details you can and we'll try to help.


Thanks for the update Harry. Sounds like you're having way to much fun!



(3 replies, posted in AlphaTrack:User Forum)

Hello Redroom,

The encoder resolution as it is now is the standard setting determined by the Steinberg control spec. Some apps allow for course/fine adjustment and some do not. I am not sure if we can alter Cubase/Nuendo behavior on our end or not, but I will make a note to look at it before our next plug-in update.



(3 replies, posted in AlphaTrack:User Forum)

Pierre wrote:

When you touch the fader the display changes rapidly between different functions (volume/mark/pan etc) as though you are rapidly selecting different controls.

If you try and move the fader the motor fights you as it cycles between the different parameters changing on the display.

The unit is about 6 months old.

I've reinstalled the latest drivers.

The problem started midway through a mixing session. No new hardware or software has been added recently. I'm using Sonar 7 with Windows XP.

Anyone got any ideas?

CS:Hello Pierre,

sounds a lot like a grounding problem creating noise in the touch sensors. Is this on a laptop or desktop computer? Connected via a USB hub or direct to the computer?

Make sure your computer has a grounded power connection. If you are using a USB hub it should be powered.


Pierre wrote:

I was connected via a USB hub.

I've connected direct to the (desktop) PC and that has solved the problem.

Thanks for your advice.