Anybody there who can help mir here ?
I have debian ETCH on NSLU2 with kernel 2.6.20 and the latest cvs v4l
driver which supports the Twinhan Startbox 2 DVB-S usb.
Loading the driver is fine
Starting vdr 1.4.5 ( compiled wit sources from etobi) without the
attached box and without drivers loaded
I am using VDR 1.4.5 with the integrated auto pid feature and without
any CAM. When tuning to an encrypted channel, the CA value gets set
accordingly and "channel not available" is displayed. So far so good.
However there are channels that encrypt only certain programs and are
free the rest of th
En/na Ondrej Wisniewski ha escrit:
I am using VDR 1.4.5 with the integrated auto pid feature and without
any CAM. When tuning to an encrypted channel, the CA value gets set
accordingly and "channel not available" is displayed. So far so good.
However there are channels that encrypt only certain
> Is there an easy way to fix this?
Edit the file dvbdevice.c, insert a line "return true;" at the beginning
of the method cDvbDevice::ProvidesCa.
With this modification you can tune to encoded channels, however you'll
never see a "channel not available", you'll just see a black screen.
This, b
I have noticed a potential bug in playing back radio channels. The playback
time of recorded radio channels is inflated by almost 40%. This has been
confirmed on four North American satellites on three different providers. The
reported time for a 10 minute recording will consistently appear a
Hi,
I've tried to use vdr with xineliboutput and streamdev-client plugins on
server to view TV from HTPC (VDR + plugins and FF DVB-C and buget DVB-C
cards). No luck so far. I'm a bit lost here so maybe someone could give
hints how to proceed.
I tried executing:
./vdr -c /opt/video/config -L /opt/
Hi,
Patrick Mackin wrote:
> I have noticed a potential bug in playing back radio channels. The
> playback time of recorded radio channels is inflated by almost 40%.
> This has been confirmed on four North American satellites on three
> different providers. The reported time for a 10 minute rec
VDR derives the playback times for a recording by a hard coded
relationship from the number of an index entry in the recording's index
file (see recording.h, FRAMESPERSEC). The default relationship of 25
frames per second doesn't suit to NTSC broadcasts with 30 frames per
second, so VDR reports a
hi,
Stone writes:
> With this modification to dvbdevice.c, I wonder if VDR will still crash
> when a timer goes off on a channel and all the sudden it becomes encrypted.
> This would normally cause a broken data stream and VDR would do an emergency
> exit.
I gave up recording encrypted chann
On 3/5/07, Stone <[EMAIL PROTECTED]> wrote:
With this modification to dvbdevice.c, I wonder if VDR will still crash
when a timer goes off on a channel and all the sudden it becomes encrypted.
This would normally cause a broken data stream and VDR would do an emergency
exit.
I *HATE* that vdr
On Sun, 4 Mar 2007, Udo Richter wrote:
Found it! And, more important: Blame Klaus! :)
Thanks. You could adapt my finnish translation update to your 1.4.x
series patch (google: vdr-1.5.1-finnish.diff)...
BR,
--
rofa
___
vdr mailing list
vdr@linuxt
11 matches
Mail list logo
