// Check whether the TS packets are scrambled:
Maybe some packets have the TS_SCRAMBLING_CONTROL bits set here.
This could be caused by recording the PCR packets since version 1.7.12.
To debug this, just disable this check, and/or put in some debug
printouts.
Thanks Klaus
I've commented
On 02/09/10 13:35, Rolf Ahrenberg wrote:
On Thu, 2 Sep 2010, Rob Davis wrote:
How do you go about understanding AC-3 within a VDR context?
(apart from reading up on it online - which now has my head spinning).
The current ATSC AC-3 support requires the 'A' source type for channels
and
Hi,
on my VDR PC i've set up openSuse 11.3 and i configured and compiled
vdr-1.7.15 from source (no RPM).
I also installed kernel 2.6.35 (compiled myself) with DVB support for
my Technisat CableStar HD2.
First test:
Starting kaffeine, the card is detected and channels can be scanned.
But if
Hi Michal,
On Sun, 29 Aug 2010 03:59:27 +0200, Michal wrote
I think there is a bug in the way streamdev switches the channel
before it starts streaming. I have only 1 tuner and suspend
behaviour in streamdev-server is set to always suspended.
Unfortunately streaming doesn't stop live TV
Hi Frank,
On 09/03/2010 05:42 PM, Frank Schmirler wrote:
Thanks for tracking that down. I've been able to reproduce this bug and
prepared a fix for CVS. Unfortunately CVS and bugtracker on vdr-developer.org
are still down. The patch won't help much if you cannot get the CVS version...
that's
On 02/09/10 13:35, Rolf Ahrenberg wrote:
On Thu, 2 Sep 2010, Rob Davis wrote:
How do you go about understanding AC-3 within a VDR context?
(apart from reading up on it online - which now has my head spinning).
The current ATSC AC-3 support requires the 'A' source type for channels
and
On Fri, 3 Sep 2010, Rob Davis wrote:
Do we need to check it's ATSC if type is 0x81? Does anything else use it and
is it a problem if it does?
The values 0x80-0xFF are so called User Private in the standard, so in
theory you cannot assume them to be ATSC. But you could detect the ATSC
// Check whether the TS packets are scrambled:
Maybe some packets have the TS_SCRAMBLING_CONTROL bits set here.
This could be caused by recording the PCR packets since version 1.7.12.
To debug this, just disable this check, and/or put in some debug
printouts.
Thanks Klaus
I've commented
