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

251

(5 replies, posted in AlphaTrack:User Forum)

Hi sonicfuel,

If you go to page 5 of the following document it will probably be most helpful to you:

http://frontierdesign.com/download/pdf/ … v1.0.4.pdf

In short, you'll only be able to do this through a plug-in in Cubsase.  For example, if you had a softsynth with these parameters you'll need to (with the AlphaTrack) navigate to the track, hit the plug-in button on the AlphaTrack, select the plug-in, navigate to the parameter, then adjust the parameter.  Using the 'flip' button on the AlphaTrack should let you flip an encoder's parameter onto the fader.

CS

252

(3 replies, posted in TranzPort:User Forum)

Hi Axiom,

Unfortunately you won't be able to use 2 different TranzPorts on the same computer. 

If you both only need to click a button I suppose you can map a redundant function to the footswitch (for example the 'stop' function).  Then the drummer, for example, can have the footswitch to hit 'Stop' and someone else would have the TranzPort's 'Stop' button on the remote itself. 

CS


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

253

(1 replies, posted in AlphaTrack:User Forum)

The latest DP plug-in  "DP 5 Plug-In v1.01" which is available here:


http://frontierdesign.com/Products/AlphaTrack/Downloads

should go here:

Open your main system drive and go to the "Library/Audio/Plug-ins/MOTU Control Surface” folder.

Then you should be able to configure the AlphaTrack in DP by opening the Setup/Control Surface Setup window. Click on the ‘+’ symbol to add a device to your configuration. Under Driver select “AlphaTrack” from the available device list. For the MIDI option select “Frontier Design AlphaTrack -16”.  You will also need to be in 'native' mode in the AlphaTrack manager.

CS

254

(1 replies, posted in Dakota:User Forum)

Hi thornbu,

It sounds like you're using ProTools M-Powered, is this correct?

If so, M-Powered requires M-Audio hardware, for example an MBox or a FireWire 410, to be able to run the software.  Even then you wouldn't be able to use the Dakota card because for the most part you can only use DigiDesign hardware in DigiDesign software.

CS


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

Hi Axiom,

If you launch Sonar and go to options/keybindings

On the left hand side is a list of key combinations.  I'd scroll through there and look for CTRL+f4, CTRL+f6, CTRL+tab.  When you highlight these it should say somewhere on the screen what the function is.  It also might say [unassigned].  But since they do something in Sonar it should just show you what the function is called in Sonar Lingo.

Then you should see if that function shows up in the list in Tools/Frontier TranzPort. 

If it doesn't then it's possible through keybindings to assign these functions a different key binding (other than CTRL+f4 etc) that is compatible with Tools/Frontier TranzPort's list. 

For example, whatever is assigned to CTRL+f4 in keybindings you can change to shift+f4 and then go into Tools/Frontier TranzPort and program a button to act as 'shift+f4' since it's already on the list.

I hope this makes sense.  Let me know if you run into any sort of trouble but it sounds like you may get what you need by manipulating these two windows. I have an older version of Sonar here so when I looked for CTRL+f4 etc. they all said [unassigned].

CS

Hi Axiom,

I think what you'll need to do is to launch Sonar and go to Tools/Frontier TranzPort.

In that window you'll see all the assignable buttons and button combinations.  In each drop-down list is an available list of functions.  I think you'll need to check this list to see if there's any available functions here that may help.  I couldn't find CTRL+f4 or CTRL+f6 or CTRL+tab on the list but it may go by another name associated with its function in Sonar.

Hope this helps...

CS

257

(3 replies, posted in AlphaTrack:User Forum)

Hi lorneyb2,

There may be an issue with these later versions of Sonar (8.5 and later) with how they handle the instrument tracks.  It seems to work in versions prior to 8.5 and we're currently waiting to hear back from them to see if there were any changes from the earlier versions that would cause conflicts with other controllers.

CS

258

(3 replies, posted in AlphaTrack:User Forum)

Hi burn4ever,

