Re: [pulseaudio-discuss] Documentation update?

2008/5/6 Lennart Poettering <[EMAIL PROTECTED]>: > On Wed, 30.04.08 13:56, Nikolai Beier ([EMAIL PROTECTED]) wrote: > > > Hello all. > > > > I noticed that http://pulseaudio.org/wiki/Modules mentions the module > > "module-detect" is mentioned two time. Perhaps the two entries should > > just

Re: [pulseaudio-discuss] Moving sources and sinks

On Sun, 04.05.08 14:15, Tanu Kaskinen ([EMAIL PROTECTED]) wrote: > > On Sat, May 03, 2008 at 04:48:05PM -0700, Nick Thompson wrote: > > Given what you say (above) about per device routing not being possible I > > think the area I'd like to concentrate on is figuring out how a module > > can det

Re: [pulseaudio-discuss] Moving sources and sinks

On Sat, 03.05.08 23:55, Tanu Kaskinen ([EMAIL PROTECTED]) wrote: > > Phew. Anyway the second question was not really answered fully. It > > might be my imprecision in stating the problem so let me try to > > distill it to the bare bones: For pulseaudio I'd like to know how or > > if a vir

Re: [pulseaudio-discuss] Moving sources and sinks

On Sat, 03.05.08 11:48, Nick Thompson ([EMAIL PROTECTED]) wrote: > fully accept that my use of pulse might be somewhat unorthodox since > it is in a speciailsed embedded system, however I also think that > multiple device support and routing is of great interest, especially > to the music co

Re: [pulseaudio-discuss] Pulse module development

On Tue, 06.05.08 01:32, Colin Guthrie ([EMAIL PROTECTED]) wrote: > Your approach is not really the recommended one. The pulsecore API is > not stable and as such isn't installed. > > If you are doing module development, the recommended method is to build > it within the pulse tree itself. Simpl

Re: [pulseaudio-discuss] Moving sources and sinks

On Fri, 02.05.08 11:27, Matt Patterson ([EMAIL PROTECTED]) wrote: > So I think what I would do is make a "combined" sink for each class of data > that routes all audio to all sources. If you disable the module to gets rid > of idle streams this will leave you with active but corked streams to al

Re: [pulseaudio-discuss] Moving sources and sinks

On Fri, 02.05.08 11:01, Nick Thompson ([EMAIL PROTECTED]) wrote: > > > Awesome Matt, if you can share your source I would love to see it. > > What you are doing sounds interesting. > > For my app I'd like to have two classes of data. For arguments sake > these are "normal" and "alert". Nor

Re: [pulseaudio-discuss] Moving sources and sinks

On Fri, 02.05.08 10:37, Matt Patterson ([EMAIL PROTECTED]) wrote: > I do agree that coding for pulse can be a steep learning curve, which is > why I opted to build all my solutions by simply connecting to the text mode > control socket and sending commands/parsing text output. I have built what

Re: [pulseaudio-discuss] Moving sources and sinks

On Fri, 02.05.08 10:20, Nick Thompson ([EMAIL PROTECTED]) wrote: > OK so I figured out the error of my ways, but I have to say this list is > pretty unresponsive in helping the community so I have to ask myself "is > pulse is a sensible choice for audio development today"? Particularly > sinc

Re: [pulseaudio-discuss] Pulse module development

Nick Thompson wrote: > On the page on the wiki about developing modules at: > > > > There's a nifty little tutorial on writing a plugin. Handy stuff. > The pulsecore headers are all referenced with prefix "pulsecore", as in: > > #include > > I fi

Re: [pulseaudio-discuss] Documentation update?

On Wed, 30.04.08 13:56, Nikolai Beier ([EMAIL PROTECTED]) wrote: > Hello all. > > I noticed that http://pulseaudio.org/wiki/Modules mentions the module > "module-detect" is mentioned two time. Perhaps the two entries should > just be merged? I guess you already noticed that the site is a wiki an

[pulseaudio-discuss] Pulse module development

On the page on the wiki about developing modules at: There's a nifty little tutorial on writing a plugin. Handy stuff. The pulsecore headers are all referenced with prefix "pulsecore", as in: #include I fished around for any pulse related -dev pk

Re: [pulseaudio-discuss] pulseaudio on maemo/n800

On Tue, 29.04.08 22:48, Colin Guthrie ([EMAIL PROTECTED]) wrote: > > Kwan Hong Lee wrote: > > The files /var/run/pulse nor /tmp/pulse-user are not created at all. I > > manually create them, but that does not help either. > > > > Maybe it's because it's tmpfs. Is there any way to change this?

Re: [pulseaudio-discuss] pulseaudio on maemo/n800

On Tue, 29.04.08 11:59, Jim Carter ([EMAIL PROTECTED]) wrote: > > > user$ pulseaudio > > > W: core-util.c: setpriority(): Permission denied > > > E: main.c: Failed to create '/tmp/pulse-user': Permission denied > > > > Can you create the folder /tmp/pulse-user yourself? Can you chown and > > chmo

Re: [pulseaudio-discuss] SHM Error Messages

On Sun, 20.04.08 21:04, Jim Duda ([EMAIL PROTECTED]) wrote: > I don't know what I have done now, but suddenly sound stopped working on > my desktop fc8 computer. I must have changed some setting ... > > I'm getting this message in /var/log/messages whenever I try to play > anything. Can anyon

Re: [pulseaudio-discuss] Re : Effects of Clock Resolution on Pulseaudio

