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

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

626

(0 replies, posted in AlphaTrack:User Forum)

WestEnd wrote:

Hi Guys,

Well when it's working, AT is fantastic, but after having it just about 5 days it's only been working about an hour.

I'm using a CAT5e USB extender through a Belkin powered hub to connect the AT since my computer is in a small machine room about 25 feet away. I'm running SAWStudio on a fresh install of Windows XP. The AT is just acting erratically, turning on and off whenever it feels like it, messing up my MIDI port assignments on SAW at will, etc.

Based on all of the things I've read here so far I'm not sure what's wrong. My computer is heavily grounded, I can't account for the integrity of the data through the extender/powered hub combo, but it looks like these things have right next to the computer, which in my case is impossible.

Any thoughts?

Thanks

Ken Dabek
West End Recording

CS:Hello Ken,

Can you try to connect the AlphaTrack directly to the computer as a test? I understand that you can't work that way normally but it might at least let you know if your Cat5 setup is inducing a problem. I have successfully used a small Geffin Cat5 extender at that length, so I know it can be done. You might also try an active USB extender cable instead of the Cat 5 if that is a problem.

Also, which side of the CAT5 is the powered hub on? It should be next to the AT.

Make sure that you don't have USB power saving enabled on your machine. As a few other on this forum have found, it can cause all sorts of headaches.

And try a different USB port for the whole setup. It could be a conflict happening somewhere.

CS

WestEnd wrote:

Yep! it was definitely the extender. I connected the AT directly to the DAW with a 3 foot USB cable and of course previously turned off the power saving features and it's been running perfectly for the last 12 hours. So it looks like I need a new extender.

Which Gefen model have you used? I was looking at the USB-1 as it is one of the less expensive models, I'm reluctant to spend $400.00 on a higher end model.

Thanks,

Ken Dabek
West End Recording

CS: I don't recall the model but USB-1 sounds right. It was pretty much their cheapest model.

You might also just try a cheap active USB extender cable with your powered hub on the ATs end if you only need to get 25'.

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 684

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
edIT wrote:

I am using a Dual Boot Macbook Pro with Cubase 4.1.3. In mac os X the "auto select" feature works fine. However in Windows XP I can't seem to get "auto select" to work even though the box is checked. Whenever I click on channels in the Cubase arrange window, the AT stays on "channel 1" and I have to use the "Track < , >" buttons on the AT to get to the channel I want to control. Any ideas?

CS:Hi edIT,

did you check the "Sync Project and Mixer Selection" in the Editing/Project and Mixer section of your Cubase Preferences?

CS

edIT wrote:

That box is checked. Still no luck

CS: Hmm, I have 4.1.3 on an XP machine and it works just ducky. Have you installed the latest AT driver AND control plug-in from our website? On Windows machines you have to check the bos during the driver installer to also update the plug-in, whereas with the Mac its a separate file.

CS

edIT wrote:

got it working you were right. the problem is when you install the Alpatrack drivers it automatically installs the Cubase component in the Cubase folder. I didn't realize that component was version 1.03 and the latest is version 1.0.4


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

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

628

(2 replies, posted in TranzPort:User Forum)

glvaughan wrote:

Help.  I've been a Transport user for years, but now I'm stuck. No icon, no binding.

I've loaded Transport 1.3 on an old iBook G3 running OSX 10.3.9.  My sole use for this setup is to trigger audio drum files (in Quicktime) to play along with at an upcoming party.  I use Midi Stroke to translate the incoming midi signals from Transport into SPACE commands on the keyboard.  This all worked great last year.

The hard drive on the iBook (blue clamshell) is so small that, in order to reclaim needed space,  I completely erased the drive and reinstalled system software and TransPort 1.3.  Now, TransPort doesn't work at all.

No icon appears in the menu bar, and I am unable to bind the remote with the TransPort unit.  When I plug in the remote via the USB port, it blinks a couple of times, but is then unresponsive - the LED doesn't blink when I press the button.  I know the computer "sees" the remote, because it shows up in the audio midi setup in the utilities folder.  So, it appears that the USB port is working.  I've also uninstalled and reinstalled Transport several times.  No luck.

