Does anyone have faderport working properly,in X1 expanded, I had it working great in X1 till I upgraded to expanded. Now the fader doesn't work. Most everything else is working.

 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. 

Mine works fine in X1/X2.  There is a Sonar bug/workaround that properly loads the dll file, and you have to write a little code to run it...I don't have the code on me at the moment though, but it's available if you Google it.   Something to do with "regsrv"....

That "code" refers to registering a dll.

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.

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

Have to take issue with that - I have been running a Presonus 16:4:2 StudioLive for almost 3 years as my main audio interface with Sonar - not had driver issues though many updates which have added tons of functionality to the console (virtual Studio Live, 6 extra graphics ability 2 send aux returns and fx to aux mixes, Smaart analysis tools, iPad control, QMix which allows musicians to control their own mixes from an iPhone and a few other things, all working, and all free.

No affiliation with Presonus, but having had such a good time with the board as well as other Presonus interfaces and products, did not think the criticism was justified.

Cheers

Grif

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.

I gave up on my Faderport.  Thinking of repurposing it to control my curtains.
 
It worked for a while, then stopped (I went through the regsvr thing).  Then I half got it working under X2, but again not the motorised fader.  Which is a pity as the fader itself is really excellent.  There were some comments about the latest firmware making it worse, but also it's now difficult to source the earlier firmware.

I ended up getting the Behringer BCF2000. 8 flying (though noiser) faders, and a load more functionality to boot.  Much better choice imho, relatively inexpensive, and with multiple faders I find it makes mixing more intuitive.

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