On Fri, 18.04.08 17:12, DSK ([EMAIL PROTECTED]) wrote: > > Most likely someone needs to spend some time to optimize the inner > > loops (mixing, resampling, converting) a bit better for ARM. > > Well the observations taken are when a single 44K file is being played with > pacat .. (so no resamp

Re: [pulseaudio-discuss] Uber-early glitch-free Testing Results

On Wed, 16.04.08 16:13, Sean McNamara ([EMAIL PROTECTED]) wrote: > * PA should not run with --system (as 'pulse' user) because you > can't use SHM transfer, you have to tweak PolicyKit to allow real-time > scheduling to the 'pulse' user, and because you have to add all > desired users (of the

Re: [pulseaudio-discuss] Can I mute rtp-recv somehow?

On Sun, 13.04.08 17:36, Jim Duda ([EMAIL PROTECTED]) wrote: > Is there a method I can use to mute the audio coming into a server via > rtp-recv? Turn down the volume of all RTP streams with pavucontrol. Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering

Re: [pulseaudio-discuss] PulseAudio with Motif?

On Mon, 14.04.08 15:45, Rémi Cardona ([EMAIL PROTECTED]) wrote: > >> You should, however, *NOT* only implement a pulse backend in your > >> application. Put an abstraction layer in between to allow to add > >> direct ALSA and ESD access, too. > > > > If I wanted to do that, I would have kept SDL.

Re: [pulseaudio-discuss] PulseAudio with Motif?

On Mon, 14.04.08 14:17, Michel Bardiaux ([EMAIL PROTECTED]) wrote: > > See the point? There's no connection between Pulseaudio (specifically > > its client library) and a given widget set. > > Actually, there is. I had done some amount of research, and had looked > at the sample clients on puls

Re: [pulseaudio-discuss] PulseAudio with Motif?

On Tue, 08.04.08 17:58, Michel Bardiaux ([EMAIL PROTECTED]) wrote: > > Michel Bardiaux wrote: > > Any example using PulseAudio for sound and Motif (or Athena) for GUI? > > > > TIA, > > Pretty please? > > I would really like to add networked audio capability to my > applications, but finding o

Re: [pulseaudio-discuss] Controlling pulseaudio daemon via dbus

On Mon, 31.03.08 13:24, Turner, Todd ([EMAIL PROTECTED]) wrote: > Hi All, > > Are there any plans for a dbus module? I see that PA uses dbus to > connect to policy kit, and that there are dbus-util.c file in the > modules package that appears to be for modules to connect to other > services li

Re: [pulseaudio-discuss] alsa pulse bugs

On Mon, May 05, 2008 at 12:22:10PM +0200, [EMAIL PROTECTED] wrote: > Quoting Colin Guthrie <[EMAIL PROTECTED]>: > > Actually just having a very quick glance at the Alsa API docs, it > > doesn't mention that this value should be 0 if there are no samples to play: > > > > http://www.alsa-project.org/

Re: [pulseaudio-discuss] alsa pulse bugs

[EMAIL PROTECTED] wrote: >> http://www.alsa-project.org/alsa-doc/alsa-lib/group___p_c_m.html#ga0d9e14a4be65209eb549e48a9f07302 >> >> Closest it says is: "It's positive and less than buffer size in normal >> situation". >> >> So perhaps this is an invalid assumption at the wine side? > > However th

Re: [pulseaudio-discuss] alsa pulse bugs

Quoting Colin Guthrie <[EMAIL PROTECTED]>: > Actually just having a very quick glance at the Alsa API docs, it > doesn't mention that this value should be 0 if there are no samples to play: > > http://www.alsa-project.org/alsa-doc/alsa-lib/group___p_c_m.html#ga0d9e14a4be65209eb549e48a9f07302 > > Cl

Re: [pulseaudio-discuss] alsa pulse bugs

Colin Guthrie wrote: > [EMAIL PROTECTED] wrote: >>> Re the snd_pcm_delay() including network latency (#3945), this clearly >>> makes sense for network streams. Does you proposed fix include this >>> delay (albeit with the improvement that it also will drop to 0 if there >>> are no samples queued)?

Re: [pulseaudio-discuss] alsa pulse bugs

Quoting Colin Guthrie <[EMAIL PROTECTED]>: Attached patches to #3943 and #3944. Please read the comments there. > [EMAIL PROTECTED] wrote: >>> Re the snd_pcm_delay() including network latency (#3945), this clearly >>> makes sense for network streams. Does you proposed fix include this >>> delay (

Re: [pulseaudio-discuss] alsa pulse bugs

[EMAIL PROTECTED] wrote: >> Re the snd_pcm_delay() including network latency (#3945), this clearly >> makes sense for network streams. Does you proposed fix include this >> delay (albeit with the improvement that it also will drop to 0 if there >> are no samples queued)? > > snd_pcm_delay() should

Re: [pulseaudio-discuss] alsa pulse bugs

Quoting Colin Guthrie <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] wrote: >> I reported three bugs to the alsa bugtracker: >> >> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3942 >> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3943 >> https://bugtrack.alsa-project.org/alsa-bug/view

Re: [pulseaudio-discuss] alsa pulse bugs

[EMAIL PROTECTED] wrote: > I reported three bugs to the alsa bugtracker: > > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3942 > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3943 > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3944 > > It's three bugs after all. Once

[pulseaudio-discuss] alsa pulse bugs

I reported three bugs to the alsa bugtracker: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3942 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3943 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3944 It's three bugs after all. Once these are fixed I expect Wine to work.