Lost all Midi Connectivity *** SOLVED ***

Evening all.

This is a strange one, all of a sudden, I have completely lost all Midi going from 2 different keyboards going into Sonar, via the Focusrite Pro26

The Midi in/outs of the keyboards go to a patchbay as do the in/outs on the Saffire - this system gives a good deal of flexibility and it's always worked, until now.

I've done the obvious things like checking that all the cables are fully engaged in their sockets, rebooted everything several times.
Both keyboards have their Midi out set to Channel 1.

One thing I can't currently check is to simply run a direct cable between a synth & the interface, because the only 2 long enough cables are inaccessible in the bowels of the rack.

In Sonar, no Midi devices are present

Any clues?


Thanks

o boy jonesy,heres a bump anyway buddy.
im about to eat dinner,when i come back in a little bit i will try to help you problem solve this if you want.

heres hoping the bump bring more traffic.
if not you may have to resort to bringing this upstairs in the light so it can be seen.

Sorry to hear about this,what a PIA these troubleshooters are.

all my best buddy.

Charlie

Oh yes - I was trying to get soft synths to trigger - soft synths already loaded within a project, they all trigger correctly from the virtual kbd in the PRV, and input echo was on for all synths.


No midi activity is visible in the little icon at the bottom of the screen


In Sonar Preferences, the Saffire is recognised with the proper ASIO driver, but there are no Midi devices listed.


The Saffire connects to the pc via Firewire.


There doesn't seem to be anything regarding Midi in the Saffire Mixcontrol software


I think that's it

I just tried that Dave, and no luck.

The problem as far as Sonar is concerned is that there's no Midi instrument available for selection

What's the likelihood of both Midi ports going bad at the same time?

I do have a telephone number for Focusrite UK support, maybe i should call them.


I will test it out later with my Saffire 6 and see what happens

Another test.

Hooked up the Saffire 6 and the QX25 to the laptop which has X2a installed, and it all works as expected.

So it's either my computer  or something in Sonar has gone awry.

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

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.

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

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.

+1 for you, Bub.