Huh... I don't seem to get this issue but I always try to use the same ports for my devices and only turn things on BEFORE I open Sonar when I need them. Always works. Actually if I don't turn them on before opening Sonar many times they don't work at all (perhaps this is why).
 
Granted I only have two USB midi units and I generally don't have them hooked up at the same time. I'll have to keep an eye on this if I start using multiple units at once.

Yup that is the behaviour beepster, everything is fine if you remember to turn things on first. Otherwise the best thing to do (for me) is to turn everything on and restart Sonar. That is the workaround. So looking at #19 we can deduct that only USB MIDI is effected. Also I understand this is a windows feature but there has to be a better way for Sonar to have a memory (or freeze a memory) of MIDI track/channel configuration.

Okay, yeah the way windows handles midi stuff is kind of a joke and it's one of the very first things I read about ages ago when I was first trying to figure out my padKontrol. You got it though. If I do happen to decide to fire up one of my dealy doodles I just save what I'm doing and restart sonar. Kind of weird but it doesn't take long. I kind have so many little rituals now when turning things on/off that one is kind of the quickest/least painless of the bunch.
 
DAWs sure are finicky. lol
 
Stupid computers.

windows version of Harrison mixbus is a daw that has no midi

Also if open a project with some MIDI devices switched off, then you save it, Cake has saved everything with rerouted inputs, when that happens it is extremely annoying, sometimes the scenario can be quite complex and time consuming to get it back. Something should be done.
 
Anyway I am proposing that the Cakewalk resolves this is come up with user definable MIDI configuration sets that do not change. For me it isn't one of those oh well it's just fiddly things. For me this should be basic functionality in any DAW, to be able to retain the MIDI device configuration. You can undo or redo editing, you can undo or redo screen positioning and manipulating, you should be able to undo, redo or freeze MIDI routing.

hmm... but how could it do that if it's windows that is rearranging/dropping things? Wouldn't it have to send a phony MIDI connection signal to the OS or something?
 
With saving I'm sure your set up and usage is far more complex than mine but I save stuff with the devices turned off and it seems to route things properly when I fire them up again. But that of course is shutting down Sonar then restarting again.
 
IDK... I'm probably not understanding what's going on... as usual. Hope you get it figured out one way or the other.

I used to frequently run into this and my solution to this problem is to set it the way you want it, close Sonar, change the attributes of ctrlsurface.dat and ttsseq.ini to read-only.
If you ever need to change, remember to remove the read-only attributes, change your setting, rinse and repeat...

> hmm... but how could it do that if it's windows that is rearranging/dropping things?

Sonar would keep a table of USB MIDI devices which would be compared everytime a USB MIDI device goes online (or offline). The track that has USB MIDI devices assigned could be flagged (automatically by default) to automatically change to a particular MIDI device when it starts up.
 
So you are saying if you boot up a project with a MIDI device turned off, then save, then close sonar, then turn on MIDI device, then open project it won't be rerouted?
 
> change the attributes of ctrlsurface.dat and ttsseq.ini to read-only.

That's a very interesting idea, I will investigate. Anyway I'm hoping Cake can introduce functionality whereby file attributes do not need to be changed.

Alex... that auto detect within windows, and you should be able to turn it off ..have a look see.

CakeAlexS
 
Sonar would keep a table of USB MIDI devices which would be compared everytime a USB MIDI device goes online (or offline). The track that has USB MIDI devices assigned could be flagged (automatically by default) to automatically change to a particular MIDI device when it starts up.

I guess I figured it already did something like that. This is the first time I've heard of the problem. I'll have to check it out.
 

So you are saying if you boot up a project with a MIDI device turned off, then save, then close sonar, then turn on MIDI device, then open project it won't be rerouted?

 
Not that I've noticed and I'm thinking through some of the projects I've done and I've definitely saved with the unit turned off many times and it was always ready to go again. However I'm not sure whether I've done it on a project where I was switching back and forth between devices. Like if I used the pK on a drum track, saved/closed, turned off the pK, reopened with the Oxygen, saved/closed, turned off the Oxygen then switched back to the pK. I mean I THINK I've done that but I can't remember specifically. I haven't really used the pK that much yet. I will be though so I guess I'll see.
 
Now does this affect devices connected VIA din through the interface as well? Seems unlikely but I'm going to be using my DX-7 as a controller soon. I just like to have these types of potential problems somewhere in the back of my brain so I don't freak out... because I'm easily freaked out. lol