Re: [vdr] Utf8-patch experiences, anyone?
Hi Alexander, Any progress on utf8 patch for 1.4.4? Merry Christmas & Happy New Year Vladimir On Wed, 2006-12-06 at 01:08 +0100, Alexander Riedel wrote: > Hi Marko, > > last debian or freetype has problems with utf8 patch. I know. :-/ > Version for > 1.4.4 will fix it. > You can try older freetype versions or wait. > > Und also link to German wiki: > http://www.vdr-wiki.de/wiki/index.php/Utf8-patch > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
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 include a call to the plugins. A plugin that did "schedule" an EPG-scan or similar could tell VDR during start up, that VDR woke up because of this scheduled event set by this plugin. At the moment I use a relatively complex patch that does some "maintainance" task during the night. If it would be possible to modify the wakeup-time in a plugin I could re-implement the complete patch as a plugin. Regards, Joachim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Problems compiling mailbox plugin 0.4.0
Hi! I'm having problems with mailbox plugin. When I try to compile it I get: Plugin mailbox: make[1]: Entering directory `/vdr-system/vdr/PLUGINS/src/mailbox-0.4.0' g++ -fPIC -g -O2 -Wall -Woverloaded-virtual -fno-operator-names -D_GNU_SOURCE -DHAVE_VDR=1 -c -DPLUGIN_NAME_I18N='"mailbox"' -I./AxLib/include -I/usr/include/imap -I../../../include -o AxLib/src/Mail/CallBackDispatcher.o AxLib/src/Mail/CallBackDispatcher.cpp In file included from AxLib/src/Mail/CallBackProcessor.h:37, from AxLib/src/Mail/CallBackDispatcher.h:40, from AxLib/src/Mail/CallBackDispatcher.cpp:42: AxLib/src/Mail/c-client-header.h:30:22: c-client.h: No such file or directory Am I doing something wrong? Running Debian Sarge and vdr 1.4.2 -J- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problems compiling mailbox plugin 0.4.0
Am Sonntag 31 Dezember 2006 13:45 schrieb Jere Malila: > I'm having problems with mailbox plugin. When I try to compile it I get: [...] > AxLib/src/Mail/c-client-header.h:30:22: c-client.h: No such file or > directory Install libc-client-dev Package. Greetings Michi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
On Sunday 31 December 2006 13:36, Joachim Wilke wrote: > 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 include a call to the plugins. A plugin > that did "schedule" an EPG-scan or similar could tell VDR during start > up, that VDR woke up because of this scheduled event set by this > plugin. > At the moment I use a relatively complex patch that does some > "maintainance" task during the night. If it would be possible to > modify the wakeup-time in a plugin I could re-implement the complete > patch as a plugin. > 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). Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
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 should be implemented in the vdr core not in scripts. Regards, Joachim. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
On Sunday 31 December 2006 14:15, Joachim Wilke wrote: > 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 should be > implemented in the vdr core not in scripts. > How could vdr know what the system does otherwise. I think here the principle of KISS should be applied: keep it simple stupid. Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
Matthias Schwarzott schrieb: On Sunday 31 December 2006 13:36, Joachim Wilke wrote: 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 include a call to the plugins. A plugin that did "schedule" an EPG-scan or similar could tell VDR during start up, that VDR woke up because of this scheduled event set by this plugin. At the moment I use a relatively complex patch that does some "maintainance" task during the night. If it would be possible to modify the wakeup-time in a plugin I could re-implement the complete patch as a plugin. 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's exactly what my Gen2VDR distribution is doing, and it works fine. It's not the job of vdr to guess why it was started, but it would be nice if vdr offers an option to shutdown after next recording ( maybe via svdrp call ). -- Helmut Auer, [EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
On Sunday 31 December 2006 15:02, Helmut Auer wrote:
> Matthias Schwarzott schrieb:
> > On Sunday 31 December 2006 13:36, Joachim Wilke wrote:
> >> 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 include a call to the plugins. A plugin
> >> that did "schedule" an EPG-scan or similar could tell VDR during start
> >> up, that VDR woke up because of this scheduled event set by this
> >> plugin.
> >> At the moment I use a relatively complex patch that does some
> >> "maintainance" task during the night. If it would be possible to
> >> modify the wakeup-time in a plugin I could re-implement the complete
> >> patch as a plugin.
> >
> > 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's exactly what my Gen2VDR distribution is doing, and it works fine.
> It's not the job of vdr to guess why it was started, but it would be nice
> if vdr offers an option to shutdown after next recording ( maybe via svdrp
> call ).
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).
Matthias
--
Matthias Schwarzott (zzam)
Written by Matthias Schwarzott <[EMAIL PROTECTED]>
GENTOO_NO_PREPARE
diff -ru --exclude='*.o' vdr-1.3.36-orig/svdrp.c vdr-1.3.36/svdrp.c
--- vdr-1.3.36-orig/svdrp.c 2005-12-29 00:02:26.0 +0100
+++ vdr-1.3.36/svdrp.c 2005-12-29 00:18:45.0 +0100
@@ -293,6 +293,9 @@
"Updates a timer. Settings must be in the same format as returned\n"
"by the LSTT command. If a timer with the same channel, day, start\n"
"and stop time does not yet exists, it will be created.",
+ "DOWN [ ]\n"
+ "Starts an automatic shutdown (with 5 minutes waiting time) in given\n"
+ "minutes or now if no number was given.",
"VOLU [ | + | - | mute ]\n"
"Set the audio volume to the given number (which is limited to the range\n"
"0...255). If the special options '+' or '-' are given, the volume will\n"
@@ -1342,6 +1345,16 @@
Reply(501, "Missing timer settings");
}
+extern time_t LastActivity;
+void cSVDRP::CmdDOWN(const char *Option)
+{
+ if (isnumber(Option))
+ LastActivity = time(NULL) - Setup.MinUserInactivity*60 + strtol(Option, NULL, 10)*60;
+ else
+ LastActivity = time(NULL) - Setup.MinUserInactivity*60;
+ Reply(250, "Automatic shutdown triggered");
+}
+
void cSVDRP::CmdVOLU(const char *Option)
{
if (*Option) {
@@ -1413,6 +1426,7 @@
else if (CMD("STAT")) CmdSTAT(s);
else if (CMD("UPDT")) CmdUPDT(s);
else if (CMD("VOLU")) CmdVOLU(s);
+ else if (CMD("DOWN")) CmdDOWN(s);
else if (CMD("QUIT")) Close(true);
else Reply(500, "Command unrecognized: \"%s\"", Cmd);
}
diff -ru --exclude='*.o' vdr-1.3.36-orig/svdrp.h vdr-1.3.36/svdrp.h
--- vdr-1.3.36-orig/svdrp.h 2005-12-29 00:02:26.0 +0100
+++ vdr-1.3.36/svdrp.h 2005-12-30 02:28:08.0 +0100
@@ -59,6 +59,7 @@
void CmdDELC(const char *Option);
void CmdDELR(const char *Option);
void CmdDELT(const char *Option);
+ void CmdDOWN(const char *Option);
void CmdEDIT(const char *Option);
void CmdGRAB(const char *Option);
void CmdHELP(const char *Option);
diff -ru --exclude='*.o' vdr-1.3.36-orig/vdr.c vdr-1.3.36/vdr.c
--- vdr-1.3.36-orig/vdr.c 2005-12-29 00:02:26.0 +0100
+++ vdr-1.3.36/vdr.c 2005-12-29 00:09:49.0 +0100
@@ -89,6 +89,8 @@
exit(1);
}
+time_t LastActivity;
+
int main(int argc, char *argv[])
{
// Save terminal settings:
@@ -395,7 +397,7 @@
int PreviousChannel[2] = { 1, 1 };
int PreviousChannelIndex = 0;
time_t LastChannelChanged = time(NULL);
- time_t LastActivity = 0;
+ LastActivity = 0; // now being a global variable
time_t LastCamMenu = 0;
int MaxLatencyTime = 0;
bool ForceShutdown = false;
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problems compiling mailbox plugin 0.4.0
Michael Brueckner wrote: Am Sonntag 31 Dezember 2006 13:45 schrieb Jere Malila: I'm having problems with mailbox plugin. When I try to compile it I get: [...] AxLib/src/Mail/c-client-header.h:30:22: c-client.h: No such file or directory Install libc-client-dev Package. That was it. Thank you very much. I tested this mailbox plugin and it is very useful for me! -J- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Aw: Re: [vdr] vdr xine-plugin fbxine
- Original Nachricht Von: Reinhard Nissl <[EMAIL PROTECTED]> An: VDR Mailing List Datum: 30.12.2006 21:37 Betreff: Re: [vdr] vdr xine-plugin fbxine > > but fbxine does not understand the MRL vdr > Are you sure that you execute the correct fbxine binary? I forgot in the parameter _pes ! > It seems that your binary still loads an xine-lib which doesn't know > anything of the vdr:// MRL. > > What I expect from fbxine is : to adjust my tv-out better to the size of > my tv > Well, fbxine is not responsible for that. fbxine just takes care to > decode the stream into the frame buffer. Things like setting resolution > or overscan mode are either a matter of fbset or some other tool which > might be hardware dependent. It seems with fbxine I see less on the monitor an all on the tv. That's ok. The only drawback I see still is when I change several times the channels, fbxine hangs or stops. Maybe it depends of the quality of the transmission and I have to do some adjustement concerning the color for the tv Thank you for your help, Reinhard! Cheers H.Braun ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Fix EPG for UPC direct
On Fri, 8 Dec 2006, Thiemo Gehrke wrote: UPC is a provider for middle european countries (Czechia, Hungary and Poland). They use iso6937-2 for encoding their EPG data so this looks quite strange in the vdr. Hello the applied patch made no diffrence on my system, you can see the snapshot here: http://sysphere.org/~anrxc/upc.png -- PGP:0xA8916BBD | JID:anrxc|sysphere|org | sysphere.org/~anrxc/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Mplayer plugin does not always play files
I just stumbled in a problem while watching an mpg file using mplayer plugin. There was something causing vdr ro restart. vdr: [3846] record /srv/vdr/Amyn_lailla/2006-12-31.18.59.50.99.rec vdr: [5462] ERROR: /dev/dvb/adapter1/dvr0: Device or resource busy vdr: [3846] timer 55 (5 1859-1955 'Smallville') start vdr: [3846] record /srv/vdr/Smallville/2006-12-31.18.59.50.99.rec vdr: [5465] ERROR: /dev/dvb/adapter1/dvr0: Device or resource busy vdr: [5460] ERROR: video data stream broken vdr: [5460] initiating emergency exit Firstly, does using mplayer plugin cause device or resource busy error? Secondly, why cant I resume playing the mpg file I was watching? The mpg file is just a cut and repack of a vdr recording (ProjectX). And I had just watched a couple similar recordings. When restarting all drivers is reloaded. Last line in log after trying to restart play is: logger: *** DEBUG: Variable CMDLINE has value "/usr/bin/mplayer -vo mpegpes -ao mpegpes -framedrop -cache 4096 -slave -nolirc -quiet" Which is exactly same as when the replay works. I have noticed that sometimes I have to restart VDR to make it play the files on a mounted usb drive after mounting it. I have vdr-1.4.4 and vdr-mplayer-0.9.15. I've got two dvb-c cards (one ff and one budget). VDR seems to work otherwise normally. I could not find anything related wrom the mail archive. Anybody know any solution? \\Kartsa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
