What's wrong with jack ?
ricardolameiro at gmail.com
Tue Jun 1 14:32:50 BST 2010
Well, I have been reading the messages and there is a couple things that
people don't discuss or maybe don't know.
As of Ubuntu/UbuntuStudio 10.04, Jack is on the main repositories, this is a
huge improvement from the past. what does this mean?
If you do a fresh install, at install time, either alternate install or
ubiquity will prompt the user if they want to install and setup jack.
This means that the audio group and the settings are made on install time.
Another thing is that the settings now are at
more info at https://help.ubuntu.com/community/UbuntuStudioPreparation
<https://help.ubuntu.com/community/UbuntuStudioPreparation>There is also
underway, some efforts to use Jack2, that is Dbus enabled. this will
enable"in theory" a good and seemingly interaction with PulseAudio. thing
aren't perfect, true, but sometimes we need to help each other to find the
better solutions, and also, try to give that solutions to the devs.
The devs have families to, lives, they dont work for canonical,
ubuntustudio is a community project, and i think sometimes people forget
that, they just want it working without giving nothing back.
I love this discussion, because at least some people want it to become
better and do exchange info. So i hope with all of our efforts as users, we
could help as much as we can the dev team. this is a win for all of us.
2010/6/1 Hartmut Noack <zettberlin at linuxuse.de>
> Am 01.06.2010 14:08, schrieb Pablo Fernandez:
> > I find it neater the way it is now. As a user, I think the case
> > is similar to /etc/apt/sources.list and
> > /etc/apt/sources.list.d/someother.list
> > Particular configurations for particular goals are in a separate file.
> > Someone in the LAU list mentioned other examples and gave better reasons.
> > Anyway, the user does not have to bother anymore with editing a system
> > file.
> > More authoritative reasons are here:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507248
> Very interesting read - thanks for the link!
> This discussion shows quite clearly, where the overall problem with
> pro-audio on Linux lies: Those, who do the good work in building Distros
> like Debian do not know about pro-audio. If you tell them, that it is so
> demanding, they see a risk for their overall working system/security
> etc. And they are apalled to hear, that there are some crazy people out
> there, that want to have a 970MB-File locked into memory to be
> accessible with less then 10ms latency.
> This I understand but I do absolutely not understand, that these
> tech-people do not react like this:
> "Well quite interesting stuff, you crazies do there - let us do whatever
> possible and sane to make our system support such incredible features!"
> They act more like:
> "Comeon, do not bother us with such strange single-user
> niche-applications. Do this if you like but stay away from our great
> system settings that work so well for dozens of years now."
> > I like when Steve writes "common doesn't mean correct".
> I am not sure if he really knows, what he is talking about.
> The whole thing is, that jack, though it is a user-process, needs to be
> priviledged even more than the avarage root-process in order to work
> properly for the user. And this is not a bug or a flaw in the design of
> jack but simply a neccissity. This process needs to access data as fast
> as technically possible. Can the kernel-memory management guarranty
> that? Apparantly not. So you have 2 decisons:
> 1.) have a system set up conservatively for everyone, that runs normal
> Desktop-Apps and thats it. No RT-apps on Linux at least not for users
> with higher skills in tweaking system settings.
> 2.) find a sane way to let the user decide, what he/she likes to do with
> the system-setup.
> > We will have to learn again :)
> Everybody needs to learn every day.
> >> Plus, as you mention yourself later on, the script must set up group
> >> audio as well, this is a no-brainer and I really do not know, why the
> >> packagers do not implement that.
> > I didn't say exactly so. I think a package script must not deal with
> > and groups.
> > But the distro should do it, imho.
> You mean: group audio should be set up in the initial install and the
> first user should be in that group?
> >>> For the rest, qjackctl launches pasuspender so pulseaudio is (almost)
> >> of
> >>> the way.
> >> I recommend that. It works very much OK for me.
> >>> Afaik, a cleaner approach than pasuspender or the rm you suggest in
> >> getting
> >>> rid of pulseaudio is the following:
> >>> qjackctl --> Options tab, execute script on startup:
> >>> pulseaudio -k
> >>> (this kills pulseaudio) (artsshell sounds like jurasic)
> >>> However, pulseaudio will respawn automatically if you don't do the
> >>> following:
> >>> $ sudo edit /etc/pulse/client.conf
> >>> Change the line:
> >>> ; autospawn = yes
> >>> to:
> >>> autospawn = no
> >>> If you wish to start pulseaudio, once the jack session is finished:
> >>> $ pulseaudio --start
> >> This methods I tried in Open Suse 11.2 and it broke my system so
> >> globally and totally that I abandoned the OpenSuse-Installation. So I
> >> really recommend to check out, if pasuspender does the trick
> > In my case, pasuspender does the trick but I don't want a pulseaudio
> > running at all.
> > https://help.ubuntu.com/community/UbuntuStudioPreparation#Pulse%20Audio
> > recommends creating a *~/.pulse/client.conf* with "autospawn = no"
> > of editing the system wide /etc/pulse/client.conf as I suggested) and
> > put "pulseaudio -k" as a "Startup Application".
> The latter looks promising. If I find the time, Ill try it just for
> curiosity ;-)
> best regs
> Ubuntu-Studio-users mailing list
> Ubuntu-Studio-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
Fagote / Contrafagote
Bassoon / Contra-bassoon
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ubuntu-Studio-users