I just released my SD1 simulation, and now it is time to explain why is inside this plugin. Not everything in the original pedal was simulated, and different schemes were used to tackle the different stages.
It’s time for a new release of the toolkit. Much has been done in terms of basic filters, but also to simplify usage (static and shared libraries are compiled, no need to reset the pipeline before calling process…).
How to explain the different kind of audio effects and how to understand what their use is? Although I learnt a lot by practice, there is sometimes the need for some theory and for experiments. I tried to find a book that matches these two points: good theory and proper practice. I’ve chosen this book, with tracks on a CD for experimentation. Was it really what I was looking for?
I think I’ve said it already, I have a rock band. Currently, we are recording our first album, and while we used Traktion in the past, I’m considering moving to Sonar (it is continuously updated and has a great reputation, also I’ve played a few time in the past with its ancestor Cakewalk).
So let’s talk about the book’s comprehensive guide.
After Music Theory for Computer Musicians, Composition for Computer Musicians, here is Harmony for Computer Musicians. Michael Hewitt builds on some topics from the preceding books to dig in the complexity of harmony.
Continue reading Book review: Harmony for Computer Musicians
Two weeks ago, I’ve reviewed Michael Hewitt’s second book, Composition for Computer Musicians. I’ve decided to go for Hewitt’s first book, dedicated to the explanations of music theory.
Continue reading Book review: Music Theory for Computer Musicians
My biggest hobby remains music. As a former trumpet player, current drummer and bass player, I spent a lot of time studying solfege, and a little bit of composition. Besides this, I’ve mixed an album for one of my former bands, mastered some tracks for others (and my current one), so I’m also a computer musician. This is why this book from Michael Hewitt was of high interest to me.
Continue reading Book review: Composition for Computer Musicians
Some months ago, I’ve modified the AGain plugin sample from the VST SDK to add a Qt window. At that time, I encountered an issue with Vsthost, which is a common VST host. The issue was that in windowed mode, the plugin’s UI wasn’t displayed. With Traktion, I didn’t have this problem, but the minihost (a sample from the SDK) also didn’t use the UI size.
When developing pyvst, I has to implement the retrieval of the size of the plugin, and I’ve decided to add this to QtAGain. I was surprised to see that it actually work with just giving back the UI size (so fixing this was less than 5 lines).
So now, I know that to impelment an UI for a VST plugin, I have to implement:
- but also getRect()
Don’t make the same mistake as I did, do implement all three of them, even if your favorite VST host can live without getRect().
P.S.: Mixing Qt for VST UIs and wxPython for pyvst works really fine!