I haven't tried it yet. I'm not in a big rush, as the new driver seems to be the same as the last beta one
(MOTU Pro Audio Installer 4.0 (71199)) - and this is the one I had the most problems with.
 
I was thinking that it might work better if I install it over the old driver - rather than when I had the 3 betas installed over the top of each other - but I'm not overly confident.
 
I'll get around to it soon - but the old driver works great, so I'm reluctant to "rock the boat" ;-)
(don't worry, I always do though...)

OK - I tried the new driver, and it's just the same as the beta. I can't be bothered trying to get the interface connected every few times I boot up :-(
 
I was able to reconnect sometimes by power cycling the interface, but disconnecting the USB cable made no difference (well, I only tried it once). I also tried another USB port, and it came right up - disconnected (!)
Anyway - there's nothing wrong with my USB port because the older driver works fine.
 
I've gone back to the 1.6 driver - which works fine.
 
I'll go see if I can log a support incident on the MOTU site.

I just had this happen again yesterday. Out of clear blue interface was seen by Windows etc but no sound. Powered down computer fully as well as MOTU and that didn't fix it. Unplugging and plugging USB cable was the fix. I've also discovered that after full power down, removing the line cord from the computer also fixes this problem.
 
One thing I noticed was that some of my USB ports somehow got the power management "Allow this computer to manage the power" turned back on. I know they were all off so I suspect the recent Anniversary Update reset them.
Other than that, I'm stumped.

steveo42
I just had this happen again yesterday. Out of clear blue interface was seen by Windows etc but no sound. Powered down computer fully as well as MOTU and that didn't fix it. Unplugging and plugging USB cable was the fix. I've also discovered that after full power down, removing the line cord from the computer also fixes this problem.
 
One thing I noticed was that some of my USB ports somehow got the power management "Allow this computer to manage the power" turned back on. I know they were all off so I suspect the recent Anniversary Update reset them.
Other than that, I'm stumped.

FWIW, The Anniversary Update for Win10 does reenable some settings and background apps.

jbraner
OK - I tried the new driver, and it's just the same as the beta. I can't be bothered trying to get the interface connected every few times I boot up :-(
 
I was able to reconnect sometimes by power cycling the interface, but disconnecting the USB cable made no difference (well, I only tried it once). I also tried another USB port, and it came right up - disconnected (!)
Anyway - there's nothing wrong with my USB port because the older driver works fine.
 
I've gone back to the 1.6 driver - which works fine.
 
I'll go see if I can log a support incident on the MOTU site.

steveo42
I just had this happen again yesterday. Out of clear blue interface was seen by Windows etc but no sound. Powered down computer fully as well as MOTU and that didn't fix it. Unplugging and plugging USB cable was the fix. I've also discovered that after full power down, removing the line cord from the computer also fixes this problem.
 
One thing I noticed was that some of my USB ports somehow got the power management "Allow this computer to manage the power" turned back on. I know they were all off so I suspect the recent Anniversary Update reset them.
Other than that, I'm stumped.

Could both of you please open a ticket with MOTU support ??? i.e. log in @ MOTU.com => MOTU Tech Links. They are very responsive on that official channel (compared to the email box that listed with the AVB driver download, which ended up in digital nirvana) ... it would be good for them to see that this is not just happening on my computer.
 
 
 
 

Could you all check something?
What happens if you power down the AVB units (prior to starting your machine).
Then, once booted into Windows... turn on the AVB/s.
Does the problem persist?
 
Are you all on Win10 with the Anniversary Update applied?

Rob - I opened a ticket today ;-)
 
Jim - that's not gonna fly for me, as I like to boot in to my "non music" partition - and then the music partition. Shutting everything down every time - just in case the MOTU driver is going to screw up - is a nuisance. Especially when the 1.6 driver is rock solid.
 
Yep - I'm on Windows Anniversary update, but I think the beta drivers (and this new one is just the same as the last beta one from August) did the same thing before the Anniversary update.
Also - the update didn't change any of my USB port power settings.
 
 
UPDATE: I just got a fairly lame response from support, saying to try a new cable and a different PC. To me - the old driver wouldn't be rock solid if I had a bad cable...

Hi John,
 
All I'm suggesting is to try booting into Windows (DAW install for you) with the AVB powered off.
Once Windows is up/running, power up the AVB.
It may or may not have an effect... but it's worth a quick test.
 
I agree that the older driver is rock-solid.
Round-trip latency wasn't particularly bad with this driver   
For those unfamiliar... 4.9ms at a 64-sample ASIO buffer size/44.1k
 

Hi Jim,
 
I'll install the new driver tomorrow again - and play around and try it.
I've had to change the cable for MOTU support and they want to see a video of what it looks like when it's "broken".
 
I've powered the MOTU off and on again - when it's"broken" - and sometimes it fixes it and some times it doesn't.
I'll play more tomorrow (but I'd rather work on some music)...

Jim Roseberry
Hi John,
 
All I'm suggesting is to try booting into Windows (DAW install for you) with the AVB powered off.
Once Windows is up/running, power up the AVB.
It may or may not have an effect... but it's worth a quick test.

Hi Jim,
I think you're on to something here. Sorry, I was getting grouchy last night (I'm in the UK) as this is a PIA - but I did more testing today. When I first installed the new driver (I'd gone back to 1.6) it didn't work at all. I tried pulling out the USB cable a few times - and it worked sometimes and other times it didn't.
 
Your method is the best workaround - this seems to work every time (so far, I'll let you know if it fails). Here's what I do when it's "broken":
- Power everything off
- boot up the PC (Ultralite AVB still off)
- bring up the Ultralite AVB after the PC has booted.
 
twice this seemed like it wasn't working - but the devices in control panel disappeared and re-appeared, and then it was working.
So - so far, I've been able to get it working with this recipe - whenever it goes "bad".
Sometimes it works fine - without doing anything special (I know this because I also tried to find a recipe for "breaking" it)
 
I have a case open with MOTU, and have gone over all of this with their guy. I've sent screen shots etc etc - so we'll see. I can't believe that this is only a problem for me - and a few others here.
I don't mind running on the old driver - but I feel it makes sense to try to figure out why the "new, improved" one doesn't work consistently.