jbraner
Drocket,
I found that when it rebooted, it couldn't pick up an ip address - it just hung. I just switched it off and on again and it was fine (but not updated).
When I gave it a fixed ip address (now I always know what to point my browser to too) it worked fine, and I've done 3 or 4 updates this way.

Thanks John,
 
I will keep that in mind if/when I have to do another update.
 
Andrew.

steveo42
The videos are a good place to start to learn the routing which initially I found confusing, although very powerful. This page also contains the latest beta software. Make sure you have updated the firmware first and follow the directions to the letter.
 
http://www.motu.com/avb/index.html#avb-download-additional-resources
 

Mine came with the latest firmware installed - but it's easy to check if your DAW is connected to www. simple button click in the WebUI or also available from the MOTU discovery App, which is installed automatically and can be found among the taskbar popups ... I would assume it even alerts you of a new firmware (?)
 
Make sure you download the latest drivers (http://motu.com/download). Install the "Pro Audio" driver, which is still beta (last update v4.0 Jul 29, 2016).
 
The routing tutorial videos are nice for showing what's possible, but until you get hands on, you don't fully grasp it. So this will take time to fully exploit it ... but the routing/mixer options were a key argument for ordering and checking out the AVB.

So just to recap - using the internet and your router is only for things like downloading firmware updates, or configuring your MOTU with a phone or ipad.
 
Otherwise, you just use a browser instead of a Windows (or Mac) app. The MOTU has to be attached to your PC (via USB) or it wouldn't produce any music - so you can access it via a browser over this USB connection (using the MOTU discovery App), or else you can attach to your PC (or via a router) with a ethernet cable and access it this way with your browser (just using normal ip address)
 
EDIT - those new drivers are called "beta" but they're good. They've been around for at least three versions (of beta) for the last few months - and they work fine.

BTW - last night I tested for proper alignment of audio files (i.e. record latency compensation).
 
While my Roland interfaces were always spot on (i.e. did not require a manual offset), I had to apply +82 samples offset (@96kHz) to obtain proper alignment - anyone else seen that?
 
The required offset seems to be constant across different ASIO buffer settings, so it is fine to define once and leave it (see "Sonar Preferences / Sync and Caching / Manual Offset" at bottom of tab, set to +82, keep "Use ASIO Reported Latency" checked")
 
However, there is one potential pitfall: If you change the number of channels on the AVB to be sent from/to the computer, the interface name in Sonar changes (as it contains the number of I/O in the name). Hence, you will have to remember to redefine this in case you change the AVB to use more/fewer channels.

Rob[atSound-Rehab]

steveo42
The videos are a good place to start to learn the routing which initially I found confusing, although very powerful. This page also contains the latest beta software. Make sure you have updated the firmware first and follow the directions to the letter.
 
http://www.motu.com/avb/index.html#avb-download-additional-resources
 

Mine came with the latest firmware installed - but it's easy to check if your DAW is connected to www. simple button click in the WebUI or also available from the MOTU discovery App, which is installed automatically and can be found among the taskbar popups ... I would assume it even alerts you of a new firmware (?)
 
Make sure you download the latest drivers (http://motu.com/download). Install the "Pro Audio" driver, which is still beta (last update v4.0 Jul 29, 2016).
 
The routing tutorial videos are nice for showing what's possible, but until you get hands on, you don't fully grasp it. So this will take time to fully exploit it ... but the routing/mixer options were a key argument for ordering and checking out the AVB.

1. The Beta drivers don't show up when you click the update button from the GUI. At least not as of the last version. I'll check again when a newer beta gets released.
 
2. What I did, was have the GUI opened on my other monitor as I watched the videos so I could duplicate what was being presented in real time. This is how I remember it best. YMMV as different people have different methods of learning material.
Either way it will definitely take time although I don't think it's as complex as RME TotalMix :)
 

HighAndDry
Ok   thank you all so much.  I will probably be all over this thread.  I am eager to get it.  It arrives tomorrow.  From the EM review I read, this is a complicated unit.  Lot of capabilities.  

 
I'd be amazed if you didn't like the 1248.

• Great fidelity
• Great low-latency performance
• Extremely flexible
• Solid drivers

I agree Jim.. MOTU has an excellent set of interfaces with these AVB units. 

steveo42
 
2. What I did, was have the GUI opened on my other monitor as I watched the videos so I could duplicate what was being presented in real time. This is how I remember it best. YMMV as different people have different methods of learning material.
Either way it will definitely take time although I don't think it's as complex as RME TotalMix :)
 

One thing to be aware of, though logical once you know: you should not try to change the routing while Sonar playback is running ... which is logical when it comes to I/O channels between Sonar and the AVB.  However, it also applies to the internal AVB routing.
 
I had tried to set up monitor routing using the internal AVB mixer DSP while having sound from Sonar sent to the interface (like you would do in a live show environment, e.g. ok Analog IN 3 is receiving the bass signal, let's route it to MIX IN 3 ...). It took me awhile to figure why I just don't get any output, but apparently you need to make all routing decisions before opening Sonar, or at least apply changes by opening the AVB web interface via Sonar audio preferences to have them accepted.  While playback is running, it keeps throwing changes away when closing the web interface ... which is good as it provides safety and stability as in multi-control environment from several PCs, Phones, tablets, etc.

Really impressed with what I tested so far ...

• Great routing options (now that I understand how it works)
• Internal latency only 0.6 msec (e.g. if analog IN 1 is routed to analog OUT 2 while also grabbing the feed to record it in Sonar, perfect for sneaking the MOTU into a chain without causing an noticable latency)
• I can play K5 Abbey Road drums or AD2 via the e-drum kit at ridiculously lower buffers (64 samples + 48 safety @ 96 kHz) which translates to truly imperceptible latency (something I could not do on any interface I owned before)

 

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.