• SONAR
  • MIDI controller not working in CbB SOLVED!
2018/07/18 01:25:27
Phoen1xPJ
I just moved and hadta pack up my studio. Everything was fine b4 move. Today I finally got everything hooked up and everything's working except my 'lil Alesis Q49 key controller. It does not trigger any hard or soft synths in CbB. I checked it in MIDIOx and it was working fine. I checked in device manager hidden devices and found two instances of grayed out Q49 which I deleted. Still no joy so I unplugged from port and put in different physical USB port. No joy. I uninstalled & reinstalled in Device Manager. No joy. I double checked USB Power Management in Device Manager. Nope. Oh... I verified with each change the Q49 was selected in Instruments in CbB. That's the bottom of my bag of tricks. OH... i'm in latest build of Win 10 and latest CbB.
 
Any of you good folks pa-leese give my some ideas to get my old friend working again... thanks!
2018/07/18 08:41:02
azslow3
Try to delete TTSSEQ.INI. You will find it in "%APPDATA%\Cakewalk\<Sonar version>". If I remember correctly, CbB is "Cakewalk Core".
2018/07/18 09:50:10
Phoen1xPJ
Ah yes... the file time forgot... I renamed and let CbB make new one and all was there. I hadta redefine instruments but OK. Now a NEW wrinkle. Q49 still not working. My control surface was not working and I hadta fix in Preferences/Control Surfaces. Now the control surface works and GUESS WHAT... the Q49 works too! Joy joy! OK, test time. Exit CbB, reopen. It did not remember the control surface setting and Q49 not working. Reset control surface and it and Q49 work again! WTF? 
 
OK... how do I get the control surface settings to stick? They did b4 my studio migration.
 
Thanx for the tip, azslow!
2018/07/18 13:12:28
msmcleod
I've been caught out with this several times, where the Control Surface settings have "stolen" my keyboard's MIDI port and I'm pulling my hair out to find out what is wrong.
 
Basically anything that causes Windows' enumeration of the MIDI devices to change can cause these settings to change.
 
I've found that as long as I never change USB ports, and make sure all my MIDI devices are plugged in/switched on before booting up, the settings seem to be fairly static.
 
However if something does change (like me forgetting to switch on my MidiSport 8x8s), Sonar / CbB seems to remember the changed setup, and it takes a few reboots for it to settle down again.
 
 
2018/07/18 14:01:51
azslow3
Phoen1xPJ
OK... how do I get the control surface settings to stick? They did b4 my studio migration.

You have mentioned that you have grayed out MIDI devices... For all MIDI (and Audio) which HAD grayed out duplicates (connected to different USB ports), it can be required to remove and re-install current device port.
 
So, delete ALL MIDI devices in the Windows Device Manager. No need to check "remove driver", just reboot after deletion (probably re-inserting will work as desired as well). In Sonar, remove all Surfaces and disable all MIDI. Just in case, remove TTSSEQ.INI again.
While sounds drastic, it takes under 1 min to complete. And any time I had related problems (with MIDI or Audio) everything was normal for me again.
 
The bug exists in Sonar since... forever. That shows the team capability to fix simple things. Do you still wonder why it was sold by Roland and abandoned by Gibson?
2018/07/18 14:23:31
Phoen1xPJ
HA! I sussed the quick solution... rename ctrlsurface.dat and be sure control surface is correct in Prefs. Exit CbB, it will write new ctrlsurface.dat, then restart CbB. Voila! All is well again! I just guessed this one... 
2018/07/18 14:26:41
azslow3
Ah... I have not understood your last issue. Your guess for it was correct
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account