Re: [pulseaudio-discuss] several seconds delay while playing video with timer-based audio scheduling enabled
Trying paplay, it has the same result, then I think it has nothing to do with the video player. Thanks vivian -Original Message- From: pulseaudio-discuss-boun...@mail.0pointer.de [mailto:pulseaudio-discuss-boun...@mail.0pointer.de] On Behalf Of xing wang Sent: Friday, May 06, 2011 11:38 AM To: General PulseAudio Discussion Subject: Re: [pulseaudio-discuss] several seconds delay while playing video with timer-based audio scheduling enabled 2011/5/5 xing wang wangxingchao2...@gmail.com: 2011/5/5 Colin Guthrie gm...@colin.guthr.ie: 'Twas brillig, and xing wang at 05/05/11 10:24 did gyre and gimble: Hi community, I met a weird issue when playing video on Meego Platform. if turn on timer-based audio scheduling, there's nearly seconds voice delay during playing video. The abnormal phenomenon disappeared after turn it off. I use 2.6.37 kernel and 0.9.22 pulseaudio version. As suggestions (http://0pointer.de/blog/projects/pulse-glitch-free.html) the pulseaudio's glitch-free works on newest Alsa/Kernel/Pulseaudio, newest everything. After some google search, there's no obvious finding about similar issues. Meanwhile i guess the official release of glitch-free must be verified about tsched feature, so it's not a bug but a usage mistake,such as some config file wrong for my platform. So if anyone had meet same issue or could you provide some suggestions, that would be appreciated much. What video player is being used? It is perhaps making some really dumb assumptions about things and thus breaking (and using too much power too!) It's Meego default player meego-qml-launcher. Maybe wrong here. Qml-launcher is only one app launcher, the exact app name is meego-app-video, it's one QML based application. --xingchao Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] start-pulseaudio-x11 failed
Hi, all: Has anyone met the issue on start-pulseaudio-x11(pulseaudio-0.9.21). When running start-pulseaudio-x11, the pulseaudio daemon will terminated after a while. The error info it reported: Alsa-source.c: Device suspended... Core.c: We are idle, quitting... Main.c: Daemon shutdown initiated. Module.c: Unloading module-device-restore... And I tried to comment out #/usr/bin/pactl load-module module-x11-publish display=$DISPLAY /dev/null #/usr/bin/pactl load-module module-x11-cork-request display=$DISPLAY /dev/null The pulseaudio daemon can be launched successfully. Any comments on this? Best Regards, vivian ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] start-pulseaudio-x11 failed
Yeah, there is no session manager running in my X session. Thanks for your quick reply, it helps a lot. Thanks --vivian -Original Message- From: pulseaudio-discuss-boun...@mail.0pointer.de [mailto:pulseaudio-discuss-boun...@mail.0pointer.de] On Behalf Of Colin Guthrie Sent: Thursday, February 04, 2010 5:37 PM To: pulseaudio-discuss@mail.0pointer.de Subject: Re: [pulseaudio-discuss] start-pulseaudio-x11 failed 'Twas brillig, and Zhang, Vivian at 04/02/10 08:43 did gyre and gimble: Has anyone met the issue on start-pulseaudio-x11(pulseaudio-0.9.21). When running start-pulseaudio-x11, the pulseaudio daemon will terminated after a while. It smells like you've not got a session manager running in your X session. Check the script and see the bit where it checks for $SESSION_MANAGER If this module fails to load then PA will honour the idle timeouts (this is perfectly normal - PA is designed to exit after a period of inactivity) as the session manager connection will not keep PA alive. PA should autospawn again, but it wont support the x11 root window property setting and thus wont support piggy backing on top of SSH's X11 forwarding. Hope this helps. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] RTP receiver problem, jumpy samplerate
Erich Boleyn wrote: [Ed note: Just scanned pulseaudio list today after a bit of haitus and noticed a few messages about RTP issues, comments below] Zhang, Vivian vivian.zh...@intel.com wrote: Nickie Deuxyeux wrote: Hello everyone, I am struggling to make my simple RTP setup work correctly. I have one sender and one receiver, both running the latest pulseaudio 0.9.15. Normal module-native-protocol-tcp works fine with pulseaudio client (I am using mplayer to test) running from the sender side, but when I start the pulseaudio server on the sender side and start the receiver side, I have the following output: I also met the same issue on PA 0.9.15, :( Anyone works fine with rtp module or has some ideas about it? I use Pulseaudio and RTP in my home for audio through 5 rooms and 7 machines total. The current RTP code uses resampling based on instantaneous feedback from the buffer levels and assumptions of the current time. To work correctly without continuous audible distortion, it really requires the glitch-free mode to be enabled and active on a machine with basically no load. Even then I have found it is troublesome. I currently have resampling disabled via a trivial patch, but never contributed it to the list because the goal is to fix the resampler control algorithm in RTP. Not being able to run the same remote audio on any 2 sets of speakers because they drift apart is really annoying. I have a bug opened in the pulseaudio.org bugtracker (#477) at: http://www.pulseaudio.org/ticket/477 My Wife has let me know it can't persist in this state, and I just got a bit of free time to rub together, so the next 2 weekends are allocated for working on this and putting a proper debouncing algorithm into the resampler control logic in module-rtp-recv. Please check out my comments in the bug ticket and/or email me directly if you are interested. Current estimate is that it will be probably next weekend before I have a robust fix, but possible that this weekend will do it. Unfortunately ahead of that is patching the ALSA 1.0.19 drivers to backport the fix which was recently found for the hda-intel snd_pcm_avail bug(s). Pulse keeps crashing on the 2 machines with hda-intel sound hardware right now, also a wife-friendliness problem. :-P None of the patches applied cleanly, so I'm having to reverse-engineer the changes between 1.0.19 and ALSA git-current. In any case, I'll post that to this list as well when I get it done. Hi, Erich: Thanks for your explanation. Any update for fixing RTP issues? It really blocked some of our works. Or could you send me the trivial patch for disabling resampling, then we can have a quick fix, thanks a lot. Thanks. -- vivian ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] The usage of RTP modules
Hi: I am trying module-rtp* of pulseaudio but got a bad latency and glitchy audio. Here are the steps I did: 1. Loaded module for RTP: load-module module-null-sink sink_name=rtp load-module module-rtp-send loop=1 source=rtp.monitor load-module module-rtp-recv 2. Set default sink to rtp and then run speaker-test -c2. 3. Checked the result: read the pa log (the log is attached) and tried to capture the UDP packages it sent. module-rtp-send.c reported warnings: Failed to push chunk into memblockq. Are there any other configurations I should do to make the RTP work ok? Any comments are welcomed. :) Thanks. -- vivian pu.log Description: pu.log ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Time of the final 0.9.15 release
Hi Lennart: Very glad that you are approaching the final 0.9.15. We plan to use PA 0.9.15 in the alpha release of our distribution, the time is March 20. Since some of our projects' development are based on PA 0.9.15, do you have the clear schedule for the final release of 0.9.15. It will be a great help if we can have the stable release of PA 0.9.15 before our alpha. :) -- Thanks. Zhang Vivian Intel(SSG/OTC) China ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
