Delay in loading MIDI interface drivers?

I've been noticing more often that if I launch Sonar (I'm still using X3 Producer, forgive me) right after booting up my computer, I'll have issues playing back MIDI tracks or not having my controller available, because my MIDI interface drivers are not loaded. They will eventually load after a few minutes, though, but in the past (in earlier versions of Sonar and in previous computers) I never had this problem. Can I tweak my system so my MIDI interface drivers (I have an M-Audio Midisport 4x4 for my hardware gear and an M-Audio Axiom 61 as a controller) load faster? Both are also connected to a USB 1.1 hub (but connected to a USB 2.0 port). Would that be a factor?

ShellstaX
I'm using X3 Producer too ;) My / Your prerogative - no need for forgiveness.
 
My initial thought was that you PC would have to know about them before they'd be selectable / usable to Sonar.
 
Have you got the latest M-Audio drivers?
 

 
Yes. No new updates have come out in a while.
 

ShellstaX
Your USB hub configuration could indeed be an issue ... and easy to test ... by removing it from thequation (even if only temporarily.
 
Desktop or Laptop?
How many onboard USB ports / types?
What's using them (e.g, my mouse works fine via a hub).
 
Definitely MIDI and not Audio?

Desktop.
Onboard...quite a few USB 2.0 and a few 3.0 ports.
Mouse, iPod interface, Printer and hub, which goes to all MIDI-related uses: M-Audio Midisport 4x4, M-Audio Axiom 61, Tranzport and a software dongle for Propellerhead Reason. 
 
Come to think of it, the Tranzport driver never loads up with a delay, it's always available, so it might not even be the hub.
 
I have no issues with any audio drivers.

Why would you use a USB 1 hub for anything? A USB 2 hub should be backward compatible, and if a hub is needed could be purchased for a couple of bucks these days. Some older equipment will not work on USB 3 but do you have anything so old it will not work on USB 2. If you have available USB sockets, I agree that it makes sense to bypass the hub at least for diagnostic purposes. When I try to attach a USB 1 hub to my Win7-64 machine I get a helpful message saying that I could get better performance with a newer technology.

slartabartfast
Why would you use a USB 1 hub for anything? A USB 2 hub should be backward compatible, and if a hub is needed could be purchased for a couple of bucks these days. Some older equipment will not work on USB 3 but do you have anything so old it will not work on USB 2. If you have available USB sockets, I agree that it makes sense to bypass the hub at least for diagnostic purposes. When I try to attach a USB 1 hub to my Win7-64 machine I get a helpful message saying that I could get better performance with a newer technology.

Well, a) Because I had it lying around; and b) MIDI does not require USB 2.0 speeds -- None of the interfaces on that hub involve audio.

lfm
If computer is all new check out if any chipset or bios updates are available.
 
First thing I would do.

The computer and motherboard (self-built machine) are circa mid-2012. And I don't have any problems with any other driver loading -- just those two M-Audio MIDI interface drivers.

elsongs
Okay, I replaced the USB 1.1 hub with a USB 2.0 hub...The issue hasn't changed. Now I think it's a SONAR issue rather than a Windows issue; upon boot-up, when I check the Device Manager, the Midisport 4x4 and Axiom 61 drivers show up in the "Sound, Audio etc devices" section, but when I open Sonar X3e and go to Preferences -> Devices, the drivers still haven't shown up. After checking maybe 5 minutes later, they show up.
 
Is this normal behavior then?

The delay is certainly weird, but still doubt it's to do with Sonar.
Some enumeration calls to system to find which midi devices there are - is pretty much all they can do.
Computer just starting up, can take some time for everything to work and be responsive, but five minutes seems long.
 
What I experienced on a job I had - was that my machine was pretty much unusable for 12 minutes after startup. System admin fixed by letting my Norton antivirus be installed locally.
 
Any antivirus there - that might hold on to things until tested a lot of things?
Try and disable and startup if you can.
 
I had a Evolution UC.33 controller some years back, and had some issues getting events through - using as midi ports in/out too.
Then M-Audio came with V5.x drivers and it was better.
Not delays for devices to show up like you experience, more of not always getting events, only now and then.
 
I later got a EMU Xmidi 2x2 usb interface, and never had an issue.