I use Transport in my recording studio with a Mac G5 and Cubase 4, where everything runs fine.  That eliminates any problems with the TransPort hardware.

So, what am I missing and how do I get this back up and running properly?

CS: Hello glvaughan,

If you aren't getting an icon for the TranzPort Manager then it won't bind. So we have to sovle that problem first and then the binding will probably be fine. Since we know the unit physically works on another machine then we can focus on the Mac. Is there any chance that when you   installed the OS on the Mac that you chose not to install the BSD Subsystem in an effort to conserve HD space??? That would do it. TranzPort needs that code to operate correctly.

If this is the case then run the OS installer, select 'Customise' and just add the BSD Subsystem back in.

CS

glvaughan wrote:

Bless you Brian!  You were absolutely on target.  Thinking I had no need for it, I chose not to install the BSD subsystem.  Once I installed BSD, the missing icon magically reappeared.  Thanks so much for your prompt solution.  Massive relief here.


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

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
dariin wrote:

Hi
I change to Tiger on my studio and  bought a laptop that comes with Leopard fot home.
In neither one works Alphtrack. I thought it was my new Nuendo 4 but is the OS.
When are you doing an update?

Thanks

James Steele wrote:

This is odd.  I'm using Alphatrack with Digital Performer and using the latest version of Leopard and it's the bee knees over here.  Well apart from rare times when I lose communication with the AT... but for the most part it's working.

Simplemind: Hi,

CS is out of the office today, so let me see if I can help. Lots of users run AlphaTrack on Tiger and Leopard, in a wide variety of configurations and applications. I don't have a copy of Nuendo 4 handy, but I'm running AT with Cubase 4  right now on a Macbook Pro with 10.5.2.

Let me see if I can add anything to what you have tried. Now, when you click the "+" in the upper left hand of the Devices Dialog window there should be a Frontier AlphaTrack in the list, which might be easy to miss if you are only looking for AlphaTrack. Once you have selected it you will see Frontier AlphaTrack in the Remote Devices section and clicking that will show a new panel on the right for selecting the MIDI input/output along with key mappings.

One thing that I'd seen on one of our earlier Nuendo setups was a "component" folder instead of or in addition to the "components" folder. When you put the AlphaTrackCN.bundle file into "components" are you seeing other bundles as well? And, finally, if you still aren't seeing it could you open Console (Applications/Utilities) before firing up Nuendo and then as Nuendo starts up see if you are getting any relevant error messages.

Let us know what you find.

CS: Hi Dariin,

one other note, you didn't mention if the AlphaTrack was bing recognized by the computer itself. When you connect the unit do you see an AlphaTrack icon appear at the top of your screen? If so then the drivers are probably working just fine and I would check as Simplemind suggests above.


If not then either something is wrong with the driver install, or the USB connection. Let us know what you can and we'll be glad to help.

CS

dariin wrote:

I can see the AT icon on the top of my screemn
Ok, problem solve.
Sorry for taking so long to answer.
It finaly works, it was my fault because I put the bundle in the Contents folder instead of the Component folder inside the Contents one.

Thanks very much

CS: Fantastic!

Enjoy,

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

630

(3 replies, posted in AlphaTrack:User Forum)

Hello Domenico,

Ya, I think maybe you missed something. If you check the Cubase/Nuendo guide at http://frontierdesign.com/download/pdf/ … v1.0.4.pdf you will find that F1 and F2 are used to control Page/Prameter Up and Down in the various button modes. For example F1/F2 select bands in EQ mode, or sets of parameters in Plug-In mode.

Hope that helps.

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 684

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

631

(0 replies, posted in TranzPort:User Forum)

Royce wrote:

Hi .
PC  - XP SP2
Installed latest Tranzport drivers (device manager shows 1.4.0.0)
There are no MIDI input or outs in MidiOx or Sonar

Windows Audio service is Started in the Administrative Tools\Services control panel.

Installed and rebooted several times.
Removed all other Midi devices.
Tried WDM properties
  tried to used audio /not use audio - Map and don't map
  Midi features turned on
  Mixer on/ off

Any thoughts?

Royce

CS: Hello Royce,

