Does anyone know whether the eepg plugin should "just work" with the Huffman encoded EPG broadcast on Freeview (DVB-T) HD channels in the UK? (Someone mentioned it on here a week or so back.)
I'm pretty sure the EPG data is encoded in exactly the same way as it is on Freesat, i.e. DVB-S, and eepg can decode that EPG. I'm trying to work out whether it should currently be able to do it (and I need to configure something before it'll work), or whether I should try to add support for it. A quick scan of the source code looks like the terms "freesat" and "freeview" are used interchangably in it.
Currently, I have completely garbled EPG on HD channels! I can add decoded EPG grabbed via xmltv but the EPG gets overwritten with the garbled version.
(What's vdr's policy on EPG data added through SVDRP, etc., being overwritten by data from the EIT?)
Cheers,
Laz
Am 21.08.2011 23:09, schrieb Laz:
Does anyone know whether the eepg plugin should "just work" with the Huffman encoded EPG broadcast on Freeview (DVB-T) HD channels in the UK? (Someone mentioned it on here a week or so back.)
Yes, it does (next DW already programmed). In a recent version Freesat huffman decoding has been destroyed, in the most recent version this should have already been fixes.
- M.
On Thursday 25 Aug 2011, Mario Schulz wrote:
Am 21.08.2011 23:09, schrieb Laz:
Does anyone know whether the eepg plugin should "just work" with the Huffman encoded EPG broadcast on Freeview (DVB-T) HD channels in the UK? (Someone mentioned it on here a week or so back.)
Yes, it does (next DW already programmed). In a recent version Freesat huffman decoding has been destroyed, in the most recent version this should have already been fixes.
Hmmm...When I tried it, it didn't seem to touch any of the EPG received from the HD channels, so it remained unreadable.
I'll give it another go this weekend, and I'll enable a few more debug messages...
Cheers,
Laz
On Friday 26 August 2011 13:33:52 Laz wrote:
On Thursday 25 Aug 2011, Mario Schulz wrote:
Am 21.08.2011 23:09, schrieb Laz:
Does anyone know whether the eepg plugin should "just work" with the Huffman encoded EPG broadcast on Freeview (DVB-T) HD channels in the UK? (Someone mentioned it on here a week or so back.)
Yes, it does (next DW already programmed). In a recent version Freesat huffman decoding has been destroyed, in the most recent version this should have already been fixes.
Hmmm...When I tried it, it didn't seem to touch any of the EPG received from the HD channels, so it remained unreadable.
I'll give it another go this weekend, and I'll enable a few more debug messages...
HD, ITV HD, and other encoded channels alone. It does, however, scramble the EPG for some other, totally unrelated channels on a range of MUXes! I presume it thinks it's encoded and tries to unencode it, scrambling it in the process. One channel EPG that becomes scrambled is QVC so no real loss there!
;-)
I thought it had been doing this scrambling when I tried it earlier in the week but have now proved it to myself.
Time to start adding some more printfs...
Laz
On Fri, 26 Aug 2011 20:42:38 +0100 Laz laz@club-burniston.co.uk wrote:
HD, ITV HD, and other encoded channels alone. It does, however, scramble the EPG for some other, totally unrelated channels on a range of MUXes! I presume it thinks it's encoded and tries to unencode it, scrambling it in the process. One channel EPG that becomes scrambled is QVC so no real loss there!
;-)
I thought it had been doing this scrambling when I tried it earlier in the week but have now proved it to myself.
Time to start adding some more printfs...
The first byte of encoded strings should be 0x1f, followed by 1 or 2 indicating which table should be used (one is optimised for titles, the other for descriptions). "Normal" strings either start with a printable character for the default character set or a code < 0x20 indicating the character set. I use eepg too, but I haven't noticed it scrambling anything (this is probably the first time I've looked at QVC's schedule though ;)).
On Saturday 27 August 2011 01:18:31 Tony Houghton wrote:
On Fri, 26 Aug 2011 20:42:38 +0100
Laz laz@club-burniston.co.uk wrote:
I thought it had been doing this scrambling when I tried it earlier in the week but have now proved it to myself.
Time to start adding some more printfs...
The first byte of encoded strings should be 0x1f, followed by 1 or 2 indicating which table should be used (one is optimised for titles, the other for descriptions). "Normal" strings either start with a printable character for the default character set or a code < 0x20 indicating the character set. I use eepg too, but I haven't noticed it scrambling anything (this is probably the first time I've looked at QVC's schedule though ;)).
Over the evening, it scrambled more and more channels!
:-s
Thanks for the pointer to 0x1f! Now I know where to look.
(I assume that eepg only decodes EPG that comes in "over the air" and doesn't touch any EPG alread stored.)
Laz
I too have seen occasional EPG data on other channels become garbled.
Is it possible that 'other transport stream' EIT data when received on the HD channel transport stream, is sometimes Huffman compressed? This of course is regardless whether the Eepg plugin is present or not.
--- On Sat, 27/8/11, Laz laz@club-burniston.co.uk wrote:
From: Laz laz@club-burniston.co.uk Subject: Re: [vdr] eepg plugin with UK freeview (not freesat!) EPG To: "VDR Mailing List" vdr@linuxtv.org Date: Saturday, 27 August, 2011, 10:46 On Saturday 27 August 2011 01:18:31 Tony Houghton wrote:
On Fri, 26 Aug 2011 20:42:38 +0100
wrote:
I thought it had been doing this scrambling when
I tried it earlier
in the week but have now proved it to myself.
Time to start adding some more printfs...
The first byte of encoded strings should be 0x1f,
followed by 1 or 2
indicating which table should be used (one is
optimised for titles, the
other for descriptions). "Normal" strings either start
with a printable
character for the default character set or a code <
0x20 indicating the
character set. I use eepg too, but I haven't noticed
it scrambling
anything (this is probably the first time I've looked
at QVC's schedule
though ;)).
Over the evening, it scrambled more and more channels!
:-s
Thanks for the pointer to 0x1f! Now I know where to look.
(I assume that eepg only decodes EPG that comes in "over the air" and doesn't touch any EPG alread stored.)
Laz
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Slightly off topic but I recently uninstalled the EEPG plugin and reverted back to pure XMLTV data as I was finding it introduced too much instability into my VDR setup. With the plugin I would have problems with my DVB-S2 card causing VDR to restart with the 'broken stream' error code every week or so. Since removing the EEPG plugin I've returned to having flawless VDR uptime and stability again.
On 24 October 2011 12:50, Stuart Morris stuart_morris@talk21.com wrote:
I too have seen occasional EPG data on other channels become garbled.
Is it possible that 'other transport stream' EIT data when received on the HD channel transport stream, is sometimes Huffman compressed? This of course is regardless whether the Eepg plugin is present or not.
--- On Sat, 27/8/11, Laz laz@club-burniston.co.uk wrote:
From: Laz laz@club-burniston.co.uk Subject: Re: [vdr] eepg plugin with UK freeview (not freesat!) EPG To: "VDR Mailing List" vdr@linuxtv.org Date: Saturday, 27 August, 2011, 10:46 On Saturday 27 August 2011 01:18:31 Tony Houghton wrote:
On Fri, 26 Aug 2011 20:42:38 +0100
wrote:
I thought it had been doing this scrambling when
I tried it earlier
in the week but have now proved it to myself.
Time to start adding some more printfs...
The first byte of encoded strings should be 0x1f,
followed by 1 or 2
indicating which table should be used (one is
optimised for titles, the
other for descriptions). "Normal" strings either start
with a printable
character for the default character set or a code <
0x20 indicating the
character set. I use eepg too, but I haven't noticed
it scrambling
anything (this is probably the first time I've looked
at QVC's schedule
though ;)).
Over the evening, it scrambled more and more channels!
:-s
Thanks for the pointer to 0x1f! Now I know where to look.
(I assume that eepg only decodes EPG that comes in "over the air" and doesn't touch any EPG alread stored.)
Laz
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr