Tim wrote:I prefer Ubuntu Studio myself. It's (I think) the distro with the biggest user support group and that's nice if you're a starter.
And it's quite stable and looks good. Heard very good things about 64 studio though. But I'll stick to Ubuntu Studio..
There's a caveat with Ubuntu (and derivs like Studio) and jack though:
the jack pcm plugin for alsa is not included. You can get this enabled
by rebuilding the appropriate pkg (libasound2-plugins) though.
My personal opinion on this is that's a flaw in the design of the
distro. I'm sure the Ubuntu maintainers have their reasons, but the
Studio derivs also not enabling it tells me its not as good as it
If you don't have a need for that pcm plugin, or are willing to
rebuild libasound2-plugins pkg to include it, by all means, check the
distro out. I liked it for most of the things I used it for, until I
came across the jack pcm plugin limitation.
Oh, under Ubuntu Gutsy, if you rebuild libasound2-plugins to include
jack pcm, there's a bug in alsa (assertion failure or similar) that
crashes the thread or app trying to use jack pcm plugin. Seems to be
an issue with resampling.
After trying all this on the above, I simply went to Debian testing
(lenny, which Ubuntu is based on). They include the jack pcm plugin,
and alsa doesnt exhibit the assertion failure I experienced under
My understanding, though untested, is that alsa bug is fixed in
Ubuntu's upcoming Hardy Heron release, but Hardy still doesnt include
the jack pcm plugin by default.
Hope that helps....
Having the plugin enables you to use non-jack aware audio apps to use jack.
You can create pcm devices in your .asoundrc that invoke the jack pcm
plugin, and configure the non-jack aware app to use the specific pcm
you set. All of this of course assumes you're using the jack audio
raboof wrote:metasymbol wrote:I also tested ubuntustudio, which is a joke for me.
Any particular reason?
studio32 wrote:keep a very positive atmosphere.
Users browsing this forum: No registered users and 4 guests