Re: [pulseaudio-tickets] [PulseAudio] #771: RAOP streams are delayed
#771: RAOP streams are delayed -+-- Reporter: takkat | Owner: coling Type: defect | Status: new Milestone: | Component: module-raop-* Resolution: |Keywords: streaming airport express -+-- Changes (by Chris56): * cc: c.hems...@gmx.net (added) * type: enhancement = defect Comment: Will there ever be any work done on this problem? I would rather call it a defect than an enhancement. With the 5 secs of delay that I observe seeking within some music is almost impossible...at least a nuisance. I must say I have no idea of the internals of Airport Express music handling. However, I discovered, that as soon as I enable the iTunes option, a permanent! stream of 200 KBytes/sec is being transmitted to the Airport Express. Given both wlan connections (computer-router, router- Airport) this chews up 400KBytes of (limited) wlan bandwith for silence. Is this the way it should be?? Chris -- Ticket URL: http://pulseaudio.org/ticket/771#comment:4 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #771: RAOP streams are delayed
#771: RAOP streams are delayed -+-- Reporter: takkat | Owner: coling Type: defect | Status: new Milestone: | Component: module-raop-* Resolution: |Keywords: streaming airport express -+-- Comment(by coling): What it's labelled as really has no bearing whatsoever so feel free to call it what you want :) It is fully intensional that the silence is transmitted as without it, the APEX gets into a strange state and we can no longer reconnect to it without restarting PA. Even unloading and reloading the module isn't enough. It's all rather strange. So sending silence keeps the connection open and thus allows us to use it. Also the timing methodology is totally basic. It uses the buffer of the APEX itself to implement flow control where as we should really be feeding it data in real time. This is all complex stuff. There is also a much more accurate timing model available in the Airtunes v2 protocol, but it's not fully understood or reverse engineered yet. Some work has been done to get it working but the results still cause choppy sound at present. It's all work in progress, but as a lot of it is guess work it's a very slow process. If you'd like to help out with reverse engineering the protocol and such like, please let me know and I'll put you in touch with the right people. -- Ticket URL: http://pulseaudio.org/ticket/771#comment:5 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #771: RAOP streams are delayed
#771: RAOP streams are delayed --+- Reporter: takkat | Owner: coling Type: enhancement | Status: new Milestone: | Component: module-raop-* Resolution: |Keywords: streaming airport express --+- Comment(by bendavis78): I get about a 7-8 second delay here. Would be awesome if this could be fixed! -- Ticket URL: http://pulseaudio.org/ticket/771#comment:3 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
Re: [pulseaudio-tickets] [PulseAudio] #771: RAOP streams are delayed
#771: RAOP streams are delayed --+- Reporter: takkat | Owner: coling Type: enhancement | Status: new Milestone: | Component: module-raop-* Resolution: |Keywords: streaming airport express --+- Comment(by coling): Yeah this is a known limitation of the driving code just now. Volume changes are passed over a control channel to the device so are acted on immediately even if the device has a full buffer. If the app in question is clever, it passes on the volume changes to lower down the stack the change will be immediate but if it attenuates the data it's sending out it will have the delay. I'll be fixing this at some point when I rewrite the timing code. Just finding it hard to find the time for that as it's a rather complex process. -- Ticket URL: http://pulseaudio.org/ticket/771#comment:1 PulseAudio http://pulseaudio.org/ The PulseAudio Sound Server ___ pulseaudio-tickets mailing list pulseaudio-tickets@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
