Quick one for all us Faderport users

I have noticed that this happens if the midi hardware inputs and outputs have changed since the project was created/saved. When the faderport starts to behave randomly and the project stops loading, if you move the fader manually the project will continue to load. You then still have to delete and reinstall the faderport under control surfaces to have it operate correctly.
 
Once the project is resaved with the correct midi io settings all seems fine.

I occasionally get the fader jogging up and down and the project will never load after touching the fader (that stops the jogging).
 
If I kill SONAR and restart everything is OK. No need to do anything. This can happen on recent or old projects.

BobF
I'm disappointed to be reading this as I just ordered a FaderPort ...

I have really only found it be be a problem when opening old projects with different midi IO Bob. It has worked perfectly since I resaved the projects with the faderport installed.

gustabo
And once I have everything set the way I want it set, I set the attributes for ctrlsurface.dat and ttsseq.ini to read only.
 

Thanks - great idea. I always back them up but never thought to do that.

When this happens, I usually end up killing SONAR (taskkill /f /im sonarplt.exe at an admin command prompt) and then just unplug the FaderPort before restarting.  Unfortunately, SONAR's handling of restoring device settings seems to be essentially random so then I have to dig back through the settings and make sure the FaderPort MIDI and control surface ports are correct.  
 
In my experience, this seems to mostly be associated with missing plug-ins.  For example, I have my Waves licenses on a USB stick that I move back and forth between my main system and a laptop and basically can't open projects with Waves plug-ins without going through FaderPort hell if I forget the USB stick.  Something with SONAR's control surface initialization code seems to conflict with the plug-in loading code which causes it to get stuck on startup.  It seems most likely to happen if I'm missing a plug-in or a license or have an expired eval license (not uncommon scenarios) but I'm pretty sure it has happened to me without this.  
 
Another issue I've had from time to time is that the FaderPort motor stops working.  Changing tracks causes it to assign its current position to the newly selected track's level instead of moving to represent that track's level.  The only way to solve this that I've found is to rerun the firmware installer.  My guess is that the FaderPort has some sort of onboard memory that gets corrupted and the firmware installer resets that.
 
Pretty frustrating that a device that is supposed to make life easier ends up resulting in so much time and frustration :(
 

tenfoot
 
Check out the posts above about editing the ttseq.ini file and Gustavo's tip about locking the ttseq and ctrlsurface.dat files Dave. That should solve any random assignment behaviour.

Thanks for the heads up!  I did see those posts and was planning to play around with that later. 

BobF
I'm disappointed to be reading this as I just ordered a FaderPort ...

and you did well. It's a nifty little piece of hardware that will serve you well. Of course PreSonus doesn't care for the DAWs that don't sell big numbers and are not StudioOne of course. I also use Digital Performer and it's a nightmare to use it in that environment. PreSonus says that MOTU was late in delivering the specs to their developers so they missed the window of opportunity to have the correct drivers coded. Interesting statement, no?
Installing Faderport for Sonar requires a little bit of command line jiggery pokery, but it works.
Also, in my case updating the firmware rendered the machine lifeless and had to roll back to have it installing and working fine.
Let us know, I'm happy to help