John
Adam I must say you do stand your ground. I admire that. I can also see why you are saying the things you say. It may behoove CW to change how none and omni work in the input for MIDI tracks. That said, to me its not a problem. Never has been. There is no good reason to have a MIDI track that is empty with no input available for it. When i create a new MIDI track I always set it up to receive MIDI from my MIDI keyboard or my wind controller. I do have a CS as well as hardware synths, 3 of them. All can send out MIDI. Sonar works just fine for me.
I recall using Cubase some years back It was SX 1, 2 and 3. On occasion my CS would produce notes sounding on MIDI tracks. One reason was is there was no clear way to prevent Cubase from routing MIDI output to the MIDI tracks. Clearly an annoyance. Where here I really don't see a real problem. After all this has been the way Sonar has worked for as long as I can remember. Also it would seem that if it were a really awful bug don't you think the board would be lit up with complaints from the early days? It just doesn't bother us much.
I would end this discussion here and send a bug report to CW or a feature request. We forum members are not equipped to do anything about it. This is a peer to peer forum not a way to contact Cakewalk.
Hello John,
Thank you for the mature rational response. I wish others spoke to me the same way, then I wouldn't have had to resort to such lows.
Anyway, I get what you are saying, why have a "none". I was hoping it would stop MIDI data from erroneously entering the track, but who knows. It also resorts to "omni" if you currently don't have your MIDI controller plugged in, which could cause issues.
I have been done a long time ago, the only reason this thread lives is because I respond to everyone. I don't have to, but I choose to.
Cakewalk is already involved with me via private message, so lets see what happens.
Thank You!
-Adam