Showing posts with label electronics. Show all posts
Showing posts with label electronics. Show all posts

Thursday, July 29, 2010

The Expanded Barracks Home Studio

Ladies and gentlemen, it's the newly-updated and fully-equipped Barracks Home Studio.

I've splurged a bit during the last few weeks. Errrr, actually, I've splurged quite a lot. My desire to raise my setup to the next level -- a level capable of semi-pro mastering -- has opened the floodgates in a terrifying way: when you find out how little you know, you also find out how much more you NEED.

Replace "Need" with "Want," if you like.

But my mixing and mastering quest will be detailed in another post. For now, this is where my studio stands today. And like an egocentric goof I'm going to tell you what's inside, in order of when it was acquired (more or less).
  • Akai S700 Sampler: The first instrument I bought that I still actually use, though its disk drive died several years ago. I picked this up mid-90s from Sherwood Music so I could hold my own within Mindsculpture, a band I was in at the time. It's incredibly easy to use, has a large sample capacity, and sounds pretty damn good...but the single mono out reduces its usefulness unless you're manually playing the thing.
  • Tascam Portastudio 424 Cassette 4-track: My second 4-track, after the first one suffered a tragic head loss. Most of my old pre-DAW music was recorded on this thing. Effect sends and returns, variable speed control, 2-band EQ, and extremely smooth operation. For a while I used it as a mixer and a pre-amp, but it's so noisy that it's almost useless. Now I just use it to get at my old master tapes.
  • DOD Digital Delay System R-910: I don't remember where I got this, which makes the following fact even stranger: it has almost no online presence whatsoever. No pictures. No manuals. No description. That's strange because it's so much fun! You can change your effects (flange, chorus, double, and echo) on the fly, apply a repeat hold, change all your settings smoothly...it's a real-time dub monster! Strictly monophonic, however, and it sounds a bit sharp. Here's a picture:

  • Ensoniq ESQ-1 Keyboard: About five years ago my neighbours had a garage sale, and this was the little gem they were selling FOR TEN DOLLARS. They were unable to get any sound out of it so they assumed it was broken (they were plugging a stereo headphone jack into the right mono port, no doubt), and I gleefully gave them twenty for it because I hated to see them get ripped off. Well, the battery immediately died (which is a huge deal for these keyboards), which also erased all the presets. I splurged on a Syntaur soundset cartridge and was back in business. It sounds weird and complicated in all the right ways, but I have yet to really devote the time to explore it. Downsides: you can't smoothly edit sounds while you play them, and there is no MIDI thru.
  • iMac Aluminum Desktop Computer: Now we're entering the modern era. Wonderful computer power. I'm running Logic Pro.
  • Korg NanoPad, NanoKontrol, and NanoKey Controllers: They certainly have their uses, but I get frustrated having to FIGHT them so often. Whether it's flaky detection thanks to their custom USB drivers, or an inability for their Kontrol Editor to update the devices occasionally, or keys getting stuck on they keyboard...well, you DO get what you pay for, and I certainly still use them. Here's my recent assessment.
  • Lexicon MX300 Effects Processor: I use this mainly for lush stereo reverb applied selectively to the mix, not to alter individual tracks...but now I can be more flexible because of...
  • ...the Presonus Firestudio Project 10x10 Firewire Interface: I've upgraded from the old 4x6 Firebox, for the simple reason that I was craving more effect send/receive capability. It's working perfectly and was an easy transition from the Firebox. Its editing software is SO simple, and it doesn't run NEARLY as hot as the Firebox (though maybe that's because it has a bigger surface area). Anyway, this is the lynchpin of the new studio setup.
  • Vox ToneLab LE pedal/effects/amp modeler: I bought this from my father and am only now really exploring it. I've had some bad impressions so far with a consistently harsh digital distortion, but that may be because of my source material, my amp settings, or my volume setup (probably all three). The expression pedal is beautiful just on its own for adding dynamics to a synth pad.
  • Beyerdynamic DT 990 Pro Headphones: These started me on this upgrade project, because they revealed to me everything that was deficient about my equipment and my technique. Some things you don't WANT to hear, unless you have the means to fix them! Now I do.
  • iZotrope Ozone 4 Mastering Plugin: Do you want to know how much better and more professional your music can sound? Just try the demo. I can vouch that it operates just as sweetly as you can imagine. Even if you aren't trying the product, you should read their "Mastering with Ozone" guide, which is FULL of tips, information, and explanations for the neophyte mastering student.
  • KRK Rokit 5 G2 Close-Field Studio Speakers: I bought these today to finally bring my studio to a functional state. They're small (and I need to elevate them about two feet somehow) but they give an even tone that's far beyond anything I've ever owned before.
