Slightly off topic but still related to the Ultralite AVB, does anyone know what the impedance the headphone socket can drive? I am looking at buying a set of HD 650 headphones and they are rated at 300 ohms.
Thanks,
Andrew.
 
Edit: If anyone is interested, just heard back from MOTU and the built in amp is good for 60 to 600 ohm headphones.

I just got hit with the "not loading" problem today. What I find is that everything recognized in Windows and even the MOTU Discover app, but I get no sound anywhere in Windows and something like "No ASIO Device Found" in all my DAW programs.
 
Power on/off/etc doesn't fix it.
I found that changing the sample rate via the MOTU Discovery app, seems to wake it up.
So if it's at 48k, I change it to 44k, make sure MOTU is default device in Windows,  reboot (not sure if this needs to be done) and now it's fine.
 
Weird bug because it doesn't happen all the time.

That's exactly what I'm seeing steveo. I'm glad it's not just me - as I hate having a "unique" problem that doesn't happen to anyone else ;-)

The "non beta" driver never has a "connection" problem, so I'm sure they'll fix this.

jbraner
That's exactly what I'm seeing steveo. I'm glad it's not just me - as I hate having a "unique" problem that doesn't happen to anyone else ;-)

The "non beta" driver never has a "connection" problem, so I'm sure they'll fix this.

If I get a chance today, I'm going to file a bug report. I can definitely say that having fast startup on aggravates it. Since I unchecked that option it only happened once. I think you are right, it's some kind of timing problem when the PC is booting. I also noticed that doing a restart vs complete shutdown aggravates it and once it's in the failing state doing a power down won't recover it but when it's working, which is 99.999 percent of the time, I have never had it fail when doing a complete power down and then power up.
 
This is going to be tough to explain to MOTU :)
 
 

steveo42
I also noticed that doing a restart vs complete shutdown aggravates it ...
 

I assume all of you are on win10? Because this might also be partly a windows issue (OMG!) ... I'm seeing similar issues with the ESI MIDI interfaces i.e. working perfectly when coming from a cold boot but after a reboot only 1 of the 2 units shows up and to get both working again needs a USB hub power cycle (fast boot disabled) ... yet, ESI may just have a similar driver issue as MOTU (it's a complicated world)

Yep Win 10 64 bit here.
 
steveo - I've been in touch with MOTU support about this, so the more people that report this problem, the better! ;-)
 
Rob - that's interesting. The thing is, the MOTU driver from March (before the beta versions) never does this. I went back to it, just to prove that I'm not making things up (about the "good old days of the old driver" ) and it works perfectly.
 
I run a dual boot machine, so I reboot a lot. That's how I noticed this problem a lot.
 
Also - I've never had Fast Startup enabled.
 

steveo42
I just got hit with the "not loading" problem today. What I find is that everything recognized in Windows and even the MOTU Discover app, but I get no sound anywhere in Windows and something like "No ASIO Device Found" in all my DAW programs.
 
Power on/off/etc doesn't fix it.
I found that changing the sample rate via the MOTU Discovery app, seems to wake it up.
So if it's at 48k, I change it to 44k, make sure MOTU is default device in Windows,  reboot (not sure if this needs to be done) and now it's fine.
 
Weird bug because it doesn't happen all the time.

I'm also seeing this more frequently now, so I'm considering going back to the official driver from May.
 
Is there a specific firmware version that goes with the May drivers or are you using later firmware?
 
Is there any penalty on latency or performance since MOTU states "Ultra-low latency performance for both Thunderbolt and USB operation" for the beta drivers?
 
 

I'm just using the latest 1.2.8 firmware and it's fine. Just use the "control panel" rather than browser to change buffer settings.

I don't see any difference in latency. I think the big thing with the beta drivers is the thunderbolt support (my Ultralite AVB is USB only) and more granular settings for buffers. They go down to way lower latencies, which I can't use anyway (the computer craps out).

I run the old drivers on 128 at the lowest "safety" setting (7.8ms RTL)
Beta ones at 128/48 (8ms RTL)

jbraner
I'm just using the latest 1.2.8 firmware and it's fine. Just use the "control panel" rather than browser to change buffer settings.

I don't see any difference in latency. I think the big thing with the beta drivers is the thunderbolt support (my Ultralite AVB is USB only) and more granular settings for buffers. They go down to way lower latencies, which I can't use anyway (the computer craps out).

I run the old drivers on 128 at the lowest "safety" setting (7.8ms RTL)
Beta ones at 128/48 (8ms RTL)

Strange. Last night I tried to use the official drivers from May March 23 2016 with the latest firmware version and the AVB was not seen by the computer at all ...
 
 
EDIT: Just saw that there is a new beta driver for Mac dated yesterday ... I wonder if there are upgraded PC drivers about to be released as well ...
 
 
EDIT #2:  I wonder if windows firewall still could be a source of troubles (reported fixed for the official version, but for the beta? there are no logs)
 
MOTU AVB Installer v1.5 (Release Date 2015-11-23)

• Fixed an issue where Windows Firewall would interfere with device connectivity.

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...