Does the TranzPort task bar icon show up when you connect the USB interface? And does it link to the TranzPort remote ok?

Can you elaborate on the "all other MIDI Devices"? More specifically, what devices do you currently have, AND previously had since the last XP install? It may be that you have maxed out the XP MIDI port list and need to clean some out. You can find details on that problem here.

CS

Royce wrote:

Hi CS
Does the TranzPort task bar icon show up when you connect the USB interface? Yes
And does it link to the TranzPort remote ok?        The binding? Yes

I have been using the TranzPort for some time and it has been working beautifully.

Devices... MidiSport 4x4 , BCR2000 - Midi Yoke - but all were happy before.

I have now removed my MidiSport & BCR2000

I had a look at the URL - regedit- and although there are multiple entries of the same driver the list only goes to Midi6

I deleted all of them anyway and uninstalled the tranzPort drivers and my M-Audio Delta 66.
Rebooted and XP found them both, but in regEdit  Midi to midi3 are all wdmaud.dll
MidiOx can't find a Midi interface.

Both TranzPort Drivers appear in Device manager

Thanks for the help
Royce

CS: Very strange. Normally if the unit is binding and the task bar menu is working then we know the drivers are loaded properly and the computer is seeing it just fine. At that point the 2 things that can then prevent its MIDI ports from showing up are the Windows Audio Service being disabled, or too many MIDI ports. Both of these seem to be ok on your system.

You could try connecting to a different USB port however I'm not sure that will help. Assuming not, I would try removing the drivers and resources following the steps as detailed on page 10 on the TranzPort User's Guide, and doing a clean install.

CS

Royce wrote:

Hi CS
I did a complete clean install and still no luck.
Looks like the many hours of a XP install unless you can think of anything else?

Thanks anyway

Royce

Delax wrote:

I have the excact same problem.

The Windows Audio service is started and the blue icon is visible and it works in ITunes.
It is just not visible any where in windows as a MIDI device and not in Cubase 4 either.

I got a Synchrosoft and an ILok and AMT8 8 MIDI port device from Emagic on USB too.

Could it be the AMT8 that is shadowing?  I also have an old SB Live for windows sound.

I'll try for some time and return it if I can't make it work.  Itunes tranzporting is not enough for me and life is too short for windows driver hell.

I find it a little strange that the driver says 1.4.0.0 when the installer is named 1.4.1?

Delax wrote:

Ok now I have solved the problem.

Tranzport is made to show up in devicemanager as two devices. TranzPort and TranzPort WDM Interface.

Somehow the WDM interface had a yellow exclamationmark wich it certainly shouldn't have after installing the 1.4.1 exe file. (windows could not restart by it self either)

I just thought it was windows seeing the same device twice.

Just update the drivers from the devicemanager->update driver on the unknown device(I updated the TranzPort too) and it will turn into the TransPort WDM Interface wich is the MIDI device.

It is the fact that windows finds two devices that is mistaken for a windows buggy "I have found a lot of brand new hardare" shit :)

The installation file TranzPort_Win_Setup_1.4.1.exe seems not to work in all situations.  I had to update the unknown device afterwords with the drivers from the exefile to make it work.

Royce wrote:

Thanks Delax.
I tried all of that before. I don't have the yellow question marks on any of the drivers.
I reinstalled all the Midi devices (BCR, BCF MidiSport 4x4) and everything is working except the Tranzport.
All the lights are on but no Tranzport midi device in the list.
I reinstalled the 1.0 version from the CD, but still no luck.

Royce wrote:

I finally tracked down the solution.
The Plug and Play enumerator was somehow uninstalled. I have no idea how.

From this web page
http://weblogs.asp.net/lkempe/archive/2 … 75765.aspx

   1. In services, check that WinAudio service is enabled, set to automatic, and running.
   2. In Device Manager, System Devices check that Plug and Play Software Device Enumerator is installed and running

If not , then you need to reinstall it:

   1. Copy machine.inf from %windir%\inf to your desktop
   2. Remove line ExcludeFromSelect=*
   3. Use Add new hardware wizard using the Have Disk option
   4. Select the machine.inf you saved on the desktop
   5. Install Plug and Play Software Device Enumerator