How does all this fit together? Basically I use Logic Pro as the central hub, with the Firestudio Project as a router for all my effects, external equipment, and monitoring options. It's a beastly patchwork of equipment but it all fits together now, and my hope is that I can finally CRAFT some music instead of simply hacking away at it.

Several projects are on the go, including a few collaborations that are far outside my comfort zone. More on that soon!

Wednesday, July 14, 2010

Talkie Technology in 1930

By September 27, 1930 the talkies had hit their stride. The technology had advanced to a point where procedures for recording sound were standardized and efficient, but as the wonderful Morris Markey tells us in his New Yorker article entitled "Hit the Switch!", things were still uncertain in the studios.

Markey takes a trip to Stage B "in the Paramount studio at Astoria" to see the filming of a new movie (possibly "Follow the Leader") starring comedian Ed Wynn. He discovers that studios are no longer sound-proofed and cloistered the way they were in the early days of the talkies, but some new equipment has certainly arrived.
There were four cameras. Three of them were the familiar movie cameras, a little bulky with their sound-insulation but recognizable. The fourth was the sound camera. Instead of a lens, it was fitted with a microphone at the end of a very long, very thin telescopic arm. The arm thrust out from the camera like the tentacle of an insect, and the microphone at its end was poised immediately over the spot where the action was to take place--high enough to be invisible to the lenses of the other cameras. As the actors moved about, the arm could be extended or shortened, raised or lowered in an instant so that the sound-collecting microphone always hovered over them.

The sound camera does not carry its own film. It merely carries certain electrical equipment which transmits the sound from the microphone to a telephone wire. The telephone wire carries the speech of the players to the central sound-recording room in the basement.
It's interesting that Markey doesn't know the names for any of this equipment, and so relates to it as though it were simply refurbished from the silent film days. The "boom microphone" is a "sound camera," even though it has nothing whatsoever in common with the other cameras. The cable which carries the sound is a "telephone wire."

He goes on to describe the somewhat magical goings-on inside the basement room where another camera stares at "infinitesimal reeds" which vibrate to the transmitted sound impulses. The light which shines between these vibrating reeds creates the visible sound wave which is recorded onto film for later playback. Was this REALLY how it was done?

He also mentions the "control booth," a little "soundproof room on wheels." Inside sits a man who monitors the recorded sound and controls the volume. This man -- credited as a "sound recordist" and possibly Ernest Zatorsky -- actually stops the entire shoot by walking out and protesting:
"There's a hum," he said, glancing vaguely toward the ceiling and the arc-lamps.

"What kind of hum?" asked the director.

"Something technical," said the young man. "It's an induced hum. I told 'em they'd have to fix it. This stuff sounds lousy."
The director, unable to solve or even understand the problem, walks helplessly off the set. "Like lost sheep, the actors and the helpers drifted out after him and the young man of the booth, nodding with satisfaction, picked up his hat and went home."

Sunday, September 13, 2009

Korg Nanos and Logic Studio

UPDATE: After you read this, check out my "two months later" review.

I'm saving money, right? I've got a mortgage and new furniture and a brand-new bed, and God only knows how much money I'll be taking home from work once all those expenses kick in. So I've been counting my pennies and going out less and eating cheaper food...

...and then I bought these.


They comprise the "Korg Nano Series," three very cheap and powerful MIDI controllers that you can hook up to your music software and do amazing things with.

It should be obvious what the "NanoKEY" is for: it's a two-octave, velocity-sensitive, polyphonic keyboard that's perfect for tapping out melodies. My "workhorse" keyboard is an enormous and heavy Ensoniq ESQ-1, and it's sheer overkill when I just want to tinker. But I can plunk the NanoKEY down on my lap and use it without any setup or bother. It just works.

Likewise the "NanoPAD," which is ostensibly for drum programming but can also be used to make wonderfully freaky noises. It has a touchpad which you can squish your finger around on, bending and modulating notes with total abandon.

