-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 64Studio is based on Debian. You can add Debian sources to a 64Studio install without breaking it. The lead dev was the lead in the Agnula/Demudi project. So he has a long history with all things linux audio, and Debian specifically.
64Studio builds and tests their own rt enabled kernel, as well as keeping up to date its version of jack(some of this stuff can get reall stale under Debian). There have been lots of improvements in the last year, especially relating to multi-core Also, the apps the ship by default with 64Studio (or are a part of their repository) have been built with jack in mind. They also have more up to date versions of Ardour than is found in Debian stable or testing. As for coming from the windows world. I would say forget everything you know. Once you become familiar with how the pieces fit together, and what your work flow is, you will find that not all your knowledge is useless. The biggest problem I see with people new to linux audio (well linux or bsd in general) is that you try to directly translate your windows experience into linux. Linux is not windows. Say that 100 times. Some things look similar, but there is a lot of important differences under the hood. For example, there is no jack equivalent under windows. One of the foundations of a linux DAW simply does not exist in Windows, so how you think of your DAW will be different. I have also met people for whom a Linux DAW was not appropriate. I am not one of those people, but you may be. I/we/you don't know yet. I would also prepare for frustration. Imagine finding out that your hardware (say an RME Fireface) is not and likely will not ever be supported under Linux. That would suck. Of course I had this experience when switching from win9x to 2k/xp, which is why I looked at moving my DAW to linux in the first place. IMO the pain of learning a new environment is worth it. Also, the rest of the hardware will be getting stressed with an RT kernel, and you likely trying to do low latency work. Motherboard chipset is important, are you over-clocking, etc. Binary drivers such as nVidia and ATI are notorious for causing problems. My DAW is a dedicated machine that does nothing else. It has an integrated ATI video device, but I use the non-3d open source xorg driver, not the proprietary fglrx module. I took care to build a machine that was solidly supported by linux, you may not have that luxury. I am not sure what exactly you will be using your machine to do, so I am not sure what hardware to recommend. Rick Norman wrote: > > > >64Studio is, as I am sure many people are sick of me saying, is > >currently my favourite distro for this sort of thing. > > > Gustin, > > How would you compare 64Studio to, say, a Debian Etch setup > with Ardour, jack, etc. installed for audio work? Are the differences > significant enough to make it worth creating some extra space for > an install? > > I've started to play with audio under linux, but I haven't made it very > far just yet (I come from a Cubase and Cakewalk background on > Windows, so I have a *lot* to learn in this area). > > Rick > > > > ------------------------------------------------------------------------ > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHoY2awRXgH3rKGfMRAumLAJ0Z5aYi2Ro3Fzpy68zwt7/VACNpgQCfblx6 OTNISWWACBItfZLMLkpDQqs= =/qWD -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
