• Hardware
  • MOTU AVB interfaces - driver 73777, now 73991
2017/09/28 04:32:48
Rob[at]Sound-Rehab
Hi Guys!
 
Just realized that there is a new MOTU AVB driver (73777) - released 2 days ago ... and apparently there was another release in August which was not announced on their front page (hence I missed that one).
 
Click the links below to download from MOTU site.
 
 
MOTU Pro Audio Installer v4.0+73777 (Release Date 2017-09-26)
  • Fixed intermittent USB updater download problems.
  • Fixed an issue that caused Discovery App to miss devices.
  • Supports AVB stream channel names for ASIO.
  • Supports WaveRT for better experience with YouTube and other multimedia clients.
  • Pro Audio Driver Read Me for all MOTU AVB interfaces
 
MOTU Pro Audio Installer v4.0+73263 (Release Date 2017-08-14)
  • Fixed intermittent USB updater download problems.
  • Fixed an issue that caused Discovery App to miss devices.
  • Supports AVB stream channel names for ASIO.
  • Supports WaveRT for better experience with YouTube and other multimedia clients.
  • Pro Audio Driver Read Me for all MOTU AVB interfaces
 
 
Check that you are using the latest firmware (from June 2017!): http://motu.com/proaudio/index.html#avb-download-additional-resources
 
 
2017/09/28 04:39:00
Rob[at]Sound-Rehab
FYI, I haven't tried it yet but will install right away and report back after a few days.
 
The last driver in June was a step up for low latency performance. This one apparently fixes 2 issues that make the use of it more convenient: discovery app not always spotting the device (I had that happen but could always access from Sonar preferences, so no show stopper) and AVB stream names for ASIO (which should be a nice feature if you are like myself networking 3 AVB devices with different configs at different times; hence this should always now tell you inside Sonar what you are routing to USB input)
 
 
2017/09/30 19:05:30
jbraner
I just installed the one from August - and was going to report here.
I'll install the new one tomorrow and will try it out this week - and report back here too.

Thanks for the heads up Rob 😉
2017/10/04 01:50:49
maximumpower
Are you having issues with the MOTU interfaces? Is that why they are releasing new drivers?
2017/10/04 05:59:11
Rob[at]Sound-Rehab
maximumpower
Are you having issues with the MOTU interfaces? Is that why they are releasing new drivers?




no, not really. yet MOTU still manages to push the performance of their latest drivers even further up (e.g. another step up on low latency performance was released in June, which IMHO now kicks competitors like RME in the b***).
 
the latest update was mostly improving "cosmetic" things that are still very useful, like e.g. have channel names of AVB networked MOTU devices automatically appear in Sonar as ASIO channel name, which is super helpful if you have >30 inputs permanently cabled up and selectively only use some of them for smaller session, like I do with 20+ XLR leads into the live room and numerous hardware synths plugged in the control room while I rarely need both at the same time.
2017/10/04 08:39:16
jbraner
It seems fine here so far. The only weird thing I get (and it's the same as the one from June) is that sometimes SONAR (when you first open it) tells me it's found a new driver and wants to replace ie "MOTU Pro Audio" with "MOTU Pro Audio analog 1". Then other times it's the opposite.
Don't quote me on the second name - I just click OK and get on with it, and it works fine.
Maybe it gets confused with "friendly names"?
 
 
2017/10/04 10:28:39
jbraner
Here's what I get every so often. (bearing in mind that nothing at all has changed from last using SONAR)
This screen when I open SONAR:

 
 
And this is the friendly names that I've set up:

 
 
Everything works fine, so I just click OK (on that first screen) and get on with it ;-)
2017/10/05 06:42:37
Rob[at]Sound-Rehab
Strange. I have never seen that but I do not use the friendly names anymore since switching to MOTU.
 
With friendly names you get shorter names BUT you miss out on a great feature from MOTU which is naming the input channels on the routing matrix and having that displayed automatically as ASIO input names.  Hence I label what is plugged into the interface in the routing matrix (and configs can be saved/restored there) and find it much easier to pick the right input in Sonar.  BTW, I also use different MOTU configs to shorten the list of I/O in case when I do not need it (e.g. mixing heavy projects, recording singer/songwriter tracks).
 
This may not be so relevant to you but worth a try whether this "fixes" that strange behaviour. 
 
BTW friendly names are stored in the AUD.ini file, which accumulates whatever you used over the years. You could try to backup that file and remove all ALIAS names for MOTU and see if that helps.
2017/10/05 08:49:54
jbraner
I'm gonna have a look at this...
2017/10/05 14:15:51
jbraner
I cleaned out my AUD.INI file. There was a load of crap in it - I think this was because the driver changed from something else to "MOTU Pro Audio".
 
It just added a new MOTU section to my cleaned out file, and I fixed the names a little in the MOTU Routing settings - AND I mad a little friendly name - something like MOTU Main out 1/2 instead of MOTU Main out 1.
 
So we'll see if it stops being confused ;-)
 
Meanwhile the new drivers seem fine. I haven't pushed them (interms of low latency) but I will be recording again soon - so I'll drop the latency and see how they respond ;-)
12
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account