thing-a-day 1: euphonix mc mix review part 1

Introduction

After my photography buddies insisted that 90% of photography is your digital darkroom workflow, and convinced me to switch to Adobe Lightroom, I’ve been struggling to get my studio workflow similarly streamlined. I grew up on studio production in the late 1980s, meaning large analogue mixers, one channel per input, and everything mixed down to 8 sub-mixes running to a 1/2″ 8-channel reel-to-reel recorder (Tascam 38). I naturally think in terms of taking everything down to 8 busses, then doing a final mixdown “live” from tape to 2-track. It’s a two-step workflow that I can do in my sleep. It’s also 20 years out of date – long due for an overhaul.

So when I saw this press release from MOTU (makers of my DAW, Digital Perfomer, and my PCI-based audio interfaces) touting a new “high-end” control surface – the Euphonix Artist series – I decided the time had come to make a change. (The forthcoming MOTU Volta plugin pushed me over the top.) I’d heard of tons of difficulties using Mackie Controls and HUIs with DP previously, so reading an honest-to-goodness press release from MOTU left me hopeful they would proactively work to make the Euphonix devices the best control surface for DP. So, I bought a cheap used MOTU 24i to accompany my 1224, and ran every device in my studio directly into the computer. Knowing some of the limitations I might experience being an early adopter, I spent the cash on the MC Mix. I figured that 8 tracks of full-motion faders and endless rotary encoders (MC Mix) would be preferable to 4 tracks + a touchscreen (MC Console), as I’m used to grabbing for knobs and only looking at a meter bridge. Later, I rationalized, I could add the MC Console if I wanted. Also, my friend dys4iK gave me a Shuttle Xpress, which I use as a jog/shuttle/transport device – meaning I don’t need another one just now. (Review forthcoming.)

Unboxing

The MC Mix comes well-packed in an attractive box. The device itself is well weighted, and feels solid in your hands. A big kudos to Euphonix for only using red, yellow and green LEDs; no bright blue LEDs blinding you from this device! The OLED track indicators are also quite attractive and understated, with very little lag and no discernible flicker in my incandescent-lit studio. If I had any complaint about the physical device, it’d be that the rotary and fader knobs are made from metallized plastic. I guess for the powered faders this is understandable – less mass to push around – but a bit surprising based on their look. Still, they slide nicely, and after the initial “plastic surprise,” I haven’t thought twice about the build quality. The box also includes a hefty power supply, and a piece of 6-foot Cat 5 Ethernet cable. This went straight into the second NIC of my DAW. I would have preferred a slightly longer cable coming from the line-mounted power brick to the MC Mix itself, but I can’t complain, really.

Setup

Installation was straightforward under OSX 10.5.6. Connect power and the networking cable to the MC Mix, then load the OSX driver. As Euphonix frequently releases driver updates (especially targeted at improving Digital Performer compatibility!) it’s best to download the latest drivers from Euphonix’ site directly, ignoring the packed-in CD-ROM. EuControl launches at boot with a spinning green logo in the Dock. After the EuControl driver detects the MC Mix, the logo stops spinning, and the 8 MC Mix OLED displays change from the Euphonix logo to 8 dotted boxes — a gratifying indication that communication has been established. The control panel for the driver has a large “Upgrade Firmware” button that does exactly what it says, trouble-free. There are also settings to fix specific tracks to specific sliders (“layouts”), as well as toggle various behaviour of the device. I left all of these on their defaults.

The quick start and user guide for the MC Mix are straightforward, and worth a good read. Five buttons on the left of the device select various modes – what the manual calls knob sets. Used in various combinations, you can access all of the features of a traditional mixing console, as well as settings for plug-ins / channel inserts. By selecting a specific channel in the CHAN mode, parameters for a single channel are spread out across the 8 rotary encoders, and can be paged through separately. This is a particularly nice feature, though there are some implementation problems in the current driver that cause difficulty with DP6 (see below).

