MOTU AVB interfaces - new driver available

v4.0+72091 from March 1, 2017 now available
 
Download @ http://motu.com/avb/index.html
 
FYI, I have been using intermediate beta version v71666 for 2 months and it contained some properly working improvements compared to v71418 from Nov 2016
 
 
MOTU AVB Installer v4.0+72091 (Release Date 2017-03-01)

• Added a workaround for PCI USB host controller cards with poor timing.
• Improved the audio engine timers.
• Improved Discovery app performance.
• Fixed an issue where sample rate changes could cause a stop error.
• Fixed an issue where unplugging UltraLite AVB could cause a stop error.
• Fixed an issue that prevented sample rate changes from Presonus Studio One and Pro Tools.
• Fixed an installer issue in 32-bit environment.
• Pro Audio Driver Read Me for all MOTU AVB interfaces

MOTU AVB Installer v4.0+71418 (Release Date 2016-11-01)

• Fixes an intermittent issue where a device fails to get detected upon restarting the computer.
• Pro Audio Driver Read Me for all MOTU AVB interfaces

Were you one of the ones that had initial issues with the Motu AVB?  I followed that thread very closely as this interface is on my short list.  What is keeping it from the top is the potential driver issues.

Thanks for the heads up Rob - I'll give it a try.

I've been using this driver for about 2 weeks after MOTU sent it to me to test. I was having highly intermittent clicks using heavy hitter VSTi like Ivory, balls to walls, all options on. Would happen after a minute or so of playing. Didn't have to be recording, just playing would do it. Drove me crazy. Buffer/Safety buffer size didn't matter until I went to something like 256 which of course made playing a VSTi impossible due to the latency.. Samplitude would report "Lost ASIO Buffer" when I got the clicks. If I was recording, it usually wasn't printed but sometimes it was. On playback sometimes it happened at the same time in the recording, other times it didn't. That's what was driving me crazy. It was all over the place. My gut feeling was the MOTU was losing sync after some period of time because these clicks never happened early on in playing or recording. My system is highly optimized but even so I tried all kinds of additional "stuff"... Even dragged out the ancient MAudio Delta 66 which had no problems at all. BTW the MOTU had problems with 2 different System boards. An Asus and a Gigabyte. Same symptom. Finally filed a techlink with MOTU and they sent me the driver.
Bingo.
All fixed.
I'm running 64ms with 16 safety buffer @48k and I can literally load up Ivory or Ravenscroft, turn on everything to the max, hit the sustain pedal and do glissandos for hours without a click or a pop.
I could not do that with the previous driver although loading it down with audio tracks and FX didn't seem to provoke anything. Just VSTi aggravated it for some reason.
LatencyMon barely registered, even with the older driver.
Processlasso showed nothing unusual.
I was just about to sell the unit.
 
Reaper and Studio One V3 latency is 1.6ms in and 1.6ms out for 3.2ms RTL......
That is amazing performance....
 
I have a MOTU Ulatralite AVB.
P.S. It is all about the driver and the company that makes the unit. An interface with great sounding boutique pre-amps, or a gazillion features is nothing but a brick if the drivers are not up to the task. Granted, not everyone is ITB and many who are recording real instruments using the direct monitoring features that most interfaces offer, have far less to worry about concerning RTL and tight drivers but even still, support matters. Honestly if someone asked me about MOTU and Windows 3 years ago I would have said, MOTU is a MAC oriented company. And from my perspective that was true. Not anymore. They are laser focused on Windows which is a good thing. 
Just my 2 cents.
 
 

These drivers seem to work fine here. I still get crackles in a busy project when I go to 64 samples (64 or 48 offset), but it doesn't freak out like it used to. ;-)
 
setting at 128 (offset 48) still works fine for me and gives me 8 ms RTL @ 44.1 KHz. This is perfectly useable.
 

Well I'll be damned! 64 with 16 works fine and gives 3.6 ms RTL at 44.1.
Thanks for pointing this out Steve!

I can still only run one or two amp sims (S-Gear) like this till it crackles a little - then I have to bounce or go back to 128/48. 128 with lower safeties also works fine now - and never used to - so this driver ver is definitely optimised better

So it seems some combinations of buffer/safety are better than others, and bigger isn't always better ;-)

That's exactly what I thought ;-)

This may or may not help but it worked for me.
 
With Chrome, you can't zoom the text size too large or it will not work. So open a web page, say Google.com, and hit CTRL - (minus key) to reduce the size of the text. Close Chrome and then try the MOTU interface. I had the same problem a while ago and it was driving me crazy. 
Zoom to 80 % works for me

Maarkr
nope, went down to 50% and it still wouldn't load.

Rats!
That is weird.
Only thing I can think of is maybe some extension in Chrome  that is causing problems.
Mine works here, no Ethernet hooked up though.