On 05/18/07 01:24, Petri Helin wrote:
Klaus Schmidinger wrote:
How many DVB devices does your system have?
Are you sure there was one free when that timer should have been
recorded?
What was the priority of that timer?
I tried to recreate the situation by disabling the decrypting for the
Hello
Just in case it might help: I had this problem some months ago.
It turned out that cron died from time to time. the system restarted
syslogd and cron - but too late for the recording.
Reason for this: A weak powersupply.
Regards
Wolfgang
On 05/18/07 01:24, Petri Helin wrote:
Klaus
VDR User wrote:
I've recorded/watched a lot of tv in the last couple days and so far I
haven't noticed any problems with this patch. I am currently using v3
(the patch I attached to my previous post) with vdr-1.5.2.
Do you know how large the buffers usually grow?
If you haven't reduced vdrs
Klaus Schmidinger wrote:
On 05/18/07 01:24, Petri Helin wrote:
So now there is additional entries telling that the channel is not
available (Kanava ei ole käytettävissä!). But what is that strange
entry about VPS recording staring (VPS-tallennus on alkamassa!)? I
didn't create a VPS timer...
On 5/20/07, Artur Skawina [EMAIL PROTECTED] wrote:
VDR User wrote:
I've recorded/watched a lot of tv in the last couple days and so far I
haven't noticed any problems with this patch. I am currently using v3
(the patch I attached to my previous post) with vdr-1.5.2.
Do you know how large
VDR User wrote:
On 5/20/07, Artur Skawina [EMAIL PROTECTED] wrote:
VDR User wrote:
I've recorded/watched a lot of tv in the last couple days and so far I
haven't noticed any problems with this patch. I am currently using v3
(the patch I attached to my previous post) with vdr-1.5.2.
Do
On 5/20/07, Artur Skawina [EMAIL PROTECTED] wrote:
Thanks. It seems that 648k was the largest size ever used for a buffer,
which is less than 1/3 of the full size (2M for Result,Transfer and TS).
The Recorder buffer was typically at 5% of its max size, ie 300k instead
of 5M. No overflows w/ v3
hi,
you could try to use femon (the console application) in the dvb-utils
package.
Alasdair Campbell schrieb:
When trialing vdr-femon-1.1.0 with vdr-xineliboutput-1.0.0_rc1 I
receive the following error when trying to view the signal information
of my recording server via my streaming only
Alasdair Campbell wrote:
When trialing vdr-femon-1.1.0 with vdr-xineliboutput-1.0.0_rc1 I
...
Any advice gladly received!
Try the current versions?
Femon 1.1.4: http://www.saunalahti.fi/~rahrenbe/vdr/femon/
Xineliboutput 1.0.0rc2: http://phivdr.dyndns.org/vdr/vdr-xineliboutput/
-Petri
On Sun, 20 May 2007, Alasdair Campbell wrote:
Is this a known problem or is there something more I need to configure
for my specific setup?
Yes, it's a known problem reported only in xineliboutput setups: somehow
cDevice::ActualDevice()-CardIndex() returns invalid values. I cannot
reproduce
Hello,
I am using vdr-1.4.7, and vdr-lcdproc-0.0.10-jw2, to drive a 16x2 characters
imon VFD module.
The display is really nice, but 16x2 isn't enough to display all datas. I
would customize lcdproc to
remove all EPG informations, and display only time, channel number and
channel name.
Could
Am Sonntag, 20. Mai 2007 schrieb kafifi:
Hello,
I am using vdr-1.4.7, and vdr-lcdproc-0.0.10-jw2, to drive a 16x2
characters imon VFD module.
The display is really nice, but 16x2 isn't enough to display all datas. I
would customize lcdproc to
remove all EPG informations, and display only
12 matches
Mail list logo