Most important, however, is the "NanoKONTROL," which comes with nine faders and knobs and eighteen buttons. You can decide for yourself what you want these controls to do; since the NanoKONTROL has four different "scenes" that you can switch between, I've programmed the fourth scene as an eighteen channel mixer (I'll explain how I did that in a second), the third scene to accomplish common editing tasks (changing the zoom level, switching tools), and the second scene for controlling EQ parameters. The first scene is for whatever tweaky thing I want to do at the moment...changing the cutoff and resonance of a synth, for instance.

The NanoKONTROL also has six buttons for controlling the transport...it's nice to be able to play, record, stop, and move the playhead without ever touching the mouse or keyboard.

The three devices are lightweight and tiny, and can all be run off an unpowered USB hub. And you damn well better use a hub, for reasons I'll cover in a second.

Bad Things About the Nanos

You get what you pay for. The keyboard is certainly not for performance...it's good enough for recording, but it occasionally drops notes.

As for the controller, the faders are short, none of it is motorized, and it receives no feedback from your editing software, so it is rarely in sync with what you're doing; if you tweak something in your software and then try to tweak it with the controller, the position of the controller and the value in your software will not match. This isn't crippling, but it does lead to twitchiness.

Also, since it has no assignable labels on it, it's very easy to forget how each control is assigned. And you can't get a nice shuttle/jog setup because none of the knobs are continuous; they all have a beginning and end.

But when you spend $80 for a controller you don't expect those kinds of features. These units are for hobbyists and for quick-and-dirty experiments; they aren't professional gear. Sigh.

Bad Things About Logic Pro

The real problems come when you try to integrate the NanoKONTROL with Logic Pro. In some ways it makes sense that the procedure is difficult: both Logic and the controllers are so freely configurable that it's impossible to offer a single solution. You, the user, must make decisions about how you want to use the controller...and then you must teach the hardware and the software to speak to each other.

Configuring the Nanos themselves is super-easy: you download the Korg Kontrol Editor and use it to tell the nanos how they should behave. Which MIDI channel will they use? Which notes and/or control codes should they send for each pad, fader, button, and knob? Should the buttons act as toggles -- sending a different code for each press -- or should they be "momentary," sending one code when depressed and a second when released?

Korg also tells you that, if you want to use more than one Nano at a time, you need to install their USB MIDI driver. I don't know if this is really necessary or not...I did it as a last resort when things seemed to be going haywire (see below).

Your nightmare only begins when you need to tell Logic how to use the NanoKontrol. You need to use Logic's "Controller Assignments" dialog, which you can access by pressing Command-K. Remember that shortcut...you'll use it a lot.

The Controller Assignments dialog is the dark smelly butthole of Logic Pro. It's ancient and unfriendly and buggy. It can just as easily make your dreams come true as it can totally destroy hours of hard work.

If you are faced with the task of configuring your NanoKontrol within Logic, my first advice is to READ THE LOGIC PRO CONTROL SURFACES SUPPORT MANUAL, but when it tells you in chapter one that you must "add" the device to Logic Pro, DON'T BELIEVE THEM. Logic cannot detect the NanoKontrol so it can't be "added" in the usual way. Skip chapter one entirely. Chapter two -- "Customizing Controller Assignments" -- is the one you need to read.

My next piece of advice is to NEVER USE THE EASY VIEW. It's confusing and gives you no idea of what you're actually doing. Skip right to the Expert View and do everything in there...

Key Commands

...unless you're assigning Key Commands, which is best done in the Key Commands dialog (Option-K). If you want to assign a button on your NanoKontrol to a keyboard shortcut in Logic -- and there are hundreds of them -- then use the Key Commands dialog...just select the command you want to execute, click the "Learn New Assignment" button, and press a button on your NanoKontrol. Presto!

This is great for the transport buttons (Play, Stop...) and for things like "Page Forward" and "Switch to Scissors Tool." It is NOT, however, useful for the knobs and faders, or for special controls inside plugins. For those you need the Controller Assignments dialog.

Additional Key Command tips: use the Search field to find the controls you're looking for, and NEVER try to resize the columns; you'll end up with the first column becoming half its width, therefore obscuring most of the commands, and you will not be able to fix it. You'll need to hover your mouse over the commands to receive tooltips, which don't always appear. Grrrrrr!

Controller Assignments

