[Resolved] Presonus FaderPort Problem

I remember just a few weeks ago reading in this forum that somebody had a fix for the FaderPort. When I open a SONAR project, the motorized fader goes crazy, jumping up and down and the SONAR project will not open.
 
I have searched several times trying to find the post that had a solution for this. I cannot find it anywhere. Can anyone help?
 
Thanks,
-Charles

If you move the fader on the faderport the project may continue to open. (the faderport will need to be removed then re-added in order to function) If not, remove the faderport from the control surfaces list under preferences prior to opening the project, and then add the faderport and resave the project. It usually happens when you open projects that were created before the faderport was installed due to the midiport order changing.

Thats a tricky one Charles. It should stick. Just make sure there are no tracks in the project that have the faderport set as their input/output. If that does not work, you may need to edit the Sonar ttseq configuration file so that the faderport is the last input and output on your port lists and then repeat the resaving process. Since doing that I have had no issues with the faderport, so it is probably worth the time regardless.

...wicked
I also remember this being the sign that the Faderport is dying. :-(

 
 
That may have been coincidence. Mine did this when it was brand new and has since worked flawlessly for years. It is the port order of the saved project that is causing this issue. OP said it works in new projects.

 
Do you  have your RME ufx set  active as midi inputs/outputs under midi preferences? (only your faderport is listed under the midi inputs/ outputs in the last entries at the end of the ttseq where final port order is set) If not, you need to activate is as a midi output device under preferences and then set it as the first and second midi outputs under preferences using the 'moved checked devices to top' function, then recheck the ttseq for port order.
 
Once active, your ttseq should be set as below (see last input/output entries)
 
[Options]
PumpDataMsec=250
[MIDI Out Device Map]
0=Microsoft GS Wavetable Synth
DeviceCount=4
1=UFX Midi Port 1
2=UFX Midi Port 2
3=FaderPort
[MIDI In Device Map]
0=UFX Midi Port 1
DeviceCount=3
1=UFX Midi Port 2
2=FaderPort
[MIDI Input Devices]
0=UFX Midi Port 1
1=UFX Midi Port 2
2=FaderPort
MaxInPort=2
[MIDI Output Devices]
0=UFX Midiport 1
1=UFX Midiport 2
2=FaderPort
MaxOutPort=2
[MIDI Echo Devices]
MaxEchoPort=-1

However, I still have to delete the Control Surface and add it back in. But only for this one project.
 
At least it loads so it is better than when we first started out. Thank you so much for taking time to help me with this.
 
Although I have to do that work-around, I am happy that I can at least load the project and use the FaderPort.
 
I can survive...ha ha ha.
 
Thank you,
-Charles

Sorry - posts out of synch:)
 

Yeah, I set the properties to read only and it still does it. The project will stall until I move the fader. After moving the fader the project will finish loading. The transport will work after that, but the motorized fader won't work until I delete the control surface and add it again.

Really strange. But really, I can live with it. Thank you for helping me this much. I do appreciate it.

Yes, confirmed all those steps. But it is better than it was. The only annoyance now is having to delete and re-add the Control Surface on this one project. I hope to be done with this project in another week or so anyway.
 
Maybe I will see if Cake Tech Support has any ideas next week. But, either way, I don't look for things to complain about, rather I look for ways to be productive. This is not a showstopper, just a head scratcher. In the end, I will prevail.
 
Well, in my part of the world it is very late so off to bed I go. Thank you for your time. Good night, or good day or something like that...

Have you tried azslow's driver?

azslow3 has done some fabulous work bringing CS support up to date.  The FaderPort specific stuff is at http://www.azslow.com/index.php/topic,163.0.html
 
 

Cool. I'll check it out shortly. Thank you.

Here is the recent post discussing this problem:
http://forum.cakewalk.com/Quick-one-for-all-us-Faderport-users-m3393905.
 
As I mention on that thread, for me this always ends up being an issue with something other than the FaderPort such as a missing/expired plug-in license.  It's weird since you'd think these things would be completely unrelated but I'd guess that somehow the initialization of the FaderPort conflicts with plug-ins that try to pop up license windows during initialization.