>-- Original Message --
>Date: Mon, 30 Jan 2006 07:23:18 +1100 (added by postmaster(a)iprimus.com.au)
>From: vdr-request(a)linuxtv.org
>Subject: vdr Digest, Vol 12, Issue 89
>To: vdr(a)linuxtv.org
>Reply-To: vdr(a)linuxtv.org
>
>
>Send vdr mailing list submissions to
> vdr(a)linuxtv.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>or, via email, send a message with subject or body '…
[View More]help' to
> vdr-request(a)linuxtv.org
>
>You can reach the person managing the list at
> vdr-owner(a)linuxtv.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of vdr digest..."
>
>
>Today's Topics:
>
> 1. vdr 1.3.41: channel up/down doesn't work (Stefan Huelswitt)
> 2. Re: Confirm messages (Darren Salt)
> 3. Re: 1.3.39, "Menu button closes" true: No menu from replay
> (Joachim Wilke)
> 4. Re: vdr 1.3.41: channel up/down doesn't work (Joachim Wilke)
> 5. Re: vdr 1.3.41: channel up/down doesn't work (Luca Olivetti)
> 6. Re: vdr 1.3.41: channel up/down doesn't work (Stefan Huelswitt)
> 7. Re: Confirm messages (Dave P)
> 8. Re: Confirm messages (Darren Salt)
> 9. Re: kvdr 0.64 released (Qwasi)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Sun, 29 Jan 2006 18:18:28 +0000 (UTC)
>From: s.huelswitt(a)gmx.de (Stefan Huelswitt)
>Subject: [vdr] vdr 1.3.41: channel up/down doesn't work
>To: vdr(a)linuxtv.org
>Message-ID: <drj0tk$9aq$1(a)video.local.muempf.de>
>Content-Type: text/plain; charset=us-ascii
>
>Hi,
>
>I just tested vdr 1.3.41 and found that switching the channel
>with up/down doesn't works anymore.
>
>Hitting up/down brings up the channel info for the current
>channel only. I can hit the key as many times as I want, nothing
>more happens.
>
>I can switch to the channel if I enter the number directly and
>the up/down keys work fine e.g. in menu.
>
>I'm using a LIRC remote. Tested with plain vdr/no plugins too.
>
>Regards.
>
>--
>Stefan Huelswitt
>s.huelswitt(a)gmx.de | http://www.muempf.de/
>
>
>
>------------------------------
>
>Message: 2
>Date: Sun, 29 Jan 2006 18:11:27 +0000
>From: Darren Salt <linux(a)youmustbejoking.demon.co.uk>
>Subject: Re: [vdr] Confirm messages
>To: vdr(a)linuxtv.org
>Message-ID: <4DF0EF7CDF%linux(a)youmustbejoking.demon.co.uk>
>Content-Type: text/plain; charset=us-ascii
>
>I demand that Tony Houghton may or may not have written...
>
>> In <4DF0E0017A%linux(a)youmustbejoking.demon.co.uk>, Darren Salt wrote:
>>> I demand that Laurence Abbott may or may not have written...
>>>> On Fri, 2006-01-27 at 14:00 +0100, Klaus Schmidinger wrote:
>>>>> Since version 1.3.38 the Red button in the Schedule menu immediately
>>>>> creates the timer and marks the event with 'T'. [...]
>
>>>> I upraded from 1.3.36 to 1.3.40 last weekend and noticed this new
>>>> behaviour last night. I like it a lot! [...]
>
>>> Just wait until you want to record a film on, say, ITV2. You know, one
>of
>>> those which is split in half so that they can stick in some other
>>> programme, the scheduled start and end times of which are works of
>>> fiction.
>
>> I've found that a nuisance too. You have to get used to it, because in
>> printed TV guides they often just list it as one programme with a note
>that
>> there's a break for something else in the middle. I think it would be
>> worthwhile for VDR to check whether the next programme but one after the
>> one you're recording has the same name.
>
>That won't always work - see ITV1, Wednesday, 9pm (which is one of the
>examples which I've posted). There are *four* intervening EPG entries.
>
>I suggest looking for another programme which is scheduled to begin within
>45
>minutes of the end of the selected programme. (This would cover films being
>split by the 10pm news on BBC1 while not triggering false positives caused
>by
>quick repeats on ITV2.)
>
>Obviously, where the gap between the two parts exceeds the sum of the timer
>margins, two timers should be created. An option to append the second
>recording to the first would seem to be reasonable.
>
>--
>| Darren Salt | nr. Ashington, | d youmustbejoking,demon,co,uk
>| Debian, | Northumberland | s zap,tartarus,org
>| RISC OS | Toon Army | @
>| Retrocomputing: a PC card in a Risc PC
>
>When things are going well, something will go wrong.
>
>
>
>------------------------------
>
>Message: 3
>Date: Sun, 29 Jan 2006 19:25:27 +0100
>From: Joachim Wilke <joachim.wilke(a)gmail.com>
>Subject: Re: [vdr] 1.3.39, "Menu button closes" true: No menu from
> replay
>To: VDR Mailing List <vdr(a)linuxtv.org>
>Message-ID: <2a954dbc0601291025r13af17bav(a)mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>2006/1/22, Udo Richter <udo_richter(a)gmx.de>:
>> > With 1.3.39 and "Menu button closes" set to true, the main menu doesn't
>> > open if any replay control is active. The attached patch fixes this
by
>> > resetting a !IsOpen cControl to WasOpen=false.
>>
>> This slipped the 1.3.40 release somehow, but the attached patch still
works.
>
>Just a remark: It seems, that in 1.3.41 this is still not fixed.
>
>Joachim.
>
>
>
>------------------------------
>
>Message: 4
>Date: Sun, 29 Jan 2006 19:26:35 +0100
>From: Joachim Wilke <joachim.wilke(a)gmail.com>
>Subject: Re: [vdr] vdr 1.3.41: channel up/down doesn't work
>To: VDR Mailing List <vdr(a)linuxtv.org>
>Message-ID: <2a954dbc0601291026g69391623k(a)mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>2006/1/29, Stefan Huelswitt <s.huelswitt(a)gmx.de>:
>> I just tested vdr 1.3.41 and found that switching the channel
>> with up/down doesn't works anymore.
>> I'm using a LIRC remote. Tested with plain vdr/no plugins too.
>
>For me, also using LIRC, switching channels with up and down works.
>
>Joachim.
>
>
>
>------------------------------
>
>Message: 5
>Date: Sun, 29 Jan 2006 19:26:45 +0100
>From: Luca Olivetti <luca(a)ventoso.org>
>Subject: Re: [vdr] vdr 1.3.41: channel up/down doesn't work
>To: VDR Mailing List <vdr(a)linuxtv.org>
>Message-ID: <43DD08E5.8000302(a)ventoso.org>
>Content-Type: text/plain; charset="iso-8859-1"
>
>En/na Stefan Huelswitt ha escrit:
>
>> I'm using a LIRC remote. Tested with plain vdr/no plugins too.
>
>Not very helpful but I can say it works here with lirc and a boatload of
>patches and plugins.
>
>Bye
>--
>- Yo tambi?n quiero una Europa libre de Patentes de Software -
>- I want a Software Patents Free Europe too! And you? -
>---------------------------------------------------------------
> EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es
>
>
[View Less]
Hello list,
I've just installed the em84xx plugin - yes the realmagic driver is now working under kernel 2.6 :-)
For using the em84xx plugin I have to disable the watchdog timeout, otherwise it will kill vdr every some minutes.
The watchdog is set to 60 seconds, and even is zapping is working the watchdog strikes back:
Jan 29 21:03:27 [vdr] [6887] switching to channel 7
Jan 29 21:03:34 [vdr] [6887] switching to channel 6
Jan 29 21:03:35 [vdr] [6887] switching to channel 5
Jan 29 21:03:36 [vdr]…
[View More] [6887] switching to channel 4
Jan 29 21:03:38 [vdr] [6887] switching to channel 3
Jan 29 21:04:03 [vdr] [6898] PANIC: watchdog timer expired - exiting!
or even harder:
Jan 29 21:01:25 [vdr] [6143] ERROR (dvbdevice.c,211): Connection timed out
Jan 29 21:01:26 [vdr] [6144] channel 6 (SAT.1) event 20:15 'Jumanji' status 4
Jan 29 21:01:27 [vdr] [6144] channel 7 (ProSieben) event 20:16 'Catch Me If You Can' status 4
Jan 29 21:01:27 [vdr] [6144] channel 8 (KABEL1) event 20:15 'Sag niemals nie' status 4
Jan 29 21:01:29 [kernel] [ring0 received 5000 interrupts so far (skipped 1 for other devices sharing line)]
Jan 29 21:02:06 [vdr] [6137] switching to channel 7
Jan 29 21:02:12 [vdr] [6137] switching to channel 8
Jan 29 21:02:35 [vdr] [6137] switching to channel 9
Jan 29 21:02:36 [vdr] [6253] cAudioRepacker(0xC0): skipped 306 bytes while syncing on next audio frame
Jan 29 21:02:40 [vdr] [6137] switching to channel 10
Jan 29 21:02:40 [vdr] [6148] PANIC: watchdog timer expired - exiting!
ok - channel 10 is a Premiere Channel and I do not have a card, but why does this result in an immediate watchdog exit?
I thought that the watchdog will wait at least for the given time ( -w 60 ).
--
Helmut Auer, helmut(a)helmutauer.de
[View Less]
Hi Klaus,
With 1.3.39 and "Menu button closes" set to true, the main menu doesn't
open if any replay control is active. The attached patch fixes this by
resetting a !IsOpen cControl to WasOpen=false.
Cheers,
Udo
--- vdr-1.3.39-old/vdr.c 2006-01-15 18:33:54.000000000 +0100
+++ vdr-1.3.39/vdr.c 2006-01-15 18:38:28.000000000 +0100
@@ -795,8 +795,12 @@
bool WasMenu = Interact && Interact->IsMenu();
if (Menu)
DELETE_MENU;
- …
[View More] else if (cControl::Control() && cOsd::IsOpen())
- cControl::Control()->Hide();
+ else if (cControl::Control()) {
+ if (cOsd::IsOpen())
+ cControl::Control()->Hide();
+ else
+ WasOpen = false;
+ }
if (!WasOpen || !WasMenu && !Setup.MenuButtonCloses)
Menu = new cMenuMain;
}
[View Less]
Hallo,
as there were still compile errors with 1.2.6 there is a new version
of eggtimer plugin:
- now compiles with VDR 1.2.6 (at least I hope)
- added finish OSD translation (thanks to Rolf Ahrenberg)
http://194.95.44.38/~pjuszack/digicam/download/vdr-eggtimer-0.0.4.tgz
Have fun
Peter
I am pretty sure that this problem apperars in one of the last three
vdr-versions:
Recording from hr3 with DVB-C:
Jan 28 12:26:10 linvdr user.err vdr: [3078] cVideoRepacker: found system
start code: stream seems to be scrambled or not demul
Jan 28 12:26:44 linvdr user.info vdr: [2997] timer 2 (4 1640-1750
'Smallville') set to event Sam 28.01.2006 16:15-16:50 'Ritas
Jan 28 12:29:55 linvdr user.info vdr: [3016] channel 25 (hr-fernsehen) event
12:30 'c't magazin' status 4
Jan 28 12:30:01 linvdr …
[View More]cron.notice crond[3038]: USER root pid 3080 cmd
convert.pl -q -s
Jan 28 12:30:36 linvdr syslog.info -- MARK --
Jan 28 12:33:50 linvdr user.info vdr: [3013] channel 7 (RTL2) event 12:25
'In guten wie in schweren Tagen' status 4
Jan 28 12:35:01 linvdr cron.notice crond[3038]: USER root pid 3081 cmd
convert.pl -q -s
Jan 28 12:35:38 linvdr user.debug vdr: [3078] PES packet shortened to 1656
bytes (expected: 1840 bytes)
Jan 28 12:35:38 linvdr user.err vdr: [3078] cAudioRepacker(0xC0): skipped
392 bytes to sync on next audio frame
Jan 28 12:40:01 linvdr cron.notice crond[3038]: USER root pid 3082 cmd
convert.pl -q -s
Jan 28 12:41:06 linvdr user.err vdr: [3078] cVideoRepacker: found system
start code: stream seems to be scrambled or not demul
Jan 28 12:43:29 linvdr user.info vdr: [3013] channel 4 (RTL Television)
event 12:40 'Hor mal, wer da hammert!' status 4
Jan 28 12:43:45 linvdr user.debug vdr: [3078] PES packet shortened to 1656
bytes (expected: 1840 bytes)
BER according to femon is below 400, this should be good enough.
I never noticed this with recordings on the DVB-T-device.
On vdrportal three guys reported the same problem.
[View Less]
Hi,
I'm using a diskless VDR 1.3.38 and noticed that during recordings the
network is saturated for 1-2 seconds every 30 seconds. I haven't seen
this with 1.3.22, so I asume this might be related to the
cUnbufferedFile class in 1.3.35+.
This leads to very uneven load on the vdr client (and the NFS-Server),
where I've seen 10000 interrupts per second during the flushes (a few
hundred irqs in between). I'm not sure whether this contributes to some
of my recordings being broken (c*Repacker …
[View More]errors), but I'd like to
distribute the writes more evenly.
Is there a way to get cUnbufferedFile to write the data every second, er
even continuously? The NFS-server is going to take care of writing the
data to disk anyway.
Andreas
[View Less]
Hi,
I'm having weird problems with my vdr box. It has been working fine for a
long time now, but a week ago some channels stopped showing. EPG data was
there, but the picture was blank and there was no sound. Problematic
channels were all in the same transponder (not sure if this is the correct
term, kanavanippu in Finnish). I started investigating the problem today and
noticed that if I hook up my video projector to the vdr-box the channels
won't show. If the projector is not hooked up, the …
[View More]channels show OK (I
checked this with vdradmin).
Has anybody else had similar problems? How did you solve them? I have a
spare display adapter and I might give it a try tomorrow.
The most puzzling thing here is the fact that the vdr-box has worked fine
for quite some time before this.
I'm using LinVDR 0.7 with kernel 2.6.12.
-Sami-
[View Less]