Hi folks,
The segfault was introduced in xineliboutput's cvs between 28.01.2010
and 29.01.2010
The following change produces it:
--- xine_input_vdr.c.old2010-02-13 14:13:48.670894516 +0100
+++ xine_input_vdr.c2010-02-13 14:13:56.246141788 +0100
@@ -4,7 +4,7 @@
* See the main source
Hi
I'm using vdr 1712 + patched cvs streamdev + xbmc pvr-testing2.
While watching some dvb channels on xbmc I can see in vdr log strange logs as
Feb 13 15:40:55 arvdr vdr: [2154] switching to channel 22
Feb 13 15:40:55 arvdr vdr: [2154] info: Channel not available!
really I can watch this
Hi
I have vdr 1712 + vdr-xine 093
during of watching regular mpeg2 channels sometimes the sound is disappeared
and in the logs I can see
Feb 13 21:31:06 arvdr logger: fixing sound card drift by 1352 pts
Feb 13 21:31:07 arvdr logger: 200 frames delivered, 0 frames skipped, 4 frames
discarded
Hi list,
One of the known problems of the FF-DVB cards is the bandwidth
limitation, that is addressed by the full-ts-mod for example. However,
there are still enough FF cards out there that are not and wont ever be
modded, and these cards tend to produce broken recordings on high
bandwidth
Why not just use ttpci-bwlimit.diff to patch the driver? There is also a
patch floating around that lets you select what to block.
On 2/13/2010 1:15 PM, Udo Richter wrote:
Hi list,
One of the known problems of the FF-DVB cards is the bandwidth
limitation, that is addressed by the full-ts-mod
What's the proper way to configure a different lirc socket path with
runvdr-extreme? Eg. I need to pass --lirc=/var/run/lirc/lircd to VDR,
as this is the new default lirc socket path with lirc 0.8.6.
--
-Tor
___
vdr mailing list
vdr@linuxtv.org
