At Fri, 30 Apr 2010 08:44:24 -0500,
pl bossart wrote:
>
> >> I am aware that some changes would be needed in pcm_lib.c, where all
> >> the error checks are done.
> >
> > Plus all the API changes in the ALSA kernel framework, the ALSA kernel/
> > userspace interface, and the alsa-lib interface.
>
Lennart Poettering wrote:
On Wed, 23.01.08 14:36, Hynek Hanke ([EMAIL PROTECTED]) wrote:
Hi!
please, I just want to ask if there is some Python programming interface
to PulseAudio or some bindings for the C library that one could use?
I (as the maintainer of PA) am not aware of any such
Daniel Chen gmail.com> writes:
>
> Are you actually using rtp actively? If not, disable it.
Well, after things have settled down (see below) it's only using about 10% of
the
CPU, about 5% each for making audio devices available to the network and for
using audio devices from the network. I
On Fri, May 14, 2010 at 12:57 PM, Brian J. Murrell
wrote:
> This didn't resolve the issue...
>
>> or
>> linux-alsa-driver-modules-$(uname -r) from ppa:ubuntu-audio-dev.
>
> But this did.
>
> Given that this was the solution in Karmic too, I'm wondering why, whatever
> installing this packages fixe
Paul Menzel users.sourceforge.net> writes:
>
> You already posted the same question to the list four weeks ago [1].
Yes, it would seem you are correct. That was about a different release of
Ubuntu. I had hoped that "third party" pieces that I had to gather together at
that time to get a sys
Paul Menzel users.sourceforge.net> writes:
>
> Did you try to record something or use the microphone?
No.
> Maybe it is related to ticket #758 [1] which commit [2][3][4] in ALSA
> fixed for me kind of. What CODEC chip do you have in your system?
Is this the answer to that question:
[31738.770
Daniel Chen gmail.com> writes:>
>
> Considering just the Lucid case, the fix for this symptom was only
> committed Tuesday, so I don't think it conceivably could have made it
> into Lucid.
Well, I suppose that's fair enough. I had just figured that since the same
procedure fixed the same pro
On 05/12/2010 03:54 AM, Antoine Martin wrote:
On 05/12/2010 03:48 AM, Antoine Martin wrote:
On 05/11/2010 11:29 PM, Tanu Kaskinen wrote:
On Tue, 2010-05-11 at 12:21 +0700, Antoine Martin wrote:
Add-to-wishlist: ability to use codecs here would be nice. I doesn't
look like I can use ladspa
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 Luc
Hi Bill
On Fri, May 14, 2010 at 03:19:32PM CEST, Bill Cox wrote:
> My question is: should I enable this by default for all Vinux users?
> Vinux is slightly modified Ubuntu Lucid for the blind. If I install
> this on the Vinux ISO, will users automatically get upgraded
> linux-alsa-driver-modules w
On Fri, May 14, 2010 at 3:19 PM, Bill Cox wrote:
> My question is: should I enable this by default for all Vinux users?
I strongly recommend against doing so. These are daily builds of
alsa-driver that track the daily stable snapshots in Takashi's web
space on kernel.org. And, as Luke notes previ
> The biggest problem I can foresee is the handling of PCM position.
> In the current implementation, the PCM position continues to go over
> the buffer size until the certain boundary that is close to long int
> max. Without interrupts (i.e. snd_pcm_period_elapsed()), this
> position update won't
Lennart Poettering wrote:
On Wed, 23.01.08 14:36, Hynek Hanke ([EMAIL PROTECTED]) wrote:
Hi!
please, I just want to ask if there is some Python programming interface
to PulseAudio or some bindings for the C library that one could use?
I (as the maintainer of PA) am not aware of any suc
Ok. Thanks for the feedback.
Bill
On Fri, May 14, 2010 at 9:27 AM, Daniel Chen wrote:
> On Fri, May 14, 2010 at 3:19 PM, Bill Cox wrote:
>> My question is: should I enable this by default for all Vinux users?
>
> I strongly recommend against doing so. These are daily builds of
> alsa-driver th
Hello,
I'm new on this mailing-list. I tried asking this question on
general-purpose forums, but I realise this is too specific. I hope this
place is better suited.
I have my own server. And I thought it would be nice to have this server
hooked up to the HiFi, and thus enable any PC on the L
Here is my latest set of patches before I forget about them.
Still some work to be done on the alsa-lib one, for some reason the
hw_param->flags field I used gets overwritten if I don't use the
hw_device. I suspect this is due to some black magic with the
pcm->hw_flags when slave devices are used.
On Wed, May 12, 2010 at 12:21 PM, Rafal Wojtczuk <
ra...@invisiblethingslab.com> wrote:
> On Sun, May 09, 2010 at 09:24:27AM +0300, Marco Ballesio wrote:
> > On Fri, Apr 23, 2010 at 6:10 PM, Rafal Wojtczuk <
> ra...@invisiblethingslab.com> wrote:
> > > Again, can I have a simple sound sharing over
Hi,
as I posted a couple of threads ago, an example through GStreamer can be
found here (two-liner, one on server and one on client) without the need for
a proper server:
http://www.gstreamer.net/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-gstrtpbin.html
The on
Hi Lennart,
I'm afraid this is getting lost. Can you apply?
Thanks,
Daniel
On Fri, Mar 19, 2010 at 05:32:21PM +0100, Daniel Mack wrote:
> All API calls are now consolidated in AudioObject* calls, the old model
> has been deprecated in 10.6. Follow that change.
> ---
> src/modules/coreaudio/modu
19 matches
Mail list logo