What a business. I though that the plug and play service was running but I missed this.
Thanks for all the effort guys.

Royce

CS:Wow, good find Royce. I have to admit, not being an expert in all of the deep, dark secrets of Windows myself, I never would have known that one. You get a gold star for the day!

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 684

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
Wanda wrote:

I have tried this on several machines with a WaveCenter card and I get freezes and very slow response. Plogue Bidule uses ASIO drivers and works well with other cards such as Gina3G.
Any help would be great!

Marcos wrote:

I have same problem when using WC/PCI with ASIO, in Samplitude or Logic Audio...

CS: Hello Wanda and Marcos,

not sure why you would have difficulty using your Wavecenter cards with ASIO apps but we can take a look at it here. I have used Wavecenter with all of the above listed programs. Can you tell us a bit more about your systems, applications, and driver versions?

Have you checked IRQ assignments on your computers? Try moving the Wavecenter to another PCI slot if it is sharing with graphics, networking or another audio device.

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

Regards,

CS

Wanda wrote:

Hello CS, I have tried this on several machines.

Intel 3.2
Intel 925 x motherboard
WinXP SP2.

Also: Intel core2 2.4 E6600
Intel DG965WH Mobo
onboard video
2 gigs 667
WaveCenter is on IRQ22 and shares with no other device.
No other audio devices are turned on in the bios.

I have seen other posts at Plogue and others have this issue.

Please help resolve this.
Thank you

CS: Hello Wanda,

We are in Germany at the Music Messe for the rest of this week. I'll look in to it further when I return.

CS

CS: Hello Wanda,

Yup, we are back, and I am guilty as charged. Totally forgot to check this out when I got back.

So I spent some time playing with this today. It appears to be true that the Wavecenter creates a CPU loading issue. Much more so than even the bigger Dakota card does. This is due to a combination of factors. First, the Wavecenter does more of its processing in the computer's CPU than the larger Dakota does by design (the Wavecenter is an older, less efficient, design).

And secondly, and probably more importantly, Bidule does not appear to offer the user a way to enable only specific hardware channels for use. This is a big deal because unlike WDM audio, the ASIO spec calls for all enabled channels to be active ALL OF THE TIME. Even if they aren't actually playing audio at the time. This means that all 20 Wavecenter channels (10 in + 10 out) are loading the CPU the moment you add it, even if you only have a single VSTi output assigned. Most programs, like SONAR or Cubase allow you to enable only the channels that you are actually using, thus eliminating the problem.

In the next few days we will look to see if there is anything we can do to ease the problem. I just don't know yet if we can do too much.

However, by using the Wavecenter as a Windows Direct device instead of ASIO it seems to work fine.

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 684

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
Jim Bannockx wrote:

Hi,
I try to use alphatrack as much as possible in my working environment. Now , when i'm in arrange window in logic and I use my mouse to select a bus (sends) on a highlighted track the slider on the right changes directly to the bus slider, to make the changes i wanna do. On the other hand, if I do the same on alphatrack. I select send... destn. bus 1. I can see the change on the selected track but the slider on the right stays on output 1-2, it will not change to the bus slider for further editing. This is the case when the  selected bus track is empty, without plug-ins.  If there is a plug-in active, it works.
For me it's a small problem because, after inputting a bus on a track with alphatrack, I have manually to select the bus track to put a plug-in on it.  so,more movements to do..

that's it. Hope my english is not soooo bad.
grtz. Jim

CS:Hello Jim,

Your English is fine, but I am not sure I fully understand your post. Is the following correct?

Task: Adding a send to a track, and giving it a previously unused destination, ex. Bus 3, which has not been configured in the Mixer yet for any other track and does not currently appear in the Mixer window.

Result: If done using the mouse Logic will automatically add, and display the new Bus channel to the Mixer window and show it on the right side of the Track Inspector panel. You can then add plug-ins to the desired Bus channel directly from the Track Inspector, or the Mixer.

If done with AT, Logic does not automatically display the new Buss channel in the Mixer window so it doesn't appear in the Track Inspector either. Meaning you must add it to the Mixer window manually the first time, after which it behaves as expected.