There are a couple things to make sure of.  One is to make sure that in 'Device Setup' you don't have "All MIDI" checked for your AlphaTrack under MIDI setup.  Also, you shouldn't have AlphaTrack selected directly in your MIDI track either.  You shouldn't need to configure the AlphaTrack in Cubase other than in the 'device setup' window.

CS

259

(5 replies, posted in AlphaTrack:User Forum)

Hi ilovepunk,

If I could give you a timeline for a driver update I would.  All I can say at this point is that there is no update yet. 

I thought we've responded to this saying that in a couple weeks we would have a more definitive answer as to whether we will proceed with an update or not and unfortunately I may have jumped the gun by mentioning 'a couple weeks' but we're currently uncommitted to it and still don't have a definitive answer.

CS

260

(2 replies, posted in AlphaTrack:User Forum)

Hi BB54,

It's possible it's the grounding issue and it's also possible that there's a possible intermittent hardware issue with the fader.  If you've had it for 3 years on an ungrounded computer and it's always worked then I would first try and recalibrate your AlphaTrack by pressing shift+stop+f4 then try the AlphaTrack and see if you get better results.

If you don't then let me know exactly how the fader is moving during this recalibration.  Run it a few times and just let me exactly how the fader moves.  This will may reveal some issues.

If when all said and done it still doesn't work then I would try the AlphaTrack on a computer that you know is grounded just to see if it works on that computer.  Again, perform the recalibration if it fails to work on the grounded computer. 

If you don't have a grounded computer around then you can try a laptop running on its battery (power cable unplugged) and see if you get better results.

CS

Hi Rob,

The latest driver works and is compatible with Snow Leopard and I haven't heard of any issues with DP7.  What kinds of 'performance issues' are you noticing?

By the way, we did get your email that you sent to customer support, however, your email address didn't appear when we hit 'reply' to answer you back.  So you may want to check that out in case this happens to other people as well. And if you email our customer support make sure you include your email address.

CS


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

262

(5 replies, posted in AlphaTrack:User Forum)

Hi ed1,

Since you live in Spain, if you or someone you know is handy with a soldering iron you may want to try checking the following post:

http://frontierdesign.com/forums/post/1438/#p1438

We prefer to do these here but if you're willing to it may help these issues.

CS

263

(5 replies, posted in AlphaTrack:User Forum)

Hi ed1,

It's possible that there's an intermittent fader connection in a wire or wiring harness causing these issues.  That could cause it to work sometimes and not work other times.  If this happens again, try the recalibration.  If eventually the recalibration doesn't work let me know, it could be a problem like I explained above.

CS

264

(3 replies, posted in AlphaTrack:User Forum)

Hi Strat1376,

I finally got a copy of Sonar 8.5 and everything seems to be working properly in Windows 7 except for some changes cakewalk has made to their instrument tracks.  Long story short, you used to be able to access EQ parameters from Instrument tracks, but now they're just recognized as 'midi tracks' and this doesn't let you control EQ with a controller.  Waiting for a response from Cakewalk on this issue.  But everything else works normally.

I'm guessing you have a 64-Bit Windows 7 machine and want to use Sonar 32-Bit.  The error message you've mentioned sounds like it's possible that when you were manually registering the plug-in (.dll file) you may have typed a character or two wrong in the command prompt.  I'd double check that and if you're still having issues I recommend sending a screenshot or two to (of the command prompt and any error messages) to support@frontierdesign.com

CS

265

(3 replies, posted in AlphaTrack:User Forum)

Hi lorneyb2,

If you're using EW Play in another program (like Logic, etc.) as a plug-in then you should be able to get to the 'mod wheel' parameter by using the AlphaTrack's 'plug-in' mode button and then paging through the parameters until the 'mod wheel' parameter is found, then you'll be able to use the encoder (or fader if you use the flip button on the AlphaTrack) to control the mod wheel.

Hope this helps....

CS

266

(18 replies, posted in AlphaTrack:User Forum)

Hi fabiotto,

You can try uninstalling the AlphaTrack then reinstalling it.  Also, when you reinstall it (at the end of the installer) does it say that the installation was successful?

Then *After your computer finishes rebooting*

