Chris Randall: Musician, Writer, User Interface Designer, Inventor, Photographer, Complainer. Not necessarily in that order.
 

Tags: Interfacial


April 18, 2018

Dante Inferno...

by Chris Randall
 



A month or so ago, I got turned on to the concept of Dante, which is an audio-over-Ethernet protocol used primarily by big production houses and live sound reinforcement. (I imagine it was invented by someone that had to run a 48-channel snake from the stage to the front-of-house every night, and got sick of being covered in spilled-beer-and-shoe-dirt slime.) In the simplest terms, think of a network, but instead of files and web sites, it serves digital audio. You use normal IT shit like switches and CAT 6 cable, but your goal is shunting massive channel counts of digital audio at ludicrously low latencies instead.

I had known about it for years (you can't help but see the references if you're looking at high-end AD/DA converters, since the usual suspects in that world all have Dante capability). I didn't really think about the ramifications until a friend beat me over the head with the concept. My ultimate goal in my home studio/office is simplicity. The fewer cables I have run, and the fewer conversions I have to deal with, the happier I am. It is especially attractive to me because I run multiple computers of different flavors, and having their I/O talk to each other in more-or-less real time would be excessively handy.

Once I was tipped to the potential, the full OCD Experience kicked in, and I started thinking about replacing my current rat's nest of I/O and monitor controlling. The main attraction to me is ultra-low-latency computer-to-computer connections. I've always thought it is dumb to convert to AES or SPDIF to do a digital computer-to-computer audio interaction, and so do the Dante people. Nominally, a computer-to-computer connection in Dante would be the same as any old-fashioned way, with expensive converter boxes in the way. But Audinate (the company that invented Dante and is the Keeper Of The Holy Scriptures regarding the format) got that sorted in a big way, with three pieces of software that make Dante in a home studio an attractive option.



The first is Dante Controller, which is essentially a virtual patchbay that lets you connect Dante sources and destinations. Dante gear all has a Gigabit Ethernet port, and you basically just run everything to a normal Gigabit Ethernet switch in a star fashion. Dante Controller sees everything on the network, and lets you set clock masters and routings and shit. Controller is free.



The second piece of software is the Dante Virtual Soundcard. This is an ASIO and CoreAudio/WDM driver that works like any other sound card driver; it has 64 ins and outs (which is mildly comical in something like Live. Did you know the I/O panel scrolls? Neither did I) and ludicrously low latency. Any computer running the Virtual Soundcard and connected to the Ethernet rig throws its I/O to the network, and shows up in the Dante Controller patchbay. The driver is US$29 per computer.



The third piece of software is the one that seems like magic to me, and which is useful whether or not you have a Dante system. I only assume it isn't more well-known is because Audinate's business model doesn't lend itself to marketing to hobbyists and home studio folks. It is called Dante Via, and basically lets you route _any_ audio source in your computer to any other. Think of it as Soundflower or Audio Hijack, but on pharmacutical-grade methamphetamines. You can run either this or the Virtual Soundcard. It shows up as an ASIO destination in software that supports that, or a WDM/CoreAudio destination elsewhere. Instead of 64 I/O, you get 8 channels, but otherwise, it is more or less the same, as far as how the DAW works. You just drag-and-drop your sources to your destinations, and you can mix-and-match anything as you see fit and turn any piece of software or I/O in to a sender/receiver. Dante Via is US$49 per computer (which is incredibly cheap considering what you get) or US$59 for a combo of the Virtual Soundcard and Via. There is a 15-day demo of Via on the site.

I purchased a Focusrite RedNet X2P to be my main monitor controller. It comes with a pair of Focusrite's high-end mic pres (their good stuff, not the prosumer Scarlett series). This can be powered off a POE Ethernet switch, so it's just one CAT6 cable to the switch and that's that. It is built like a god damn main battle tank, and is one of those Just Plug It In And Go Because It's Really Well Made For People That Don't Want To Dick Around kind of things. My Adam nearfields go from that, and my desk situation is sorted. I connected the Skull Canyon NUC and my main computer to the switch via their Gigabit Ethernet ports, and with the former running the Virtual Soundcard and the latter running Via (I also use the computer for games, and would like to hear YouTube videos and shit), I have VCV Rack running on the NUC, with multi-channel audio at no noticeable latency running in to Live, with Live Link providing wireless sync over my home wi-fi network. (Note that the X2P comes with a license for the Virtual Sound Card, as well as some Focusrite plugins I'll probably never use, but never say never, right?)

