Blind users of Ubuntu Lucid, and Vinux 3.0, are reporting that on many
machines, volume is muted at the initial boot, both for the LiveCD and
after the install. We have added a keybinding, so that blind users of
Vinux can press Insert+PageUp to increase the volume, and this works
in most cases.
Hi, Dan. Thanks for the pointer to linux-alsa-driver-modules! I did
not know about the ubuntu-audio-dev PPA. I installed it this morning,
and the ratelimit.c messages seem to have stopped.
My question is: should I enable this by default for all Vinux users?
Vinux is slightly modified Ubuntu
Ok. Thanks for the feedback.
Bill
On Fri, May 14, 2010 at 9:27 AM, Daniel Chen seven.st...@gmail.com wrote:
On Fri, May 14, 2010 at 3:19 PM, Bill Cox waywardg...@gmail.com wrote:
My question is: should I enable this by default for all Vinux users?
I strongly recommend against doing so
Vinux is a customized version of Ubuntu for the blind. Our users rely
on PulseAudio for speech, and we have everything working well now
days. Now that Ubuntu Lucid has shipped, we're close to shipping what
I think will be a very popular release of Vinux, meaning we'll have
lot's of regular users
In Ubuntu Lucid, as well as Vinux, we get a ton of syslog messages
like the one in the subject line. At least one power-user thinks this
is related to kernel panics, and always removes PulseAudio because of
this error. Here is the bug report at launchpad.net:
Thanks! That's probably enough to get me started.
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
, Lennart Poettering
lenn...@poettering.net wrote:
On Sun, 07.02.10 22:54, Bill Cox (waywardg...@gmail.com) wrote:
Finally, disable group-based authentication to use the sound system.
Edit /etc/pulse/system.pa. Find the line that reads:
load-module module-native-protocol-unix
and change
Here's what I don't understand. Why doesn't PA run in system-wide
mode, but still do all the same user-permission checks it does now,
and only authorize the current user to access the sound card? Is
there any advantage in running the whole PA daemon in user space? Why
have multiple PA processes
will continue to complain about in PA
is it's inability to deal with multi-user sound.
Bill
On Wed, Feb 10, 2010 at 6:32 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Bill Cox at 10/02/10 10:50 did gyre and gimble:
Here's what I don't understand. Why doesn't PA run in system-wide
PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Arun Raghavan at 10/02/10 19:26 did gyre and gimble:
On Wed, 2010-02-10 at 11:16 -0500, Bill Cox wrote:
Ok, the new glitchless code sounds cool. Reducing the interrupts
seems close to pointless from a power savings view, unless
@shivers.mail0.org wrote:
Bill Cox:
While the right way is not system-wide mode, in practice, I find
system-wide mode to be very stable and usable on Ubuntu systems that
have multiple users trying to send sound to the speakers.
So, I'm still wondering: what *is* the right way for this use
The corking stuff in PA is very cool. I don't think anyone objects to
it. But couldn't we quell all the PA stinks! posts by just allowing
some processes/groups/users to have constant access to audio?
Comparisons to MAC and Windows have been going on for a while, and the
PA guys are basically
While the right way is not system-wide mode, in practice, I find
system-wide mode to be very stable and usable on Ubuntu systems that
have multiple users trying to send sound to the speakers. It's easy
to get Ubuntu Karmic and Lucid to use PulseAudio in system-wide mode.
For systems that require
Sweet! There are a number of games I've heard people have trouble
with. I look forward to the next Ubuntu update.
Bill
On Thu, Jan 14, 2010 at 7:28 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Fri, 15.01.10 00:11, Lennart Poettering (lenn...@poettering.net) wrote:
I think what
On Tue, Jan 5, 2010 at 8:01 AM, Lennart Poettering
lenn...@poettering.net wrote:
I have discussed this with Kay now and he'd very much prefer to do
this with a proper idle session that some tool (maybe some wrapper
around the speakup daemon) registers in CK, instead of patching
udev-acl.
On some mailing lists, I've read that some users avoid PA partly
because older games they like to play wind up having delayed sound. I
would guess that there is a way to configure PA for specific
applications that run in user space to run with lower latency. First,
how would I do that for a
On Tue, Jan 5, 2010 at 9:19 AM, Lennart Poettering
lenn...@poettering.net wrote:
Yes, the speakup daemons need to be modified so that they can be run
as a normal user instead of root, and then can deal with devices (both
audio and those special speakup kernnel devices) being assigned and
taken
I'm trying to build a Vinux (blind-user Linux distro) release based on
Ubuntu/Lucid. There's too much code to rewrite to have everything
working the right way with pulseaudio by May, so I want to release
Vinux/Ubuntu Lucid with the system-wide hack.
I've enabled PA to start in system wide mode
Yes, it's running as user 'pulse' like this:
/usr/bin/pulseaudio --system --daemonize --high-priority
--log-target=syslog --disallow-module-loading=1
Bill
On Mon, Jan 4, 2010 at 11:09 AM, Ng Oon-Ee ngoo...@gmail.com wrote:
On Mon, 2010-01-04 at 11:02 -0500, Bill Cox wrote:
I'm trying to build
everywhere. There are still tons of goobers, but they're
all of the sort I can work out.
Thanks!
Bill
On Mon, Jan 4, 2010 at 12:02 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Daniel Chen at 04/01/10 16:56 did gyre and gimble:
On Mon, Jan 4, 2010 at 11:02 AM, Bill Cox waywardg
will be full dealing with all the other crap that's
still goofy for accessibility, like the fact that gksu doesn't work
with Orca. Vinux/Ubuntu Lucid is going to be awesome for the blind.
Thanks!
Bill
On Mon, Jan 4, 2010 at 12:07 PM, Bill Cox waywardg...@gmail.com wrote:
Wow! That's a lot
, Jan 4, 2010 at 1:29 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Fri, 01.01.10 22:25, Bill Cox (waywardg...@gmail.com) wrote:
On Thu, Dec 17, 2009 at 4:52 AM, Lennart Poettering
lenn...@poettering.net wrote:
I don't see why anyone would want to have audio when changing to root
On Mon, Jan 4, 2010 at 1:35 PM, Lennart Poettering
lenn...@poettering.net wrote:
I dont see why the speech tools should be handled in any way different
from the other acessibility tools we ship: in that they are part of
the session. While I am no accessibility expert I am kinda sure that
on
. I hear it integrates well with
Braille displays.
To put it simply, I cannot even imagine creating a Vinux distro (linux
for the blind) without speakup and consoles!
Bill
On Mon, Jan 4, 2010 at 1:58 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Fri, 01.01.10 23:50, Bill Cox (waywardg
On Mon, Jan 4, 2010 at 2:26 PM, Lennart Poettering
lenn...@poettering.net wrote:
... an alternative could be to fix speakup to
simply watch CK and disable itself as long as long as somebody is
logged in.
Users need to be able to press Ctrl+Alt+F1 at any time and get to a
speeking console. It
On Mon, Jan 4, 2010 at 2:37 PM, Lennart Poettering
lenn...@poettering.net wrote:
Also, the sepakup device access should be handled by udev-acl as
well. That would probably require non-trivial patching in the speakup
tts daemon though.
I'm completely ignorant of udev-acl, but if this is the
On Mon, Jan 4, 2010 at 3:37 PM, Lennart Poettering
lenn...@poettering.net wrote:
Right. So why not fix orca and make everything work fine in Gnome? I
mean, lets fix things properly, not carry on with kludges.
I'm guessing you're and Emacs user. What's wrong with Vim? Why don't
we simply
On Mon, Jan 4, 2010 at 3:48 PM, Lennart Poettering
lenn...@poettering.net wrote:
The problem of course is that the tts daemon needs to watch this too
and not choke if the device access to that soft_synth device goes
away.
Ok, so I could modify both espeakup and speechd-up to use udev and
deal
On Mon, Jan 4, 2010 at 4:01 PM, Lennart Poettering
lenn...@poettering.net wrote:
If you feel the need to support multiple alternative solutions for the
same problem and effectively double your maintainance work you are
welcome to do so, but that's your choice, and hence it is *your* job
to
On Mon, Jan 4, 2010 at 4:03 PM, Lennart Poettering
lenn...@poettering.net wrote:
They wouldn't have to link to udev at all. As mentioned they should
simply use inotify() and access() to minitor devices access coming and
going on /dev/soft_synth.
Got it. That makes it clearer.
On Mon, Jan 4, 2010 at 4:38 PM, Lennart Poettering
lenn...@poettering.net wrote:
Dude, if you as your questions on the ML while everyone is on
christmas/new year holidays, you cannot expect immediate and
comprehensive replies.
Well, for that I apologize. If you want to see a socially
Hi, Colin. I like your proposal, but I think I'd like to implement it
in two phases. I'd like to skip step 1 for now, and not deal wit CK,
but as you say, make speechd-up headless, and write the PA modules
you suggest to pipe sound from speechd-up. CK isn't working properly
with PA in Ubuntu
On Sun, Jan 3, 2010 at 12:39 PM, Halim Sahin halim.sa...@freenet.de wrote:
Here are my thoughts about pulse:
Ok This will my last post in this thread
I can put in a good word for Halim. He's been very helpful in the
last several weeks working out issues with Orca and the back end sound
I've removed gdm from my Lucid system, after Tony Sales
(founder/driver of Vinux) suggested it. I'm already feeling rather
attached to my gdm-less system. It now boots into a very nicely
talking console login prompt. I just login, do whatever I like on the
console, and type 'startx' if I want
can use it.
If this is acceptable, I volunteer to write it.
Thanks,
Bill
On Sat, Jan 2, 2010 at 8:17 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Bill Cox at 01/01/10 21:58 did gyre and gimble:
However, even with these changes, there are bugs due to pulseaudio's
user-based
use of the mic?
Adding such hooks, or using existing ones sounds very promising to me,
though I'm nearly 100% ignorant currently of CK.
Bill
On Sat, Jan 2, 2010 at 10:01 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Bill Cox at 02/01/10 14:20 d isid gyre and gimble:
Hi, Colin
Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Bill Cox at 02/01/10 15:03 did gyre and gimble:
Hi, David.
On Sat, Jan 2, 2010 at 1:08 AM, David Henningsson
launchpad@epost.diwic.se wrote:
I was just thinking, and this idea is perhaps not 100% thought through,
but it could be worth
-dispatchers conflict on the port. But, it should not be a
problem restarting these deamons as needed. If the audio card leaves,
there's no reason to have these processes hanging around.
Bill
On Sat, Jan 2, 2010 at 4:47 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Bill Cox at 02/01/10
I spent a few hours trying to figure out how well this scheme could
work for Ubuntu/Lucid. Things are in bad shape. Speakup basically is
incompatible with PA on Lucid for now. The problems seem to come from
multiple PA instances not sharing properly. If you switch-user to a
new user on Karmic
Sorry... my laptop has a tendency to accidentally click, and I sent
that last e-mail unfinished.
Anyway, I don't believe I've evern seen multiple copies of PA running
in Ubuntu work properly together, and the open bug about this on
bugs.launchpad.net has had no progress or interest. If I write
there every get hacked because you shared the Alsa back-end
with another user? Anyone?
Thanks,
Bill
On Thu, Dec 31, 2009 at 12:27 PM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Bill Cox at 31/12/09 17:13 did gyre and gimble:
Thanks for the info. Is there a simple way to kill
No, the problem happens when I switch to a new user.
On Fri, Jan 1, 2010 at 5:08 PM, Daniel Chen seven.st...@gmail.com wrote:
On Fri, Jan 1, 2010 at 4:58 PM, Bill Cox waywardg...@gmail.com wrote:
However, even with these changes, there are bugs due to pulseaudio's
user-based structure. Today
On Thu, Dec 17, 2009 at 4:52 AM, Lennart Poettering
lenn...@poettering.net wrote:
I don't see why anyone would want to have audio when changing to root
for admin purposes. Playing music certainly does not fall under admin
purposes.
Ever consider what happens when a blind user switches to root,
On Wed, Dec 23, 2009 at 6:57 AM, Lennart Poettering
lenn...@poettering.net wrote:
And this is the problem because it works with alsa, simply add every
user you want to give audio access to the audio group and it worked.
Even with OSS this worked. But PA breaks this behaviour.
First of all, we
On Wed, Dec 23, 2009 at 9:13 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Halim Sahin at 23/12/09 13:24 did gyre and gimble:
The Problem can be summarized in one sentence:
Pulseaudio currently breaks multiuser systems and is only useful for
one-user-desktop.
Actually no,
On Thu, Dec 24, 2009 at 11:14 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Markus Rechberger at 24/12/09 14:02 did gyre and gimble:
I think it's pretty clear what the problem is.
PA does not support multiple users on one system..
I told you if you intend to replace the
On Thu, Dec 24, 2009 at 11:29 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 23.12.09 15:26, Halim Sahin (halim.sa...@freenet.de) wrote:
Hi Col,
1. I gave you some examples what doesn't work as expected.
How should I run my text-to-speech server before login to have
On Thu, Dec 24, 2009 at 12:27 PM, Lennart Poettering
lenn...@poettering.net wrote:
We actually cover that inside of gdm, where you can get access to the
boot messages.
Lennart
Speakup doesn't stop reading when the user logs into Gnome. When we
type Ctrl+Alt+F1, we get a console screen which
I am trying to get Ubuntu/Lucid working well with applications for the
blind and visually impaired. Orca is working quite well now with
pulseaudio. The other critical application is speakup, which reads
text on the Ctrl+Alt+F1-6 consoles. Speakup has issues with
pulseaudio, and I need some
at the console until I log in.
There is also no audio at the gnome login. Grr...
Isn't there any way to get audio working before a user logs in?
Bill
On Thu, Dec 31, 2009 at 10:34 AM, Bill Cox waywardg...@gmail.com wrote:
I am trying to get Ubuntu/Lucid working well with applications for the
blind
Thanks for the info. Is there a simple way to kill off the gdm
pulseaduio when the user logs in? Some sort of hook I can tie into?
Thanks,
Bill
On Thu, Dec 31, 2009 at 11:26 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
'Twas brillig, and Bill Cox at 31/12/09 16:07 did gyre and gimble
Since I didn't get much response with my more polite e-mail, here's
what I really think, given my current ignorance about pulseaudio...
PulseAudio is cool, but I fear it's over-engineered by some Ph.D's
with too much elegance in their solution, and not enough real world
experience. Run as user?
I wrote a super-simple test using the pa_simple API. I have some
sound data in a static array. I call getchar(), and then call
pa_simple_write, in an infinite loop. When I run this, and just hit
enter several times, I expect to hear the sound played once each time
I press enter. Instead, it
Blind/VI users of Ubuntu Jaunty, Karmic, and now Lucid alpha1 find
their linux machine close to unusable. The reason is that there is
about a 1/2 second delay between pressing a key and hearing any
feedback. As a result 100% of blind/VI users who use Ubuntu as their
primary machine disable
I downloaded from git the latest pulseaudio repository and recompiled
on Ubntu Lucid. The speech performance is excellent! There are
several goobers that we already had when disabling pulseaudio: the
volume control disappears, the volume starts muted after boot, and I'm
sure the other usual
55 matches
Mail list logo