One interesting shortcut mentioned in the manual – holding Shift and touching a fader – will reset it to 0.0dB. Looking at the silkscreening on my MC Mix, when zeroing the fader the value is actually about 0.5dB; it would be nice if there was a calibration feature in the driver to align 0.0dB exactly with the silkscreened position. As it stands, I’ll just look at the value on the OLED display or my monitor instead.

In Action – CueMix

Before jumping into Digital Performer, I figured I’d give the surface a spin with CueMix, using the Mackie Control and HUI emulation modes. Often I’m just jamming in my studio, and don’t want the weight (and intimidation!) of a full DAW. CueMix most closely matches the analogue mixer I used to use for just this purpose, letting me set pans and levels via faders and knobs, controlling the rest via MIDI routing. This requires drag-and-dropping the CueMix application onto the Euphonix control panel, selecting the correct emulation mode, and rebooting (!) Once you’ve finished that, you create a new Mackie Control or HUI device in Audio MIDI Setup, connecting the new Euphonix MIDI device to the Mackie Control or HUI device via one in and one out port. Be sure to set the manufacturer and device in Audio MIDI; CueMix uses this to determine the correct emulation mode. (The Euphonix MIDI device sports 4 pairs of in-out MIDI ports, presumably necessary if you link together up to 4 MC Mixes or 3 MC Mixes and 1 MC Control. I just used the first pair of MIDI ports.) Finally, you enable and configure the control surface from the Control Surfaces menu in CueMix. I checked the Application Follows Control Surface setting in the menu, in the hopes that CueMix would scroll horizontally as I paged left and right with the MC Mix. Sadly it doesn’t, even with EuControl set to Auto-bank to selected track and CueMix set to Application Follows Control Surface. (Incidentally, it’s disappointing that CueMix doesn’t get wide enough to shall all of my channels, even though I have the screen real estate. CueMix will show a maximum of 24 channels + 1 master horizontally. Fixing either of these two problems would result in a useful workaround.)

Immediately upon trying the Mackie Control emulation mode, I encountered a problem. The track titles displayed on the MC Mix OLED displays were actually the track title for the first channel, spread out across the first 6-7 OLED displays. Switching to HUI mode correctly assigned track names to each track, but there are still bugs: I can only display the first 3 letters of a track name, plus a single digit. As an example, a track named “CS-80 L” displays as “CS-” only. I also noticed that CueMix’s faders go from -inf to 0dB, while the silk-screening on the MC Mix goes from -inf to +12dB. Not a problem – EuControl maps +12dB (MC Mix) to 0.0.dB (CueMix), giving you the full slider length for use in CueMix. Support still isn’t perfect: the MC Mix shortcut of holding shift and tapping a fader to set it to 0.0dB still uses the (approximate) silkscreen 0.0dB level, which translates to -4.9dB in CueMix. Similarly, the gain for each track displayed on the OLED is with respect to the silkscreening, not the CueMix level (-inf to +12.0 dB). So, with the fader all the way up, the OLED displays +12.0 dB, but CueMix recognizes it as 0.0dB. This is a minor nuisance, but one I’d have not expected, especially in emulation mode. This is further complicated by the fact that live channel levels don’t display on the MC Mix – only in CueMix itself. (Sadly, this limitation still exists in DP6 as well.) The blame here may well lay with MOTU in their HUI control of CueMix; I’ve not used a real HUI with CueMix so I don’t know if it has the same limitations.

Of the other controls, mute and solo work as expected, except for the fact that the MC Mix has an “ON” button instead of a “mute” button. This is a strange choice on the part of Euphonix, but one I can live with – as long as I make the mental shift to expect the button to be lit instead of extinguished. Bank Left and Right, along with Nudge Left and Right, work as expected, shifting channels by 8 or 1 across the surface of the MC Mix. OLED displays and illuminated indicators shift along as expected. Pan works fine – though the rotary encoders are a bit jumpy with fast movements, they’re just fine at slower speeds. Oddly, trim mode won’t stay selected; after a fraction of a second, the rotary controls switch back to pan mode. This is a definite bug. Finally, none of the other knob set buttons have any effect. As a result there’s no way to access input mutes from the MC Mix, nor the CueMix talkback buttons.