It is early days for Dante in a small studio right now, and many of the I/O solutions that are promised aren't quite here yet. I can easily just plug in a high-end convertor or mic pre rack to the system and it'll just show up. Audinate is releasing a 2-channel class-compliant USB dongle so you can plug in iOS or visiting laptops to the network with ease, and there are several 2-channel AES, SPDIF, and analog solutions to bring legacy gear in to the fold. ProCo and Radial also have similar small-and-cheap solutions either already released or in the works. I've only had this rig working for a day, so I can't really speak to its robustness, but it performed flawlessly with the above VCV-on-another-computer situation, as well as an hour or so with World Of Warcraft and a brief writing session in Live. I gave the mic pres on the X2P a quick check to make sure they worked, but I can't really speak for their all-around applications at this point. I'll put up another post with further thoughts after a month or so with this system.

 
April 21, 2015

Crandall's Simple Steps To Avoid UI Suck...

by Chris Randall
 

When I gave my talk on UI design for music software at UCSB, at the end of the talk, I attempted to distill my rant to its essence, and provide a simple set of guidelines for uX and UI for plug-ins and apps for musicians. While some of this seems self-evident, I came up with these steps with the idea of providing some insight in to our world for engineers and academics that might not have any experience with professional musicians.

These are by no means Rules™ that must be adhered to, but rather some simple tips to keep your software product from looking like Pd. Basically. I break them all the time, but I have 75+ commercial products under my belt, so I get to do what I want. :-)

1. LIGHT ON DARK
Musicians are generally either in a dark studio/spare bedroom/basement or on stage, and generally working in the evening or at night. Looking at a bright white slab of screen can be irritating, and occasionally painful. A UI for musicians should be lighter colored elements on a dark background. The accepted guideline for contrast is 4.5:1 for normal text and 3:1 for large text. In real world RGB terms, assuming a black background, your text should be at least #959595 or lighter. (I prefer lighter.) Dark text and elements on a light background just sucks for the most part, but if you do it, maintain the same contrast ratio for any element that provides information to the user.

2. USE A MODERN DISPLAY FONT
Traditional fonts (and yes, I include the venerated Helvetica in this group) were not designed for readability on high-resolution computer screens at small sizes. They were designed for signs and newspapers. Don't use them. Make the effort with a modern display font, designed for modern systems. I am a DIN whore, I won't deny. But you can do far worse than Source Sans Pro, which is free as in your mom, and made by Google specifically for modern high-resolution displays. (Google actually makes quite a few modern display fonts for UI work that are free-ish.)

3. FLATTER IS BETTER
Unless, in addition to being a top-notch DSP engineer, you're also highly skilled at using 3D modelling software to make user interfaces, Don't Do It. There is a place for skeumorphism in audio software: this place is usually reserved for interfaces meant to ape vintage gear, to provide the user with a familiar experience. So I won't dismiss it out of hand. But it's something best left to pros. You're far better off just making a circle with a little line on it for a knob. It's hard to fuck that up.

4. MAKE THE UI FIRST
When an engineer or academic sort is intent on making a piece of commercial (or professional, at least) music software, he/she tends to get the DSP done first, then put a UI on it during or after the process. This results in a product that doesn't have a holistic feel. It is far better to codify your initial DSP idea, then design and code a full UI, then fit the DSP in. There's no law that says you can't change the UI during or after the process, but it really helps make a better product when you're building to a set goal, rather than "seeing where things lead." Sometimes, that's unavoidable, but you should really see where things lead before you draw the first pixel.

5. ASK A MUSICIAN
Designing products for musicians, if you're not one, results in bad products. You wouldn't want to buy a car designed by someone that doesn't drive, would you? There are... well, I won't say "standards," but there are ways of doing things in the music world that can perhaps go against normal uX conventions, and if you've never made music for money, in the studio or on stage (preferably both) then you should get somebody in your Circle of Trust that has, and does. And I don't mean at the beta-test stage. I mean as soon as you have the UI coded. Fitting the DSP in to a musician-friendly context is much better than trying to make a scientific/academic chunk of DSP musician-friendly by brute force after the fact.

Anyhow, these are just ideas that some may find helpful. If I'm way off the reservation, or other designers that read this blog have some different (or better) ideas, by all means hit up the comments.
 

Displaying 1 to 2 of 2 available blog entries.