If this is an accurate description of the problem you are seeing then I believe this is a low level difference in how Logic handles external controllers vrs. mouse/keyboard control and may not be something we can control.  I will check with our Logic plug-in programmer to confirm whether we have any options to more closely emulate the Mouse behavior but my guess is that we don't. I'll post back when I know for sure.

CS

Jim Bannockx wrote:

You described exactly the problem I have. Thanks for the quick response. If no solution is available  right now, I change my templates in logic, and put some plugins on the first 8 busses, in case I need them. A workaround 4 the moment.
By the way , it's great to have straight to the point feedback.... Great company.

grtz. Jim.

CS: Hello Jim,

ok, we had a chance to look at this a bit deeper, and just as I suspected, it is an issue within Logic itself. We can't be sure if it is intended behavior for some reason, or more likely an oversight in their external control code. If you try the same thing with a Mackie Control for instance, you will see the same result.

You current work-around seems like a good way to deal with it for the time being.

CS

Jim Bannockx wrote:

Thank you for the answer.
J.


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

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

634

(0 replies, posted in TranzPort:User Forum)

holywellwalker wrote:

After a year of flawless operation, my tranzport is doing strange stuff. Brand new batteries, link light showing on both controller and receiver, but nothing comes up on the tranzport's screen when I press buttons ( with the exception of the battery check).

Nothing has changed software, system or cable wise. Only a few days ago I was showing someone how great this unit was- I have reinstalled the mac driver, restarted, changed batteries.  Still kaput. Any ideas please?

Mac G5 dual 2.7 Ghz running 10.4.11,  Logic 7.2.0 etc

CS: Logic may have just confused its MIDI settings, which is not all that uncommon. Go to Logic/Preferences/Control Surfaces/Setup and highlight, then delete the TranzPort icon. Close and relaunch Logic. Normally that will fix it.

CS

holywellwalker wrote:

OK. That works. Thank you.


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

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

635

(3 replies, posted in AlphaTrack:User Forum)

dogpatch wrote:

Hi,
I have installed the latest support for AlphaTrack in Logic 8. All of the functions seem to work as expected (dedicated keys, function keys, etc), except the motorized fader will not control the onscreen fader. The other way works - when I switch to a new track, the fader snaps to the correct position, and when I move the onscreen fader with the mouse, the motorized fader tracks it. However, when I move the motorized fader, the fader onscreen does not reflect the change.

Any ideas? Could I have an incorrect parameter in the setup?

Thanks.

Setup:
AlphaTrack Manager Version 1.3.0

AlphaTrack.bundle Version 1.1

LogicPro 8.0.1

Mac OS X  10.4.11
4 x 2.5 GHz PowerPC G5

CS: Hello dogpatch,

there are a few things you can check. First try the 'Rebuild Defaults' option under Logic, Preferences/Control Surfaces. If that doesn't do it open 'Setup' from the same location, highlight the AlphaTrack icon and make sure that the MIDI In and Out settings on the top-left are both set to 'Frontier AlphaTrack'. If THAT doesn't do it then delete the AlphaTrack icon altogether, close Logic and relaunch.

Lastly, try calibrating your unit by pressing Shift+Stop+F4 and releasing.

CS

chris.buck wrote:

Hello, same sort of thing as Dogpatch querie. The alphtrack fader moves the screen fader , the screen fader dosent move the alphatrack fader.  Also when I change track from the alpha track buttons or clicking on a track on the screen, the alphatrack fader dosent move to the screen fader level set on that track but the track fader position jumps to the alphatrack last know position. as you can imagine this is a pain.

There also appears to be 2 alpha tracks in the setup menu in control services, one of them changes to italics!  i trid to delete it but cannot see how too within logic. There is only 1 alpha track component within the loic midid packages.

I have tried the bypass controller, set up etc within control surfaces, i havent tried the calibrate controller yet. Both the alphatrax midi channels are selected within setup also.

Strange as it was working perfectly until a few days ago.

Thanks.

Setup:
AlphaTrack Manager Version 1.3.0

AlphaTrack.bundle Version 1.1

LogicPro 8.0.1

Mac OS X  10.5 2 x 2 GHz PowerPC G5

CS: Hey Chris,

