Hi Joe.

In device manager I can see the PRO26, but there's nothing that I can see relating to Midi

What I can see is exactly the same settings that are present for the device that does work ok, the Saffire 6 on the laptop

Going a  little further with the device manager approach -- Seems there is still a limitation of 10 MIDI devices (present or past) in Windows.  This may be masking the device you actually have plugged in.

Instructions by Craig Anderton to fix (which refers back to a Cakewalk forum article!). Basically, it uses a way to expose all the non-present devices. For example, different devices that were attached at one time to a USB port. Look in the Sound Video and Game section for midi devices; also check in the USB section. Then uninstall the ones that you don't expect to be there. Not really a problem to delete them freely, because they will reinstall next time they are plugged in.

You can refer directly to the microsoft procedure to view and uninstall the non-present devices. For Windows 7, the command prompt (or command .bat file) must be started by being run as administrator. (Right-click command prompt and select run as administrator.)

Bill B.

I saw a similar problem with my M-Audio Fast Track Ultra recently.

In my quest to streamline my DAW and make things work better/faster, I tried disabling Windows Sound System completely. I went in to System Configuration and prevented it from loading. 

Everything worked except my Midi port on my Fast Track Ultra. For some reason Sonar will not see it unless I have Windows Sound System enabled during boot up. My thinking was, it's a port in a separate USB Midi device and it should work, but I'm obviously wrong. Took me forever to figure out what was going on until I realized I had disabled Windows Sound System a few days prior. I hadn't used the Midi port right away after I did the tweak.

Did you change any settings in Windows Sound System?
Have you in the past and maybe performed a Windows Update that may have changed something?

Just thought I'd post this in case it may trigger a memory of something you changed.
Good luck.

Bub.

Woah, this rings a bell.

Bill, I'll take on board exactly what you said, but I think Bub has it nailed - I did disable Windows Sound a few days ago - I bet that's it

I'll get back to you.

Bristol_Jonesey


Woah, this rings a bell.

Bill, I'll take on board exactly what you said, but I think Bub has it nailed - I did disable Windows Sound a few days ago - I bet that's it

I'll get back to you.

Just did a quick bit of research and it looks like someone else noticed a similar issue:
http://duc.avid.com/showthread.php?t=327655

SOLVED!! 

A few days ago i was going through the Windows Start up programs and services in msconfig. 

i disabled Windows Sound and Windows Audio Endpoint Builder. 

It seems that Sonar need both of these to be running to allow midi data to pass. 


Thanks to all who chimed in, and special thanks to Bub who nailed it first go!

Bristol_Jonesey

SOLVED!! 

A few days ago i was going through the Windows Start up programs and services in msconfig. 

i disabled Windows Sound and Windows Audio Endpoint Builder. 

It seems that Sonar need both of these to be running to allow midi data to pass. 

Thanks to all who chimed in, and special thanks to Bub who nailed it first go!

Awesome!


I saw a noticeable improvement when I had it disabled, too bad there isn't a way around this.

It seems a bit of a kludge just to get Midi IO, but what do I know.

+1 for you, Bub.