Now for the hard part: the infinitely configurable faders and knobs and plug-in stuff.

Logic Pro remembers the last thing you touched within the interface. If you open a plug-in -- like the EFM1 synth, for instance -- and then click on a control -- such as the FM knob -- then Logic will remember that you touched it.

If -- immediately after touching it -- you go to the Controller Assignments window and click the "Learn Mode" button, the following things will happen:
  • A new control called "Learned" appears in the Control list.
  • The "Learn Mode" button becomes shaded, indicating that Logic is ready to associate the last thing you touched (the FM knob) with the next MIDI message it receives.
So when you twist a knob on the NanoKontrol (or move a fader or press a button), the NanoKontrol sends the MIDI message associated with that knob/fader/button (which you can set in the Korg Kontrol Editor), and Logic assigns the control to the MIDI message. Presto! The Control list will show something like "Learned - EFM1: Carrier FM Intensity," and when that list object is selected you will see information about the "class" of the control (see the Control Services Support Manual), the device which sends the MIDI message ("nanoKONTROL SLIDER/KNOB"), and nifty options for setting the value (see the manual again).

Here's the awful shit you must now remember to do:
  1. If you are finished assigning controls, CLICK THE LEARN MODE BUTTON TO EXIT LEARN MODE. If you don't do this you will screw everything up. As long as that button is shaded, Logic is hijacking everything in order to link controls with MIDI messages. Do not touch anything else in the interface or twiddle ANYTHING on the NanoKontrol before exiting Learn Mode.
  2. If you want to assign another control, however, then click something else in the interface (like the EFM1's "Harmonic" knob), then twist another knob on the NanoKontrol -- resulting in a new control assignment -- and keep doing this until you've assigned everything. But remember to click the Learn Mode button when you're done! Otherwise you will reassign controls, or assign multiple knobs to the same thing, and untangling that mess can be hell on earth.
  3. Kick whoever designed the Controller Assignment window squarely in the ass. "Learn Mode" button which acts as a toggle? This is NOT part of Apple's design specifications, I'm sure.
Once Learn Mode is off, twiddle your assigned knob. It'll work! You can now tap the keys on your NanoKey and use the knob to change the FM Intensity of the notes. Brilliant! That's why you bought this thing!

If you're using the NanoKontrol to change the automation on a track -- say, to change the FM Intensity for MIDI notes recorded on one of your tracks -- you need to switch the track to either "Latch" or "Touch" mode (read the regular Logic Manual), then hit "Play" (not "Record") and twist the knob as the notes play. The changes are recorded to the track as automation values, which you can go back and edit.

If you want to use the NanoKontrol as a mixing desk, you want to assign your controls to the "Fader Bank" channel strip within the "Channel Strip" class, then set which Fader Bank track you want to assign the control to. This is BEST done in the Mixer window, because when you use "Learn Mode" after touching a channel strip control in the Mixer window, the Controller Assignment window automatically uses the proper Fader Bank and track number. Otherwise, if you do this in the Arrange window, the control will be assigned to just the "selected track."

Remember when I mentioned that I'd assigned the nine sets of controls in Scene Four to be an eighteen-channel mixer? That's because I set one of the buttons to perform a "Mode Change," to toggle between two sets of controller assignments: one for tracks 1 to 9, the other for tracks 10 to 18. By changing modes you can infinitely extend your number of assignments, but this requires planning (because you have to add all your assignments to new Zones and Modes within the Controller Assignment window).

Fortunately, if you fiddle with something on your NanoKontrol, its assignment is highlighted within the Controller Assignments window, which can help you fix mistakes like multiple assignments. But that's the only user-friendly thing about the window: you cannot sort or group your assignments in the list -- they appear underneath whatever you have selected at the time -- and you can't make changes to the parameters of multiple assignments at once, and you can't drag assignments between zones and modes.

As if that didn't suck enough...

Logic Studio Can Forget Your Assignments

Until you realize this -- and why it happens -- you will be SCREAMING IN ANGUISH.

There is a terrible bug in Logic Studio. Each time you add or remove a MIDI Input device to your computer, Logic Studio's list of MIDI devices changes. And it seems that your controller assignments -- those hundreds of knob-and-fader connections you've so painstakingly created -- are not mapped to specific MIDI devices, they are rather mapped to the number of the MIDI device within Logic Studio's list. And if the ordering of the devices in the list changes -- because you've added or removed a MIDI device, simply by unplugging its USB or Firewire cable -- it is highly likely that all of your controller assignments will map to the wrong MIDI device.

So attach all your USB MIDI devices to a single hub, keep them always plugged in (at least when using Logic), and don't swap them around. If you do, you will find that your assignments no longer work. You can manually select each assignment in the window and reset its MIDI Input device (the manual claims that doing this for one device will reset all assignments which use a similar device, but I don't think I believe them), or you can try plugging everything back in and hoping that the list sorts itself back in the original order, but whatever you do DON'T BLAME YOUR NANO. It is Logic's fault.