it actually sounds like you are having the exact opposite fader behavior as dogpatch, but in this case I still think it has the same root cause. Something is messed up in your Logic Preferences. You want to begin by deleting all AlphaTrack icons in the Logic Control Surface Setup. Just highlight the icon and select 'delete' from the 'Edit' pull-down menu on the Setup panel. If you have 2 of them for some reason then be sure to delete them both. Then close Logic and relaunch it.

Let me know if that doesn't do it.

You should perform the calibration routine as well just for good measure.

CS

chris.buck wrote:

Hello CS

tried all the things above.I deleted the drivers, the bundle from logic midi contents, reloaded them all etc. the alphatrack fader now just drives to the top even after the calibration. when i pull the fader down it just drives straight back up to the top again, even when i not in logic!

do you think there may be  problem with the device? not sure if my warranty has now expired also.

regards, Chris.

CS: Well if you have any other computer handy (Mac or PC) you can always try loading just the basic drivers on it to see if the same behavior occurs.

When you perform the recalibration routine does the fader travel up and down normally?

Try opening the Mac Audio/MIDI Setup panel and creating a New Configuration on the MIDI page.

If you are still having troubles give our support line a call at 603-448-6283 x107.

CS

dogpatch wrote:

Hi,
I tried the first 3 suggestions (rebuild defaults, Midi in/out, delete icon) and they had no effect on the behavior. However, recalibrating the unit DID fix the problem. Thank you for your help.

chris.buck wrote:

hello CS

I started from scratch again last night, removed every thing. reloaded everything re-calibrated the fader and bob's your uncle it all worked ok. Really chuffed. Thanks CS. had a guess at your name, is it Carl Summers? just a guess.

Makes me so happy when all works well in my computer world.

Kind regards, Chris

CS: Glad to hear you both got everything sorted out.

No Carl here, but good try.

Enjoy,

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 684

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

636

(0 replies, posted in AlphaTrack:User Forum)

jpoprock wrote:

Hey all. I've been messing with my new Alphatrack and it's great. I must say there is quite a bit of a learning curve to it though. There are so many shifts and alt functions that it will take some memorizing. But for basic functions, it's great!

I was fixing a vocal track last night with Autotune 4 and I noticed when the plugin was active, that some of the parameters were surrounded by a blue box. Weird parameters that I'd never use. Midi stuff I think. I wasn't quite sure if those were assignable, or if AT just senses what it can control and does it?

Also, when I pressed the Plugin button, and then turned it, it would cycle from A-G. Autotune was on A, but when I'd turn the knob to cycle thru them and return back to A, Autotune wasn't available. I'd have to close the plug in box that was once Autotune, and then reopen the plugin window to see the contents. Mind you, I didn't have any other plugs running except Autotune, but I feel that when I returned to A after turning the dial, Autotune should have been infront of me and it was not.

Any tips?

Thanks!
Jason

CS: Hello jpoprock,

While in Plug-In mode you can scroll through each of the insert slots (A-G) of each channel. Because of the way AlphaTrack has to communicate with ProTools, if you scroll to quickly, it can loose track of which slot it is looking at. In that case simply changing channels or modes momentarily will usually correct its focus.

Anyway, the blue highlighted parameters that you see on a plug-in window should appear in groups of 4, and move as you scroll through a particular plug-ins parameters. This is because an actual HUI (which all 3rd party manufacturers have to emulate in ProTools) has 4 parameter control knobs and banks through them in sets of 4. The highlighted ones are to show you where the actual HUI knobs a focused at that moment.  With AlphaTrack, as you scroll though parameters (1 at a time) it will go through each of those 4 highlighted ones, and then jump to the next set of 4 (1 at a time). So the highlights just give you some idea of what group od parameters the AlphaTrack it going through at that moment.

Hope that helps.

CS

637

(2 replies, posted in AlphaTrack:User Forum)

Hello APUser,

- yes, I can see the RPG-8 fader thing happening occasionally too. I am not sure what causes this device to interpret the touch message as in increment in some cases. I will make a note to check this at the next opportunity.

- It appears that Reason doesn't send an initial device channel message if launched with the mixer selected. This one may be out of or control but we'll note it for checking as well.

