Slashdot Mirror
Ask Slashdot: Linux and the Home Recording Studio?
wjcofkc writes: Somewhere between IT jobs I found myself spending 2 1/2 years employed pretty deeply in the local music industry. It was a fantastic experience. Left and right I saw people using very expensive proprietary software. I never saw anything that a similar Linux counterpart, or a suite of Open Source counterparts could not do. Needless to say, I preached the good word. Unfortunately, I never exploited any opportunities to provide a demo. One thing concerned me. If you have a full DAW setup, it's not just software; there is always some sort of hardware interface of varying complexity involved and playing through an amp into a microphone connected to a computer is not an acceptable way to record. I recently purchased a Lexicon Alpha 2-Channel Desktop Recording Studio interface based on vague mentions that it might work with Linux. After plugging it in for the first time, I fired up Audacity and Ardour. The device was available to select as an interface with zero configuration and it works perfectly. My question to the music geeks among us: what is your take on the state of Open Source pro audio software? And what successes and failures have you had with studio hardware?
I remember Ubuntu Studio being a thing years ago. I haven't been active in the Ubuntu community for a while know. I don't know what happened to the project. It had a real time kernel that seemed interesting.
One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
Somewhere between IT jobs I found myself spending 2 1/2 years employed pretty deeply in the local music industry.
You were unemployed for 2.5 years following the Great Recession. I understand your situation. I was unemployed for two years (2009-2010), underemployed (working 20 hours per month) for six months, and filed for Chapter Seven bankruptcy. Alas, I spent my entire looking for a job.
Comes with a realtime kernel, jack, and Ardour all set up and ready to go. There's no other distro to use for a home studio. I used it in my home studio years ago with an 8x8 PCI audio card, and it was great. I haven't used it in a while but the project is still being maintained, so you might check it out.
For what you trying to accomplish, there are more open source programs available for Windows than any other platform. If your computer is stand alone, you need not worry about phone home telemetry, or just use Windows 7. Auto Tune alternatives are widely available for Windows than Linux, if that matters to you. Otherwise, Linux is great if it meets all your projected needs.
Actually I use a low latency build of the Linux kernel, otherwise you would be right. Jack would be... jacked. It is something I had to learn.
Brought to you by Carl's Junior.
'Recording Studio' -> Get a Mac. Seriously. CoreAudio is probably *the* best audio subsystem on the planet, currently, Proprietary or Open Source.
I tried Ardour with my FireWire mixer (32ch in & out). Even with a realtime kernel, JACK would instantly eat 100% of a CPU core when connecting to the mixer, and I'd get dropouts. You have to manually tweak buffer sizes & sample rates to target a specific latency. Not to mention the entire JACK core would crash mid-recording sometimes. Ardour itself is amazing for an open-source DAW, but it's hobbled by broken subsystems as dependencies.
PulseAudio is like WDM on Windows - you're going to get absolute crap for latency, next to no control over sample rates and buffers unless you start digging through the Pulse configs, restarting the service yourself... it's meant as a 'consumer' audio playback engine, at *most* you'll want to use its recording side for, say, voice chat, livestreaming with Open Broadcaster Suite, that sort of thing. It also has a bad habit of assuming 'multichannel' means 'surround'.
The only other system that you can get by with would be ASIO on Windows, but then you're dealing with the typical Windows issues, hoping your mixer/interface manufacturer has created Windows drivers for your system, those drivers actually work and don't crash, etc. Your interface is a few years old? Only has drivers for WinXP/Vista? Good luck!
This is *the* one big place (video editing being the other) where Macs are still King. CoreAudio is literally plug-and-play, and can handle sample rate conversions, clock sync master/slave settings, etc. (Audio MIDI Preferences.app for details) - you can even merge multiple disparate interfaces into one combined virtual interface (though you risk timing issues with wildly disparate hardware).
You can assume almost every Pro Audio hardware manufacturer designs and tests on Macs & OS X *first*, and then hacks together a Windows ASIO & (maybe) WDM driver as an afterthought. All your 'regular' Windows apps will be using WDM - games, Skype, what have you, and all your Pro apps will be using ASIO. Two different drivers for two different sets of applications. On a Mac? CoreAudio is the same for everyone. Games and 'regular' apps use the same backend as Pro Tools or Ableton or Logic.
tl;dr: I tried the whole 'Linux DAW' thing years ago, gave up, got a Mac, actually spent my time getting stuff done and not fighting broken systems/drivers.
Aaron Wolf gave a talk about this at SCaLE14x this January.
Link: https://opensource.com/life/16/1/configuring-linux-for-music-recording-production
I used Ubuntu with Ardour for about 4 years (2005-2009) doing a ton of recording. The machine I ran on was a 2.7Ghz dual-core, 2GB of RAM, and I used a sound card known to work well with Linux at the time (can't remember the brand, disinclined to open the machine up and find out for the purposes of this post). I have a friend who, during the same time frame, bought a Mac Pro and Pro Tools, paid someone from Pro Tools to come to his studio and train him, and bought a bunch of preamps, etc. He was writing songs and working some kind of deal with a publisher in Nashville.
Long story short, because my apparent knack for arranging (and programming realistic-sounding drum parts), he ended up sending all of the bed-track work to me. Typical project size was 40+ tracks. I built a Qt app to listen to incoming MIDI events from my drum machine, played hi-res drum samples, and recorded each drum output into Ardour. There was a TON of effects plug-ins that ranged in quality from "utter crap" to "very darn good". The overall recording quality was about what you'd expect a basement-studio guy to produce: That is to say, equal to what my ProTools friend was producing. As for performance and stability: I remember that when the machine was trying to play 40+ tracks with a lot of effects and play the drum parts too, it would run into some difficulty that resulted in it sounding like the drummer was a bit drunk. The solution was to record the drum tracks by themselves in a pass, then it was fine.
Overall, I was very happy with it. I ended up doing the bed tracks for an actual album for another guy later, and then sort of lost interest in recording in my basement and moved on to other things. I've been thinking lately of getting back into it, to see where things are technology-wise. It was fun.
Choosing a DAW is much like choosing a programming language & IDE in one, all your knowledge becomes domain specific, and as such, as soon as you get serious it's difficult to consider open source options seriously.
No.
The only thing that is partly stuck to the program is the workflow. If you just know in which order to press the buttons and don't know what they do or why they do it, then sure, you knowledge applies only to that program. But if you know what the tools are doing then you can jump to pretty much any DAW on the market and make it work. You'll be slightly less efficient because of changes in workflow while getting used to the new workflow. And the bigger the difference, the weirder it is for the first couple of hours. Jumping from ProTools to Ableton Live is quite weird, for example.
I've jumped between ProTools, Ableton Live, and Reason with no problems. I've also played around with Logic, Reaper, and Cubase.
Reaper is quite nice, and works well. Also very easy to grok the workflow as it is a simple one that is quite like ProTools in that it relies heavily on an old workflow that would fit an audio engineer from the 1980s or 90s.
Reaper rocks for that price!
Lots of experience with this.
1) Real Time Kernel (compile it if you have to)
2) Ardour (My best results are with Ardour 2 so far)
3) Jack Audio
4) Rosegarden (for midi)
5) Linuxsampler (convert midi to audio using professional samples)
It doesn't hurt to have 8 cores, 32 GB RAM and tons of HD.
With 2 40" 4K screens I can display just the ardour mixer with 30-50 tracks across one screen.... and have room for the other apps.
I've done many tracks.... easily up to 70 tracks... with plugins... low latency....
The future's good and the present is nothing to sneeze at. I've used Audacity as my primary audio editor for years. Admittedly, my requirements are pretty lightweight, but it does what I need.
I use Ardour on Fedora, connected to a Focusrite Saffire Pro 40, and heavily using the great and opensource Calf Studio Gear Audio plugin suite. Everything works really well, and the setup could be used to put together a really high quality album. We almost exclusively use it for recording church services, which doesn't exercise the full potential of the setup. One of these days I'll have time to put together a project that takes advantage of more of the capabilities we have.
Checkout Bitwig. It's basically Ableton for Linux, damn near an exact clone. Multi-track recording, VST support, arrangement and performance type views.
Full disclosure: I'm a middleware guy, and I greatly prefer to run linux as a server operating system. I have 25+ years of experience as an IT administrator and am more than a power user on linux. Off the clock, I make music and have used PC and Apple based DAWs for 20+ years, starting with a Pentium 75 with a Turtle Beach soundcard back in 1994. Today, my wife is a pro voice actor (if you listen to Pandora, you've likely heard her) and we maintain a professional level recording studio in our home. Said studio runs Windows 10 and Cubase 8.5 for a DAW.
That said: There are better platforms upon which to do digital audio. If you're doing this with any intention of making money, spend money on your operating system. Linux struggles to be a decent desktop OS as it is; there's no need to introduce driver issues and under-supported DAW software into the mix, while at the same time dealing with a dicey desktop OS.
Windows and OSX are by no means perfect - but they're supported solutions that DAW software and interface drivers are specifically coded for. Open source is fantastic in the enterprise, but I would never, ever risk my wife's career on community supported software. As it stands, running Windows is dicey enough - and we'll be moving (back) to OSX once I work out a monitor/keyboard/mouse sharing solution that doesn't cost an arm and a leg.
Even with a realtime kernel, JACK would instantly eat 100% of a CPU core when connecting to the mixer, and I'd get dropouts.
I have the intuition (not so much an intuition) using a real time kernel would increase the CPU load rather than decrease it. Perhaps the "tick rate" or whatever it is of the real-time feature can be configured.
In another vein you remind me why I don't use a "3D accelerated" desktop in linux, I like to keep a top window running when needing to keep tabs on things and this just results in crazy CPU load spikes by the window manager, Xorg or both.
Pulseaudio does have a cool feature, you can add one silly line of configuration and get a "mono output" virtual device, which is useful if one of two speakers is broken or you're listening to a "left ear" youtube video. That's the one good thing I could say about it. I do audio consumption.
The future's good and the present is nothing to sneeze at. I've used Audacity as my primary audio editor for years. Admittedly, my requirements are pretty lightweight, but it does what I need.
I've done some audio editing in the past where I take raw inputs, clean them up, add effects & other work as needed, then produce a final track. While I can do that with Audacity, I find it harder to do than with SoundForge (an MS-Windows only program). I'm sure some of my preference is what I'm used to, but it's always felt to me that Audacity just makes things a little harder than they need to be, or is missing something I'm looking for (it might even have what I want but is called something else that I don't recognize so I think it can't do what I need). I appreciate what the team has done in giving us Audacity, and it's fine for when I need to take a recording and trim the ends or something else dead simple, but for real editing I'd *much* rather have SoundForge.
... me, I just want to get the job done so I can move on to the next job).
To use an analogy that is somewhat apropos, I actually prefer MS-Word over LibreOffice-Writer. Sure, I can use Writer to get the job done, but I always seem to have to hunt a little harder to find the task I need, or Writer randomly renders the document incorrectly occasionally (displaying into the margins is the most annoying one but it screws up in other ways too). I use Writer for simple tasks like viewing only, but for heavy editing I prefer Word.
In both cases, I'm discussing ease of use to get the job done and not about which is "freer" (which maybe be more important to some poeople
Agree. I have several Linux machines, one of which is dedicated to music production. I use (at the very least) Rosegarden, Renoise, Ardour, SooperLooper, Hydrogen, Rakkarack, a few soft synths, kmidimon, a real-time kernel and JACK. I have an M-Audio 24/96 card, and a Tascam US-122 for real world interfacing. I use an M-Audio short keyboard as a controller, a DX7s for a real keyboard feel, external reverb/echo, Kawai K4r, Roland D-110, Soundcraft mixer and a Sennheiser mike. I have a Yamaha FX-770 for a guitar interface and my whole workflow is controlled from Linux, sequenced by Linux and recorded in Linux. The only thing I would add is the use of an external MIDI clock with stop/start/resume and tempo; that, and I am currently experimenting with BLM controllers; I re-brained a Novation Launchpad and I now want MORE.
Linux is utter shite for anything requiring creativity. Just get a Mac and be happy with your work instead of living with the endless frustration that is modern day open sores software.
I whole heartedly agree, terrible waste of time.
Also pretty sure anything audio related in Linux land is going to be stillborn thanks to PulseAudio. From what I have run across, base ALSA isn't going to help much either.
Content creation whether, audio, video, 2D, 3D, or other at the professional level generally requires the ability to jump among a variety of software packages, plugins, and occasional one-jobbers. You're not going to see that anytime soon in Linux. Audio and 2D have a foothold in OSX because of ProTools and Adobe, but everything else runs on Windows workflows. 3D used to be a big one for industrial *nixes, but that ended in the late 90's / early 2000s when Microsoft bought SoftImage to port their software to NT 4.0. I run across a few Linux zealots talking about Blender and on the more professional side, Houdini, but none of those people are gainfully employed on a regular basis. Content creation is about the workflow and being able to accomplish things end to end. There's little hope there for Linux as a desktop OS unless you can restrict your use case to a subset of the software available there.
For audio production you usually need JACK which lets makes audio and MIDI connections between audio programs and I/O. And Ardour is getting to be a polished and very capable product now. Neither has any application on a normal desktop system, but for audio work they are ideal.
Linux is not yet usable for professional-quality home recording.
The article, written by a guy who claims to have "spent 2 1/2 years in the local recording industry" tells us that he recently bought a "Lexicon Alpha 2-channel" interface. Just so you know, the Lexicon Alpha 2-channel interface is a $49 POS USB interface that you wouldn't use for anything more critical than a low bit-rate podcast. Let me know when I can use an Apogee or Apollo or Avid interface with a Linux box.
Linux is a fine platform for use in a recording studio. I use it all the time, but never as a main production platform. It can be used to stream samples, for storage, and even to off-load audio processing and rendering chores. The implementation of VSTs and VSTi's in Linux is still so wonky as to be unusable. And nobody ever used Audacity in their home recording studio to produce anything professional.
I hope Linux eventually does become a viable platform for music production. I've been waiting a long time for that to happen.
You are welcome on my lawn.
Linux would be good for this, but most of the mainstream desktop UIs (KDE, Gnome, etc.) tend to be very slow and porky, so it really would take a separate desktop environment that is lightweight in order to allow Linux to be useful for an audio or audio/video platform.
It also needs a few system tweaks and, for best latency, a low-latency or even realtime kernel.
AV Linux is a Debian system so tweaked, making it very easy to use. It also comes with XFCE, which is more than enough desktop functionality to do audio and video work and llightweight enough not to get in the way.
It is better, whichever OS you use, to have a dedicated system for realtime work like multitrack audio recording and mixing. Real recording studios don't do their accounts and email on the studio computer. Not while it's being used in a recording session, anyway...
That's nice to hear that ardour is coming along still. I tried it...15 years ago? And it was super unstable on my setup no matter what I tried. Regardless, I'm still surprised Reaper Audio isn't more popular. Costs $60, and does as much as Pro Tools, Cubase, etc in my experience. It ain't free, but it might as well be compared to the price of proprietary competitors.
I love Linux and open-source software. I used a Linux desktop for 15+ years as a software developer. For servers, it's a no-brainer. I'm rooting for Linux.
For audio work, I won't touch Linux with a 10-foot cattle prod. It's just not there yet, and it's not going to be anytime soon.
I spent several years attempting to keep Linux at the center of my studio, and I wish I hadn't. The user experience for a seasoned studio engineer is light-years behind Windows and Mac. I was forced to compile real-time kernels and custom versions of Ardour, got rid of my MOTU interfaces because the manufacturer hates Linux, spent countless evenings swearing at xruns, and developed a well-honed contempt for JACK's almost Windows NT-like stability. Working with MIDI and audio required lashing Ardour, Rosegarden, and Hydrogen together with duct tape and wishful thinking. Audio latency was never decent enough to use most effects while monitoring.
Every time I hit record with other musicians, I said a small prayer to the USB bus gods that nothing would explode mid-take. This is not a mindset conducive to creativity.
Did it actually work? Yes, after a fashion. There are some bright spots: Alsa Modular Synth sounds awesome, the Calf Audio plugins are as good as anything on the proprietary side of the fence, and Ardour is serviceable in a 2003 kind of way. I managed to record a few albums of material using that setup, but it was not an experience I would recommend to anyone. It felt like I was doing more tech support than creating.
Eventually I sucked in my open-source pride and bought a Mac with Logic Pro X on it. Pretty much everything that I've done on it worked right out of the box. It hurt my soul to hand $3K to an Apple Store genius, but now I spend my free evenings recording instead of swearing. I can only hope that Richard Stallman doesn't show up at my front door to lecture me, or worse yet, sing that god-awful GNU song at me.
Time is money, and free time is the most expensive of all. If you value your creative time in the slightest, don't bother with Linux. Get a Mac or PC, load it up with an industry-standard DAW, and make some noise. You may not please St. Ignucius, but you will at least be productive.
I'm an actual recording engineer who's worked for Justin Bieber, Kanye West, VictoriousRush and her that rubs her minge on a wrecking ball and let me tell you that yes, they totally do.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
If you last tried Ardour 15 years ago, you owe it to yourself to try it again now. It took a major boost in features in the Ardour 3 release, and increased its polish for version 4. All in all, it's an excellent tool to make use of for music or other forms of audio production.
The Penguin Producer
I intend to use Lubuntu with LXDE and an Awesome (window manager, not superlative) desktop. No PulseAudio, very minimal system usage, and full access to KXStudio, which provides an immense collection of programs that can cover just about every possible function, especially when you take Jack, Ardour, Claudia, and the immense collection of plugins available.
The Penguin Producer
Reaper is now my go-to for audio recording, editing, and mixing. Works on Linux, Mac, and Windows, and costs less than a new video game. It supports an enormous number of VST and Dx plugins (the latter sadly only on Windows), and works instantly with nearly every DAW or audio interface I've thrown at it (provided there are drivers for your OS). I've recorded, edited, and mixed two commercial albums on it (small-scale, but still selling 1000+ copies each). I'm not a mastering engineer, so I can't speak to its capabilities there, but for everything else... it took me an age to give up on my old PARIS rig, but Reaper even supports my old PARIS audio files...
I used to work for a defence contractor on software that, I discovered later, was being written for the NSA to use in the spying programme. No joke, this actually happened. I am posting this AC via Tor just in case.
I want you to keep than in mind when I say...
I don't even know where to begin with this.
First off, Windows has continued to be non-standards compliant, inconsistent in its directions, and has haphazardly dealt with security updates. I shouldn't have to wait for months to have a security vulnerability patched. Have they gotten better? Yes. But this licensing garbage that's tied to the firmware for 8 and up, and Office licensing that's tied to email is a horrendous endeavor to maintain.
If you want to consider Linux a failure of a desktop on the account of Gnome, Pulse Audio, Unity, and SystemD, you fail to realize that each one of those are simply software packages running on top of the operating system. Most of the issues you describe are either anecdotal, or simply a regurgitation of what you've heard. I've never had problems with Pulse Audio, nor has anyone that I know personally. Gnome I've had issues with when attempting to integrate with an existing installation, but that was during 3 Beta, Unity sucks, and is is sluggish, but it isn't buggy. SystemD, a lot of people complain about it, and I understand why, it's a complete overhaul, overbearing/far reaching, but since it's adoption out of Beta, I've yet to have ANY workstation or server have any reliability/stability problems. There have been minor configuration issues occasionally, but nothing that's atypical from normal software upgrades.
I feel bad responding to a first post troll but wrong is just wrong. I'm an amateur musician in the Olympic sense (I've never been paid for it in a meaningful way). It turns out you can do incredible things with a Linux desktop and just as much (if not more) with a Linux recording setup. Now, would I suggest using a Linux set up when trying to collaborate with other musicians? No. Sounds like a terrible plan. Can you record decent sounding multitrack stuff on your own with the right equipment? Absolutely.
http://soundcloud.com/chuck-bl...
It's not music that most people will like but it was recorded completely using a fedora studio spin. It can be done.
"Watch your cornhole, bud."
I suppose it is just too hard these days to imagine recording music (the question was about a home RECORDING studio) as actually meaning RECORDING musicians performing on instruments.
I can assure you that there are plenty of people using Linux to do that, without the issues you're describing above. I'm also going to assume that you live in the USA, because if you lived in Europe (notably Germany) I think your perception of Linux would be quite different.
> Let me know when I can use an Apogee or Apollo or Avid interface with a Linux box.
Some Apogee products are USB audio compliant, so they are plug-and-play and always have been. Other Apogee products started getting Linux support five years ago.
https://www.youtube.com/watch?...
Apollo? Sure thing:
https://thecrocoduckspond.word...
Some professional "hardware" runs on embedded real-time Linux - all that DAW functionality isn't done by tubes anymore, there's an OS inside that workstation. And that OS is not Windows.
You will want to download a real time kernel and use Jack, not Alsa, for professional audio work.
OK, sorry. You want advice? If you want to do professional quality work in your home studio, you have to start with a Windows PC or Mac. Run Cockos Reaper. Use your Linux box to offload streaming and processing work via Reapers ReaMote technology, for rendering and for sample streaming. You'll get the best of both worlds.
Then, once a year or so, install a real-time kernel distro and the latest Audacity and see how far it's come. Keep hope alive that there will eventually be an all-OSS solution for DAWs.
You had said you were a 2 1/2 year veteran of the music industry, and I made assumptions from that. In regards to that Lexicon Alpha: invest in a decent mic preamp if you plan to use any live mics and run the output of that into the Alpha. It'll make a world of difference. ART makes some very decent cheap preamps that sound pretty damn good for the price (probably about $30).
Seriously friend, good luck. I shouldn't have assumed anything about your level of experience. I used some really shitty setups when I was first starting out. I learned a ton from trial and error and asking smart-asses like me for help.
You are welcome on my lawn.
A minute ago it was "you can't use Apogee on Linux, and professional use only use Apogee etc". Now it's "that Apogee gear is crap, now that I know Linux supports it just fine". I guess only the Scottish Apogee model is any good, eh?
Everybody is mistaken sometimes. Knowledgeable people get that way by by -learning- when they are presented with new information. Ignorant people refuse to learn anything, instead moving the goalposts and playing no true Scotsman when new information is presented.
Take a close look at the owner's manual for your DAW. You just might be surprised and find a FOSS disclosure in there.
I know that "Get a Mac" seems like a trite statement to a lot of people, but in the case of professional audio and video production, there really isn't any reason to do otherwise. Your choices for professional studio compatibility are ProTools or Logic, and everything else (Abelton, etc.) is pretty much only used by hobbyists, not professional studios.
FWIW, my current home studio setup is still a Power Mac G5 Dual 2.0 GHz machine with 1 GB of RAM and a 160GB SATA-1 drive. I use a second 160GB SATA-1 drive for my recording deck. My interface is an M-Audio Delta 1010 (24-bit/96 KHz), the PCI-X version (this is the last Mac that actually works with the PCI-X card). I'm running Logic 7.2 still, because it works for what I need, which is for recording a small rock band. I have an M-Audio Octane 8-channel mic preamp fronting it, and the outtput goes through a Presonus Central Station before hitting my Sennheiser HD280 cans and M-Audio Studiophile BX8 nearfield monitors. My microphones are a pair of M-Audio Solaris large diaphragms with Shure Beta 57A and 52A dynamics. I use a LaCie Electron Blue 19 CRT monitor. All in all, a very respectable home studio setup, circa 2005, which is when I bought it.
I can easily record 16 tracks with a shit ton of software plugins including multiple convolution reverbs before running into CPU or disk speed problems. This workstation is not used for anything other than recording, and ten years later, it's perfectly functional, if limited to Mac OS X 10.6 (I keep it off the Internet, mostly). If I needed a bit more speed, I could run a RAID-0/1, add RAM, or add a tc electronic PCI DSP card to handle the reverbs and some of the other effects, rather than having the Mac calculate everything. But, the fact is, I rarely run into insurmountable problems with the amount of bandwidth in this machine. There have been times when I've needed to "freeze" certain tracks in Logic in order to avoid CPU snags, but I'm recording a four-piece rock band: drums, bass, guitars, vocals.
This whole system was literally plug and play. You are simply not going to find anything that works this simply or this well in Linux, not even now, in 2016. Eventually, this system will be replaced with something new and a Firewire or Lightning A/D/A box, and I'll upgrade to whatever version off Logic is current, but there's no need to fix what isn't broken. Logic is, to my knowledge, the only system other than ProTools that is capable of using Avid/Digidesign ProTools HD interfaces.
I use Bitwig Studio and Renoise as my DAW's of choice. Hard to beat really I use a Scarlett 2i4 and have a bunch of hardware . Arturia Beatstep , Korg minikeys , Waldorf Blofeld. Never had any issues getting it to work I use Ubuntu for the desktop. Neither DAW are open source but both have a thriving community .I'm happy to support vendors that support Linux. You can hear some of my stuff here.
http://www.soundcloud.com/poly...
No Mac or windows machines were used on any of my tracks.
Electronic Music Made Using Linux http://soundcloud.com/polyp