steveo42
One thing I noticed with my AVB is that once in a while the MOTU app in the taskbar tray won't start when clicked on. Also occasionally I was getting an "ASIO Buffers Can Not Be Set" message once in a while when starting Reaper or Studio One (different message, same result, no interface).
This was VERY intermittent.
 
I traced this down to having Fast Boot turned on in Windows 10. It started after the Anniversary Update so evidently that update turned it back on as I did have it turned off prior to the update. I did turn it off again and have not seen the message since. My boot drive is an SSD so it's ridiculously fast anyway. 
 
I'll continue to monitor but thought I would mention it in case anyone else has the problem.

Thanks for the info. I noticed (only two times so far but still) that the AVB was not recognised as audio interface by Sonar after booting the DAW (but a reboot fixed it). I need to check whether Fast Boot is enabled ...

jbraner
Also - I've never had Fast Boot enabled (I had to look it up, as I'd never heard of it)

For folks who don't know, Fast Boot is enabled by default.
If you haven't turned it off, it is enabled.

It's not enabled or turned on if you don't have "hibernate" enabled...

jbraner
It's not enabled or turned on if you don't have "hibernate" enabled...

FWIW, I never have hibernate enabled.   
By default, Fast Boot is enabled.
The Anniversary update for Win10 does re-enable Fast Boot.
 
If you've got a dual-boot machine, you'll want Fast Boot disabled.
Otherwise, you'll see odd data loss... and other abnormalities.  
This is true even if you use separate drives for each OS.
 
There's no absolute right/wrong with this setting.
For many folks, it won't hurt anything to have Fast Boot enabled.
 
If you suspect it's causing an issue with the MOTU, disable it.
SSD on modern build will boot fast regardless...
 
 

It's called "Fast Startup" my bad... Us old timers love the word "boot".. lol !
Anyway, I have never had hibernate enabled on any of my personal machines.
I just don't see the need for it these days as I'm running either WD Black drives or SSD.
It boots from SSD in 5 seconds.
 
Thanks Jim for confirming the Anniversary Update turned Fast Start Up back on.
I knew I never turned it on and my minor headaches started right after the update.
 
One other thing I noticed was with Fast Startup enabled, I restored an image from Macrium Reflect, which I have been using with no problems for years, and with that image, I could not get the Ultralite AVB to work at all. Same ASIO buffer could not be set messages. Reinstalling MOTU Discovery app (latest beta) fixed it.
I suspect the Fast Startup being enabled when I originally imaged or maybe restored the drive was the cause.
Seems suspicious.
 
Just tossing this out there for folks to try if they are having oddball problems.
 
Here is where it lives:
 
Search for and open “Power options” in the Start Menu.Click “Choose what the power buttons do” on the left side of the window.Click “Change settings that are currently unavailable.”Under “Shutdown settings” make sure “Turn on fast startup” is enabled/disabled   

really really starting to like the AVB routing capabilities
 
I managed to link Sonar and Mixbus in realtime last night simply using the AVB routing options, didn't think this was possible (here)

steveo42
New firmware and driver released today , September 1, 2016, for the AVB series. 
Get it here:
 
http://www.motu.com/avb/i...d-additional-resources

Thanks mate. I get them right away - any details on what they changed? couldn't find it ...

I'm getting pretty much the same issues with this version.
I'm wondering if I just need to be patient and wait for these drivers to load - before trying to access anything that needs sound.
Is anyone else seeing anything like this?

I'm not sure what others are doing, but I'm sure Jim Roseberry mentioned *not* using 3rd party add-on USB ports.

jbraner
I'll post this in a seperate post:
I've gone back to the "non beta" drivers from March (2016) and they are loading perfectly - every single time.
I've been having problems with the beta drivers - where sometimes, there is no audio interface for SONAR (or any other Windows apps) to use. It's gotten a little worse with each beta version - and I'd have to power cycle the Ultralite AVB and/or the PC and/or mess with buffer settings (and then put them back where I want them) - to get the driver to load - so SONAR etc can see the interface.
 
Once loaded - the drivers work great - it's just a problem actually loading the driver. (especially after a reboot)
 
Just to check my sanity, I went back to the non-beta driver and it works perfectly.
 
Win 10 64 bit, Asus P8Z77-V using a (onboard) Intel USB3 port with no other devices sharing.

I guess that's why these driver are still "beta" and updated about once a month.
 
In my case they have worked OK so far; I don't get any problems when changing buffer sizes etc. However, sometimes the MOTU is not picked up when booting PC and MOTU at the same time (seems OK if MOTU is on when PC boots)

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.

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.

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)

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?
 
 

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.