Hi,
I'm trying to configure xineliboutput 1.0.3 with VDR 1.7.1. Compilation and installation seems to go ok, but playback doesn't work. I can see OSD in opened window, but when it gets to the channel itself CPU usage jumps to 100% and the log contains:
Nov 30 01:24:17 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:17 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (185008 bytes) ! Nov 30 01:24:17 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (185008 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:17 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:17 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (192000 bytes) ! Nov 30 01:24:17 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (192000 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:18 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:18 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (243888 bytes) ! Nov 30 01:24:18 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (243888 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:18 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:18 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (260816 bytes) ! Nov 30 01:24:18 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (260816 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:19 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:19 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (245728 bytes) ! Nov 30 01:24:19 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (245728 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:19 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:19 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (242416 bytes) ! Nov 30 01:24:19 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (242416 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:20 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:20 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (249776 bytes) ! Nov 30 01:24:20 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (249776 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:20 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:20 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (257320 bytes) ! Nov 30 01:24:20 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (257320 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:21 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:21 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (268176 bytes) ! Nov 30 01:24:21 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (268176 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:21 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:21 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (268912 bytes) ! Nov 30 01:24:21 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (268912 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:22 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:22 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (237632 bytes) ! Nov 30 01:24:22 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (237632 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:22 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data ! Nov 30 01:24:22 htpc vdr: [13512] [input_vdr] get_buf_element: jumbo PES (215000 bytes) ! Nov 30 01:24:22 htpc vdr: [13512] [input_vdr] vdr_plugin_write: PES too long (215000 bytes, max size 8192 bytes), data ignored ! Nov 30 01:24:23 htpc vdr: [13512] [xine..put] cXinelibDevice::PlayAny: invalid data !
Any ideas?
Thanks.
-----Oorspronkelijk bericht----- Van: alex.betis@gmail.com [mailto:vdr-bounces@linuxtv.org] Namens Alex Betis Verzonden: zaterdag 29 november 2008 22:31 Aan: vdr@linuxtv.org Onderwerp: [vdr] xineliboutput - invalid data
Hi,
I'm trying to configure xineliboutput 1.0.3 with VDR 1.7.1. Compilation and installation seems to go ok, but playback doesn't work. I can see OSD in opened window, but when it gets to the channel itself CPU usage jumps to 100% and the log contains:
-- SNIP -- Any ideas?
You have two options:
- Go back to 1.7.0; - Use the LIVEBUFFER patch by patching VDR 1.7.1 with the VDR-Extensions patch;
See http://linuxtv.org/pipermail/vdr/2008-October/017948.html for more information.
Thanks.
Regards,
Niels Wagenaar
On Sat, Nov 29, 2008 at 11:47 PM, Niels Wagenaar n.wagenaar@xs4all.nlwrote:
You have two options:
- Go back to 1.7.0;
- Use the LIVEBUFFER patch by patching VDR 1.7.1 with the VDR-Extensions
patch;
See http://linuxtv.org/pipermail/vdr/2008-October/017948.html for more information.
Thank you Niels. Looks like it works.
Few questions: Does you (or anybody) know where I can find explanation of every module in that extension pack in English? For an average SD channel, how long the default 5MB buffer of LIVEBUFFER can store the data? What happen when the buffer is full? Old data is discarded or the new data is ignored?
Thanks.
On Sun, Nov 30, 2008 at 10:36 PM, Alex Betis alex.betis@gmail.com wrote:
On Sat, Nov 29, 2008 at 11:47 PM, Niels Wagenaar n.wagenaar@xs4all.nlwrote:
You have two options:
- Go back to 1.7.0;
- Use the LIVEBUFFER patch by patching VDR 1.7.1 with the VDR-Extensions
patch;
See http://linuxtv.org/pipermail/vdr/2008-October/017948.html for more information.
Thank you Niels. Looks like it works.
Few questions: Does you (or anybody) know where I can find explanation of every module in that extension pack in English? For an average SD channel, how long the default 5MB buffer of LIVEBUFFER can store the data? What happen when the buffer is full? Old data is discarded or the new data is ignored?
Two more questions... :)
In channels list I see an unknown character before the channel name (for me it looks like a square. It appeared after the extension patches. Anyone knows how to get rid of it?
I remember long ago when watching channels that were recorded (or probably time shifted) on the disk I saw a bar that shows the location in the buffer. Anyone knows if its possible to see that bar for LIVEBUFFER shifting?
Thanks.
-
Alex Betis -
Niels Wagenaar