gmp
 
 IN the past when that has happened a reboot won't fix it, I need to reboot the AVB box with my computer totally shut down. Next time this happens I'll hold off rebooting the AVB box and see if it's just the driver not being recognized for that onetime or if it requires the box rebooting.

are you using the latest AVB driver v2.0+71418 from Nov 1, 2016 from http://motu.com/avb/index.html ? MOTU came up with this one due to us insisting to look into and fix the problem of the AVB not being recognized after (re)boot.
 

ryecatchermark
I can re-create the static recording problem through Thunderbolt by using MOTU Audio Console or CueMix and then going back to Sonar to record.

 
which makes you #3 to demonstrate that Sonar and CueMix/webUI seem to have problems when they send data via the same USB port
 

ryecatchermark
BUT, when I totally disabled my laptop's WiFi in device manager, The 828x with Thunderbolt seemed to work perfectly fine... even when monitoring and recording at a 64 sample buffer size.  When I re-enabled WiFi, the problem came back.

So, I tried USB again after disconnecting the Thunderbolt cable... this time the USB connection seems to be running really stable, even at a 64 sample buffer size.  The USB connection WAS giving me random problems before... maybe recent Windows 10 or Sonar updates fixed it?

 
wait and observe. I doubt that win10 updates have yet made a difference to the better (considering the recent issues they in troduced to other Soanr users)
 

ryecatchermark
The problem is that I need to be connected to WiFi for my Waves Plugins license to work (and you may need to be on WiFi if your audio console is using a web browser???).

to that there is an easy solution: use WAVES Central to move your licenses to a normal USB stick and turn it into a dongle. I did that a long time agon and it works fine.
 

Yeah, I might have to go back to the Waves plugin license being on a USB stick... I was trying to avoid it as I already have an iLok to plugin sometimes as well.
Mark.

Yes I'm using the latest AVB driver v4.0+71418 from Nov 1, 2016

FYI, I opened a support ticket with MOTU last week and added a lengthy problem description. I got a short reply last night, so we at least got the communication going. If anything comes out of that ... I'll let you guys know

I'm in conversation with MOTU as well. I am going to try a RME Babyface Pro next week and let you know if it has similar issues.
Mark.

I received a beta driver last night, which I put thru a 3 hour test. It seems to behave a lot better as regards interference with webUI open in different browsers (basically, I could not get it to cause the serious dropouts I could produce before) and it also seems to perform better (but not perfect) with that Sonar MMCSS option (so that is still under investigation / being discussed with MOTU support) ... I still wish someone from Cakewalk would comment and share more information rather than the "keep it checked" that's all there is in the manual.
 
In these 3 hours of recording no audio file corruptions occurred, but I need to test that a lot longer as this was a rare but serious issue.
 
The driver is confidential and explicitly not to be shared/distributed, but if it proves to be better in the long run, MOTU should make it public shortly after (happened the same way last time)

This may vary with that MOTU driver (although I thought they were unified now...) but with the MOTU Ultralite 3 which I have, the ASIO driver itself enables MMCSS when in use, so the checkbox in SONAR has no effect.  The WDM driver does not enable MMCSS so the checkbox in SONAR does do what it's supposed to.

KPerry
This may vary with that MOTU driver (although I thought they were unified now...) but with the MOTU Ultralite 3 which I have, the ASIO driver itself enables MMCSS when in use, so the checkbox in SONAR has no effect.  The WDM driver does not enable MMCSS so the checkbox in SONAR does do what it's supposed to.

how do you find out whether the driver itself enables MMCSS or not?

Monitoring the MMCSS service - it's set to manual by default, but firing up SONAR with ASIO mode being used turns it on; reboot and try WDM and it doesn't.

I unchecked MMCSS. I recorded a mix routed back into Sonar from my analog mixing console and when I listened back to it, I found 2 bad glitches on the intro that weren't there while I was recording, so I decided I better check the box for MMCSS again.
 
In the past all glitches were audible, so when I heard one, i could just back up and punch back in to fix it. I'll just wait until they fix this.
 
I'm very encouraged by the beta driver. Great work pressing MOTU. I had no luck with them for well over a year. I hope we get this resolved once and for all.