Hi Klaus,
I have noticed a PMT parsing issue with VDR version 1.7.x. The bug is still
present in version 1.7.3 but the behaviour is worst because it segfaults.
First I found out that 2 lines where added in the ParsePmt method.
Data += Data[0] + 1; // this is the first packet
Length
Hi,
On Mon, 19 Jan 2009 10:44:18 +0100, Alexw wrote
> I have noticed a PMT parsing issue with VDR version 1.7.x. The bug
> is still present in version 1.7.3 but the behaviour is worst because
> it segfaults.
>
> First I found out that 2 lines where added in the ParsePmt method.
>
> Data +
On 19.01.2009 11:06, Frank Schmirler wrote:
> Hi,
>
> On Mon, 19 Jan 2009 10:44:18 +0100, Alexw wrote
>> I have noticed a PMT parsing issue with VDR version 1.7.x. The bug
>> is still present in version 1.7.3 but the behaviour is worst because
>> it segfaults.
>>
>> First I found out that 2 line
http://www.atric.de/IR-Einschalter/index.php
http://www.atric.de/IR-Einschalter/com.html
http://www.atric.de/IR-Einschalter/download/manual_en_rev4.pdf
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Sorry about this message, please ignore it, it was just meant for later
reading at home...
Lucian Muresan wrote:
> http://www.atric.de/IR-Einschalter/index.php
> http://www.atric.de/IR-Einschalter/com.html
> http://www.atric.de/IR-Einschalter/download/manual_en_rev4.pdf
_
I have already tested the inversion. Reducing the length and after moving to
the new offset. This change does not solve the issue. The Length variable can
still decrease to a negative value.
What happen when the byte offset is greater than 188?
_
On Mon, 19 Jan 2009 11:20:45 +0100, Alexw wrote
> I have already tested the inversion. Reducing the length and after
> moving to the new offset. This change does not solve the issue. The
> Length variable can still decrease to a negative value.
>
> What happen when the byte offset is greater tha
Quoting Lucian Muresan :
> Sorry about this message, please ignore it, it was just meant for later
> reading at home...
>
> Lucian Muresan wrote:
>> http://www.atric.de/IR-Einschalter/index.php
>> http://www.atric.de/IR-Einschalter/com.html
>> http://www.atric.de/IR-Einschalter/download/manual_en_
Yes Frank you are right. The problem is coming from bad CRC in the PMT (and
the same apply to bad PAT). If Pmt.CheckCRCAndParse() fails, bad PMT data
should be skipped.
@Klaus: will you look at this enhancement before rolling out 1.7.4?
___
vdr m
On Mon, 19 Jan 2009 13:32:07 +0100, Alexw wrote
> Yes Frank you are right. The problem is coming from bad CRC in the
> PMT (and the same apply to bad PAT). If Pmt.CheckCRCAndParse() fails,
> bad PMT data should be skipped.
Bad CRC is caught by CheckCRCAndParse(). What I had in mind is a wrong va
- Original Message -
From: "Joerg Bornkessel"
To: "VDR Mailing List"
Sent: Sunday, January 18, 2009 2:24 PM
Subject: Re: [vdr] ATSC a good primers guide? (Moving from Italy to the
USwith my VDR setup)
>> So, would the DVB-T card just work with ATSC or is it fundamentally
>> different
On Mon, 19 Jan 2009 00:47:17 +0100
Gerald Dachs wrote:
> I have made some experiments with xineliboutput and vdpau, it looked
> promising, but at least I had to give up for now. I have used vdr 1.6.0,
> xineliboutput 1.0.3, nvidia driver 180.22, xine-lib-vdpau from 20090113
> and xinelib 1.1.90hg
Hi Gerald,
Gerald Dachs schrieb:
> [...] The biggest problem is that if I switch
> channels it happens that the video starts to flicker. You can see that
> between the pictures of the current channel the pictures of the previous
> channel appear. Restarting vdr-sxfe fixes it till the next channel
> I had the same problems. I didn't notice that the picture flickering
> (do you get big patches of mostly green garbage?)
No, not at all, always still pictures that was seen before.
> was triggered by
> channel changes, but that could well be the case.
Only with channel changes here, and only w
> I read something similar on the MythTV mailinglist.
> >From http://www.gossamer-threads.com/lists/mythtv/users/366684:
> > In the end I believe it was accidental code bugs when he was
> > porting the automatic letterboxing patch over to work with VDPAU
> > that caused him to end up with his OSD g
On Mon, 19 Jan 2009 17:40:17 +0100
Gerald Dachs wrote:
> Yesterday I have switched back to the use of vdpau, because I got now
> periodically hick ups with xv and xxmc, the last time I had this working
> correct I had another CPU, mainboard and nvdida driver :(. The loss of
> sync is less disturb
Am Mon, 19 Jan 2009 17:03:34 +
schrieb Tony Houghton :
> On Mon, 19 Jan 2009 17:40:17 +0100
> Gerald Dachs wrote:
>
> > Yesterday I have switched back to the use of vdpau, because I got
> > now periodically hick ups with xv and xxmc, the last time I had
> > this working correct I had another
On Mon, 19 Jan 2009 18:26:22 +0100
Gerald Dachs wrote:
> Am Mon, 19 Jan 2009 17:03:34 +
> schrieb Tony Houghton :
>
> > What graphics card/chip have you got? AFAIK xvmc/xxmc only works on
> > NVidias up to 7x00 and VDPAU is for 8x00 and newer. If your CPU usage
> > dropped significantly with
Am Mon, 19 Jan 2009 17:40:44 +
schrieb Tony Houghton :
> I'm fairly sure xvmc (which xxmc is based on) isn't supported on
> Nvidia 8x00 and newer. 20-30% CPU usage isn't much problem, so as you
> aren't receiving HD anyway I'd stick with stable drivers, ffmpeg and
> xine etc until VDPAU is know
On Sun, Jan 18, 2009 at 3:56 PM, Alex Betis wrote:
> On Sun, Jan 18, 2009 at 3:44 PM, Ville Aakko wrote:
>
>> If I understood the issue correctly, Alex (the OP) has problems
>> because the USB receiver gives BOTH kb events and makes a lirc device,
>> and the KB events are not wanted and cause pro
On Mon, 19 Jan 2009 18:57:51 +0100
Gerald Dachs wrote:
> Am Mon, 19 Jan 2009 17:40:44 +
> schrieb Tony Houghton :
> > I'm fairly sure xvmc (which xxmc is based on) isn't supported on
> > Nvidia 8x00 and newer. 20-30% CPU usage isn't much problem, so as you
> > aren't receiving HD anyway I'd s
I want to replace my UK Sky digital box with VDR (I only want the free
to air channels) for watching/recording TV over HDMI on my plasma. So
far everything is working OK, I have vdr 1.7.3 and xine running on an
ASUS M2N VM-HDMI (nvidia) mobo with the s2-liplianin drivers for my Nova
SD2 card.
Am Mon, 19 Jan 2009 21:39:29 +
schrieb Tony Houghton :
> On Mon, 19 Jan 2009 18:57:51 +0100
> Gerald Dachs wrote:
>
> > Am Mon, 19 Jan 2009 17:40:44 +
> > schrieb Tony Houghton :
> > > I'm fairly sure xvmc (which xxmc is based on) isn't supported on
> > > Nvidia 8x00 and newer. 20-30% CP
On 20 Jan 2009, at 08:28, Gerald Dachs wrote:
Am Mon, 19 Jan 2009 17:40:44 +
schrieb Tony Houghton :
I'm fairly sure xvmc (which xxmc is based on) isn't supported on
Nvidia 8x00 and newer. 20-30% CPU usage isn't much problem, so as
you aren't receiving HD anyway I'd stick with stable drive
24 matches
Mail list logo
