jbraner
Make sure you are actually running the old driver. I know it sounds dumb - but I had to uninstall / reinstall a couple of times before I was actually running the "old" driver. The beta ones never really get uninstalled.

The old one looks different if you look in Windows control panel, and it loads a different file if you check under device drivers.

When I'm back at my PC, I can give you the exact files if you need...

thanks, mate. i appreciate it. the first time around the driver definitely did not get uninstalled completely. the 2nd time I got a different audio preference GUI but no connection ... so there might have been some remnants left (especially as silly me installed the older driver before uninstalling the other one, expecting this thing to do it right by itself, not realizing this is a different installation package)

There are always remnants ;-)
Even when you "uninstall" in device manager - it doesn't really...

In Windows Device Manager:
 
Here's what the "old" driver looks like

 
 
and this is what the beta driver looks like

 
 
You'll notice that the (beta driver) MOTUProAudio.sys never gets deleted - so make sure you're actually running the older driver.
 

Thanks. I gave it another go and this time (why not before?) unstalling the AVB PRO driver and installing the USB AVB worked. So the device now seems to get recognized easier (well, it showed everytime I tested turning AVB or DAW off and on).
 
However, I cannot access the routing matrix as the other MOTU apps still dont find the device (???); turning firewall off makes no difference. I could possibly access it from another PC connected via LAN, but then I can't use the AVB port to hook up a 2nd device ...
 
Also, there is quite a penalty on the achievable lowest latency I can get as I need to use double size buffer which boost it from 4 ms RTL to >9 ms ...
 
So for now, the PRO driver with its occasional quirks of not showing still wins

Rob[atSound-Rehab]
Thanks. I gave it another go and this time (why not before?) unstalling the AVB PRO driver and installing the USB AVB worked. So the device now seems to get recognized easier (well, it showed everytime I tested turning AVB or DAW off and on).

I just thought I'd mention it - since I had to "uninstall" a few times before it actually installed the right (older) driver. ;-)
 
 

However, I cannot access the routing matrix as the other MOTU apps still dont find the device (???); turning firewall off makes no difference. I could possibly access it from another PC connected via LAN, but then I can't use the AVB port to hook up a 2nd device ...

Hmmm, that works fine here. I'm even still loading that little system tray thing

I *do* use a fixed ip address on the Ultralite though. Maybe that helps?
 
 

Also, there is quite a penalty on the achievable lowest latency I can get as I need to use double size buffer which boost it from 4 ms RTL to >9 ms ...

That's also different from what I'm seeing. I get more or less the same latency settings (actually the exact same settings) on both.
 
 

So for now, the PRO driver with its occasional quirks of not showing still wins

Please keep us up to date on this OK? Also - let us know if a new beta driver comes out, and if you have any luck with the "losing connection to the MOTU device" problem
 

jbraner
Please keep us up to date on this OK? Also - let us know if a new beta driver comes out, and if you have any luck with the "losing connection to the MOTU device" problem

Will do. I also contacted MOTU on this subject. We'll see if/how they respond ...

jbraner

Rob[atSound-Rehab]
Also, there is quite a penalty on the achievable lowest latency I can get as I need to use double size buffer which boost it from 4 ms RTL to >9 ms ...

That's also different from what I'm seeing. I get more or less the same latency settings (actually the exact same settings) on both.
 

OK, I might have been unjust regarding latency. NI Kontakt 5.6 was also installed meanwhile and apparently K5.6 needs more resources than before for the same project. So the projects where I had to increase the buffer all use K5.6 (and of course this also applies to the AVB PRO driver now)

jbraner
Please keep us up to date on this OK? Also - let us know if a new beta driver comes out, and if you have any luck with the "losing connection to the MOTU device" problem
 

quick update from my end regarding this situation:
 

• no new driver update, but the "v4.0+71199 | Sep. 1, 2016" AVB drivers are now the official ones. the ones from March are gone from the download page ...

• I only see the connection issues rarely i.e. sometimes the device registers @ win10 (i.e. is seen by MOTU settings & routing app) but not by Sonar (maybe 1 out of 10 times). it usually does not happen if I boot studio devices including the MOTU before booting the DAW.
• Interestingly, I had one occasion where neither booting DAW nor MOTU gave me access to the ASIO drivers in Sonar. Simply unplugging & plugging the USB cable at the back of the MOTU solved that (which is a bit of a hassle as it is fully cabled in a large equipment rack) ... anyway, what's difference in win10 between a power cycle of the USB device and a cable unplug/plug action???

• I did email MOTU support about 10 days ago and did not even get an acknowledgement that they received my enquiry. This may just be due to being located in Europe and support via website is only for US (???). so pls anyone located in the US seeing this problem contact MOTU, we may have a bigger chance to get a reply from MOTU this way.
• Meanwhile I run 2 devices (2x 1248 networked via AVB) and while it took me about a week to set up the best routing from the zillion options you get, I am extremely impressed by how these 2 units act together as one gigantic audio device (clocking, direct monitor across devices, headphone mixes, etc). I managed to hook up all control room gear, outboard and live room connections to the input the MOTUs provide and can now simply operate by changing routing presets rather than fiddling with patch bays and fighting poorly labelled multicore output jacks.

 

Thanks for th eupdate Rob.
 
I'll need to try the new drivers, and report back...

jbraner
Thanks for th eupdate Rob.
 
I'll need to try the new drivers, and report back...

Have you had a chance to give the latest drivers a try? I just heard back from MOTU saying that this is not a "known" issue and I should check USB port, cable, etc ... yet I do remember having a similar issue on the backup DAW (?) and you guys see it, too (???)
 
If you do get the connection problem again, pls check if unplugging the USB cable from the unit while powered does fix it (it seemed to work here twice which is odd as I don't understand this i.e. power cycle does not change it, but pulling the cables does, yet the USB plug sits very tight in that connection, so it can't be lose connection thing ...)