This one isn’t documented, but is very helpful: switching CueMix’s console between output buses is accomplished using the Mix button and each fader’s SEL button. In this mode, each channel represents a pair of outputs, with bus muting working via each channel’s On button. Once you’ve switched to the bus you want to work with, use the Input button to return to channel mode. Once I discovered this, it was a snap to mix and assign my 34 inputs across the 14 outputs I have between my MOTU 1224 and 24i interfaces.

In short – despite its many small bugs, HUI mode for CueMix is functional, allowing me access to volume, pan, mute and solo across all available CueMix buses. Hopefully, MOTU will bring native EuControl support to CueMix as well, possibly updating the application to match their newer CueMix FX application for FireWire interfaces. (A girl can dream, can’t she?)

Tomorrow: the MC Mix under Digital Performer 6.01.

microblogging sillyness

Today a friend linked me to this article in the NY Times about networks, the US presidential inauguration, and twitter. Here’s the key quote, emphasis his/mine:

Biz Stone, co-founder of Twitter, said the company was hoping to sidestep network hiccups. He is not expecting the same traffic spikes as during the election, when the site was flooded with as many as 10 messages a second, but says the service “will nevertheless be doubling our through-put capacity before Tuesday.”

Because of all the hype Twitter gets, I couldn’t believe the figure was so low, so I checked elsewhere. “Twitter had by one measure over 3 million accounts and, by another, well over 5 million visitors in September 2008.” Simple math says there’s about 2.5 million seconds in a month, so 5 million impressions translates to one request every half a second. Presuming each query pulls a few pictures as well as text, 10 messages a second sounds about right based on published data. Let’s further assume each message is the size of an average Twitter page; mine came in at 34,100 bytes just now, or 341,000 bytes a second.

Bandwidth wise, that’s 2.728 Mbit/s, or roughly the bandwidth of 2 T1s. My home DSL line can push 700 kbit/s. With 5-6 of them bonded together, and the appropriate back end servers, I could run Twitter out of my basement.

It also isn’t very much, if you compare it with other semi-synchronous messaging technologies like IRC, Jabber and IM servers, who have been capable of pushing more data per second since well over 15 years ago. I’m sure mainframes were doing similar amounts of data I/O 30 years ago.

The snarky nerd in me wants to smear Ruby on Rails, the technology platform on which Twitter relies, but others did that 2 years ago already (and yes, that link defends the technology, and makes the ridiculous assumption that you can’t build in scalability.) I’m convinced it’s the incorrect application of a specific technology to solve a problem for which it is ill-suited. Perhaps the Twitter infrastructure never planned to expand so greatly, but I find it laughable that we’re in 2009 and that “important” services like Twitter can’t survive a “flood” of 10 messages a second. My friend agrees: “no i’m sure facebook is laughing at the 10 messages/a second ‘flood’ too.”

I’m also quite surprised that such a “popular” site, one that gets so much hype and marketing, really doesn’t get that much use. For comparison, here’s the figures for the Top 10 sites. Being generous and assuming those 5 million hits for Twitter are all unique visitors, that means the largest sites see more than 25 times the traffic it does. Facebook sees at least 10 times the number of unique visitors, and certainly will push more content, what with all the pictures and rich media it has vs. twitter’s limited use of graphics (small avatars only). Of course, none of this even gets into what AWS/S3 and content accelerators push from a pure bandwidth standpoint.

Increasingly, I’m convinced microblogging sites are hiveminds for particular flavours of individual. Disingenuously: StumbleUpon/Digg are “OMG LOOK AT THIS LINK!” Twitter feels like “marketing marketing SEO yadda yadda bend to my will.” Plurk is “cheerleader YAY happy happy dancing banana.” BrightKite is “mommy! mommy! look at me now!” And yes, IRC is probably the Wild Wild West. Others I know have made similar comparisons between LiveJournal, mySpace, Facebook and Friendster. I’m not sure what predestines a technology for a specific sort of person, but the link is there. This might make a good research paper. ;)

