test
 
Dang forum gremlins
 

tried putting a virtual midi cable between it and sonar?

Anderton

AdamGrossmanLG
Also I did not delete the file as Anderton assured me its not a Sonar issue.

That's not true, and if you can't read what I wrote correctly, it begs the question of whether you can read the solutions that others have offered correctly. For the record, I said:
 
"Well of course it very well could be [a bug], and it's even likely. But whether it's a bug in SONAR, Windows, the controller, USB handling, hardware, or the user's understanding of how all these work together is the question."
 
And:
 
"And if it's only happening for you, wouldn't it be logical to say it's MOST LIKELY something specific to your system or installation?"
 
And:
 
"You want to believe it's something with SONAR. Fine, maybe it is and I realize that's your go-to."
 
Facts are facts. Good luck.

Well you have suggested many times it is a user issue or other environmental issue..  I also opened up that file to check what is inside it.... not much really?  Seems like it will just re-create the input and output entries.  Maybe I will have to re-do my control surface?

Either way, I didn't do it because I didn't understand the point?  Is this how I am supposed to work with the product, always having to delete this file?   
 
Oh and I don't WANT to believe anything, and have no care in the world who's "Fault" it is.  Software is complex, especially Sonar.  Of course there is always going to be something that needs some fixing, and I understand that.  Originally when I came here to this forum, I thought I would just point it out to hopefully bring awareness and maybe it can get resolved in a future release.   I always am friendly to start, no reason not to be.  I just found it a little frustrating (as you may remember from some other posts), where I am running into people claiming I have a poor attitude or who don't like I am criticizing the product.   I feel everyone took what I was saying too personally to be honest.

Anyway, lets just hope we can finally figure this out. I will report back here.  I haven't used the DAW the last 3 days, next week I will and will report back here.

Anderton
 
provide a recipe to reproduce
 

That's everything in a nutshell right there!  The secret sauce for success! 

It did occur to me that one area where SONAR may be different from other DAWs is in sending the local control off MIDI message to prevent note doubling with controllers that have synth engines. 

Delete the file already. If that doesn't work then there would be no reason to delete it again. If it does work there would be no reason to delete it again (at least until you make another hardware change). 
 
Testing this will take less time than it has taken me to write this post (I admit I am a slow writer).
 
Whatever, I wish you luck. 

pwalpwal
tried putting a virtual midi cable between it and sonar?

AdamGrossmanLG

pwalpwal
tried putting a virtual midi cable between it and sonar?

nope.  don't know what that is and why should it be needed?   Sonar should be able to recieve the midi data without it, just like every other application on my PC.

I think that to try this test you will need to place something in front of Sonar, such as MIDI-OX to do the port mapping from your controller as input, to "Internal MIDI" via LOOPBE.  Setup in MIDI-OX "Options > MIDI Devices".  From there you can easily setup the input to output port mapping.
http://www.midiox.com/index.htm
 
Then in Sonar, you would setup your MIDI devices by unselecting your controller, and selecting "Internal MIDI" (LoopBE) as your MIDI input.  This way Sonar is only interacting directly with the LoopBE MIDI driver.  Process of elimination! 
 
I tested this setup and it works.  You can also open up the MIDI monitor in MIDI-OX, which gives you a break-out box of the MIDI messages in real-time.
 
The MIDI flows like this: 
MIDI controller >> MIDI-OX >> LoopBE >> Sonar
 
Press a key on the controller, and Sonar will see it.

Matron Landslide

Anderton

AdamGrossmanLG
Also I did not delete the file as Anderton assured me its not a Sonar issue.

That's not true, and if you can't read what I wrote correctly, it begs the question of whether you can read the solutions that others have offered correctly. For the record, I said:
 
"Well of course it very well could be [a bug], and it's even likely. But whether it's a bug in SONAR, Windows, the controller, USB handling, hardware, or the user's understanding of how all these work together is the question."
 
And:
 

"And if it's only happening for you, wouldn't it be logical to say it's MOST LIKELY something specific to your system or installation?"

 
And:
 
"You want to believe it's something with SONAR. Fine, maybe it is and I realize that's your go-to."
 
Facts are facts. Good luck.

Actually it is kinda true, and you kinda did, at least you certainly left him with the impression that it wasn't SONAR, it was probably this from page 1, among other things
 

Anderton

AdamGrossmanLG
probably just poor coding as usual with Cakewalk.

 
Actually it's almost certain that it isn't, given that no one else is chiming in to say they've experienced this problem.
 

 
And that quote that you used to try and show you didn't say it
 

"Well of course it very well could be [a bug], and it's even likely. But whether it's a bug in SONAR, Windows, the controller, USB handling, hardware, or the user's understanding of how all these work together is the question."
 
 

well, it actually came from a reply to me, which was well after the event in discussion where you at the very least certainly gave the OP the impression that it wasn't SONAR. tisk tisk
 
Facts are facts
Good Luck
 
 

When I read Anderson's post my thought was he's saying it may be a bug and it may be in any of the puzzle parts (multiple software packages or system software, drivers, etc) and that to not get locked in on one item (In this case Sonar) or it will be that much harder to find.....and branch out....don't just say or assume it's Sonar. He was pretty clear.

Personally, when I run into hardware to DAW MIDI oddness one of the first things I do is use a MIDI monitoring application to find out exactly what a device is sending and what’s been sent to it.

In the case of a Sonar setup, that means running MidiOX. The input and output slots in a MIDI track get pointed at that, then connect MidiOX to the hardware device’s ports and start pressing keys and buttons and turning knobs to see what’s being sent where, check the channels being used are what I think they are etc.

It might be worth trying if it hasn’t already been done. Just to check that everything is configured as it’s supposed to be.

One of the things about audio applications is that no two of them have identical preferences dialogues, and sometimes one application might make assumptions which “just work” while another needs more detailed configuration.

As well as the “main” MPK ports there are a bunch of “extra” ins and outs showing in the Sonar preferences screenshot. It might be useful to check on what they do. Also MIDI clock settings if on-board sequencers or arps are involved. Some stuff simply refuses to work unless sent clock even if the functions which use it aren’t being used.

I don’t know the MPK225, and the manual isn’t very illuminating. I do know that over the years I’ve connected a pretty wide range of MIDI hardware to Sonar, including multiple controllers or MIDI-sending hardware at the same time, and never run into a problem like this that didn’t come down to something somewhere needing a setting changing. The trick is to find out which setting in what stage of the MIDI chain from controller via Windows to DAW is the culprit.

So, this long running issue has been resolved?

welp, I guess this will never be resolved.
 
Onwards and upwards...