Hi list,
The program code for automatic and manual shut down and for automatic
restarts for timer recordings is in VDR 1.4.x very complex and
error-prone, and behaves strange in some situations. With Klaus'
permission I am working on a re-implementation for the upcoming 1.5.x
developer builds of VDR.
I now want to publish a first draft version for testing and further
comments. Not all issues are fixed yet, but it already gives an
impression of the new code.
http://www.udo-richter.de/…
[View More]vdr/patches.html#shutdownhttp://www.udo-richter.de/vdr/patches.en.html#shutdown
New:
- Shutdown related code is now in shutdown.[ch]. vdr.c mainly delegates
the work to the cShutdown class, that does all necessary steps for
manual or automatic shutdown.
- cShutdown tracks whether there is an interactive user or not. (eg.
Min User Inactivity run out)
- cRemote tracks time of last key press separately and autonomously.
- The old 5-minute "Press any key to cancel..." message got replaced by
a 5 minute countdown message that counts in 10-second steps
- Since the new code is modularized, plugins will have access to
activity tracking, can mess with inactivity state, and can initiate
shutdown behavior similar to the kPower button.
(But, please, only if you have to. ;) )
Fixed:
- Pressing power button while recording playback works again, instead of
doing nothing visible. (and not shutting down within 5 seconds at
playback end.)
- Show 5-minute shutdown message after background activity ends, if
power button was pressed but not confirmed
- Not freezing the VDR main loop while 5-minute shutdown message
- Background activity now cancels the 5-minute shutdown message
- Not messing with watchdog (and forgetting to re-enable) while 5-minute
shutdown message
- Timers set via SVDRP while in 5-minute shutdown message did not start
and were not considered for reboot time.
- Calling the main menu action of a plugin and closing a menu doesn't
count as user activity any more
Todo:
- Start the 5-minute countdown 5 minutes _before_ min user inactivity
runs out. (also does not add 5min to SHUTDOWNRETRY any more)
- Fix negative time in shutdown confirm if VPS timer is in run-out phase
Possible changes:
- Make the 'inactive' mode (waiting for background activity to end, then
shut down) more visible to the user:
- Suggestion was to put up a message 'VDR will shut down when idle.
Press power button again to force shutdown' before starting the
confirms.
- Alternative may be a message 'VDR will shut down later when idle' if
shutdown was not confirmed
- Alternative may be to permanently put up a message 'VDR is waiting
for background tasks to complete'.
- What should happen if a user confirms to shut down while a running /
pending timer is scheduled. Currently, VDR will reboot after
MinEventTimeout, but VDR could also reboot at the next timer that
starts after MinEventTimeout - or never.
- There is a feature request that the caller should be able to notify
VDR whether VDR was started manually or automatically. (VDR currently
guesses by searching for nearby timers)
- There is a feature request to start the external shutdown script
asynchronously, so the shutdown script does not block VDR any more.
- A 'bug' in the old code allows to automatically shut down VDR at the
end of a playback, though this was probably never intended. It could
however be re-added as 'feature'.
There's some debug output code to monitor the various timers on console.
If you don't want that, you can disable it in vdr.c, search for #define
DebugTimeouts and comment it out.
Cheers,
Udo
[View Less]
Anyone know why VDR won't pick up the different channels on this frequency?
All I get is Kiosque, but I know there are
Cine+ Foot 1 2 3 4 etc..?
apart from hacking it by hand, anyone know of a solution?
Hi,
I have two cards in my video server:
Technotrend/Hauppauge WinTV Nexus-S rev2.3)
Hauppauge Nova-S-Plus DVB-S [card=37]
lspci:
01:0c.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
01:0c.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
01:0c.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
01:0c.4 Multimedia controller: Conexant CX23880/1/2/3 PCI …
[View More]Video and Audio Decoder [IR Port] (rev 05)
01:0f.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
when I use szap to change the channel, I can switch, record, switch,
record .... (record with "cat /dev/dvb/adapter1/dvr0 >/tmp/tsvideo".
But when I try to record with vdr, I get the following errors and
nothing will be record:
(with plain vdr-1.5.0 and plain vdr-1.4.0 and v4l-dvb from yesterdays hg):
Feb 9 12:02:00 video vdr: [30529] connect from 127.0.0.1, port 60607 - accepted
Feb 9 12:02:00 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') added
Feb 9 12:02:00 video vdr: [30529] closing SVDRP connection
Feb 9 12:02:00 video vdr: [30529] switching device 2 to channel 1
Feb 9 12:02:00 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') start
Feb 9 12:02:00 video vdr: [30529] Title: 'Tagesschau um zwölf' Subtitle: ''
Feb 9 12:02:00 video vdr: [30529] record /data/nobackup/video/Tagesschau_um_zwölf/2007-02-09.12.00.50.50.rec
Feb 9 12:02:00 video vdr: [30529] creating directory /data/nobackup/video/Tagesschau_um_zwölf
Feb 9 12:02:01 video vdr: [30529] creating directory /data/nobackup/video/Tagesschau_um_zwölf/2007-02-09.12.00.50.50.rec
Feb 9 12:02:01 video vdr: [30529] recording to '/data/nobackup/video/Tagesschau_um_zwölf/2007-02-09.12.00.50.50.rec/001.vdr'
Feb 9 12:02:01 video vdr: [30529] connect from 127.0.0.1, port 60610 - accepted
Feb 9 12:02:01 video vdr: [30529] closing SVDRP connection
Feb 9 12:02:01 video vdr: [30603] file writer thread started (pid=30529, tid=30603)
Feb 9 12:02:01 video vdr: [30604] recording thread started (pid=30529, tid=30604)
Feb 9 12:02:01 video vdr: [30605] receiver on device 2 thread started (pid=30529, tid=30605)
Feb 9 12:02:01 video vdr: [30606] TS buffer on device 2 thread started (pid=30529, tid=30606)
Feb 9 12:02:03 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') set to event Fre 09.02.2007 12:00-12:15 (VPS: 09.02 12: 00) 'Tagesschau um zwölf'
Feb 9 12:02:09 video vdr: [30537] frontend 1 timed out while tuning to channel 1, tp 111836
Feb 9 12:02:10 video vdr: [30529] connect from 127.0.0.1, port 60614 - accepted
Feb 9 12:02:10 video vdr: [30529] closing SVDRP connection
Feb 9 12:02:10 video vdr: [30529] connect from 127.0.0.1, port 60617 - accepted
Feb 9 12:02:10 video vdr: [30529] closing SVDRP connection
Feb 9 12:02:27 video vdr: [30529] connect from 127.0.0.1, port 60622 - accepted
Feb 9 12:02:27 video vdr: [30529] closing SVDRP connection
Feb 9 12:02:32 video vdr: [30603] ERROR: video data stream broken
Feb 9 12:02:32 video vdr: [30603] initiating emergency exit
Feb 9 12:02:32 video vdr: [30529] emergency exit requested - shutting down
Feb 9 12:02:32 video vdr: [30604] recording thread ended (pid=30529, tid=30604)
Feb 9 12:02:32 video vdr: [30603] file writer thread ended (pid=30529, tid=30603)
Feb 9 12:02:32 video vdr: [30529] buffer stats: 0 (0%) used
Feb 9 12:02:32 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') stop
Feb 9 12:02:32 video vdr: [30529] saved setup to /etc/vdr/setup.conf
Feb 9 12:02:32 video vdr: [30534] tuner on device 1 thread ended (pid=30529, tid=30534)
Feb 9 12:02:33 video vdr: [30606] TS buffer on device 2 thread ended (pid=30529, tid=30606)
Feb 9 12:02:33 video vdr: [30605] buffer stats: 0 (0%) used
Feb 9 12:02:33 video vdr: [30605] receiver on device 2 thread ended (pid=30529, tid=30605)
Feb 9 12:02:33 video vdr: [30533] CI adapter on device 0 thread ended (pid=30529, tid=30533)
Feb 9 12:02:33 video vdr: [30535] section handler thread ended (pid=30529, tid=30535)
Feb 9 12:02:34 video vdr: [30537] tuner on device 2 thread ended (pid=30529, tid=30537)
Feb 9 12:02:34 video vdr: [30538] section handler thread ended (pid=30529, tid=30538)
Feb 9 12:02:36 video vdr: [30529] =====================
Feb 9 12:02:36 video vdr: [30529] EPG bugfix statistics
Feb 9 12:02:36 video vdr: [30529] =====================
Feb 9 12:02:36 video vdr: [30529] IF SOMEBODY WHO IS IN CHARGE OF THE EPG DATA FOR ONE OF THE LISTED
Feb 9 12:02:36 video vdr: [30529] CHANNELS READS THIS: PLEASE TAKE A LOOK AT THE FUNCTION cEvent::FixEpgBugs()
Feb 9 12:02:36 video vdr: [30529] IN VDR/epg.c TO LEARN WHAT'S WRONG WITH YOUR DATA, AND FIX IT!
Feb 9 12:02:36 video vdr: [30529] =====================
Feb 9 12:02:36 video vdr: [30529] Fix Hits Channels
Feb 9 12:02:36 video vdr: [30529] 3 15 Dok&Deb, hr-fernsehen, KiKa
Feb 9 12:02:36 video vdr: [30529] 4 5 SWR2, SWR2, 3sat
Feb 9 12:02:36 video vdr: [30529] 6 418 MDR SACHSEN, hr-fernsehen, WDR Köln, Bayerisches FS, Das Erste, Phoenix, arte, ...
Feb 9 12:02:36 video vdr: [30529] =====================
Feb 9 12:02:36 video vdr: [30529] exiting
Feb 9 12:02:36 video vdr: [30529] emergency exit!
so why can I get ts streams from the second dvb card and vdr doesn't get
any bytes ?
--
Gruß
Dieter
--
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
From field.
[View Less]
Hi,
I was trying to apply the latest xine patches (that come with xine-0.7.10) to
cvs of xine-lib and I have hit a problem. The patch is looking for this
line to replace:
-dsputil_mmx.o dsputil_mmx.lo: CFLAGS=`echo @CFLAGS@ | sed -e
's/-funroll-loops//g; s/-O[0-9]/-Os/g'`
+dsputil_mmx.o dsputil_mmx.lo: CFLAGS=$(shell echo @CFLAGS@ | sed -e
's/-funroll-loops//g; s/-O([0-9]|s|$)/-Os /g')
But, now the original line looks like this:
dsputil_mmx.o dsputil_mmx.lo: CFLAGS=$(shell echo @CFLAGS@ | …
[View More]sed -e
's/-funroll-loops//g; s/$$/ -Os/')
Should i just leave it as is now?
Best Regards.
[View Less]
---------- Weitergeleitete Nachricht ----------
Betreff: Re: Noch was
Datum: Dienstag, 27. Februar 2007
Von: Matthias Schwarzott <zzam(a)gentoo.org>
An: Helmut Auer <helmut(a)helmutauer.de>
On Montag, 26. Februar 2007, you wrote:
> P.S. Benoetigt Ihr evtl. noch einen ebuilder ? Was muesste ich dafuer
> fuer Vorraussetzungen mitbringen ?
Generell brauchen wir immer mehr Leute :)
Weil es hat ja eh nicht jeder jede Hardware, und auch nicht unbedingt die Zeit
alles zu machen.…
[View More]
Voraussetzungen: Am besten ebuild Kentnisse, geht aber auch ohne
so schwer ist das nicht
Eigentlich ist so ein ebuild shell-code
Beste doku dazu ist die hier (mit vielen Beispielen):
http://devmanual.gentoo.org/
Oder du schaust einfach mal in ein paar ebuilds rein.
Matthias
--
Matthias Schwarzott (zzam)
-------------------------------------------------------
--
Matthias Schwarzott (zzam)
[View Less]
Hi,
this patch allows plugins to replace the VDR mainmenus "Schedule", "Channels",
"Timers" and "Recordings" by a different implementation.
There are already a few plugins around which do something like that, using
their own idea of a patch. So Tobias Grimm, Martin Prochnow, Christian
Wieninger and me made an effort to find a common solution for the problem. The
patch is based on a suggestion of Christian Wieninger back in March 2006
(http://www.linuxtv.org/pipermail/vdr/2006-March/008234.…
[View More]html). It is meant to
be an interim solution for VDR 1.4 until (maybe) VDR 1.5 introduces an
official API for this purpose.
Please note that no plugin supports this patch yet. We wanted to introduce it
to the list first. Maybe there are some additional requirements we didn't
think of.
You will find more detailed information in the patch file.
Enjoy,
Frank
[View Less]
Hello,
I am getting ts continuity errors in vdr with my tt 2300.
Since 3 weeks I am trying to optimize my system.
Now there is the Question of signal Problems.
I did not have any problems with my other telestar receiver so I did not
check the signal before.
Femon shows the folowing on RTL on astra 19,2.
status 1f | signal ac7c | snr d6dd | ber 00001200 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ac73 | snr d6dd | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ac7b | snr …
[View More]d6f2 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ac7c | snr d73a | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ac7d | snr d719 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ac77 | snr d6fb | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ac67 | snr d6e6 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal adb8 | snr d6f8 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ac74 | snr d70d | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ac78 | snr d6dd | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ac5e | snr d6e3 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
Are these values ok or not?
Can someone compare these output with the same card?
Thanks
--
Halim Sahin
E-Mail:
halim.sahin (at) t-online.de
[View Less]
Hi,
now its time to have a second VDR.
It should boot completely via PXE and run everything over NFS
(completelty diskless). It will mount everything from my Master-VDR
server.
The first step was easy, I moved all the config files to /etc/vdr, so
I will be able to hold a own configuration on each host.
The second computer will only have one DVB card (FF) so it should don't
do any EPG scan, but it should use the EPG file from my Master-VDR.
Is that possible?
(the epg-file is saved in /…
[View More]video0 and that directory should be mounted
via NFS)
Best regards,
Matthias
--
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
[View Less]