camera dead

You might have noticed that my last few posts have been image-less. This isn’t because I’m protesting visual communication. I love it – in fact, I’m downright jealous of what most other bloggers pull off with the visual design of their sites!

My camera died. Yeah, the “new old” Olympus C-5050 I bought broke. I only have myself to blame. The camera was on my kitchen counter. I reached for it, but scooted it off the counter, dashing it on the floor. The damage could have been worse – only the mode dial came off. I can’t just reattach it using the screw hack someone posted, because the impact on the floor cut through traces on the flexible PCB. And they’re too fine to bridge easily. Besides, disassembling to the point where I could even consider repairing that damage ended up cracking a couple of very delicate plastic tabs, ones designed to hold the whole thing together. I could try and glue all of it together, but…

Someone on eBay has the entire mode dial assembly for $39, plus $8 for shipping to Canada. Soon I’ll have a working camera again, and by then the studio should be warmer, so lots more pictures and music for everyone.

Oh, and I’ll have my first actual honest to goodness conference submission done by then too (deadline: Dec. 18th). It’s been a long time coming but it’s good to have actual research data and prepare it for publication again. YES!

howto fix mackie onyx firewire under osx 10.5.5

After upgrading Waynemanor Studio’s Intel-based Mac to OSX 10.5 (10.5.5), I was unable to get the Mackie Onyx 1640 FireWire interface to stream audio successfully to/from the Mac. When playing audio from the Mac to the Onyx (just from the System Preferences Sound panel, selecting the Onyx FireWire 0838 output for system sounds and clicking the Purr sound – no DAW software), I’d get the spinning beachball for ~10s, then stuttering, clicking, popping sound would come out. Actually running my DAW made things worse; the application would hang, and Force Quit didn’t help. (Power cycling the Onyx allowed the Force Quit to work.)

Mackie lists this audio driver rollback (PDF) on their website, but the first try at it didn’t work. Here’s how I managed to finally get everything working correctly under Apple OSX 10.5.5:

  1. Sign up for an Apple Developer Connection account. It’s free, and required to download the software you need.
  2. Download both the FireWire SDK 26 for Mac OSX and the FireWire SDK 24 for Mac OSX.
  3. Mount both image files and install the package files from both (FireWireSDK26.pkg and the confusingly-named FireWireSDK23.pkg). This will create directories under /Developer on your system drive.
  4. From /Developer/FireWireSDK26/FireWireComponents, install the Leopard Final drivers. Reboot.
  5. From /Developer/FireWireSDK26/FireWireComponents, install the FireWireAudio 2.4 drivers. Reboot.
  6. Select Software > Extensions on the left-hand browser. Look for AppleFWAudio, and make sure it is version 2.4.0.
  7. From /Developer/FireWireSDK24/FireWireComponents, install the FireWireAudio 2.0.1 drivers. Reboot
  8. From the Apple menu, select About this Mac, then click the More Info button to start System Profiler.
  9. Select Software > Extensions on the left-hand browser. Look for AppleFWAudio, and make sure it is version 2.0.1.
  10. Go to the System Preferences > Sound panel and try sound output to the Onyx Firewire 0838. It should sound clear as a bell.

I don’t know why installing the latest SDK FW base drivers and the FireWireAudio 2.4 drivers first was required before the 2.0.1 drivers would correctly fire up, but it was. One warning: do not install the Leopard FireWire (not FireWireAudio) drivers from the 24 SDK. This caused my machine not to boot correctly, and I had to repair it using another machine.