Tip: Sometimes, when you twist a knob or push a fader that you haven't used in a long time, you will find that it doesn't immediately work; this is probably because it isn't "in sync" with the object it's controlling. Try moving the control all the way in one direction, then all the way back to the other direction, and I bet it will work again. Otherwise open the Korg Kontrol Editor and make sure the Nano is connected. If that doesn't work, open the Controller Assignments window and see what sort of evil crap that Logic Studio has done to the assignment.

I think that covers it. I'm very happy with my Nanos, and more than a little cross with Logic. Fixing the Controller Assignments window should be a top priority for them, and this is a bug they've known about for years...do something, people!

PS: All of your assignments are stored in a file called com.apple.logic.pro.cs. Every time I make a change to my assignments I make a backup of that file (it's in your user's Library/Preferences folder).

PPS: My NanoPad came with the wrong USB cable...a full-size one instead of the required mini. This is strange.

Saturday, June 28, 2008

In Praise of Elton John's Drummer

If you grew up listening to radio pop-rock during the '70s, you may be aware of a distinctive drum sound that has never reappeared.

I don't know exactly how to describe the sound. The simple explanation might be that the kick drum and snare drums are gated, have their volume boosted across all frequencies, and then are sent through an effects processor which adds a short plate reverb. Michael B. Tretow -- who produced some early ABBA singles which used this technique -- described it as sounding like a turkey being thrown against the wall.

Yes it does, a bit.

You'd hear this drum sound on any highly-produced pop-rock song which wasn't yet experimenting with disco: ABBA, Electric Light Orchestra, Supertramp, Harry Nilsson...and the "classic" Elton John line-up.

During my "breakfast walk" this morning I choose -- at random -- to listen to Elton John's "Goodbye Yellow Brick Road" double LP. Besides being perfect in almost every way -- the exception being "Jamaican Jerk-Off," which makes me scream every time -- this "thumpy drum" sound appears in most of the songs...you can hear it in "Benny and the Jets" and "I've Seen That Movie Too," though it would be used at its most extreme in "Better Off Dead" on his subsequent "Captain Fantastic Album."

While luxuriating in this distinctive sound I found myself paying attention to the elaborate rhythms of Elton John's band at the time. Considering that the songs were nominally based around piano, there's a surprising amount of rhythmic interplay between ALL the instruments, with Nigel Olsson's drums being particularly tricky. Again, I don't know which "drumming terms" to use, but I suppose the right word is "fills." Olsson's fills are perfect. He'd never hit a drum unless it accented the rhythm that the other instruments were playing at the time.

So here's to a drum sound that I haven't heard again since...

...though now that I think about it, you can hear a similar effect in "The W.A.N.D." by Flaming Lips, which must be one of the greatest songs ever, and is always an intricate thrill to dance to:



Given what I understand to be a Flaming Lips tendency to pay "homage" to their '70s influences, I suppose this make sense.

Thursday, May 29, 2008

A Very Stinky Lunchour

The last time I quoted a conversation between two prototypical "Stinkies," the transcription was referred to as "a weird sort of poetry." I couldn't have agreed more.

Now I'm happy to present you with an extended transcript of BOTH SIDES of a stinky conversation, including a bonus "Muffy vs. Stinky" moment at the end.

During lunch today at Tim Horton's, the stinkies sat down at the table next to me as I was trying to write on my portable "Alphasmart Neo." The male stinky (Robert) wears suspenders and looks a bit like a turtle. The female's plumage is brighter -- pink shoes and fuzzy baby-blue pantsuit -- but her mental abilities appear far below Robert's...she repeats herself endlessly and always seems to be annoying him.

Their conversation here starts with the two of them sitting down, then the female stinky lurching to her feet and asking:

