I'm going to start a new thread - because the other one is titled "New Thunderbolt Drivers..."
(http://forum.cakewalk.com/New-Thunderbolt-Drivers-for-MOTU-m3411304.aspx)
 
The new beta drivers are for USB *and* (now supported in Windows) Thunderbolt.
I'm just using the USB driver for my Ultralite AVB.
The first version did away with the "hidden buffer" controls - but they're there in the new beta version.
 
Now you can change buffer size AND "Host Safety Offset" - all done in the web interface. (no more control panel)
Both buffer size and host safety offset go down to 8 samples! Setting both to 8 samples shows up as 0.7ms RTL (!) in SONAR - and is, of course, unusable - for me anyway.

I'm not really able to get lower latencies with this driver - but between the two settings, you can make changes in much smaller increments, so it might help everyone get settings that are "just right".

I also think that maybe some combinations might be better than others (eg is it better to set lower buffer settings and higher offset, or higher buffer size and lower offset? you could achieve the same latency with various combinations like this). My PC just does not like buffer size of 64 samples. The ampsim channels just go berserk and seem to self oscillate - in to the red!

MOTU told me:
"The buffer size setting is pretty straight forward, but the safety offset is where it requires a “tuning”.  Generally speaking, I’d say 48 samples is a good number to start this process, and work down/up to test it against your system."
 
So the new beta driver is much more configurable than the last one. We're on the right track now.

Can you tell me what version you are running?  I have the May 18 version from the web site and don't see the "offset" settings.  I'm assuming you have a later version than I do.
 
It seems to work OK, but there are a couple of things that don't seem right, but I am moving from an UltraLight mk3 so I'm not entirely sure how it is supposed to work.
 

1. I am only getting a single pair of inputs/outputs through Windows, each one called "Out 1-2".  I expected to see many outputs.
2. The inputs/outputs in Sonar don't seem to be impacted by the number of channels specified in the "Computer setup" section of the configuration.

 
I will reach out to Motu, but I'm wondering if you are seeing #1 and #2.
 
Thanks in advance,
Robert

That's the version I'm running.
MOTU Pro Audio Installer 4.0 (70505).exe
 
The offset setting in in the browser access to the Ultralite AVB - right next to the buffer size settings.

 
 
I can access all the inputs/outputs - so it sounds like something is not right.
Have you got the latest firmware installed? 1.2.7?
You can safely "downgrade" to the non beta driver (and older firmware if you want) and then try updating again?
 

Those new USB drivers are not for all devices.  The driver for my 896mk3 Hybrid is still listed as Oct 28, 2015.

fireberd
Those new USB drivers are not for all devices.  The driver for my 896mk3 Hybrid is still listed as Oct 28, 2015.

The public beta drivers are for the (newer) MOTU AVB series.
 
It's good to see MOTU allowing for super low buffer settings.
Some folks will be able to make effective use of them... others won't (depending on performance/load).
Let circumstances (performance/load) dictate your limitations... rather than the driver imposing (dumbed down) hard limits.
 

Thanks for the info.
 
First I forced the 1.2.7 firmware (even though it was already installed).  No change.
Then I uninstalled all the drivers (including the older mk3 drivers) and reinstalled just the AVB beta drivers. Now I do see the Host Buffer Size/Safety Offset fields.
 
I still only see one input/output pair in the Sound control panel and only the physical ins/outs in Sonar.
 
I'll reach out to Motu -- I'll report back what I learn / find out.  

Actually, looking closer at the settings, I find the Sonar is showing all the inputs/outputs I enable.  What I didn't expect was that the names reported in Sonar were driven by the routing settings on the device.  Pretty cool -- and complicated!
 
So my only outstanding issue at this point is that I only see one stereo input/output in the Windows control panel.  Just to be clear, is this something I should expect?   Here is a snip of playback, the recording side looks the same.  This isn't really a big deal to me, I am just wondering if I'm seeing a problem:
 

 
Thanks in advance,
Robert
 
 

rwandering
 
So my only outstanding issue at this point is that I only see one stereo input/output in the Windows control panel.  Just to be clear, is this something I should expect?   Here is a snip of playback, the recording side looks the same.  This isn't really a big deal to me, I am just wondering if I'm seeing a problem:
 

 

That's normal.
Keep in mind that you can route that single Windows audio output to any of the AVB's physical (hardware) outputs.
This is done via the patch-bay...
 

Thanks -- it would be nice to have another stereo output pair there, but really not important.
 
I am amazed by the flexibility of this device.  Decoupling physical IO from virtual IO devices seems like such a no-brainer, but this is the first time I have seen it like this.  
 
Thanks for the help! 

It's good to see MOTU allowing for super low buffer settings.
Some folks will be able to make effective use of them... others won't (depending on performance/load).
Let circumstances (performance/load) dictate your limitations... rather than the driver imposing (dumbed down) hard limits.

They seem to be working fine too...