- Reason uses a Midi value scale such that hard left is -64 and hard right is 63. So using any number greater than 1 will have this result in one direction or the other. However, if we defaulted Pan control to 1 then it could take many turns to do pans and we have been criticized for doing this in the past. So we default to 8 to allow quick initial adjustment, and then fine tuning if desired after that. In course mode, a quick turn left and back to center will bring you back to 0 everytime.

- Touch strip resolution should be 1 and 4 beat resolution depending on whether you are using 1 or 2 fingers. Let us know if you are seeing something other than that.

Hope this info helps and that you enjoy using your AlphaTrack with Reason.

CS

638

(3 replies, posted in TranzPort:User Forum)

As a brief update to this. We have seen in the DUC forums several reports of PT8 installations having trouble seeing MIDI ports correctly. The usual symptom seems to occur randomly with PC users where the MIDI Control Surface MIDI Port selections show up only as 'emulated' but don't communicate successfully back to the device.

This problem is not specific to any particular brand or type of hardware. In fact there are several Digi C8 controllers users reporting the same thing.

So, while most PT8 installations appear to be working fine, there does appear to be some potential for PC based systems, to have an issue with MIDI ports. We are watching for any input or updates from Digidesign addressing this problem.

CS

Ok, so it sounds like you are stuck on step 4 above. The TranzPort User's Guide describes the binding (Link) procedure in detail. If you are only pressing the Link button on the USB interface then it will never bind. This is because both pieces need to be looking for each other at the same time. Just like setting up a wireless mouse or keyboard.

Here's the short version. Press Shift+Battery on the TranzPort remote so that it says "Binding, Please Wait.." in the display. Then immediately press the 'Link' button on the USB interface. Within a couple seconds they should find each other and the green 'Link' LED should light. If you wait more than 10 seconds between commands then the first device will give up before and there will be no joy.


CS

640

(8 replies, posted in TranzPort:User Forum)

Hello Stratcat,

I'm guessing that 1 of 3 things has happened. Either the contrast has accidentally been turned down, the TranzPort isn't in 'Native' mode, or what's more likely, the midi port settings have changed in Sonar.

You can confirm the contrast thing really easy by simply pressing the battery button. If the battery level displays ok then the contrast isn't the problem. And click on the TranzPort icon to confirm it's in 'Native' mode.

What we see a lot with Sonar specifically is that the MIDI port settings in the SOnar/Options/Control Surface setup get changed really easily if you ever launch Sonar before all of your MIDI devices are turned On  or connected. Sonar just reassigns things on its own.

Check these things out and let us know what you find.

CS

641

(1 replies, posted in WaveCenter/PCI:User Forum)

Hello Dave,

Sorry. The Wavecenter and Dakota cards work only in standard (5volt) PCI slots.
As you correctly noted, PCI-X is 3.3 volt, and PCI-E is a completely different interface altogether.

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

Hmm, ... can you tell us a bit more?  What DAW application/s you are using it with? Did you get the basic driver installed ok and just need help configuring it with your app, or its still in the box and you don't know where to begin?

Here are the basic steps.

1. go to http://frontierdesign.com/Support/Downloads/TranzPort and download the latest drivers and control surface plug-in for your DAW if applicable. Also, scroll down the page and get the latest user guide for you DAW as well.

2. With the TranzPort disconnected, run the driver installer as described in the Quick Start Guide that came with the TranzPort. Or you can download that document as well from the same location.

3. Connect the TranzPort USB interface, run the "New Hardware Wizard", and restart your computer if needed.

4. Verify that the TranzPort icon is now in your taskbar and that the TranzPort is successfully bound (Linked) to the USB interface. Binding instructions are also in the Quick Start or general TranzPort Users Guide if needed.

5. Follow the setup instructions in the appropriate DAW user guide to configure TranzPort as a controller.

If you are still having difficulties let us know as much as you can and we'll try to help you from there.

CS

643

(5 replies, posted in AlphaTrack:User Forum)

Ah, I see. I think we were both a little confused as I was not familiar with the X-Ray feature before.