You want a donut?

No, I don't want a tea donut, ohhh.

One honey dip. You want it?

Nooo.

She buys a box of timbits and puts it on the table, then stands.

You be here for a while? I'm goin' home now.

You don't need that coat.

I'm cold, my back's cold.

Ohhhh.

I don't wanna get cold on my back. I'm goin' home now. You want your coat?

NO I don't want my coat.

Goin' home now. Goin' home now.

She leaves the store. Robert, alone, sits quietly for a while, then he starts leaning toward me and saying "Ma'am? Ma'am? Ma'am?" I ignore him because I know that if I make any sort of response, he'll start talking and he won't leave me alone.

Fortunately he is interrupted by the store's mentally handicapped employee. This is amusing because the employee really likes Robert, but Robert obviously DOES NOT return the sentiment. The employee keeps telling Robert not to eat donuts because they're bad for his health and will give him a belly. The employee won't go away. He thinks Robert is his best friend.

I become aware that even the stinkies have a pecking order and I feel less bad for ignoring him.

Eventually the woman comes back. She talks with Robert for a bit, and soon I start transcribing again.

It won't last that long. Won't last that long. Got a honey dip, another honey cruller, one honey dip. Got that one. He doesn't like that, you know that? Doesn't like honey cruller. He won't eat that cruller.

How do YOU know what he ain't gonna have?

One boston cream that he'll eat tonight. One boston cream that he'll eat tonight. I tole you.

(A moment of blissful silence).

They makin' honey crullers. You think they makin' honey crullers? You think they makin' honey crullers?

HOW DO I KNOW!

Two of them back there. They two of them. You think they makin' honey crullers? You think they makin' honey crullers?

Suddenly Robert leans toward me and starts saying "Ma'am? Ma'am?" again. I ignore him, pretending to be busy. The female stinky asks him what he wants and he says "I wanna know if she gets a SIGNAL on that thing," gesturing at the keyboard. "MA'AM! MA'AM!" The female stinky says "She's busy" and Robert says "I don't care, I'LL GET MY ANSWER. MA'AM! MA'AM! MA'AM!"

He is now literally YELLING at me and the people in the store are looking at us. I glance up at him and he says "Do you get a signal on that thing?" I say "no" and go back to typing.

The female stinky says "That's a guy, not a ma'am." However confused the female stinky seems to be, I suddenly realize that she's the more socially capable one.

Robert is very disgruntled, muttering at an old lady nearby who's been staring at us. The old lady says -- by way of obvious explanation -- "She's busy," and Robert says "He wants to be like that? He wants to be like THAT?" There is some degree of gender confusion going on now. I continue typing as though nothing's happening


Eventually he calms down. I don't dare transcribe any further now that he's got his eyes on me.

Saturday, March 29, 2008

The Week of Beckzy

A month ago I set my father a task: find me a car, daddy-o! This is a point-form summary of the results, covering the last week and perhaps explaining why I haven't been up to blogging.

Saturday: While spending Easter with my parents, my father -- who works at a car dealership -- is sad to report that the perfect car for me -- actually exceeding my minimum requirements as to practicality, price, efficiency, and age -- has slipped through his fingers. Oh well, at least the family gets to come together and eat ham, car or no car.

Monday: My father calls me at work to tell me that the aforementioned car, under miraculous circumstances, is once again available. She's a blue '95 Chevrolet Corsica named Beckzy, in perfect running order, very fuel efficient and small enough for my limited spatial skills to handle. He can bring it by my workplace tomorrow for a test drive.

Tuesday: For the first time in fifteen years I am behind the wheel of a car. I have no insurance and haven't even set my eyes on Beckzy before now. A horrendous rain/sleet storm has arrived with gusting winds, and I re-learn my driving skills by sliding my white-knuckled father around the block. Even this short experience is enough to tell me that I'd be CRAZY to pass up this opportunity. I'll take it!

Wednesday: My father calls to say that Beckzy has passed her E-test and is going in for her safety. Things have taken on a sudden immediacy. Vanilla, conscious that this may be the last time she needs to drive me someplace, takes me to State Farm where I get both auto and renter's insurance at surprisingly low prices. I have a payment plan. If somebody breaks in and steals all my showgirl outfits, I will now be able to afford NEW showgirl outfits.

