Faderport

 Got it to "work" to a certain extent for X1 Expanded and X2, but never managed to get all the functions to work properly. "Window View" has never worked properly for me. 

That "code" refers to registering a dll.

Got it working ok in X2, but then I started having the issue where loading some projects with it connected makes it take forever to load, and just disconnected it. 

Personally I will never buy a Presonus product that needs to communicate with a computer. Their drivers for their audio interfaces are spotty, and the FaderPort has been the most unused piece of gear I've ever purchased, because it just never worked consistently.

Peace,

Tunes

tbosco


I have a 32bit system and here is the bug fix code required to get Faderport to operate fully in Sonar:

regsvr32 \"c:\\Program Files\\Cakewalk\\Shared Surfaces\\FaderPort.dll\"

It must be typed (in the Command Prompt) exactly as shown including quotation marks.

The 64bit fix is similar I think, but not exactly.  Google it.

It's a similar issue with the Frontier Design AlphaTrack - excepting that the 64 bit version of the driver needed to be renamed to alphatrack64.dll so it wouldn't name clash with the 32-bit one. Then both dll's are regsrv'd. I doubt Presonus is any different, and the cakewalk surface API is pretty straightforward. If you open an old project in 64-bit Sonar that has a 32-bit surface of the same name, you might have to delete the surface from the project first and then re-add it so that is will use the 64-bit version of control surface driver.

Grif I'm glad you've had better experiences with PreSonus. My post wasn't meant to be a universal declaration of their suckiness- rather, a personal conclusion based on my experience with at least 3 different PreSonus products that were designed to interface with computers and did not do so well.

At church we have a couple of Presonus units hooked up to a Mac for recording. They refuse to run at anything other than their native 96k sample rate, even thought they say 44.1, 48, 88.2, etc are supported. Half the time they don't sync properly and are not seen by Pro Tools (10.) We then have to power them off and back on again.

One of my friends just went through upgrading his system. He was using a PreSonus (Firetube?) unit at the time, which had worked fine on his 32-bit Win XP system but wouldn't work with 64-bit Windows 7. This was only a couple of months ago, so it's not like either Windows 7 or 64-bit were brand new.

Then the FaderPort for me, which was always iffy to configure, caused issues with projects loading in Sonar, and required a registry hack to work in 64-bit. The fact that the Alpha Track also had this issue doesn't make me feel any better. These are tech companies creating products to work with computers, and 64-bit versions of Windows have been around for a LONG time. If they can't engineer something to work with both 32 and 64 bit by now, that's really sad.

Since PreSonus uses the same drivers for all of their recording interfaces (Universal Control, I think?), this gave me the takeaway that their drivers are buggy with Macs in general and with anything 64-bit. To me that is unacceptable, which is why I personally won't buy any new product from them that needs to connect to a computer.

This isn't meant to be a hit piece on PreSonus itself. I have some of their other products (DigiMax FS, original BlueTube, etc) and they are solid pieces of gear. Then again, they don't need drivers. 

Peace,

Tunes

No Worries,  I was mainly curious.  I am running 64 bit albeit not with a Mac.  (Although every time  a windows user has an issue on the Presonus forums the advice is to get a mac lol) .  You may want to ask on Presonus forum - they are at least as friendly as here - I get good advice on both places.


Cheers


Grif
 

tunekicker


Grif I'm glad you've had better experiences with PreSonus. My post wasn't meant to be a universal declaration of their suckiness- rather, a personal conclusion based on my experience with at least 3 different PreSonus products that were designed to interface with computers and did not do so well.

At church we have a couple of Presonus units hooked up to a Mac for recording. They refuse to run at anything other than their native 96k sample rate, even thought they say 44.1, 48, 88.2, etc are supported. Half the time they don't sync properly and are not seen by Pro Tools (10.) We then have to power them off and back on again.

One of my friends just went through upgrading his system. He was using a PreSonus (Firetube?) unit at the time, which had worked fine on his 32-bit Win XP system but wouldn't work with 64-bit Windows 7. This was only a couple of months ago, so it's not like either Windows 7 or 64-bit were brand new.

Then the FaderPort for me, which was always iffy to configure, caused issues with projects loading in Sonar, and required a registry hack to work in 64-bit. The fact that the Alpha Track also had this issue doesn't make me feel any better. These are tech companies creating products to work with computers, and 64-bit versions of Windows have been around for a LONG time. If they can't engineer something to work with both 32 and 64 bit by now, that's really sad.

Since PreSonus uses the same drivers for all of their recording interfaces (Universal Control, I think?), this gave me the takeaway that their drivers are buggy with Macs in general and with anything 64-bit. To me that is unacceptable, which is why I personally won't buy any new product from them that needs to connect to a computer.

This isn't meant to be a hit piece on PreSonus itself. I have some of their other products (DigiMax FS, original BlueTube, etc) and they are solid pieces of gear. Then again, they don't need drivers. 

Peace,

Tunes

Works great here.

Also updated Studio One free and tested.

Works fine. Knows it is there and ready.

For Sonar, Could all be related to the audio/midi interface.

But why do S1 and Reaper work fine ????

Dissapointing.