Re: [Jack-Devel] JACK in Chrome !!

PrevNext  Index
DateThu, 17 Jan 2013 01:56:06 +1100
From Patrick Shirkey <[hidden] at boosthardware dot com>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToKaj Ailomaa Re: [Jack-Devel] JACK in Chrome !!
Follow-UpAdrian Knoth Re: [Jack-Devel] JACK in Chrome !!
Follow-UpKaj Ailomaa Re: [Jack-Devel] JACK in Chrome !!
On Wed, January 16, 2013 9:03 pm, Kaj Ailomaa wrote:
> On Wed, 16 Jan 2013 08:00:35 +0100, Patrick Shirkey
> <[hidden]> wrote:
>
>
>> This is the process for enabling jack and pulse on Debian systems.
>>
>> 1: Add the user to the audio group
>
> On Debian, the user is already a member of the audio group, but not on
> Ubuntu.
>

I recall that on a clean install of Debian Wheezy 64 bit that I had to add
the user to the audio group.
 It might be me but I only had to do it a couple of months back so its all
still pretty fresh.

>> 2: logout of the desktop to apply the changes to the user priviledges
>> 3: install "pulseaudio-module-jack"
>> 4: disable autospawn by manually editing the ~/pulse/client.conf file
>>
>>     autospawn = no
>>
>> 5: restart pulseaudio
>>
>>     pulseaudio -k
>>     pulseaudio -D
>>
>
> If this is required for you to get jackdbus grab the card from pulseaudio
> (by killing pulseaudio before starting jack), then you'd have to do the
> same on any system with the same version of pulseaudio and jack. The
> reason to that is what you explain at 7:, namely, pulseaudio suffering
>  from a bug making it not release the card at certain circumstances.
>

Not necessarily. it only kicks in if you originally start PA with
autospawn enabled.

>> 6: start jack
>>
>> 7: It may also be necessary to restart the computer after all these
>> changes to make sure pulse releases the device to jack. Especially if
>> the
>> user as already being playing audio through pulse. This is a known bug
>> with pulse and dbus not releasing the device properly.
>>
>> For the average user this is a relatively routine procedure but for the
>> n00b user these steps are daunting and challenging requiring a large
>> amount of background knowledge and definitely a frustrating user
>> experience.
>>
>> With Fedora I did not have to do any of that to get jack to work for me.
>> However I am not sure what has happened with f17/18.
>>
>
> What version of pulseaudio and jack? Which Fedora release? How is
> pulseaudio and jack configured differently on Fedora?
>

I don't know how PA is configured differently on Fedora but I didn't have
the same problems using it with that OS.

> So far, I'm not seeing any distro specific problem. Only buggy code. And
>  from what I've read, there may be more than one bug causing problems in
> pulse and jack integration.
>

The other thing that causes severe headaches is the naming of the jack1/2 
packages on Debian.



--
Patrick Shirkey
Boost Hardware Ltd
PrevNext  Index

1358348176.6916_0.ltw:2,a <54757.5.12.188.139.1358348166.squirrel at boosthardware dot com>