Re: R: [vdr] VDR Multiple frontends - Function to detect if recording in progress
Eddi wrote: Hi, To finishing adding multiple frontend support, I need a function to know inside dvbdevice.c if recording is in progress. Is there a function ready? That would be cDevice::Receiving(). Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR does not resume VPS recording after restart
Andreas Breitenbach wrote: Hi all, I am using vdr-1.4.5. If I have started a recording without VPS it does automatically resume the recording, if VDR has been restarted (either manually or caused by a reset). This is not working for a VPS recording. I just tried that and it did resume the VPS recording just fine after restarting VDR. Maybe there are specific conditions under which this doesn't work? I could imagin that in that case the recording is fully controlled by the VPS signal. IMHO there should be some vanity check for the recording with VPS to avoid nonsens, e.g the recording should stop after, let say, 8 hours, even if no VPS stop signal has been received. I used to have a recording with 1380 minutes, I guess the stop signal was never detected. This kind of check should be used for the resume after a restart as well. Having a sanity check for the absolute maximum of a VPS controlled recording might be a good idea. However, I guess this will have to be yet another setup parameter. And it should control the maximum overtime, so that it doesn't matter how long the original scheduled time is. After all, somebody might want to record a show that runs for more than 8 hours... I'll see what I can do in version 1.5. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[PATCH]: [vdr] VDR Multiple frontends (finished)
The patch that enable multiple frontend with shared bus, should be finished and on my pc it seems to be stable enough. http://tux.dpeddi.com/lr319sta/downloads/vdr_1.4.5_eddi-multiple-frontend_v5 .patch Now the patch don't switch frontend, is recording in progress. Best Regards, Eddi -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Eddi Inviato: sabato 10 febbraio 2007 11.17 A: 'VDR Mailing List' Oggetto: R: [PATCH]: [vdr] VDR Multiple frontends, another try Hi, I've made another patch to vdr 1.4.5. Now I have used your suggestion, and the patch seems to be stable. http://tux.dpeddi.com/lr319sta/downloads/vdr_1.4.5_eddi-multiple- frontend_v2 .patch At the moment I've tested it only with live view. Klaus, please look at this patch again and tell me what do you think. However I'm sure that what I'm done can be optimized. Best regards Eddi -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Eddi Inviato: venerdì 9 febbraio 2007 14.28 A: 'VDR Mailing List' Oggetto: R: [PATCH]: [vdr] VDR Multiple frontends Ok, I hope that what I have done, may describe the algorithm that I think may be necessary to get multiple frontend working. I know that the solution I choose are not the best and right, I'm not a c++ programmer! The only solution I found to close all file descriptors and /dev/dvb/adapter0/frontend0 was to add the close fd_frontend to the dvb device destructor. Eddi -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Klaus Schmidinger Inviato: venerdì 9 febbraio 2007 13.43 A: vdr@linuxtv.org Oggetto: Re: [PATCH]: [vdr] VDR Multiple frontends Eddi wrote: So what do you think should be the right way? I haven't decided yet how to do that. I just wanted to let you know that deleting the cDvbDevice is not the way to go - especially if you delete it from within one of its own member functions ;-) It's no wonder your patched version fails it you saw off the branch you're sitting on. Klaus -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Per conto di Klaus Schmidinger Inviato: venerdì 9 febbraio 2007 8.27 A: vdr@linuxtv.org Oggetto: Re: R: [PATCH] R: R: [vdr] VDR Multiple frontends Eddi wrote: I need help This is why sometimes hangs after my patch... On ProvidesChannel I delete the cDvbDevice and i make it again. Deleting the cDvbDevice is definitely the wrong way to do this. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr vdr_1.4.5_eddi-multiple-frontend_v5.patch Description: Binary data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] VDR maintenance patch 1.4.5-2
VDR maintenance patch 1.4.5-2 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.5-2.diff This is a 'diff' against version 1.4.5-1 (which is the official version 1.4.5, patched with ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.5-1.diff). Small fixes to the officially released VDR versions will be first made available as maintenance patches in the Developer directory, so that they can be reviewed and tested before a new official release is published. So please apply the above patch and report whether it works (or if it causes any new problems). This version is binary compatible to the previous one, so plugins don't need to be recompiled. The changes since version 1.4.5-1: - Removed 'assert(0)' from cDvbSpuDecoder::setTime() (thanks to Marco Schlüßler). - Fixed a possible crash when loading an invalid XPM file (thanks to Martin Wache). - Updated satellite names in 'sources.conf' (thanks to Thilo Wunderlich). - Fixed handling error status in cDvbTuner::GetFrontendStatus() (thanks to Reinhard Nissl). Have fun! Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] dvbstream and vdr streamdev streaming format difference?
Hi all, I'm thinking to write a simple udp clone of vdr streamdev plugin. I tested dvbstream, but the problem is I couldn't play dvbstream streams with videlan, which is only player that I know works with linux and windows and could play streamdev streams. Does anybody know what format streamdev streams, and why videolan could not play dvbstream streams? although dvbstream says it uses rtp over udp protocol, and videolan has an option to play this. John. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-burn vdrconver segmentation fault
Hi,
I'm desperated with this problem. I can't do dvd's from my vdr recordings.
I have tried with vdr-burn and vdrconvert-vdr2dvd.
I'm using debian etch, kernel 2.6.17.13, vdr 1.4.3
My 0.1 vdrconvert log:
STAT: Processing
/conversiones/tmp/vdr2dvd/12616/DVDMENU/Titel-1/spu-submenu-1.mpg...
STAT: VOBU 0 at 0MB, 1 PGCS^M
/usr/local/bin/vdr2dvd.sh: line 583: 20156 Segment faultnice -n
$PRIO $DVDAUTHOR -x ${UniqueMENUDIR}/dvd.xml
ERROR : Fehler bei dvdauthor -x. rc=139
NOTICE : exit!
Aufruf /usr/local/bin/postvdr2dvd.sh mit parameter :
24-02-2007 21:48:35 : Session /usr/local/bin/vdr2dvd.sh Exit
My cvs vdr-burn log:
[mplex] + mplex -f 8 -S 0 -M -o
/tmp/vdr-burn.Planeta_Tierra__Bosques.4vMnLU/VDRSYNC.0/movie.mpg
/tmp/vdr-burn.Planeta_Tierra__Bosques.4vMnLU/VDRSYNC.0/vdrsync.mpv
/tmp/vdr-burn.Planeta_Tierra__Bosques.4vMnLU/VDRSYNC.0/vdrsync0.mpa
/tmp/vdr-burn.Planeta_Tierra__Bosques.4vMnLU/VDRSYNC.0/vdrsync1.mpa
[mplex]INFO: [mplex] mplex version 1.8.0 (2.2.4 $Date: 2005/08/28
17:50:54 $)
[author] /usr/bin/vdrburn-dvd.sh: line 45: 4944 Segment fault
dvdauthor -x $DVDAUTHOR_XML
[vdr] process author (pid = 4939) exited gracefully (exit code 139)
[vdr] process author exited
[vdr] ERROR: process demux (pid = 4937) crashed (signal 15)
[vdr] ERROR: process mplex (pid = 4938) crashed (signal 15)
Any help would be apreciated.
Thanks,
Leo.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x, version 0.4
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 like on setup menu restart, but dont ask questions.
Well, that was the intention. Next time I'll do it, promise! ;)
The attached patch fixes this and actually calls ConfirmRestart, not
ConfirmShutdown.
Beside that, things are getting close to land in VDR 1.5.x, so any last
minute bug hunting is welcome.
Cheers,
Udo
--- vdr.c.old 2007-02-24 22:36:26.707746080 +0100
+++ vdr.c 2007-02-24 22:38:21.012241392 +0100
@@ -1169,7 +1169,7 @@
if (LastSignal == SIGHUP) {
LastSignal = 0;
// Confirm for any activity that blocks a restart
- if (!Shutdown.ConfirmShutdown(true))
+ if (!Shutdown.ConfirmRestart(true))
// Not confirmed, cancel.
break;
--- menu.c.old 2007-02-24 22:36:23.037304072 +0100
+++ menu.c 2007-02-24 22:38:15.016152936 +0100
@@ -2726,7 +2726,7 @@
return osContinue;
// Confirm for any activity that blocks a restart
- if (!Shutdown.ConfirmShutdown(true))
+ if (!Shutdown.ConfirmRestart(true))
// Not confirmed, cancel.
return osContinue;
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] burn(cvs) makes crash my vdr 1.4.2
Hi Leo were you ever able to fix the problem you had with this I am having exactly the same problem althouigh with vdr-1.4.5 Any help would be great Mike ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
