Faderport issues with latest update of CW

Author
myronn369
Max Output Level: -90 dBFS
  • Total Posts : 19
  • Joined: 2014/09/26 11:23:12
  • Status: offline
2018/08/09 21:33:15 (permalink)

Faderport issues with latest update of CW

 I'm having problems opening projects initially in CW, the issue seems to be with faderport. If I try to open a project with faderport  from the start screen the project will not open. If I first remove faderport from the control surfaces under preferences and then open a project it will open fine, then I can go back into control surfaces and add faderport and everything works fine. after this I can open any project with faderport with no problem until I close out CW, Once closed I will have to go through the process again. All drivers are up to date and I still run Sonar Platinum and S1 and have no problems with faderport.
#1

3 Replies Related Threads

    gustabo
    Max Output Level: -49.5 dBFS
    • Total Posts : 2591
    • Joined: 2009/01/05 17:32:38
    • Status: offline
    Re: Faderport issues with latest update of CW 2018/08/09 21:59:03 (permalink)
    Your config file got screwed up. Rename ctrlsurfac.dat and ttsseq.ini to ctrlsurface.old and ttsseq.old, start CW, redo your midi devices and control surfaces prefs.


    Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
    M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
    Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
    Adam A7X - Behritone C50A
    PreSonus Monitor Station v2 (controlling the mons)
    https://www.facebook.com/groups/sonarusergroup/

    #2
    myronn369
    Max Output Level: -90 dBFS
    • Total Posts : 19
    • Joined: 2014/09/26 11:23:12
    • Status: offline
    Re: Faderport issues with latest update of CW 2018/08/10 01:25:46 (permalink)
    Thanks gustabo for your quick response, I rename the files as you recommended and it did solve the problem temporarily. Once I closed CW and reopened it the problem was back, I checked the cakewalk core file and the 2 files had repopulated along side of ctrlsurface.old and ttsseq.old. I also tried deleting those files and they still return.
    #3
    gustabo
    Max Output Level: -49.5 dBFS
    • Total Posts : 2591
    • Joined: 2009/01/05 17:32:38
    • Status: offline
    Re: Faderport issues with latest update of CW 2018/08/10 02:08:26 (permalink)
    They get recreated when you set your midi device and control surfaces settings in prefs.
     


    Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
    M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
    Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
    Adam A7X - Behritone C50A
    PreSonus Monitor Station v2 (controlling the mons)
    https://www.facebook.com/groups/sonarusergroup/

    #4
    Jump to:
    © 2024 APG vNext Commercial Version 5.1