I was working for Bethesda Softworks, the video game company known for Elder Scrolls, Fallout, and Doom, to name a few. It was here that I met Pete Hines, the Senior Vice President of Global Marketing.
I was only 17 when I joined the company, and Pete took me under his wing and became one of many excellent mentors I had over the years. It was so useful to see what the job was about and how he worked – I learnt how a professional organization manages so many projects and people.
Other mentors include Mark Davis, the inventor of the Camelot Wheel. He had already invented it in the early 1990s, but it wasn’t well known yet. With Mixed In Key, we took the Camelot Wheel and combined it with an educational approach. This became the harmonic mixing framework that so many DJs use today.
And you were a DJ long before developing Mixed In Key. Who were your musical influences in the DJ world?
In 1996, a Norwegian DJ called DJ Prince made a website to teach people how to mix harmonically. His and Mark Davis’ websites were the only two resources available at this point. When I started DJing in 2001, their websites had a huge effect on my DJing.
When I invented Mixed In Key, I had about 14 years of software development experience and five years of DJ experience. Combining my two passions with the advice I got from my mentors made it much easier to create a useful product. And of course, a huge thanks to my dad, who was a wonderful software developer and gave me lots of time and advice.
Which zplane SDK did you license to build early versions of the product?
zplane played a huge role in Mixed In Key's history and the world of DJs in general. In 2005, there was no key detection software in existence. Even though I wanted to automate key detection for my Mixed In Key product, there was absolutely no way that I could build a key detector on my own. There were no published books, no scientific papers, and no open-source code that could do it, and certainly no LLMs like ChatGPT that could help.
zplane had a tiny Windows demo on their website that could analyze one file at a time. I thought the tech was cool so I emailed to ask if I could license it. I was the first person ever to contact them about licensing. We made a deal, and zplane became the foundation of the first version of Mixed In Key 1.0. It wasn’t long before I started improving the code and submitting feature requests.
Version 2.0 of Mixed In Key then used its own key detection, but without zplane’s initial trust in me, Mixed In Key wouldn’t exist. The technology enabled me to build a prototype that performed way better than I expected.
How easy was the SDK to implement?
It required some C++ knowledge, which wasn’t my strongest skill. I went on a website called Rent-A-Coder and posted a job listing. Two guys responded, saying that they would be interested in helping out as a side project.
This became an amazing working relationship, and almost 20 years later, both of those guys are still on my team and are responsible for some excellent software code. That code features in a series of great products that musicians love to use.
What kind of challenges did you face in the initial phases of product development?