Hi,
I've already opened a ticket with support for this but also hoping that maybe someone in the forum has already come across this and can help with some ideas.    
 
SPLAT has suddenly stopped responding to midi from my UM880 interface.  I have my Yamaha S90 connected to the UM880 with midi cables and the UM880 is connected to my computer running Windows 10.  I just upgraded to Creator about a week ago and things were still working after the upgrade.  
 
SPAT still responds to midi from USB connected keyboards but not anything connected through the UM880.  Outside of Sonar midi connected through the UM880 still works fine with my VSTs.  It also still works when using it with Ableton Live.  Just won't work inside SPLAT.  So I'm not thinking it's a driver problem with the UM880.  
 
So here's what I've done so far to try to resolve/diagnose:
1. Deleted the aud.ini file.  
2. Upgraded SPLAT to the current version including the patch that just came out.  
 
Please help if you've got any ideas.  
 
Ira.  

ibartley
1. Deleted the aud.ini file. 

May have been the wrong ini for this issue. Try deleting/renaming TTSSEQ.ini

Hi Scook,
Thanks for the quick reply and getting me on the right track.  You're right.  I removed TTSSEQ.ini then rebooted the computer and that allowed things to start working again.   After doing that I went back to the project I was working on and things got all screwed up again. 
 
After messing around with different VSTs it seems that NI's Reaktor Monark  is the one that's funking things up.  It seems that it will only respond to midi channel one.  I don't know if that's a feature or a bug.    However, after setting its track to midi channel 2 and getting no response, all other VSTs in the project stop responding to midi from the midi interface.  They will still respond to USB midi though.    
 
Anyway, that's where I am with this so far, but it seems to be a problem caused by Monark.  If I find any more info I'll post it.  
 

Well I thought removing TTSSEQ.ini and restarting solved the problem but that's not the end of it.  I'm losing the ability to input midi data everytime I stop and restart Sonar.     So here's the senario:
1. Load VST into Track 1 (Simple Instrument Track)
2. Assign midi channel 1 from the UM880 interface.
3. Record data into the track.  (that's is successful)
4. Save project and close Sonar.
5. Restart Sonar and open the previous project.
6. Try to record on Track 1.  There is no midi response.  
 
In order to get operational again I have to:
1. Shutdown Sonar
2. Remove TTSSEQ.ini file
3. Restart Sonar
4. Go to Preferences/midi/Devices and reassign the midi Inputs and Outputs.
 
I haven't gotten anything from Cakewalk Support yet.   Does anybody have thoughts on what this problem is and how to fix it.   It's driving me up the wall.  
 
Ira.

Could the drivers for the interface perhaps need to be installed again?  
 
Are the midi ports on the audio interface enabled as input devices in Sonar Preferences?
 
(the above are wild guesses, by the way)
 
Bob Bone

The problem appears to be with the um880 and Windows 10 and not DAW related as you are not the only one with this problem.  Google/bing roland um880 windows 10 and you will see that others are having the same problem.  There are no Win 10 drivers for the um880 and apparently the Win 8.1/8 or 7 drivers do not work.
 
Good luck!

MarioD
The problem appears to be with the um880 and Windows 10 and not DAW related as you are not the only one with this problem.  Google/bing roland um880 windows 10 and you will see that others are having the same problem.  There are no Win 10 drivers for the um880 and apparently the Win 8.1/8 or 7 drivers do not work.
 
Good luck!

Here's the thread and related post:
 
http://forum.cakewalk.com/FindPost/3619139
 

Hey Guys,
Thanks for the helpful comments.  I was aware of the driver problem with the UM880 (should have mentioned that).  I have been using it in class-compliant mode to work around the driver problem since I upgraded to Win 10 last year.  It's been working trouble free in this mode until now.  
 
To continue troubleshooting, I plugged my controller (Yamaha S90) into the midi ports on my MOTU Ultralite mk3.  This takes the UM880 out of the equation.  The results were the same.  After recording a track and restarting Sonar, midi input was disabled. Remove TTSSEQ.ini.  Repeat......
 
So this is not a UM880 problem.  This is a Sonar problem or combination problem with something in Windows.  I'm just about at my knowledge limit on figuring out who is the culprit here.  
 
Ira. 

I can definitely say this is a Sonar problem.   I thought the problem was confined to recorded through the midi ports.  However, I have connected to Sonar just using USB-Midi connections from my keyboard and I get the same problem.  I can record once, close and reopen Sonar.  Then midi input is disabled again.  Aaaaaargh!!!!!
 
Do I need to reinstall Sonar to fix whatever got broken?   

It probably doesn't apply here, but I recently reported a bug (that Cakewalk has replicated) whereby SPLAT doesn't respond to a MIDI controller if: 1) there is any MIDI plugin in the FX Rack, AND 2) the "ByPass FX Rack" switch is enabled.