Steffen Barszus kirjoitti:
Kartsa schrieb:
Stefan Huelswitt kirjoitti:
On 01 Feb 2007 Reinhard Nissl <[EMAIL PROTECTED]> wrote:
Heikki Manninen wrote:
I've noticed that earlier when I was using PIII 550 MHz and vdr
1.3.22 (or something about) I made a test by recording nine
channel
Hans-Peter Jansen wrote:
> Hmm, to clarify: the reliability of VPS is impaired starting from
> 00:00 CET up to which time? Which times are impared, start and/or end
> time?
All events are stopped (status 1) on 0100 CET/0200 CEST. So if you have
an event that runs from 0030 CET to 0130 CET, it wi
Kartsa schrieb:
Stefan Huelswitt kirjoitti:
On 01 Feb 2007 Reinhard Nissl <[EMAIL PROTECTED]> wrote:
Heikki Manninen wrote:
I've noticed that earlier when I was using PIII 550 MHz and vdr
1.3.22 (or something about) I made a test by recording nine
channels simultaneously and watch
Stefan Huelswitt kirjoitti:
On 01 Feb 2007 Reinhard Nissl <[EMAIL PROTECTED]> wrote:
Heikki Manninen wrote:
I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22
(or something about) I made a test by recording nine channels
simultaneously and watching a recording at
Hi,
Jouni Karvo wrote:
> > A drawback of such large buffers is that VDR is way ahead the picture
> > you currently see on screen. So if you jump forward 60 seconds, you'll
> > actually jump 70 seconds and if you jump backward 60 seconds you'll only
> > jump 50 seconds. That's why I suggested
On 01 Feb 2007 Reinhard Nissl <[EMAIL PROTECTED]> wrote:
> Heikki Manninen wrote:
>
>>> I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22
>>> (or something about) I made a test by recording nine channels
>>> simultaneously and watching a recording at the same time. I rememb
hi,
Reinhard Nissl writes:
>
> I don't think that this is a matter of vdr-xine but at least it looks
> like there is a simple solution in xine regarding the annoying pause:
> try to increase
>
> engine.buffers.audio_num_buffers
>
> and
>
> engine.buffers.video_num_buffers
Marko Mäkelä kirjoitti:
On Sat, Mar 03, 2007 at 10:12:21PM +0200, Kartsa wrote:
I did a seven minute session where I had 5 test recordings which started
one minute apart and ended at the same time. After each recording had
started I tested the responce of remote by just pussing menu button.
Hi,
Jouni Karvo wrote:
> It takes about 5 secs to start stopped disks. It is not a problem
> when starting a recording, but when recordings span over several disks
> there will be an annoying pause when it is time to start reading from
> another disk.
>
> Is there a possibility to configure (fo
hi,
as the kernel finally supports standby or spin down or whatever mode
for my SATA disks, I have set up an aggressive scheme trying to spin
down disks whenever possible. The results: 2 degrees drop in case
temperature and a significantly lower noise. And a playout "problem"...
It takes about
10 matches
Mail list logo