Here’s hoping this helps someone out in the wild. I’d post it to the Mackie forum, but the moderators there have yet to enable my posting rights. :(

plurk

Well, if you’ve visited my website in the last day, you’ll see I’ve added my plurk widget to the sidebar. I’m finding plurk altogether more motivational than twitter. A recent comparison of the two services I think was unfair to plurk, mostly due to overhyped twitter features that aren’t even working correctly half the time.

Even if Twitter solves their reliability concerns, plurk just feels more alive. It’s not a single thread with everyone’s crap mixed in (and hacks like #hashtags). It’s a threaded timeline: part web forum, part IM, and part IRC. And yes, a bit twitter, too. I like the fact that it’s Web 2.0 enough for my friends who won’t get on IRC (still my #1 place for synchronous) and that the web layout is attractive. The “get more points to get more features” thing is a pain, but I’d rather have that than some sort of “pay us $$ to get more features,” I think.

I moved over to plurk when some of my friends followed Leo Laporte over. I’m not a personality cult-er, but I do like keeping tabs on my friends. And I’m finding that plurk’s interface encourages more synchronous collaboration (read: chatting) than twitter ever did. In about 48h on the service I’ve managed 15 “plurks” (microblog entries) and 38 responses; I never hit that level of engagement with twitter.

Once they add some sort of SMS interface (I can’t get their IM interface to work…) it’ll be a sure fire hit, I think.

So you twitter types out there: would you miss me from twitter if i semi-abandoned it?

ms. “maytag” repairman

Tonight I had to repair my own dishwasher. After weeks of dishes coming out dirty, and after reviewing some references, I decided I probably had a bunged up inlet valve. HG Service Engineer for Dishwashers After much disassembly, reassembly, and testing, I discovered:

  • that even modern dishwashers still come with service technician notes behind the kickplate, though they no longer include exploded parts diagrams,
  • that, if a chopstick breaks in half in the washer, it will melt partially, then drop into the chopper assembly, further mangling things,
  • that rocks in the chopper assembly are also bad things, though the built-in plastic guard prevents them from becoming horrible things,
  • that the rubber valve assembly in the tube that feeds the middle and upper spin arms is horribly specified, and easily sticks open,
  • that by turning said valve assembly upside down, you can prevent a large leak (by mating the stuck-open hole with the normal position of the upper drawer – high or low),
  • that increasing numbers of parts inside dishwashers are now plastic, grrrr,
  • that plastic inlet valves are fragile, and moving them even the slighest bit for purposes of service can cause them to start leaking a bit during inrush of fluids (fixed for now with old absorbant facerag on floor),
  • that someone had rearranged most of the hand tools in the basement (shakes fist), and
  • that the built-in diagnostic mode for the dishwasher is fun to use.

I am waiting for the Good News that should come when the dishwasher ends its normal cycle in about 90 minutes, I open the door, and the dishes and utensils are actually clean.

joanbits 2008.03

As the snow finally melts away, I start to get busier and busier. Here’s what I’ve been up to the past week:

  • Work: supporting new projects as usual, writing position papers, working on newsletters, technical enablement, beta testing.
  • House: cooking every night (pasta from scratch, ramen from scratch, gourmet hamburgers…will try and post some pics soon), planning garden, staring at wall that needs repairing and trying to motivate to fix it, regular cleaning, indoor gardening…
  • School: Developing axiology, epistemology, methodology for design research approach. Gave guest lecture on internal Wikipedia politics.
  • Other: Dealing with horrendous migraine. Developing novel database application. Attended One Of A Kind show with friends and got fabulous clothing, jewelry, housewares. Reverse engineering synth. Looking at motorcycle today. Petting cat to deal with stress from everything else i listed.

thing-a-day 2008 over

Here’s a photo collage of the most photogenic things I made for this year’s thing-a-day. Edit: If you can’t view the video below, the original is here.

I’d recommend thing-a-day to anyone who is looking to push their comfort zone and prove to themselves that they can be creative, and can produce something a day. It was eye-opening for me.

steampunk workspace

There’s been a lot of blog linkage recently to steampunk computing modifications – steampunk keyboard one-offs, commercial keyboard offerings, laptops, R2-D2s, etc. I love the aesthetic, but I don’t really have the time (or cash) to fully modify my computing setup. Instead, when it came time to soundproof my 2nd story home office, and I had to remount my Ergotron laptop/monitor/keyboard arms, I decided to add some “steampunk” appointments.

Behold the steampunk Ergotron pole mounts:

More pre-construction, fabrication and glamour shots are available. Details after the jump.
Continue reading