[vdr] Re: vdr-1.1.15 still don't record second apid ;-(

["Rienecker, Fa. Evenio, ITS P, M" <C.Rienecker@deutschepost.de>]

> -----Original Message-----
> From: Klaus Schmidinger [mailto:Klaus.Schmidinger@cadsoft.de]
> Sent: Monday, November 04, 2002 3:13 PM
> To: vdr@linuxtv.org
> Subject: [vdr] Re: vdr-1.1.15 still don't record second apid ;-(
> 
> 
> Steffen Koch wrote:
> > 
> > Rienecker, Fa. Evenio, ITS P, M wrote:
> >  > It seems to be the following: First vdr checks whether the secondary
> >  > APID from the channels.conf is in use at the start of the recording,
> >  > i.e. if data is coming. Second, if positive it will record the 2nd
> >  > APID, if negative it will only record the primary APID. It looks to
> >  > me like there is no further checking during the recording.
> >  >
> >  > A possible workaround for this behavior is to swap primary and
> >  > secondary APIDs in the channels.conf, since the primary APID will be
> >  > recorded all the time (even if there is nothing). The down side is,
> >  > that while live viewing there will be no sound unless you press
> >  > menu/green if only one APID is in use.
> > 
> > What about not looking for data on the second APID, instead recording it
> > no matter if data is available??
> 
> I wonder where you guys are getting the idea that VDR would be "looking
for data"
> and deciding "not to record" the second APID?!

Obviously vdr is looking for data while replaying in order to offer the
choice to switch between languages.
A 'broken' multi language recording doesn't offer this. So there is no 2nd
APID in the PES. I checked that with (a patched version of) pes2aud_es.
Consequently it has not been recorded.

> If I'm remembering the code correctly, VDR sets up the necessary things to
> receive the VPID and both APIDs and then records whatever the driver
delivers.
> I can see no place where VDR would say "hey, there's no audio data on
APID2, so
> let's ignore anything there that might come later".

Which leads us back to the original point:
VDR records whatever is first in the channels.conf and tends to not record
whatever comes second (Maybe 'records empty packets' suits you better). This
is independent of which APID actually is 1st and 2nd.
But one fact is empirically proven: If the 2nd apid is not in use at the
point of time the recording starts, it will not be recorded.

> Maybe its the driver that doesn't deliver audio data on APID2 if there is
none
> from the very beginning?

Looking at the code I would confirm that VDR does everything correct.

So either there's a difference between fd_demuxa1 and fd_demuxa2 
Or the difference between DMX_PES_AUDIO and DMX_PES_OTHER is causing the
problem.
Anyway, either one hints for a driver related problem.
What puzzles me is that live viewing never poses any problem independent of
the selected APID.

CU,
Christian.

> Klaus
> -- 
> _______________________________________________________________
> 
> Klaus Schmidinger                       Phone: +49-8635-6989-10
> CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
> Hofmark 2                               Email:   kls@cadsoft.de
> D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
> _______________________________________________________________
> 
> 
> -- 
> Info:
> To unsubscribe send a mail to listar@linuxtv.org with 
> "unsubscribe vdr" as subject.
> 


-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.