Quote:
Originally Posted by
JoelFan
➡️
I assume that the Windows problem "Error message received from server: argument must be json (Code 400)" hasn't been fixed yet. I did the upgrade on my brand new Ultralite AVB, but the problem is still there. Any plan to fix it?
It's fixed and in the release pipeline. Hopefully we can get it to you soon! For now, you can work around the issue by accessing the web app via ethernet and the interface's IP address instead of USB.
Quote:
Originally Posted by
matt82aust
➡️
Who is using this device with Pro Tools? How configureable is it to workaround the 32 i/o limit within Pro Tools? If I had multiple boxes throughout the studio, am I able to patch in just the inputs required? Obviously 1 device has up to or more than 32 channels of I/O, and I know Pro Tools can be stubborn in what you can use.
Yes, that's a frustrating limitation imposed by Pro Tools on third-party hardware. The channels to and from the computer are completely routable. That means you could map whatever analog or digital ins to the first 32 computer ins you'd like. It's like a virtual patch bay. Same goes for the outputs from the computer.
Quote:
Originally Posted by
desertdome
➡️
- Is the LCD display dimmable? I can change the contrast, but haven't found a way to dim it.
No, only contrast is controllable.
Quote:
Originally Posted by
desertdome
➡️
- Do the analog outs 1-8 use one 8-channel ESS Sabre32 DAC and the mains and monitors use another 8-channel DAC? If so, any theoretical advantage to using Main 1 for left and Analog 1 for right for two channel listening so that each has its own DAC chip?
I don't know but I don't think you would hear any difference. That said, feel free to do a blind listening test and see if you can distinguish the two configurations!
Quote:
Originally Posted by
desertdome
➡️
- I use JRiver Media Center for playback. JRiver has 64-bit volume control dithered to 32-bits. The Exasound DAC has a plug-in that lets JRiver control the hardware volume of the ESS Sabre32 DAC chip. Is it possible to get similar volume control with the MOTU units?
Well, it should be possible for someone to develop such a plug-in but we have no plans to. You could use our OSC or HTTP API to control the interface and the DAC volume stage.
Quote:
Originally Posted by
Sammix
➡️
Maybe a dumb question but i need someone to clearify me.
If u connect two of these motu avb devices via the ethernet port, do u still need the adat ports for higher channel counts?
If no, can u run 24 i/o via ethernet port at all sample rates without the limitation of adat which basically stops at 48khz?
AVB (over ethernet) allows up to 128 channels in each direction and works at all sample rates. That means you could connect two interfaces and stream 128+128 channels between them at 96khz, for instance.
ADAT does work up to 96khz with SMUX but that reduces your channel count by half.
Quote:
Originally Posted by
GGPS
➡️
Hello again mrmiller,
today I had some problems with the web-gui: after some while (I think 1 hour) the connection was lost: "can not communicate with server / driver)
after a reboot everything was fine for a while and then the web-gui disappeard again.
I have it connected witzh USB to win 7 64bit. also it is connected to a router (vodaphone easybox 802) with DHCP on (but the router is not connected to Internet and not connected to my Audio PC).
We're looking into this issue currently. As a workaround, if you access the web app through its ethernet port and IP address instead of over the USB proxy, everything should work properly. The problem has to do with the USB web proxy server getting cranky, so accessing it via ethernet/WiFi bypasses it altogether. Alternatively, you don't need to restart your computer: unplugging and replugging the USB or power cycling the interface should have the same effect and take less time.