• SONAR
  • Anyone using X3 or X2 and a Faderport?
2013/12/30 19:04:04
ChuckC
This was one of my Christmas gifts from my wife I wonder how she knew I wanted it!?  haha
In any case, I got it hooked up and ran the installer, it works fine in S1, the problem is S1 so far just pisses me off as a DAW (we'll save that for another thread sometime)
I want to use this cool new toy in Sonar but sonar does not recognize the Faderport.  That is to say it does not show up in the drop down list to choose it as a controller.  I have done the research 1st and found the issue & the subsequent fix I found was that you had to copy the faderport.dll into C:\program files (x86)\cakewalk\shared surfaces  then run a windows command prompt to register that by typing:
regsvr32 C:\program files (x86)\cakewalk\shared surfaces\FaderPort.dll
 
All over online I can find people who had this problem , did this procedure and it fixed it for them.... I have no such luck.
I get the error//response/message  * The module "C:\program files (x86)\cakewalk\shared surfaces\FaderPort.dll" was loaded but the entry-point DllregisterServer was not found.   Make sure that "C:\program files (x86)\cakewalk\shared surfaces\FaderPort.dll" is a valid dll or OCX and then try again.
 
Any ideas guys?  I am lost at this point and don't want to keep poking around in admin mode and mess something up.
 
2013/12/30 21:00:33
SuperG
I use it all the time - it works great, but it's been a long time since I set it up.
 
I don't recall if you need to register the faderport.dll or not. Anyway, if it does need to be registered (as with any ocx), it must done in administrative mode, or it's not gonna work. Usually, you run cmd.exe in administrative mode, and then anything you run from there is also done in administrative mode.
 
Other than this, you need to make sure the faderport ins and outs are checked in midi devices, select the faderport under control surfaces, and assign to faderport in and out ports to it.
 
 
 
 
2013/12/30 21:05:39
trnfoot
 
works perfectly but a little tricky to install....follow these instructions using latest driver (in any version of sonar)
 
http://www.sweetwater.com...t-to-work-in-sonar-x1/
2013/12/30 21:26:30
ChuckC
SuperG-  I understand that I will need to assign inputs and outputs in sonar to use the faderport, but first.... I have to get sonar to acknowledge the faderports existence as control surface at all.
 
Trnfoot-  Those are the same steps I am talking about above.  I found those same instructions in multiple places on the web and while that seems to work for most, it is not working for me.  Apparently I am having some issue outside the norm and I don't do computer tech enough to know what to do next.
2013/12/30 21:46:55
mudgel
I had a similar problem that I couldn't fix until I enclosed the file location completely in double quotes.
regsvr32 "C:\Program................ \faderport.dll"
2013/12/30 21:48:08
mudgel
Don't forget to run the cmd line as Administrator.
2013/12/30 21:50:35
gustabo
Looks like you're either registering the 32 version of the faderport dll if you're trying to register C:\program files (x86)\cakewalk\shared surfaces or you're placing the 64 bit version into the wrong directory. The right folder for Sonar x64 should be C:\program files\cakewalk\shared surfaces.
FWIW, faderport works great here under both x86 and x64 versions of Sonar X3d but I had to hack the one of the dll's to get it to work in both, before hacking it, it would only work in one or the other because both versions of the dll are named the same thing.
2013/12/30 21:52:53
SuperG
It certainly sounds as if it's a an OCX registration issue. You could try unregistering it, followed by re-registering it. If it's correct, it'll be listed as Presonus Faderport in the control surfaces preferences. Also, just to be sure, you indicate you're using the 32-bit version of Sonar by virtue of the sharedsurfaces directory location.
2013/12/30 23:58:25
ChuckC
SuperG
Also, just to be sure, you indicate you're using the 32-bit version of Sonar by virtue of the sharedsurfaces directory location.


I thought (see I am soooo not a tech guy when it comes to computers)  the x86 denoted 64 bit (which I never understood anyway) and that the 32 bit was under the general file.?  For instance
64 bit = c:\Program files (x86)\cakewalk\ yada yada.....
32 bit = c:\Program files\cakewalk\ yada yada....
Right?  or are you telling me I have that backwards? 
 
to that end.... where we have to type regsvr32....  Does that need to be regsvr64 or regsvr86 for the 64 bit version?   I at this point have no intention of even loading the 32 bit version of X3 on my computer at all.
 
PS.  this forum rocks and you guys are awesome!  ...Just so you know.  Thank you all.
2013/12/31 00:04:08
SuperG
ChuckC
SuperG
Also, just to be sure, you indicate you're using the 32-bit version of Sonar by virtue of the sharedsurfaces directory location.


I thought (see I am soooo not a tech guy when it comes to computers)  the x86 denoted 64 bit (which I never understood anyway) and that the 32 bit was under the general file.?  For instance
64 bit = c:\Program files (x86)\cakewalk\ yada yada.....
32 bit = c:\Program files\cakewalk\ yada yada....
Right?  or are you telling me I have that backwards? 
 
to that end.... where we have to type regsvr32....  Does that need to be regsvr64 or regsvr86 for the 64 bit version?   I at this point have no intention of even loading the 32 bit version of X3 on my computer at all.
 
PS.  this forum rocks and you guys are awesome!  ...Just so you know.  Thank you all.




 
I'm sorry Chuck,
 
c:\program files (x86)\ is the 32-bit path - the other one is the 64-bit path.
 
Hope this info gets you on the right path! The Sonar denizens here are always happy to help!
 
 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account