I've been a Linux user for a while now. I still remember ordering a magazine from the US to get a copy of Redhat 7 after realizing it would arrive before the download would finish on my dialup connection... I ended up switching to Debian for a while, then Slackware, where I finally gave up XP and started using linux fulltime.
I stuck with Slackware for a few years, I think I finally switched away sometime during uni when I started using VMWare (which didn't like rc.d), but by this stage the distro didn't matter so much. Slackware was great for learning the linux subsystems and how things fit together.
Wait, this is an audio blog right? I guess it would help if I finally got around to explaining what we're here for.
Over the next few months I plan to move my windows production setup to BWS on Linux. I thought it would be worth documenting my ideas and experiences for anyone looking to do the same.
My next post will talk about PulseAudio, JACK, and how Linux handles my audio devices. For reference, JACK is started automatically and uses my audio interface for I/O in BWS, while Pulse manages my system audio and mic (so I could skype while still making tunes, for example).
Following that, I'll start to dig into the scripting API and start building scripts for my midi gear (VCM600, Quneo and APC40). In doing so, I aim to write some higher level components and useful bits that are generic enough for other controllers.
In the meantime if anyone has any questions or suggestions for future posts, leave me a comment and I'll see what I can do.
No comments:
Post a Comment