Thursday: It turns out that I will have to go to New Hamburg in order to get plates and ownership as my father is not allowed to forge my signature. I have 24 hours to brace myself for tomorrow's ordeal.

Friday: My father shows up at my workplace, driving Beckzy. He hands me the keys and we begin what is simultaneously a right of passage, a refresher course, a final legal hurdle, and an impromptu driver's exam. I discover that Beckzy has a ridiculous blind spot: when I turn to my left to check for oncoming traffic I can only see my headrest. We take the Expressway all the way into New Hamburg, allowing me to re-experience city streets, on-ramps, merging, highway driving, and extremely pokey small town navigation.

In New Hamburg I get the ownership, we put the plates on, I sign a ridiculously miniscule check for my dad, and Becky is mine...if I can get her home again.

After the return trip I swear that I'll never drive again: I'll just park the car in my lot and look at her, and maybe sleep in her when it's hot outside. Gradually I come to grips with the situation: I'll simply need to keep ramping up my experience until I'm really comfortable driving.

Saturday: I go to Hakim Optical for an eye test and glasses, only to discover that they don't do such things without an appointment. Since Beckzy has a quaint little tape deck I go looking for one of those audio-adapters which allow you to plug in an iPod, but I have no luck. Now I know why I kept all of those mix-tapes from my University years...driving Beckzy will be a '90s experience in more ways than one!

Friday, January 18, 2008

Lexicon MX300

Today, on a lunch-hour whim, I committed myself to buying a multi-effects processor. The one I settled on was the Lexicon MX300. I could only get sparse information about the other options in the store, but the MX300 seemed to be the most flexible, so I chose it.

It was also the highest priced. As I endured the inevitable Long & McQuade cashier wait (during which the people ahead of me always bather to the salespeople about their exceptional musical virtuosity) I was inches away from chickening out...I don't really NEED an effects processor, and I could put that money towards something more necessary...

So imagine my surprise that, when we rang it in, the unit was actually MARKED DOWN a hundred dollars from the list price. Imagine the surprise of the cashier as well. It was obviously "a sign."

My previous multi-effects processor was an ART which -- I discovered later -- was notorious for flakiness and dull sound. As for the flakiness, yes, after half an hour it would start to show impossible numbers on its display and then would shut down with an eardrum-shattering squeal. That squeal turns up in a lot of the music I recorded with it.

I've only had the Lexicon for a few hours so I can't vouch for its reliability, but I can certainly say this: all reverbs are NOT created equal, and the MX300 sounds absolutely SUBLIME. I didn't know what I was missing until now. It has a complexity of sound to it that I never knew was possible, leagues beyond the ART's relative flatness.

Granted, the ART could chain more than two effects together (depending on the complexity of the effects themselves), but the MX300 effects are so rich that you really don't NEED to use more than two.