Currently it appears that AlphaTrack can not access that command. for the exact reason you mention. We would need to either expand the AlphaTrack Tools list to include those additional commands. Or provide a literal key-stroke selection in the AlphaTrack Tools menu that would allow it to work in conjunction with the Sonar Key Bindings menu. The later of these 2 options was done with our TranzPort controller which was introduced before Cakewalk added the Tools menu options. This way users could continue to use existing Key-Bindings if they chose to.

Anyway, I will put in a feature request on the wishlist. I can't say when it may be addressed yet but at least it will be officially logged. Thanks for clarifying your request.

CS

644

(4 replies, posted in AlphaTrack:User Forum)

Hello Fabio,

No reset on the AlphaTrack. But its not likely that the problem is actually with the AlphaTrack itself, but rather with the way Nuendo is interpreting its messages.

Here's some things to check.
1. click on the AlphaTrack desktop icon and make sure it is set for 'Native' mode.
2. Check your Device Setup configuration and make sure that you have 1 instance of AlphaTrack and both MIDI ports are set to itself. There should be no other controllers such as Mackie Control assigned unless you actually have one of those devices also connected.
3. Go to Device Setup/MIDI Port Setup and make sure that AlphaTrack is NOT enabled as an "All MIDI" device. Or an MIDI tracks in your project could incorrectly react to AT messages.
4. Try removing the ALphaTrack from the Device Setup and adding it back in again. This might reset Nuendo preferences in case they have become corrupt.

I'm  assuming that it was working ok previously and that you have current updates for ALphaTrack and Nuendo3. . Are there any other changes that you have made to your MIDI configuration since that time?

Check these things out and let us know any new details that you can. Also, Mac or PC? OS?

CS

645

(10 replies, posted in AlphaTrack:User Forum)

When you installed the new plug -in  did you be sure to delete the existing AlphaTrack.bundle that originally shipped with Logic. The Apple version is very buggy and if somehow they were both on your computer it might cause all sorts of bad things to occur.

CS

646

(4 replies, posted in AlphaTrack:User Forum)

Ya, you are probably right there. I suspect 99 was the displayable character limit in our code, or something like that at the time. I believe PT itself allows 999.  I think you are the first person to mention it to us though.

I'll enter it in the 'wishlist' for future attention but I just can't guaranty it will happen to soon.

CS

647

(2 replies, posted in AlphaTrack:User Forum)

Hi Sunshy,

Very ggod question, but I don't believe it is possible. I am not aware of any way  for us to access individual clips in that way using the current Steinberg SDK.

We would have to do a mouse emulation or something of that nature with a knob which another hurdle altogether. Something for us to put on the wishlist. :)

CS

648

(5 replies, posted in AlphaTrack:User Forum)

Hello MurMan,

The 'Key Bindings'  in the SONAR plug-in doc are actually referring to the command set in the Sonar/Options/Key Bindings list rather than simple key stroke emulations. The Sonar/Tools/AlphaTrack menu gives you a shortcut for setting those up put doesn't offer all of the potential options of Sonars complete Key Bindings page. For instance, context sensitive pairings can only be made using Sonar's own Key Bindings page.

There may also be better abilities to bind key stroke combinations but I am not sure of that. However the Key Bindings list is pretty extensive and includes the ability to open/close most windows and functions.

So, if you can't find what you are looking for in the AlphaTrack Tools menu, check out the Sonar/Options/Key Bindings panel and perhaps you can find it there. Just remember, if you start editing with the Key Bindings panel, it will supercede anything that you have setup on the AlphaTrack Tools menu.

CS

649

(6 replies, posted in AlphaTrack:User Forum)

Hi Gothboy,

glad to hear you sorted out the problem. Ya, I can see that might be confusing.

On the marker thing, Pro Tools will only allow us to move through them in numerical order.  This means that if you drop markers out of sequence on the timeline, AlphaTrack (or any device using HUI emulation) will jump back and forth in  the same order as you dropped them. Kind of annoying really, but unfortunately nothing we can change from our end.

CS

650

(6 replies, posted in AlphaTrack:User Forum)

Hello Gothboy,

I'll have to look at this one. We've never heard this symptom before. What tool do you have selected from the toolbar when this happens?

CS