[vdr] Re: ANNOUNCE: bitstreamout-0.42i (Was: AC3 over Soundcard (live and replay))

["Dr. Werner Fink" <werner@suse.de>]

On Thu, Jan 30, 2003 at 12:34:16PM +0100, =?iso-8859-1?Q?H. _Sch=F6bel?= wrote:
>  
> > Hagen ... is it possible to run VDR without transfer mode?
> 
> For "normal" channels (the few on cable available channels) is viewing
> without transfer mode possible, but there is no channel with ac3  :-(

Pro7 over satellite does provide AC3 ... as I can hear day for day ;^)
With transfer mode the `replay' way should be win over the direct
`channel switch' way.  I don't now how to make sure that this works
without switch/control in the plugin interface of VDR.

> 
> > Btw: Do you've applied the audio patch from the bitstreamout 
> > sources and recompiled vdr? 
> 
> Yes.
> 
> > And do not use `-a' option in combination with the plugin.
> 
> THAT was apparently my main fault (shame on me). No I use the plugin
> without VDR's -a option an the (old) errors are blown away :-) Now I can
> see Pro-7 without the ringbuffer overrun - but i can't hear anything.
> The other channels (without ac3) don't have this behavior.
> 
> Jan 30 12:19:02 video vdr[3059]: switching to channel 3
> Jan 30 12:19:03 video vdr[3128]: transfer thread started (pid=3128)
> Jan 30 12:19:03 video vdr[3129]: receiver thread started on device 3 (pid=3129)
> Jan 30 12:19:03 video vdr[3130]: INSTREAM: Synchronize AC3 thread started (pid=3130)
> Jan 30 12:19:03 video vdr[3130]: INSTREAM: thread can not set process priority: Success
> Jan 30 12:19:08 video kernel: buffer empty    < ???
> Jan 30 12:19:16 video vdr[3059]: switching to channel 4
> Jan 30 12:19:16 video vdr[3128]: transfer thread ended (pid=3128)
> Jan 30 12:19:16 video vdr[3129]: receiver thread ended on device 3 (pid=3129)
> Jan 30 12:19:16 video vdr[3059]: cTS2PES got 1 TS errors, 2 TS continuity errors
> Jan 30 12:19:16 video vdr[3059]: cTS2PES got 0 TS errors, 1 TS continuity errors
> Jan 30 12:19:16 video vdr[3059]: cTS2PES got 0 TS errors, 2 TS continuity errors
> Jan 30 12:19:16 video vdr[3059]: buffer stats: 26132 (2%) used
> Jan 30 12:19:16 video vdr[3130]: INSTREAM: Synchronize AC3 thread ended (pid=3130)

That means that you receive on device 3 e.g. Pro7 and transfer the
data to device 1.  Aha ... maybe wrong class.  In transfer mode you
should see messages from cReplayOutAC3 class ("REPLAY: ...") because
in transfer mode actually the cPlayer class is used.

> I try to set in spdif.conf the -D parameter with 0,2 (like manpage and
> /proc/alsa/... said), but there is an error direct on vdr start:
> 
> Jan 30 12:10:04 video vdr[2588]: S/P-DIF: Wrong card,device arguments (0)  <<<<<<<<<<<<<<<<<<

Hmmm ... let's see ... found.

> 
> > What without the audio patch happens?  Note: with an 
> > unpatched VDR you should not do a replay of Record using AC3 
> > nor using the transfer mode, the current VDR version does 
> > never clear or close the external cAudio plugins (IMHO this is a bug).
> 
> Don't try it, but i know this behavior from the past (want to clear this
> with your plugin :-)  ). The replaying of recordings with ac3 included
> is no problem (with forwarding also no problem):
> 
> Jan 30 12:15:30 video vdr[3059]: replay /video/%@Das_Jesus_Video,_Teil_1__/2002-12-05.20:18.50.50.rec
> Jan 30 12:15:30 video vdr[3059]: playing '/video/%@Das_Jesus_Video,_Teil_1__/2002-12-05.20:18.50.50.rec/001.vdr'
> Jan 30 12:15:30 video vdr[3059]: loading /video/%@Das_Jesus_Video,_Teil_1__/2002-12-05.20:18.50.50.rec//marks.vdr
> Jan 30 12:15:30 video vdr[3086]: dvbplayer thread started (pid=3086)
> Jan 30 12:15:30 video vdr[3086]: resuming replay at index 372 (0:00:14.23)
> Jan 30 12:15:30 video vdr[3087]: non blocking file reader thread started (pid=3087)
> Jan 30 12:15:30 video vdr[3088]: REPLAY: Forwarding AC3 thread started (pid=3088)
> Jan 30 12:15:30 video vdr[3086]: BOUNCE: buffer overflow 
> Jan 30 12:15:30 video vdr[3086]: BOUNCE: buffer overflow 
> Jan 30 12:15:42 video vdr[3088]: REPLAY: Forwarding AC3 thread ended (pid=3088)
> Jan 30 12:15:42 video vdr[3089]: REPLAY: Forwarding AC3 thread started (pid=3089)
> Jan 30 12:15:42 video vdr[3086]: BOUNCE: buffer overflow 
> Jan 30 12:15:44 video vdr[3089]: REPLAY: Forwarding AC3 thread ended (pid=3089)
> Jan 30 12:15:44 video vdr[3090]: REPLAY: Forwarding AC3 thread started (pid=3090)
> Jan 30 12:15:44 video vdr[3086]: BOUNCE: buffer overflow 
> Jan 30 12:15:46 video vdr[3090]: REPLAY: Forwarding AC3 thread ended (pid=3090)
> Jan 30 12:15:47 video vdr[3091]: REPLAY: Forwarding AC3 thread started (pid=3091)
> Jan 30 12:15:47 video vdr[3086]: BOUNCE: buffer overflow 
> Jan 30 12:15:48 video vdr[3091]: REPLAY: Forwarding AC3 thread ended (pid=3091)
> Jan 30 12:15:48 video vdr[3092]: REPLAY: Forwarding AC3 thread started (pid=3092)
> Jan 30 12:15:48 video vdr[3086]: BOUNCE: buffer overflow 
> Jan 30 12:15:50 video vdr[3092]: REPLAY: Forwarding AC3 thread ended (pid=3092)
> Jan 30 12:15:50 video vdr[3093]: REPLAY: Forwarding AC3 thread started (pid=3093)
> Jan 30 12:15:50 video vdr[3086]: BOUNCE: buffer overflow 
> Jan 30 12:15:56 video vdr[3087]: non blocking file reader thread ended (pid=3087)
> Jan 30 12:15:56 video vdr[3086]: dvbplayer thread ended (pid=3086)
> Jan 30 12:15:57 video vdr[3093]: REPLAY: Forwarding AC3 thread ended (pid=3093)
> 
> > See into the /var/log/messages.  Do you find any messages
> > done from the plugin?


      Werner


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