I wanted knobs that I could twiddle, and the MX300 has twiddlable knobs. Although they turn with a slight clickiness, changes to all the effects are acceptably smooth (not as smooth as my DOD R-910 but that's a very different beast). The tape delay is super-cool and the ability to set tempo in BPMs is an unexpected godsend. And the Leslie rotor? Holy cow.

You can control the Lexicon with your Mac...as long as you have OSX 10.4.x. Sometimes you can take that stipulation with a grain of salt, but not in this case...it uses the CoreAudioKit.framework. So us OSX 10.3.9 users are out of luck. It will not work. Sigh.

Otherwise, though, it seems to be a fantastic unit and I'm sure we have many happy hours ahead of us.

Thursday, August 02, 2007

More Theremin in 1928

Further into the February 4, 1928 issue of The New Yorker, the talk of Leon Theremin's New York recital continues. After the initial one about pulling music from "the ether," another talks about Rachmaninoff's response to the show (intrigued but not delighted), and finally -- in the weekly "Musical Events" column -- we get a bit more substance:
Radio experts can tell you that Professor Theremin has taken the familiar howl of an unbalanced receiving set and persuaded it to play Schubert's "Ave Maria." The result, which seems to us more important than the mechanics involved in obtaining it, is a tone which varies from something like cello timbre to the vibrations of the musical saw.

The Theremophone is still in a transitory stage, we hear, and it has obvious disadvantages. As the flow of tone is continuous, it is impossible to avoid at least a suggestion of scooping, and there are not yet Teremophonists sufficiently skilled to play rapid or complicated passages... Nevertheless, here is a new musical instrument, which is based on the fundamental principle underlying all instruments and which may, in less time than one might fancy, become part of the orchestra. If this seems romantic, so once upon a time was the notion that the clarinet belonged in good symphonic society.
Romantic, yes. Clara Rockmore did her best to lend credibility to the instrument but it never joined the clarinet in regular orchestras. Theremins did show up in sci-fi film scores, and later in scattered pop songs...though much music retroactively credited to the Theremin was actually performed on the Ondes-Martenot, much to my personal disillusion.

I have seen Theremin and Theremin-ish instruments played; they keep on popping up at Legendary Pink Dots shows in one form or another. It's beautiful to hear and even more beautiful to watch, but does seem to lack diversity and still can't be played at any speed or accuracy (unless, again, you're Clara Rockmore).

Monday, July 30, 2007

The Magical Theremin

The Theremin finally made its way from Russia to America in 1928, and in the February 4, 1928 issue of The New Yorker they make a strange sort of mention of it...though I can't help thinking they were a little confused about what the Theremin actually did.
There is such a wistful flavor in the newest magic--the instrument that draws music from the ether at the wave of a hand. No one (unless it be makers of musical instruments) can fail to find a plaintive delight in this attempt to comb the infinite, to sift the sad vapor that wraps us. At a surprisingly early age we too realized that we were in the presence of a greater beauty than we could ever hope to express, that we were listening to loftier songs than we would ever be able to hurl back at the sky, even in our lustiest piping moments. At this same early age, we were aware that--for some reason or other--we were going to have to make the attempt. What a mad crochet when the Creator filled the airy regions with a sadness no one could ever distill with word, wand, or song--and then turned loose whole handfuls of mortals who knew they had to try!
Unless they're talking about some OTHER instrument, I don't believe that the Theremin, you know, actually distilled music out of the ether. Thought it probably looked like it did.

Tuesday, December 12, 2006

X-Ray Hair Removal

Right now I'm reading "Inventing Modern" by John H. Lienhard. It's a sort of personal, semi-autobiographical overview of the way technological advancements -- steam power, balloon-frame houses, elevators, X-rays, relativity, quantum physics -- brought "modern" into social consciousness in the 20th century.

While tracing the American fixation with everything "modern" during the first half of the century, Lienhard lets drop tidbits about inventions and concepts that flourished but failed, either because they were supplanted by new technologies -- cattle drives, the Pony Express -- or because they turned out to be very, very dangerous.

These stories make me sit up and say "holy cow!" Maybe he didn't intend to write a book of nifty factoids, but I sure am saying "holy cow!" a lot.

Holy Cow...The Tricho!

Apparently everybody was ga-ga about X-rays at the turn of the century, in the same way they would be ga-ga about atomic energy before VJ-Day. These X-rays could SEE THROUGH stuff! A doctor could look at the inside of your body...without opening it up first!

This was a miracle, but people just had no idea how dangerous X-rays were. We sometimes hear about the X-ray machines that children utilized to make sure their shoes fit in shoe stores, but I've never before heard of...THE TRICHO.

We all know that large doses of radiation will make your hair fall out. So why not use it as a method of hair removal? From the '20s to the mid-'40s, women went for multiple sessions at the Tricho machine. They'd sit with their chins up against X-ray emitters and get bombarded with radiation for four minutes at a time.

Their facial hair fell out, of course...but, as one website puts it:
...[it] also eventually resulted in wrinkling, atrophy, white or brown fibrous splotches, keratoses, ulcerations, carcinoma, and death for many clients.
Even after the dangers became known and the government shut down the machines, women continued to go to secret Tricho clinics...it was so effective they didn't seem to care that they'd be disfigured in 3 or 4 years. And what's more, people just loved X-rays because they were so scientific and modern.

That didn't stop them from dying, however. Apprently:
By 1970, one study estimated that over one-third of all radiation-induced cancer in women over a 46-year period could be traced to x-ray hair removal.
What eventually stopped the fad? According to doctors who coined the term "American Hiroshima Maiden Syndrome," women were turned off the Tricho by grotesque images of atom bomb survivors. Suddenly radiation wasn't so harmless anymore. So another science fad bit the dust.

The most comprehensive Tricho page I've found online is at the Museum of Questionable Medical Devices...just in case you want to learn more.