Hi list,
In the 'final' 1.0 version of the shutdown patch, and in VDR 1.5.1, a
small bug slipped through that prevented automatic shutdown after VDR
started for a recording only.
I've uploaded a new 1.1 version of the patches for VDR 1.4.5, VDR 1.5.0
and VDR 1.5.1 to my web page:
On 2/27/07, Marko Mäkelä [EMAIL PROTECTED] wrote:
This would be similar to analog VCRs, which
obviously remember the position even after being unplugged.
VCR's don't remember anything related to position, it's the tape itself that
moves (from one reel to the other), not the head in the VCR.
On Sat, Mar 03, 2007 at 04:36:03PM +0100, Klaus Schmidinger wrote:
Sorry, I forgot one feature request. In a private discussion with Klaus
a long time ago (around vdr 1.3.30), Klaus mentioned the idea of VDR
remembering the name of the last replayed recording across shutdowns.
That is,
Hi list,
Now that VDR 1.5.1 was published, I've also published the final 1.0
version of the shutdown rewrite. The changes since 0.4 are mainly by Klaus.
http://www.udo-richter.de/vdr/patches.html#shutdown
http://www.udo-richter.de/vdr/patches.en.html#shutdown
The patch is identical to the
Udo Richter wrote:
Matthias Schwarzott wrote:
In gentoo vdr package we added a small hack (attached), which
implements a svdrp call down to tell vdr it is inactive and will
shutdown in X minutes.
We call this from shutdown-scripts to let vdr retry shutdown in 5 min
(or other value if
On Sun, Jan 28, 2007 at 05:50:46PM +0100, Udo Richter wrote:
- Added #define PATCH_SHUTDOWN_REWRITE to detect the patch
Use #if VDRVERSNUM = 105xx || defined(PATCH_SHUTDOWN_REWRITE) after
final integration into VDR.
Now that VDR 1.5.1 includes the patch, I wonder if you are going to
On Sun, Feb 25, 2007 at 09:11:36PM +0200, Marko Mäkelä wrote:
On Sun, Jan 28, 2007 at 05:50:46PM +0100, Udo Richter wrote:
- Added #define PATCH_SHUTDOWN_REWRITE to detect the patch
Use #if VDRVERSNUM = 105xx || defined(PATCH_SHUTDOWN_REWRITE) after
final integration into VDR.
Now
Udo Richter wrote:
I've finished a fourth version of the shutdown rewrite. Again there are
two patches available, one for VDR 1.5.0, and one with slight changes
for 1.4.x.
Changes:
- Handle setup menu restart questions in cShutdown::ConfirmRestart()
- Act differently on SIGHUP:
Restart VDR
Marko Mäkelä wrote:
On Tue, Feb 20, 2007 at 08:52:20AM +0200, Rolf Ahrenberg wrote:
On Mon, 19 Feb 2007, Udo Richter wrote:
Rolf Ahrenberg wrote:
I've one question about this sentence:
Plugin %s wakes up in %ld min, continue?
If I'm pressing 'OK' here, does it continue the shutdown or
On 2/20/07, Marko Mäkelä [EMAIL PROTECTED] wrote:
Would it be enough to say %s wakes up?
That's fine if you don't mind using poor grammar. For example, femon wakes
up? makes absolutely no sense.
___
vdr mailing list
vdr@linuxtv.org
On Sun, 18 Feb 2007, Marko Mäkelä wrote:
On Sun, Feb 18, 2007 at 10:09:54PM +0100, Udo Richter wrote:
Editing - shut down anyway? ( no longer cutting ;) )
Schneide - trotzdem ausschalten?
Leikkaus kesken - sammutetaanko?
Hmm, this is inconsistent with most Finnish translations of
On Mon, 19 Feb 2007, Udo Richter wrote:
Rolf Ahrenberg wrote:
I've one question about this sentence:
Plugin %s wakes up in %ld min, continue?
If I'm pressing 'OK' here, does it continue the shutdown or running the
VDR?
I don't like it either, but didn't come up with a good other idea
Hi list,
I've finished a fourth version of the shutdown rewrite. Again there are
two patches available, one for VDR 1.5.0, and one with slight changes
for 1.4.x.
http://www.udo-richter.de/vdr/patches.html#shutdown
http://www.udo-richter.de/vdr/patches.en.html#shutdown
Changes:
- Renamed
Darren Salt wrote:
We re-define SIGHUP, so that it doesn't terminate VDR instantly, but
instead checks for activity. If user and vdr is inactive, act just like
sigterm, if there's some activity, ignore the signal.
An external script could then repeat sending the SIGHUP periodically until
In [EMAIL PROTECTED], Patrick Mackin wrote:
Is that HD-capable? HDTV seems quite common in NA, but currently in the
UK there are very few HD channels, only available through overpriced
subscriptions. It looks unlikely that there'll be any FTA/FTV HD until
at least after the analogue
Darren Salt wrote:
I guess the only situation that may cause a problem is if the VDR never
shuts down, eg. has no shutdown script at all. It must have some Min User
Inactivity setting, or else live viewing could be interrupted by the
automatic update.
The user inactivity setting isn't relevant
I demand that Udo Richter may or may not have written...
Darren Salt wrote:
I guess the only situation that may cause a problem is if the VDR never
shuts down, eg. has no shutdown script at all. It must have some Min
User Inactivity setting, or else live viewing could be interrupted by
the
On Sun, Feb 11, 2007 at 08:11:03PM +, Darren Salt wrote:
I demand that VDR User may or may not have written...
On 2/8/07, Marko Mäkelä [EMAIL PROTECTED] wrote:
(August already?)
Hey, I wrote that on 2007-02-08 (ISO date) or 8.2.2007 (German or
Finnish style date). I think there are
I demand that VDR User may or may not have written...
On 2/8/07, Marko Mäkelä [EMAIL PROTECTED] wrote:
(August already?)
On Thu, Feb 08, 2007 at 01:08:33PM +0200, Rolf Ahrenberg wrote:
BTW, I'm very used to VDR's current behaviour to shutdown itself after
the recording is made and don't
Darren Salt wrote:
Then there's the upgrade restart, which should be available via a signal. The
actual restart should be deferred if VDR is currently busy. (It is *possible*
to implement this via runvdr, but it's a lot easier to handle if VDR can
re-exec itself.)
H. Some kind of
I demand that Udo Richter may or may not have written...
Darren Salt wrote:
Then there's the upgrade restart, which should be available via a signal.
The actual restart should be deferred if VDR is currently busy. (It is
*possible* to implement this via runvdr, but it's a lot easier to handle
I demand that VDR User may or may not have written...
[snip]
Also, a coffee-maker is not a device used for entertainment purposes.
Nobody turns their coffee-maker on and then sits there watching it. I hope
not anyways.
They might point a camera (probably a webcam) at it, though...
[snip]
--
On Fri, Feb 09, 2007 at 05:55:54PM +, Darren Salt wrote:
I demand that VDR User may or may not have written...
[snip]
Also, a coffee-maker is not a device used for entertainment purposes.
Nobody turns their coffee-maker on and then sits there watching it. I hope
not anyways.
They
On Thu, Feb 08, 2007 at 01:08:33PM +0200, Rolf Ahrenberg wrote:
BTW, I'm very used to VDR's current behaviour to shutdown itself
after the recording is made and don't want to get rid of that one
either.
As far as I understand, nobody has suggested that we should get rid of that
feature. You
VDR User wrote:
On 2/7/07, *Klaus Schmidinger* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'd also say that the Power button should shutdown without confirmation
unless there is a recording going on or a plugin is Active().
To avoid accidental shutdowns it might still
[EMAIL PROTECTED]
Also, the user inactivity stuff is again, a bad idea. Vdr should not
assume anything or take action just because the user hasn't interacted
with it in a while. This type of behavior is simply not consistent with
other devices and not a behavior the user would expect. My tv will
On 2/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]
Also, the user inactivity stuff is again, a bad idea. Vdr should not
assume anything or take action just because the user hasn't interacted
with it in a while. This type of behavior is simply not consistent with
other
VDR User wrote:
Also, the user inactivity stuff is again, a bad idea. Vdr should not
assume anything or take action just because the user hasn't interacted
with it in a while. This type of behavior is simply not consistent with
other devices and not a behavior the user would expect. My tv
On Thu, 8 Feb 2007, VDR User wrote:
There is no reason to behave otherwise unless it's done thru some kind of
auto-shutoff? [y/n] setting. With a setting like that I suppose you could
specify to shut off at a certain time of the day or user-defined timeout
period. But force a shutdown because
VDR User wrote:
There is no reason to behave otherwise unless
it's done thru some kind of auto-shutoff? [y/n] setting.
As said above, its called Min User Inactivity and can be set to 0.
Also, a coffee-maker is not a device used for entertainment purposes.
Nobody turns their coffee-maker on
On 2/8/07, Udo Richter [EMAIL PROTECTED] wrote:
H. Can a coffee maker run VDR? :)
If it's possible, somebody will find a way! ;)
Any other existing options you want to know of?
I hadn't pay much attention to this thread until recently and the way some
things were worded made it seem
It's a safe assumption that when a user presses a power button, they intend
that the device be immediately turned off or shut down. I can't think of
any device that performs any differently. If a user wants to shut down vdr
after he's done watching a playback, he would obviously still be
On Wed, Feb 07, 2007 at 10:40:44PM +0100, Udo Richter wrote:
Marko Mäkelä wrote:
You can shut down while playback, you just have to confirm it. And if
you don't confirm it, VDR will shut down 5 minutes after the playback
ends.
Sure, if the playback ends. It won't end with my patched
Udo Richter wrote:
Marko Mäkelä wrote:
Well, that would still break this scenario: You're watching a recording
while it is being recorded. Then you get interrupted and push the Power
button. Before the timed recording finishes and VDR gets a chance to
shut down, you get back and push a
On Wed, Jan 31, 2007 at 10:55:11PM +0100, Udo Richter wrote:
Marko Mäkelä wrote:
First, and more important: Can you please suspend the playback of
recordings when Shutdown.IsUserInactive() holds?
This would break the other interesting feature, shut down VDR as soon as
the playback ends.
Marko Mäkelä wrote:
However, you're right about breaking that feature: if PlayVideo() and
PlayAudio() start refusing data when Shutdown.IsUserInactive() holds,
the playback will never end, and VDR would probably wait
MinUserInactivity (3 hours by default) until shutdown.
While playback, the
Peter Dittmann wrote:
How about a new two level inactivity timeout ?
After VDR starts the inactivity timeout uses a first short timeout (e.g.
5min) assuming that VDR has automaticly being started.
Actually, even in worst case you'll see the 5-minute-countdown, so you
already have enough time
Marko Mäkelä wrote:
Actually I would press the pause button, as I usually don't want to miss
anything. And then the playback should be halted anyway, no matter if
display is on or off.
But you surely would power the display off, to avoid burning the still
image on the CRT or plasma screen or
On Sat, Feb 03, 2007 at 10:48:42AM +0100, Udo Richter wrote:
Marko Mäkelä wrote:
Actually I would press the pause button, as I usually don't want to miss
anything. And then the playback should be halted anyway, no matter if
display is on or off.
But you surely would power the display off,
Hi,
But you surely would power the display off, to avoid burning the still
image on the CRT or plasma screen or to save the precious hours on the
lamp of your video beamer? Or maybe you have a TFT screen and do not
care about wasting electricity?
Surely this shouldn't be too difficult to
On Thu, Feb 01, 2007 at 08:27:14PM +0200, Marko Mäkelä wrote:
Maybe not switching off display while doing playback? It doesn't make
much sense anyway to run playback invisible.
It does. The typical use case is that you pause live video or start
a recording with a timer, then start
In [EMAIL PROTECTED], you wrote:
I wouldn't be so sure about the majority of VDRs using FF cards. I
haven't seen any ad for an FF card, but I have seen many ads for cheap
USB DVB-T tuners. The trend is likely to change, given that decoding
MPEG-2 is no challenge to current PC hardware.
I wouldn't be so sure about the majority of VDRs using FF cards. I
haven't seen any ad for an FF card, but I have seen many ads for cheap
USB DVB-T tuners. The trend is likely to change, given that decoding
MPEG-2 is no challenge to current PC hardware.
Also generic video cards are
In [EMAIL PROTECTED], Patrick Mackin wrote:
Also generic video cards are increasingly coming with video decoding
features, and HDTVs can be connected straight to a PC without the need
for a horrible scaler or special screen mode. Although not all the
decoding features are available to Linux,
On Wed, Jan 31, 2007 at 09:02:58AM +0200, Rolf Ahrenberg wrote:
I would rather write käynnistyy instead of the foreign aktivoituu.
But VDR starts (käynnistää) all plugins already at the beginning and
depending on the plugins behaviour it's activated on main menu action,
external trigger,
On Wed, 31 Jan 2007, Marko Mäkelä wrote:
I didn't think of that. If the verb is already used in some translation
string, it might be good to avoid using the verb in another context.
What about Laajennos herää (Plugin wakes up)?
That sounds ok.
When VDR invokes the external shutdown script,
I believe that we have reached consensus on the Finnish translation.
On Sun, Jan 28, 2007 at 05:50:46PM +0100, Udo Richter wrote:
- i18n strings:
VDR will shut down later. Press power to force.
VDR sammuu myöhemmin - pakota virtakytkimellä
VDR will shut down in %s minutes
VDR sammuu %s
Marko Mäkelä wrote:
First, and more important: Can you please suspend the playback of
recordings when Shutdown.IsUserInactive() holds? Here is the relevant
hunk from my vdr-suspend patch:
This would break the other interesting feature, shut down VDR as soon as
the playback ends. Also, this
On Tuesday 30 January 2007 19:28, Marko Mäkelä wrote:
On Sun, Jan 28, 2007 at 05:50:46PM +0100, Udo Richter wrote:
Plugin activity in %ld minutes, shut down anyway?
Liitännäinen toimii %ld minuutin päästä, sammutetaanko?
IIRC plugin has been translated to laajennos elsewhere in VDR - no
On Tue, 30 Jan 2007, Marko Mäkelä wrote:
Here are my suggested Finnish translations, and some comments and questions.
I'd use passive sentencies and no comma at the ends and try to use the
current style.
VDR will shut down later. Press power to force.
VDR sammuu myöhemmin. Pakota
On Tuesday 30 January 2007 21:56, Rolf Ahrenberg wrote:
Laajennos aktivoituu %ld kuluttua - sammutetaanko?
Should be ...%ld minuutin kuluttua...
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Tue, Jan 30, 2007 at 09:56:36PM +0200, Rolf Ahrenberg wrote:
I'd use passive sentencies and no comma at the ends and try to use the
current style.
I agree with you that it is good to maintain a consistent style.
However, The passive voice should be avoided. I quickly browsed some
tooltips
On Tue, Jan 23, 2007 at 10:19:57PM +0100, Udo Richter wrote:
Since the shutdown script runs in the background, the stdin could
probably be closed. After all, VDR should continue to 'own' stdin, and
running in the background would probably cause a conflict. However,
running the script with a
Marko Mäkelä wrote:
On Tue, Jan 23, 2007 at 10:19:57PM +0100, Udo Richter wrote:
Since the shutdown script runs in the background, the stdin could
probably be closed. After all, VDR should continue to 'own' stdin, and
running in the background would probably cause a conflict. However,
running
Marko Mäkelä wrote:
The problem seems to lie in shutdown.c, in SystemExecSession().
It won't close file descriptor 0, but it will close anything above
STDERR_FILENO (which is normally 2). This function appears to show
up in strace output as clone(). Adding close(0) to the function
fixes the
On Sat, Jan 13, 2007 at 09:48:47PM +0100, Udo Richter wrote:
A more important suggestion: Could you please add a notification method
to status.h for notifying plugins whether VDR is currently in
interactive mode?
You can poll this state on your own by calling
Shutdown.IsUserInactive().
On Tue, Jan 16, 2007 at 12:15:32AM +0100, Udo Richter wrote:
Marko Mäkelä wrote:
While VDR is running, I would guess that the only way it can become
interactive is by receiving button events from the remote control unit.
Hmm, ok, I was mainly thinking of becoming inactive - since this is
Marko Mäkelä wrote:
Right, becoming inactive is not that time-critical. I will give your
suggestion a try: in the MainThreadHook of each plugin, poll
Shutdown.IsUserInactive().
It should work, though the first key press may trigger some longer work,
and the MainThreadHook will be called at
On Wed, Jan 10, 2007 at 02:28:24PM +0100, Udo Richter wrote:
Hi list,
I've finished a second version of the shutdown rewrite. This time, there
are two patches available, one for VDR 1.5.0, and one with slight
changes for 1.4.x.
http://www.udo-richter.de/vdr/patches.html#shutdown
Marko Mäkelä wrote:
A minor cosmetic thing: the '#' of pre-processor directives should always
be located at the first column of the line.
The only indented directives are for the debug output I think, and this
will probably be removed before the final integration anyway.
A more important
Hi list,
I've finished a second version of the shutdown rewrite. This time, there
are two patches available, one for VDR 1.5.0, and one with slight
changes for 1.4.x.
http://www.udo-richter.de/vdr/patches.html#shutdown
http://www.udo-richter.de/vdr/patches.en.html#shutdown
- Fixed negative
Klaus Schmidinger wrote:
However, (don't know exactly if this has already been suggested as such)
maybe a simple feature in the new shutdown code could be to allow the
user to specify *one* time at which VDR shall be guaranteed to be up,
along with a time period for which it shall stay up. That
Udo Richter wrote:
Klaus Schmidinger wrote:
However, (don't know exactly if this has already been suggested as such)
maybe a simple feature in the new shutdown code could be to allow the
user to specify *one* time at which VDR shall be guaranteed to be up,
along with a time period for which
Klaus Schmidinger wrote:
Udo Richter wrote:
The downside of this would be that again several external tasks would
fight for one resource: the time set in VDR.
I don't see why several external tasks would fight for that time.
This is something the user would set up the way he wants it. If he
[EMAIL PROTECTED] wrote:
The alternative would be to implement a generic task scheduler and make
timers one special type of schedule. This would get REALLY big.
Yes, but it will be the much better design.
It will open the option to do VDR related timed and maintainance tasks.
There must be
Udo Richter wrote:
[EMAIL PROTECTED] wrote:
The alternative would be to implement a generic task scheduler and
make timers one special type of schedule. This would get REALLY big.
Yes, but it will be the much better design.
It will open the option to do VDR related timed and maintainance
Matthias Schwarzott wrote:
I think a much easier solution (implementable in runvdr/vdr-initscript) is:
Write down wakeup-time when shutting down and comparing that to time when
system/vdr starts (with some margin).
That would be the way I would do it. Reconstructing the reason for
shutdown
Matthias Schwarzott wrote:
In gentoo vdr package we added a small hack (attached), which implements a
svdrp call down to tell vdr it is inactive and will shutdown in X minutes.
We call this from shutdown-scripts to let vdr retry shutdown in 5 min (or
other value if needed).
Question is: Is
Christian Wieninger wrote:
perhaps this is too trivial, but why not create a daily or whatever
timer as you suggested before with a special name like '@epgscan' and
react on that?
This would be a dirty ugly hack. There must be some pseudo-recording
running so VDR does not restart the
I'm kind of surprised people even bother to shutdown vdr at all. Didn't
really how big of an issue this was until reading this thread. That's all I
have to offer the discussion at this point. My apologies. :)
___
vdr mailing list
vdr@linuxtv.org
2006/12/30, Udo Richter [EMAIL PROTECTED]:
However, it might be worth thinking about giving plugins the ability to
set a different wakeup time, so that a scheduled EPG scan plugin can be
written.
I also think that this would be very helpful for some plugins. Manual
start detection could also
2006/12/31, Matthias Schwarzott [EMAIL PROTECTED]:
I think a much easier solution (implementable in runvdr/vdr-initscript) is:
Write down wakeup-time when shutting down and comparing that to time when
system/vdr starts (with some margin).
Thats right, this is even more robust. But I think this
Hi,
Udo Richter wrote:
Actually, whether this is internally or externally, the complexity stays
the same. It would probably work mostly the same way: Tweak the wakeup
time, detect this on wakeup, start the EPG scan, go offline.
perhaps this is too trivial, but why not create a daily or
Hi,
Udo Richter wrote:
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.
Further feature request:
At least on single card systems it would be nice to have VDR wakeup e.
g. at 03:01
Hi Udo,
thanks for your great work.
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'
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
76 matches
Mail list logo
