If you’ve been paying attention to Noise Engineering blog for a while, you may be familiar with Rheyne. Also known as his alter ego, Jon Barbieri, he did a great guest post about a year ago and has been posting amazing stuff all over Facebook and Youtube and, well, all the places for a while. We were chatting recently and we batted around the idea for a follow-up post.
We talk to a lot of modular users. People interested in modular are trying to find that first case. People who have been doing modular for a while are always on the lookout for another case for their ever-expanding collection of modules.
We considered tackling this question but realized that our friend Shawn is a far better go-to for all things cases. Shawn has an impressive array of cases, but most are done on a budget, as you will see. These are the ones we were particularly interested in (and that draw the most questions everytime we stand close to him at a gig).
We asked Shawn to talk a little about his custom cases, the quest that brought him to them, and how he puts a case together. He’ll take it from here.
One of the most common queries we get here at Noise Eng regards how we create modules. Today on the blog, we’ll talk a bit about that process, and how things tend to happen here at NE.
Our first journey into software products came about because of a Twitter conversation of all things. Mattias Haagstrom is one of our many fans who reach out to us to discuss our products. He also happens to be the Product Director for Reason. He suggested that our products would be a good fit for the Reason Extension marketplace. At this point we weren’t even aware that Reason supported extensions -- Stephen had been an avid Reason user from their initial beta only until version six, and Kris had never really used it. It didn’t take us long to see the advantages inherent in their system as we are a tiny company without even a single full time programmer. The reduced barrier to entry provided by Propellerhead was a huge win for getting back into the box :)