then, plug in your AlphaTrack.  Does the AlphaTrack icon pop up?  In spotlight type in 'activity monitor' Does:

AlphaTrack Menu
AlphaTrackDaemon

show up on the 'my processes' list?

CS


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

Hi Domenico,

When you use MidiOx does the AlphaTrack show up in options/midi devices?  Does the AlphaTrack show up there under both 'input' and 'output'?

If it doesn't show up there under midi input and midi output then that means after reboot, your computer doesn't recognize the AlphaTrack as a midi device for some reason.

Another thing you may want to try is to uninstall the AlphaTrack by following the instructions here:

http://frontierdesign.com/download/pdf/ … _Guide.pdf

then reinstall the AlphaTrack and see if that helps.

Also, you may want to check this out to see if it's a possibility:

http://www.rme-audio.de/en_support_tech … q_10entryd

CS

268

(18 replies, posted in AlphaTrack:User Forum)

There is one other thing, fabiotto.  Is it possible that you're using the 64-Bit kernel in your Mac Pro?  If so, try switching to the 32-Bit kernel.  Our latest drivers don't yet support the 64-Bit kernel.

CS

269

(18 replies, posted in AlphaTrack:User Forum)

Ok, this means the drivers didn't install properly.  Can you tell me exactly how you're installing the drivers?  Just to make sure you can actually throw away the CD that came with your AlphaTrack.  Everything on that CD is available on our site but I recall having a customer that thought he was installing the latest drivers but he had the CD (with older drivers) in his CD rom and every time he tried installing the newer drivers it would, instead, take the drivers from the CD; so just get rid of the CD and let me know exactly how you're installing the drivers.  Other than drivers not being properly installed the only other thing I can think of is that the AlphaTrack isn't getting power.  Does the AlphaTrack LCD screen light up when you plug it in?  Does the AlphaTrack still work on your other computer?

CS

270

(18 replies, posted in AlphaTrack:User Forum)

Sure,

All you need to do is CTRL+click on the aux track or master track and select 'create/select Arrange track'.  The AlphaTrack will only be able to 'see' tracks in the 'Arrange' view.  So by creating these tracks in the arrange view you'll be able to access them with the AT.

CS

271

(1 replies, posted in AlphaTrack:User Forum)

Hi Ikingston,

We've been barking up that tree for some time now (Vegas and Acid support).  The TranzPort has support but the AlphaTrack support never materialized. 

Sorry.

CS

272

(2 replies, posted in AlphaTrack:User Forum)

Hi tannoy,

Sorry to hear about your AlphaTrack, unfortunately it does sound (like the others on this forum) that there is a hardware issue with the fader.  They are supposed to be tested prior to being boxed up and shipped out.  I suppose it's possible that there is an intermittent failure that passed testing and that during shipment something came loose and caused the problem you're experiencing now, it's also possible that these failures have 'slipped through the cracks'.  At any rate, like the others, all I can suggest is either returning it to the dealer you purchased it from for a replacement or you can return it here for a repair.

Sorry for the inconvenience.

CS

Hi irecord,

Unfortunately we don't have a copy of Cubase here to test it on (all the keys seem to be out of date and our request for another is taking a while).  But from what I remember I don't think you'll be able to control this with the AlphaTrack.  It would be nice, I know, but if I recall this control may not have been part of the SDK so we wouldn't have been able to map it to a control.

CS

274

(9 replies, posted in AlphaTrack:User Forum)

Hi powlow,

I tried the Oxford Reverb plug-in and I experienced the same thing you did.  It's not unusual for this to happen to controllers in ProTools for 3P plug-ins as it may be a HUI limitation.  If other controllers using HUI protocol can access more than 3 or 4 parameters on this plug-in it would be good to know.  But I don't think there's much to do about it.

CS

275

(1 replies, posted in AlphaTrack:User Forum)

Hi Whooricane,

This definitely sounds to me like a hardware issue.  The recalibration test doesn't sound like it's working right at all.  I'd return it to the dealer you purchased it from for a replacement.  Otherwise I would contact support@frontierdesign.com and see about getting it repaired.


CS