1. When did you start dabbling in music?
Throughout the years, I've studied different instruments including piano, sax, and classical guitar. I can't say that I've excelled at any of these since I was never disciplined enough to practice. I did enjoy studying music theory, and I've been interested in electronics since I was quite young. I was always taking things apart - telephones, radios, televisions, and sometimes I manage to reassemble them without ending up with spare parts. When I was two-years-old, I had this record player and I wanted to find out where the sound was coming from, so I took it apart. It was still plugged-in, and I learned about high voltage electricity - the hard way. Eventually the two interests met when I was given my first little electronic keyboard, a Casio VL-1.
2. What training have you had?
Other than a few classes on synthesizer programming at Columbia University, I have no formal training in music or recording. I'm primarily self-taught in production and recording. While in University in 1990, I recorded an album. It was MIDI synth based and I recorded it straight to DAT. I had a Roland D-50 as a controller and a rack consisting of an Akai Sampler, Korg M-1, MKS-80 Super Jupiter and a Proteus module - all being driven by the old Voyetra DOS based sequencer.
3. When did you get into recording?
I had a small project studio back in the mid 90s where we used ADATs and a Neotek console with a lot of outboard analog gear. My first real DAW was the Akai 4 track recorder. I learned early on the importance of a good front end for digital and since then, I have tried to keep my workstation up to date with good converters.
4. People you have worked with/for?
My commitments to Propellerhead Software keep me pretty busy. Between the various sound design projects and Producers Conferences , I have so little time to commit to other productions.
5. Why are you so good at training people?
I'm pretty good at deconstructing and reverse engineering processes which makes it possible for me to demonstrate how things are accomplished with music hardware and software. I love to learn about new things and I'm constantly exploring and experimenting on innovative uses of Reason.
I'm also take a lot of time to think about pedagogical approaches and try to find the best balance of information that will satisfy the curiosity of experienced Reason users while keeping the language and explanations simple enough for a neophyte.