Hi all,
 
Lately I've been having this issue where Sonar can't open my MIDI device because it's "out of memory" ... I've done a little research and found that this is actually because the MIDI device is in use by another program... The problem is, I don't have any other audio programs open. Now I'm not 100% sure but I do believe CHROME is open every time this problem happens... and usually if I close Chrome and then close and reopen Sonar it starts working again...
 
Now aside from the obvious, I shouldn't have Chrome open on my Studio PC while I'm working haha, any ideas why Chrome (or some other not audio program) would be using my MIDI device driver?
 
BTW it's an M-Audio Keystation 88es.
 
Thanks!

polarbear
Hi all,
 
Lately I've been having this issue where Sonar can't open my MIDI device because it's "out of memory" ... I've done a little research and found that this is actually because the MIDI device is in use by another program... The problem is, I don't have any other audio programs open. Now I'm not 100% sure but I do believe CHROME is open every time this problem happens... and usually if I close Chrome and then close and reopen Sonar it starts working again...
 
Now aside from the obvious, I shouldn't have Chrome open on my Studio PC while I'm working haha, any ideas why Chrome (or some other not audio program) would be using my MIDI device driver?
 
BTW it's an M-Audio Keystation 88es.
 
Thanks!

I can't help but I can state that I've had the message twice now when Sonar boots up. I have two midi controller keyboards attached and it picks on the Novation. If I close and reboot Sonar it works ok. I don't understand why it's started happening when nothing has fundamentally changed.

Grum.

Web browsers almost all have MIDI playing capability, typically using the built in Windows MIDI player. Chrome has added the ability to link your controller via the browser to distant MIDI players. No need to thank them for this wonderful new feature, it is turned on by default, and I have not been able to find any simple documented way to disable it if any chrome process is active.
 
http://arstechnica.com/in...based-synths-and-daws/
 
 
 

booo... come on Chrome haha. btw i found a couple threads about it too after posting this. and yea it's definitely Chrome and its MIDI support. ugh. i found a few suggestions on how to kill it but none of them really seem to work. i just gotta get a laptop and stay off the damn web haha