Search options (Page 3 of 33)

Hi fenders,

Is this your first pass through the automation?  If it's your first pass through there may not be any 'reference' level to 'go back' to.  Try writing automation through the song once, then go back to the beginning of the song for a second pass and see if you get different results.

Otherwise, you may want to try recalibrating by pressing shift+stop+f4 (if it's possibly a touch issue). 

If you're still having trouble, let me know exactly what steps you're taking to record automation.

CS

Hi funkytransport,

Judging by your name I'm assuming you're talking about your TranzPort's track left/right buttons and not an AlphaTrack's track left/right buttons.

What you can try is pressing shift+stop+battery on the TranzPort and this will pop up a button test screen on the TranzPort's LCD screen. 

There will be a row of characters on the top line.  Each letter represents a button on the TranzPort (excluding the backlight and battery buttons).  When a button is pressed an asterisk (*) will appear in under the respective character.  If you move the datawheel you can clear the asterisks to keep testing.  Press the battery button to end the test.

Press the track left and right buttons to see if an asterisk is placed under a character.  If no asterisks appear or if it appears intermittently then it's possible that it's in need of repair.  If that's the case, you can contact support@frontierdesign.com to get an RMA number and send it in for repair.

CS

Hi gbotica,

The screen with the asterisks is normal.  This is a button test to test the functionality of the buttons on the TranzPort.  When a button is pressed an (*) appears under the symbol representing that button.

You can get the TranzPort to stop playing your midi instruments by "unchecking" that check box that says 'In All Midi'. 

This isn't where you want to configure the TranzPort in Cubase.  Instead go back to the devices/device setup screen.  The TranzPort should be listed under remote devices there.  If it is there, click on 'TranzPort' under remote devices and on the top right of that window you'll see 'midi in' and 'midi out' fields, these should both be set to 'TranzPort'.

If the TranzPort doesn't show up under 'Remote Devices' you'll want to click on 'Remote Devices' and click on the (+) sign at the top of the window to show a controller list.  Select TranzPort from the list, and then configure it as I described in the previous paragraph.

If the TranzPort doesn't show up on that controller list then that means you don't have a TranzPort/Cubase plug-in in Cubase's 'components' folder.  If that's the case, you'll want to run the TranzPort driver installer again and this time UNcheck the box for installing the TranzPort driver and CHECK the box to install the Cubase plug-in.  This will install the 32-Bit Cubase plug-in for your 32-Bit version of Cubase.

CS

Hi Living_Culture,

What kind of computer are you using and what is the OS version?  Also, what version of Reason are you using?

The delay in switching from track to track in TotalMix is most likely because of how TotalMix handles these controllers.  The messages being sent from the AlphaTrack are instantly being sent to TotalMix.  Programs like ProTools (using HUI emulation) has similar timing limitations.

I'm not incredibly familiar with Bome's and how it handles pitchbend messages but maybe this will help you out:

http://frontierdesign.com/download/pdf/ … ve_1.0.pdf

CS

Hi funkytransport,

If you go to Logic/Preferences/Key commands.

Then type in the key command's search box "punch.  Then you'll see a list to the left.

"Set Punch out locator by playhead."

Click on that and to the right under 'Assignments' you'll see "AlphaTrack: F4" or something like that.  If you click on it and delete that then you should be able to turn that 'off'.

If you want that back you'll have to go to Logic/Preferences/Control Surfaces/Rebuild Defaults.

If you want f4 to save, go back to the key commands and type 'save' in the search there.  Then click on 'save' on the list to the left.  Then click on 'learn assignment' and press the AlphaTrack's f4 button and then exit the key commands.  Now f4 will save your Logic project.

CS

Hi takastone,

I replied to your prior post:
=============
Hi takastone,

If you click on the AlphaTrack icon and go into the AlphaTrack manager what version shows up there?

And does it say "AlphaTrack Available" there as well?

What OS are you running?

Also, when you say, "isn't working", does anything show up on the LCD of the AlphaTrack.  If you go to www.snoize.com you can download this program called midimonitor.  Launch it and make sure 'AlphaTrack' is selected under 'Sources'.  Then move the AlphaTrack knobs and confirm that data show up in the midi input window.  This will at least test to see if your computer is recognizing the AlphaTrack's movements.

CS

Hi fenders,

I think this largely depends on the program you're using.  In ProTools for example, if you had a track with 3 plug-ins (on A,B and C inserts).  Then you'll need to go to the mix window in ProTools and open one of the plugins yourself through ProTools.  Then when you switch between the different plug-ins on the AlphaTrack the window should put that plug-in on the foreground of your computer display so you can see what you're changing.  But you have to open the first plug.

I'm not exactly sure about Cubase I'll have to try it out but it may be the same.

CS

Hi islanduniverse,

First, try going to Logic/Preferences/ControlSurfaces/Setup, click once on the AlphaTrack icon and check to see that in the left column on the top that 'AlphaTrack' is selected for both midi input and midi output.

Otherwise, try going to your main drive on your computer/users/<your name>/Library/Preferences

and delete the file named com.apple.logic.pro.cs

then relaunch Logic and see if that helps.

CS

That may have been the case when Cubase first implemented the control room but that doesn't mean that it's not in the current SDK.

CS

Hi DS,

You can try hitting the 'reset' button on that window to see if that helps.

Otherwise, try clicking on 'Frontier AlphaTrack' under "Remote Devices".

Does the midi input and midi output dropdown boxes have 'Frontier Design AlphaTrack' listed there?  If not, this should be selected.

Is the AlphaTrack icon on the taskbar set to 'native' mode?  You can check by right clicking the Alphatrack icon.

CS

Hi PincoL

Did you make sure that the AlphaTrack was unplugged prior to installing the drivers?

Did you try reinstalling the drivers?

You may also want to try installing it on another machine to see if you get the same results. 

If you're plugged into a USB hub, try bypassing it and plug directly into one of your computer's USB ports.

CS

Sorry, bobulusbillman, no news yet.

CS