[vdr] [PATCH] Systemd watchdog support
Hi,
Here is a patch I use to enable systemd watchdog support in VDR. It
doesn't replace the internal watchdog, it just allow setting
WatchdogSec directive in service file so if VDR watchdog is unable to
exit, systemd take care of restarting it.
I use this patch against VDR 2.2.0 without problem for few mouths (I
set systemd watchdog to the same value than VDR watchdog to avoid
interference between them). If you are interested to include it, I can
see if it apply to dev branch, but there is only ~20 lines so it should
apply without modification.
Note that the first and last chunk are only systemd notifications about
the current state of VDR and they can be removed if needed.
Regards,
Marc.
diff -Naur a/vdr.c b/vdr.c
--- a/vdr.c 2015-02-10 15:13:12.0 +0100
+++ b/vdr.c 2016-05-02 13:37:43.180638765 +0200
@@ -170,6 +170,9 @@
// Something terrible must have happened that prevented the 'alarm()' from
// being called in time, so let's get out of here:
esyslog("PANIC: watchdog timer expired - exiting!");
+#ifdef SDNOTIFY
+ sd_notify(0, "STOPPING=1\nSTATUS=PANIC");
+#endif
exit(1);
}
@@ -234,6 +237,10 @@
#if defined(VDR_USER)
VdrUser = VDR_USER;
#endif
+#ifdef SDNOTIFY
+ time_t SdWatchdog;
+ int SdWatchdogTimeout = 0;
+#endif
cArgs *Args = NULL;
if (argc == 1) {
@@ -904,6 +911,16 @@
}
#ifdef SDNOTIFY
+ if (sd_watchdog_enabled(0, NULL) > 0) {
+ uint64_t timeout;
+ SdWatchdog = time(NULL);
+ sd_watchdog_enabled(0, );
+ SdWatchdogTimeout = (int)timeout/100;
+ dsyslog("SD_WATCHDOG enabled with timeout set to %d seconds", SdWatchdogTimeout);
+ }
+
+ // Startup notification:
+
sd_notify(0, "READY=1\nSTATUS=Ready");
#endif
@@ -958,6 +975,14 @@
dsyslog("max. latency time %d seconds", MaxLatencyTime);
}
}
+#ifdef SDNOTIFY
+// Ping systemd watchdog when half the timeout is elapsed:
+if (SdWatchdogTimeout && (Now - SdWatchdog)*2 > SdWatchdogTimeout) {
+ sd_notify(0, "WATCHDOG=1");
+ SdWatchdog = Now;
+ dsyslog("SD_WATCHDOG ping");
+}
+#endif
// Handle channel and timer modifications:
if (!Channels.BeingEdited() && !Timers.BeingEdited()) {
int modified = Channels.Modified();
@@ -1494,5 +1519,11 @@
closelog();
if (HasStdin)
tcsetattr(STDIN_FILENO, TCSANOW, );
+#ifdef SDNOTIFY
+ if (ShutdownHandler.GetExitCode() == 2)
+ sd_notify(0, "STOPPING=1\nSTATUS=Startup failed, exiting");
+ else
+ sd_notify(0, "STOPPING=1\nSTATUS=Exiting");
+#endif
return ShutdownHandler.GetExitCode();
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Deactivate a Tuner
On 20/08/2013 18:48, Brian-Imap wrote:
On 8/20/2013 6:28 PM, Brian-Imap wrote:
On 8/19/2013 11:10 PM, Marc wrote:
On 19/08/2013 21:11, Brian-Imap wrote:
Hi,
well Its exactly what I was doing, and I cant see a difference.
Here an example of two of the Cine S2 Tuners:
VDR-test-cellar (SDB1): udevadm info -a -p $(udevadm info -q path
-n /dev/dvb/adapter3/frontend0)
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb3.frontend0':
KERNEL==dvb3.frontend0
SUBSYSTEM==dvb
DRIVER==
looking at parent device
'/devices/pci:00/:00:0d.0/:02:00.0':
KERNELS==:02:00.0
SUBSYSTEMS==pci
DRIVERS==DDBridge
ATTRS{irq}==16
ATTRS{subsystem_vendor}==0xdd01
ATTRS{broken_parity_status}==0
ATTRS{class}==0x048000
ATTRS{consistent_dma_mask_bits}==32
ATTRS{dma_mask_bits}==32
ATTRS{local_cpus}==ff
ATTRS{device}==0x0003
ATTRS{enable}==1
ATTRS{msi_bus}==
ATTRS{local_cpulist}==0-7
ATTRS{vendor}==0xdd01
ATTRS{subsystem_device}==0x0020
looking at parent device '/devices/pci:00/:00:0d.0':
KERNELS==:00:0d.0
SUBSYSTEMS==pci
DRIVERS==pcieport
ATTRS{irq}==40
ATTRS{subsystem_vendor}==0x10de
ATTRS{broken_parity_status}==0
ATTRS{class}==0x060400
ATTRS{consistent_dma_mask_bits}==32
ATTRS{dma_mask_bits}==32
ATTRS{local_cpus}==ff
ATTRS{device}==0x0378
ATTRS{enable}==2
ATTRS{msi_bus}==1
ATTRS{local_cpulist}==0-7
ATTRS{vendor}==0x10de
ATTRS{subsystem_device}==0x
looking at parent device '/devices/pci:00':
KERNELS==pci:00
SUBSYSTEMS==
DRIVERS==
VDR-test-cellar (SDB1): udevadm info -a -p $(udevadm info -q path
-n /dev/dvb/adapter4/frontend0)
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb4.frontend0':
KERNEL==dvb4.frontend0
SUBSYSTEM==dvb
DRIVER==
looking at parent device
'/devices/pci:00/:00:0d.0/:02:00.0':
KERNELS==:02:00.0
SUBSYSTEMS==pci
DRIVERS==DDBridge
ATTRS{irq}==16
ATTRS{subsystem_vendor}==0xdd01
ATTRS{broken_parity_status}==0
ATTRS{class}==0x048000
ATTRS{consistent_dma_mask_bits}==32
ATTRS{dma_mask_bits}==32
ATTRS{local_cpus}==ff
ATTRS{device}==0x0003
ATTRS{enable}==1
ATTRS{msi_bus}==
ATTRS{local_cpulist}==0-7
ATTRS{vendor}==0xdd01
ATTRS{subsystem_device}==0x0020
looking at parent device '/devices/pci:00/:00:0d.0':
KERNELS==:00:0d.0
SUBSYSTEMS==pci
DRIVERS==pcieport
ATTRS{irq}==40
ATTRS{subsystem_vendor}==0x10de
ATTRS{broken_parity_status}==0
ATTRS{class}==0x060400
ATTRS{consistent_dma_mask_bits}==32
ATTRS{dma_mask_bits}==32
ATTRS{local_cpus}==ff
ATTRS{device}==0x0378
ATTRS{enable}==2
ATTRS{msi_bus}==1
ATTRS{local_cpulist}==0-7
ATTRS{vendor}==0x10de
ATTRS{subsystem_device}==0x
looking at parent device '/devices/pci:00':
KERNELS==pci:00
SUBSYSTEMS==
DRIVERS==
In this case, you can write an external program witch output the
name when you match a front end of ddbridge :
KERNEL==dvb[0-9]*.frontend0, SUBSYSTEMS==pci,
DRIVERS==DDBridge, PROGRAM=/your/program %k, NAME=%c
Something like :
if [ ! -a /path/frontendname1 ]; then echo frontendname1; exit; fi;
same with frontendname2 and frontendname3
The kernel name of the device is available if needed (%k in the udev
rule).
Marc.
Hi Marc,
you've lost me.
If FE0/0 is a DDBridge tuner, and I make the FF card tuner FE0/0,
then I still need to rename the DDBridge Tuner that
was FE0/0 to another one within FE{1-3}/0. That means potentially
overwriting the names of some of the other DDBridge
tuners, and then renaming them later on too.
Unfortunately the same rule will pop for all four DDBridge tuners, so
I guess I must keep track of what I have already renamed.
That's what the external program is intended for. It will be launched
for every tuner of the ddbridge. The example I give is basic, if the
node of the first front end isn't already created, then echo the name of
the first front end. If not, test the second node and do the same thing
for all the 4 fronts end. Maybe you can use a better logic by passing
some parameters.
Of course, this is possible only if the tuners of the ddbridge keep the
same order
Re: [vdr] Deactivate a Tuner
On 20/08/2013 19:45, Marc wrote:
On 20/08/2013 18:48, Brian-Imap wrote:
Hi Marc,
you've lost me.
If FE0/0 is a DDBridge tuner, and I make the FF card tuner FE0/0,
then I still need to rename the DDBridge Tuner that
was FE0/0 to another one within FE{1-3}/0. That means potentially
overwriting the names of some of the other DDBridge
tuners, and then renaming them later on too.
Unfortunately the same rule will pop for all four DDBridge tuners,
so I guess I must keep track of what I have already renamed.
That's what the external program is intended for. It will be launched
for every tuner of the ddbridge. The example I give is basic, if the
node of the first front end isn't already created, then echo the name
of the first front end. If not, test the second node and do the same
thing for all the 4 fronts end. Maybe you can use a better logic by
passing some parameters.
Of course, this is possible only if the tuners of the ddbridge keep
the same order but if would be weird if the driver doesn't use the
same order every time (no module loading order at this level).
You still need a rule for the FF card because there are more node
created for each adapter. Without a rule the number of this card could
change too despite the rule for the ddbridge.
To avoid overwriting when a new tuner (without a udev rule) is added,
perhaps you can start numbering at 10 or more if vdr can handle it.
Or, hows about I just go in and rename the devices, same scheme every
time. I think that would work if I knew
how to differentiate between the 4 Cine S2 tuners, currently I dont
know how to do that.
That's a more standard way but according to the output of udevadm,
there is only an empty DRIVER field after the ddbridge, nothing to
write the rule witch differentiate the tuners.
Marc
One more thing. Meanwhile, you can use the solution of blacklisting the
dvb modules and manually load them before starting vdr. This solution
should works but is not very stable: the modules name could change from
time to time and you have to take care to not start vdr before all the
front end are fully initialized.
Marc.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Deactivate a Tuner
On 19/08/2013 21:11, Brian-Imap wrote:
On 8/18/2013 8:15 PM, Marc wrote:
On 18/08/2013 19:27, Brian-Imap wrote:
Hi,
so I tried to look for some kind of info to help me identify the
tuners, this is the most interesting bit I guess:
VDR-test-cellar (SDB1): udevadm info --query=all
--name=/dev/dvb/adapter1/frontend0 --attribute-walk
looking at device
'/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb1.frontend0':
KERNEL==dvb1.frontend0
SUBSYSTEM==dvb
DRIVER==
You can use this command :
udevadm info -a -p $(udevadm info -q path -n /dev/your/path)
to get the complete tree and watch if you can differentiate your
front end with one or more attributes of the subsystems.
Marc.
VDR-test-cellar (SDB1): udevadm info --query=all
--name=/dev/dvb/adapter0/frontend0 --attribute-walk
looking at device
'/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb0.frontend0':
KERNEL==dvb0.frontend0
SUBSYSTEM==dvb
DRIVER==
VDR-test-cellar (SDB1): udevadm info --query=all
--name=/dev/dvb/adapter2/frontend0 --attribute-walk
looking at device
'/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb2.frontend0':
KERNEL==dvb2.frontend0
SUBSYSTEM==dvb
DRIVER==
VDR-test-cellar (SDB1): udevadm info --query=all
--name=/dev/dvb/adapter3/frontend0 --attribute-walk
looking at device
'/devices/pci:00/:00:06.0/:01:06.0/dvb/dvb3.frontend0':
KERNEL==dvb3.frontend0
SUBSYSTEM==dvb
DRIVER==
VDR-test-cellar (SDB1): udevadm info --query=all
--name=/dev/dvb/adapter4/frontend0 --attribute-walk
looking at device
'/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb4.frontend0':
KERNEL==dvb4.frontend0
SUBSYSTEM==dvb
DRIVER==
At the moment I cannot find anything to identify the 4 Tuners on the
Cine S2, the FF on 01:06 is easy.
I got hit by tuning problems a few days ago as the tuner without a
cable was given FE3/0. The FF got FE4/0
at that time. I'm wondering if the DDBridge driver will always
number in the correct order.
So I guess I'll try to make the FF FE0/0, and hope that the DDBRidge
driver will do the rest.
Cheers Brian
___
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
Hi,
well Its exactly what I was doing, and I cant see a difference. Here
an example of two of the Cine S2 Tuners:
VDR-test-cellar (SDB1): udevadm info -a -p $(udevadm info -q path -n
/dev/dvb/adapter3/frontend0)
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb3.frontend0':
KERNEL==dvb3.frontend0
SUBSYSTEM==dvb
DRIVER==
looking at parent device
'/devices/pci:00/:00:0d.0/:02:00.0':
KERNELS==:02:00.0
SUBSYSTEMS==pci
DRIVERS==DDBridge
ATTRS{irq}==16
ATTRS{subsystem_vendor}==0xdd01
ATTRS{broken_parity_status}==0
ATTRS{class}==0x048000
ATTRS{consistent_dma_mask_bits}==32
ATTRS{dma_mask_bits}==32
ATTRS{local_cpus}==ff
ATTRS{device}==0x0003
ATTRS{enable}==1
ATTRS{msi_bus}==
ATTRS{local_cpulist}==0-7
ATTRS{vendor}==0xdd01
ATTRS{subsystem_device}==0x0020
looking at parent device '/devices/pci:00/:00:0d.0':
KERNELS==:00:0d.0
SUBSYSTEMS==pci
DRIVERS==pcieport
ATTRS{irq}==40
ATTRS{subsystem_vendor}==0x10de
ATTRS{broken_parity_status}==0
ATTRS{class}==0x060400
ATTRS{consistent_dma_mask_bits}==32
ATTRS{dma_mask_bits}==32
ATTRS{local_cpus}==ff
ATTRS{device}==0x0378
ATTRS{enable}==2
ATTRS{msi_bus}==1
ATTRS{local_cpulist}==0-7
ATTRS{vendor}==0x10de
ATTRS{subsystem_device}==0x
looking at parent device '/devices/pci:00':
KERNELS==pci:00
SUBSYSTEMS==
DRIVERS==
VDR-test-cellar (SDB1): udevadm info -a -p $(udevadm info -q path -n
/dev/dvb/adapter4/frontend0)
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb4.frontend0':
KERNEL==dvb4.frontend0
SUBSYSTEM==dvb
DRIVER==
looking at parent device
'/devices/pci:00/:00:0d.0/:02:00.0':
KERNELS==:02:00.0
SUBSYSTEMS==pci
DRIVERS==DDBridge
ATTRS{irq}==16
ATTRS{subsystem_vendor}==0xdd01
ATTRS
Re: [vdr] Deactivate a Tuner
On 18/08/2013 19:27, Brian-Imap wrote: Hi, so I tried to look for some kind of info to help me identify the tuners, this is the most interesting bit I guess: VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter1/frontend0 --attribute-walk looking at device '/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb1.frontend0': KERNEL==dvb1.frontend0 SUBSYSTEM==dvb DRIVER== You can use this command : udevadm info -a -p $(udevadm info -q path -n /dev/your/path) to get the complete tree and watch if you can differentiate your front end with one or more attributes of the subsystems. Marc. VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter0/frontend0 --attribute-walk looking at device '/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb0.frontend0': KERNEL==dvb0.frontend0 SUBSYSTEM==dvb DRIVER== VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter2/frontend0 --attribute-walk looking at device '/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb2.frontend0': KERNEL==dvb2.frontend0 SUBSYSTEM==dvb DRIVER== VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter3/frontend0 --attribute-walk looking at device '/devices/pci:00/:00:06.0/:01:06.0/dvb/dvb3.frontend0': KERNEL==dvb3.frontend0 SUBSYSTEM==dvb DRIVER== VDR-test-cellar (SDB1): udevadm info --query=all --name=/dev/dvb/adapter4/frontend0 --attribute-walk looking at device '/devices/pci:00/:00:0d.0/:02:00.0/dvb/dvb4.frontend0': KERNEL==dvb4.frontend0 SUBSYSTEM==dvb DRIVER== At the moment I cannot find anything to identify the 4 Tuners on the Cine S2, the FF on 01:06 is easy. I got hit by tuning problems a few days ago as the tuner without a cable was given FE3/0. The FF got FE4/0 at that time. I'm wondering if the DDBridge driver will always number in the correct order. So I guess I'll try to make the FF FE0/0, and hope that the DDBRidge driver will do the rest. Cheers Brian ___ 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
Re: [vdr] VDR on Beaglebone Black
On 13/08/2013 16:27, Bruce MacIntyre wrote: Hello Everyone, This is my second post regarding putting VDR on a BBB. I was a little disappointed that no one responded to my first posting. Since then I have poured over google to find as much as I can about what I want to do. On Ubuntuforums I found a user that installed VDR using apt-get install vdr and 4 xine plugins. I was amazed that it all installed without any errors and when I rebooted the BBB it was running VDR automatically. I updated some of the configuration files but when I did apt-get install vdr-plugin-hdhomerun (to support my HDHomeRun Dual) I received an error that it wanted a newer version of VDR, but the version, 1.7.22 is newer than the plugin??? I was also hoping to get VDR version 2 because it seems to have support for HD TV and ATSC that I think I need here in the US. It seems that recording TV from the HDHR to disk is an easy task, if I can find the software to do it. My question is, does anyone think it is possible to get VDR 2 running on a BeagleBone Black (running Ubuntu 12.04) with a Silicon Dust HDHomeRun Dual as the tuner? If the 1.7 branch already works, vdr 2 should works too. The 1.7 branch is the developer version of vdr 2 and already support hd. vdr 2 was released a few months ago and should be available on the next release of your distro (probably 13.10 for ubuntu). I don't know hdhomerun but there is something called dvbhdhomerun witch is able to make the hdhomerun appears as a classic dvb device. Perhaps it's what you need. Marc. I'm an experienced user, but new to Linux. I've already spent several weeks learning and I have no problem learning more to see this finished. But am I beating a dead horse? Internet wisdom seems to indicate that MYTHTV is the way to go for the HDHomerun. But I like everything I have read about VDR. I look forward to your suggestions. Thanks Bruce ___ 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] Problem with vdr and a Hauppage WinTV-Duet
Hi, I try to use a new receiver (Hauppage WinTV-Duet, a dual dvb-t usb receiver) but it doesn't work. When I start vdr, I can see them in vdr : vdr: [16411] new device number 3 vdr: [16436] section handler thread started (pid=16411, tid=16436, prio=low) vdr: [16411] frontend 2/0 provides DVB-T with QPSK,QAM16,QAM64 (DiBcom 7000PC) vdr: [16411] probing /dev/dvb/adapter3/frontend0 vdr: [16411] creating cDvbDevice vdr: [16411] new device number 4 vdr: [16439] section handler thread started (pid=16411, tid=16439, prio=low) vdr: [16438] tuner on frontend 2/0 thread started (pid=16411, tid=16438, prio=high) vdr: [16411] frontend 3/0 provides DVB-T with QPSK,QAM16,QAM64 (DiBcom 7000PC) but when I try to use one of them, vdr complains with the following message : vdr: [16438] frontend 2/0 timed out while tuning to channel 7, tp 562 (same message for the second adapter) I can see the green led switching on (witch means vdr access the adapter) but only for a few seconds before the above message. vdr tries again without success. There is no more log with loglevel 3. I tried manually and everything works : tzap -a 2 -r -c ~/tzap.chan France 2 using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' reading channels from file '/root/tzap.chan' tuning to 58600 Hz video pid 0x0078, audio pid 0x0082 status 1f | signal ac22 | snr 00d5 | ber 001f | unc 007d | FE_HAS_LOCK status 1f | signal abe6 | snr 00dd | ber | unc | FE_HAS_LOCK status 1f | signal abdb | snr 00d8 | ber | unc | FE_HAS_LOCK status 1f | signal abaa | snr 00e6 | ber | unc | FE_HAS_LOCK ... then, I can see the channel with mplayer in /dev/dvb/adapter2/dvr0. Are there some parameters in vdr to get my adapter working ? Thanks, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for translations for VDR version 2.0.0
On 13/02/2013 17:36, Klaus Schmidinger wrote: On 13.02.2013 16:36, Bernard Jaulin wrote: Hi Klaus, If possible, here is the last french po file (and diff) according with a part of french community. Could you please take care of this one, too? msgid Setup.LNB$own msgstr It is used for device bonding and means that this device has its own satellite cable that is not shared with any other device. Klaus Hi Bernard, I found an old account for the forum but it has been deactivated when I tried to update my profile. Could you watch your framapad, I put there a possible translation for own as well as some corrections. Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for translations for VDR version 2.0.0
On 12/02/2013 02:24, syrius...@no-log.org wrote: Bernard Jaulin bernard.jau...@gmail.com writes: Bonjour, We are working on that now ! We send you a new one .po asap. Dear french fellow countryman please take a look here : http://dvbkivabien2.info/viewtopic.php?f=21t=14987 and here : http://lite.framapad.org/p/ClyUvioD5s Thanks Bernard ! I've just proposed some changes on the pad as well as comments on some weird translations. one of the worst one is definitely epg scan timeout, it shouldn't translate to epg scan length/duration in french ! :-) Hi Syrius, Sorry if I don't have a perfect French. By Temps de mise à jour du guide (h), I mean the time before the epg is updated. I agree, a more correct version would be Temps *avant* mise à jour du guide (h) witch is IMHO what this parameter is intended for. The user inactivity part is not mentioned in the original message, I don't see why it should be in the translation. For a standard user Inactivité avant rech. EPG (h) mean nothing IMHO. At least, the translation should mention that this is the *user* inactivity but even with that, I'm not sure a standard user would understand what this parameter is about. Regards, Marc. the MANUAL file from vdr source tree should be giving most of the explanations and contexts. (et pourquoi ne pas commencer par la traducton du MANUEL ? :-)) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for translations for VDR version 2.0.0
On 12/02/2013 18:14, syrius...@no-log.org wrote: Why the rush in willing to translate the po on your own then ? and why the hell are you using this sorry it's not my fault i'm not perfect kind of excuse ? this bit is just the worst translation ever, deal with it ! (not smiling anymore) To end this useless discussion, it's sarcasm too. I can use a lot of IMHO myself. sorry it's not my fault i'm not perfect because it's easy to criticize *after* someone make some work. Sorry for non French reader, but there is a French expression far that (I'm not smiling too) : inspecteur des travaux finis ! At first, I take your comments and make some changes in my translation and try to discuss with you about what I disagree. But it seems you take my comments as a personal offense and I don't see any offense in my comments (?). Fortunately, there are smarter guys there who try to sort things out (Thanks Bernard). It's not really a rush but the last French translation was quite old (2008) and the next stable release of VDR (2.0) is coming soon. You say you don't use French so it doesn't matter to you but not to me. My intend was to have at least a translation for this release even if it was not perfect. Before this, I haven't see anything here about the French translation and there was nothing in the dvbkivabien2 forum too. I'm happy now because with this intervention, I'm sure there will be a French translation in the next release, mine or an other, I don't care ! Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for translations for VDR version 2.0.0
On 11/02/2013 00:38, syrius...@no-log.org wrote: Marc v...@ekass.net writes: On 09/02/2013 15:35, Klaus Schmidinger wrote: VDR is now approaching version 2.0.0, so this might be a good time for translators to complete the internationalized texts. Hi, Here is a patch for fr_FR.po. NAK NACK NON NEIN NICHT NO :-) Regards, Marc. Hi Marc ! :) Hi Syrius, --- vdr-1.7.37/fr_FR.po 2013-02-09 14:57:00.0 +0100 +++ vdr-2.0.0/fr_FR.po 2013-02-10 16:47:46.0 +0100 @@ -14,8 +14,8 @@ Project-Id-Version: VDR 1.6.0\n Report-Msgid-Bugs-To: vdr-b...@tvdr.de\n POT-Creation-Date: 2013-02-03 16:46+0100\n -PO-Revision-Date: 2008-02-27 18:14+0100\n -Last-Translator: Jean-Claude Repetto j...@repetto.org\n +PO-Revision-Date: 2013-02-10 16:47+0100\n +Last-Translator: Marc Perrudin v...@ekass.net\n Language-Team: French vdr@linuxtv.org\n What about talking about this translation on the french forum dvbkivabien2 ? It definitely needs corrections and testing ! (etherpad ?) I wasn't aware about this forum and I never heard about some works on the French translation here, sorry. If there is some works already done on this translation, feel free to use this work and post your version. Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for translations for VDR version 2.0.0
On 11/02/2013 09:44, Klaus Schmidinger wrote: On 11.02.2013 00:38, syrius...@no-log.org wrote: Marc v...@ekass.net writes: On 09/02/2013 15:35, Klaus Schmidinger wrote: VDR is now approaching version 2.0.0, so this might be a good time for translators to complete the internationalized texts. Hi, Here is a patch for fr_FR.po. NAK NACK NON NEIN NICHT NO :-) So should I just ignore the changes made by Marc Perrudin, or are you going to provide revised translations? If so, please send the complete fr_FR.po file, just to be on the save side. Klaus Hi, Here is a revised version in case the version from dvbkivabien2 forum came to late for version 2.0.0. The only remaining string is Setup.LNB$own. I don't use LNB and I don't know how this word is used. Regards. @sirius : I used your comments : msgid off -msgstr off +msgstr Now, it's 'Inactive' (and active for on) because in the source code, this string is only used for inversion parameter. msgid Srate -msgstr Fréq. symbole +msgstr Srate These messages are for advanced users and Fréq. symbole is weird. I think it's better to keep the original name for these advanced settings. Same remark for Vpid, Apid ... msgid Content$Movie/Drama -msgstr +msgstr Film/Drame Drame in film genre has the same meaning as in English. See http://fr.wikipedia.org/wiki/Drame_(cinéma) msgid Content$Serious/Classical/Religious/Historical Movie/Drama -msgstr +msgstr Averti/Classique/Religieux/Film Historique/Drame For me, serious is for public averti, sérieux has no meaning in this context. msgid Content$News/Weather Report -msgstr +msgstr Information/Météo done. msgid Content$Athletics -msgstr +msgstr Athlétismes done. msgid Content$Motor Sport -msgstr +msgstr Sport mécanique msgid Content$Water Sport -msgstr +msgstr Sport nautique done. msgid Content$Martial Sports -msgstr +msgstr Sports Martiaux I took Sports de combat. msgid Content$Pre-school Children's Programme -msgstr +msgstr Programme pour enfant de maternelle done. msgid Content$Broadcasting/Press -msgstr +msgstr Émission/Presse I agree with you but I can't let Broadcasting ! msgid Key$Mute -msgstr Coupure du son +msgstr Sourdine Muet, I searched for it ! msgid Key$Timers -msgstr Programmation +msgstr Minuteries oh non programmation(s) c'est mieux ! I took Minuterie from XBMC because Programmation is from computer science and is a bit confusing with Programme for standard users. In everyday language, a programmation is what you do to make a programme (for TV, cinema, theater ...). msgid Channel settings are not unique! -msgstr Caractéristiques des chaînes non uniques +msgstr Les configurations des chaînes ne sont pas uniques ! Dans les 3 cas ca veut rien dire ! :-) It means 2 or more channels share the same settings witch is forbidden. msgid Channel is being used by a timer! -msgstr Cette chaîne est en cours d'utilisation ! +msgstr Cette chaîne est utilisée par une minuterie ! bof This message is displayed when you try to delete a channel and there are still some timers for this channel. msgid Button$Select -msgstr +msgstr Selectionner s/e/é/ ! :) done. @@ -844,49 +844,49 @@ msgstr Défilement rotatif vraiment ? It's from the previous translation, I don't have better. #. TRANSLATORS: note the plural! msgid Setup.EPG$Preferred languages @@ -897,13 +897,13 @@ msgstr Langue préférée tu loupes une occasion de rajouter des s ! :-) the @@... means it's an other part. Here, it's the translation of Setup.EPG$Preferred language. msgid DVB -msgstr Cartes DVB +msgstr DVB étrange Why cartes ? What about usb sticks or boxes ! msgid Setup.DVB$Standard compliance -msgstr +msgstr Conformité aux normes tu supprimes précédemment des traductions de JC, la honnêtement (et bien-sûr toujours imho) c'est mieux que conformité aux normes. No translation for this ? msgid do not pause live video -msgstr +msgstr ne pas arrêter le direct msgid confirm pause live video -msgstr +msgstr confirmer l'arrêt du direct msgid pause live video -msgstr +msgstr arrêter le direct done. msgid Setup.Miscellaneous$Show channel names with source -msgstr +msgstr Afficher le nom des chaines avec la source leur source Afficher *le* nom des chaines avec *la* source msgid Setup.Miscellaneous$Emergency exit msgstr Arrêt d'urgence @@ -1171,7 +1171,7 @@ msgstr Redémarrer emergency exit = redémarrer ??? vraiment, tu as fait attention à la réelle signification de cette option ? the @@... . ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for translations for VDR version 2.0.0
I forgot the attachment ! On 11/02/2013 11:18, Marc wrote: On 11/02/2013 09:44, Klaus Schmidinger wrote: On 11.02.2013 00:38, syrius...@no-log.org wrote: Marc v...@ekass.net writes: On 09/02/2013 15:35, Klaus Schmidinger wrote: VDR is now approaching version 2.0.0, so this might be a good time for translators to complete the internationalized texts. Hi, Here is a patch for fr_FR.po. NAK NACK NON NEIN NICHT NO :-) So should I just ignore the changes made by Marc Perrudin, or are you going to provide revised translations? If so, please send the complete fr_FR.po file, just to be on the save side. Klaus Hi, Here is a revised version in case the version from dvbkivabien2 forum came to late for version 2.0.0. The only remaining string is Setup.LNB$own. I don't use LNB and I don't know how this word is used. Regards. @sirius : I used your comments : msgid off -msgstr off +msgstr Now, it's 'Inactive' (and active for on) because in the source code, this string is only used for inversion parameter. msgid Srate -msgstr Fréq. symbole +msgstr Srate These messages are for advanced users and Fréq. symbole is weird. I think it's better to keep the original name for these advanced settings. Same remark for Vpid, Apid ... msgid Content$Movie/Drama -msgstr +msgstr Film/Drame Drame in film genre has the same meaning as in English. See http://fr.wikipedia.org/wiki/Drame_(cinéma) msgid Content$Serious/Classical/Religious/Historical Movie/Drama -msgstr +msgstr Averti/Classique/Religieux/Film Historique/Drame For me, serious is for public averti, sérieux has no meaning in this context. msgid Content$News/Weather Report -msgstr +msgstr Information/Météo done. msgid Content$Athletics -msgstr +msgstr Athlétismes done. msgid Content$Motor Sport -msgstr +msgstr Sport mécanique msgid Content$Water Sport -msgstr +msgstr Sport nautique done. msgid Content$Martial Sports -msgstr +msgstr Sports Martiaux I took Sports de combat. msgid Content$Pre-school Children's Programme -msgstr +msgstr Programme pour enfant de maternelle done. msgid Content$Broadcasting/Press -msgstr +msgstr Émission/Presse I agree with you but I can't let Broadcasting ! msgid Key$Mute -msgstr Coupure du son +msgstr Sourdine Muet, I searched for it ! msgid Key$Timers -msgstr Programmation +msgstr Minuteries oh non programmation(s) c'est mieux ! I took Minuterie from XBMC because Programmation is from computer science and is a bit confusing with Programme for standard users. In everyday language, a programmation is what you do to make a programme (for TV, cinema, theater ...). msgid Channel settings are not unique! -msgstr Caractéristiques des chaînes non uniques +msgstr Les configurations des chaînes ne sont pas uniques ! Dans les 3 cas ca veut rien dire ! :-) It means 2 or more channels share the same settings witch is forbidden. msgid Channel is being used by a timer! -msgstr Cette chaîne est en cours d'utilisation ! +msgstr Cette chaîne est utilisée par une minuterie ! bof This message is displayed when you try to delete a channel and there are still some timers for this channel. msgid Button$Select -msgstr +msgstr Selectionner s/e/é/ ! :) done. @@ -844,49 +844,49 @@ msgstr Défilement rotatif vraiment ? It's from the previous translation, I don't have better. #. TRANSLATORS: note the plural! msgid Setup.EPG$Preferred languages @@ -897,13 +897,13 @@ msgstr Langue préférée tu loupes une occasion de rajouter des s ! :-) the @@... means it's an other part. Here, it's the translation of Setup.EPG$Preferred language. msgid DVB -msgstr Cartes DVB +msgstr DVB étrange Why cartes ? What about usb sticks or boxes ! msgid Setup.DVB$Standard compliance -msgstr +msgstr Conformité aux normes tu supprimes précédemment des traductions de JC, la honnêtement (et bien-sûr toujours imho) c'est mieux que conformité aux normes. No translation for this ? msgid do not pause live video -msgstr +msgstr ne pas arrêter le direct msgid confirm pause live video -msgstr +msgstr confirmer l'arrêt du direct msgid pause live video -msgstr +msgstr arrêter le direct done. msgid Setup.Miscellaneous$Show channel names with source -msgstr +msgstr Afficher le nom des chaines avec la source leur source Afficher *le* nom des chaines avec *la* source msgid Setup.Miscellaneous$Emergency exit msgstr Arrêt d'urgence @@ -1171,7 +1171,7 @@ msgstr Redémarrer emergency exit = redémarrer ??? vraiment, tu as fait attention à la réelle signification de cette option ? the @@... . ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr # VDR language source file. # Copyright (C) 2008 Klaus Schmidinger k...@tvdr.de # This file is distributed under the same license as the VDR package. # Jean-Claude Repetto j...@repetto.org, 2001, 2002, 2008 # Olivier Jacques jacquesoliv...@hotmail.com, 2003
Re: [vdr] Call for translations for VDR version 2.0.0
On 09/02/2013 15:35, Klaus Schmidinger wrote: VDR is now approaching version 2.0.0, so this might be a good time for translators to complete the internationalized texts. Hi, Here is a patch for fr_FR.po. Regards, Marc. --- vdr-1.7.37/fr_FR.po 2013-02-09 14:57:00.0 +0100 +++ vdr-2.0.0/fr_FR.po 2013-02-10 16:47:46.0 +0100 @@ -14,8 +14,8 @@ Project-Id-Version: VDR 1.6.0\n Report-Msgid-Bugs-To: vdr-b...@tvdr.de\n POT-Creation-Date: 2013-02-03 16:46+0100\n -PO-Revision-Date: 2008-02-27 18:14+0100\n -Last-Translator: Jean-Claude Repetto j...@repetto.org\n +PO-Revision-Date: 2013-02-10 16:47+0100\n +Last-Translator: Marc Perrudin v...@ekass.net\n Language-Team: French vdr@linuxtv.org\n Language: fr\n MIME-Version: 1.0\n @@ -32,7 +32,7 @@ msgstr Impossible d'utiliser le mode transfert ! msgid off -msgstr off +msgstr msgid on msgstr @@ -47,10 +47,10 @@ msgstr Polarisation msgid System -msgstr +msgstr Syst�me msgid Srate -msgstr Fr�q. symbole +msgstr Srate msgid Inversion msgstr Inversion @@ -77,254 +77,254 @@ msgstr Hi�rarchie msgid Rolloff -msgstr +msgstr Rolloff msgid PlpId -msgstr +msgstr PlpId msgid Starting EPG scan msgstr Mise � jour du guide des programmes msgid Content$Movie/Drama -msgstr +msgstr Film/Drame msgid Content$Detective/Thriller -msgstr +msgstr Policier/Suspence msgid Content$Adventure/Western/War -msgstr +msgstr Aventure/Western/Guerre msgid Content$Science Fiction/Fantasy/Horror -msgstr +msgstr Science Fiction/Fantasy/Horreur msgid Content$Comedy -msgstr +msgstr Com�die msgid Content$Soap/Melodrama/Folkloric -msgstr +msgstr Soap/M�lodrame/Folklorique msgid Content$Romance -msgstr +msgstr Romance msgid Content$Serious/Classical/Religious/Historical Movie/Drama -msgstr +msgstr Averti/Classique/Religieux/Film Historique/Drame msgid Content$Adult Movie/Drama -msgstr +msgstr Film pour adulte/Drame msgid Content$News/Current Affairs -msgstr +msgstr Informations/Actualit�s msgid Content$News/Weather Report -msgstr +msgstr Information/M�t�o msgid Content$News Magazine -msgstr +msgstr Magazine d'information msgid Content$Documentary -msgstr +msgstr Documentaire msgid Content$Discussion/Inverview/Debate -msgstr +msgstr Discussion/Interview/D�bat msgid Content$Show/Game Show -msgstr +msgstr Spectacle/Jeu T�l�vis� msgid Content$Game Show/Quiz/Contest -msgstr +msgstr Jeu T�l�vis�/Quiz/Concours msgid Content$Variety Show -msgstr +msgstr Spectacle de vari�t�s msgid Content$Talk Show -msgstr +msgstr D�bat t�l�vis� msgid Content$Sports -msgstr +msgstr Sports msgid Content$Special Event -msgstr +msgstr �v�nement sp�cial msgid Content$Sport Magazine -msgstr +msgstr Magazine sportif msgid Content$Football/Soccer -msgstr +msgstr Football/Foot msgid Content$Tennis/Squash -msgstr +msgstr Tennis/Squash msgid Content$Team Sports -msgstr +msgstr Sports d'�quipe msgid Content$Athletics -msgstr +msgstr Athl�tismes msgid Content$Motor Sport -msgstr +msgstr Sport m�canique msgid Content$Water Sport -msgstr +msgstr Sport nautique msgid Content$Winter Sports -msgstr +msgstr Sports d'hiver msgid Content$Equestrian -msgstr +msgstr �quitation msgid Content$Martial Sports -msgstr +msgstr Sports Martiaux msgid Content$Children's/Youth Programme -msgstr +msgstr Enfant/Programme jeunesse msgid Content$Pre-school Children's Programme -msgstr +msgstr Programme pour enfant de maternelle msgid Content$Entertainment Programme for 6 to 14 -msgstr +msgstr Programme de divertissement pour les 6/14 ans msgid Content$Entertainment Programme for 10 to 16 -msgstr +msgstr Programme de divertissement pour les 10/16 ans msgid Content$Informational/Educational/School Programme -msgstr +msgstr Informationnel/�ducatif/Programme Scolaire msgid Content$Cartoons/Puppets -msgstr +msgstr Dessins anim�s/Marionnettes msgid Content$Music/Ballet/Dance -msgstr +msgstr Musique/Ballet/Danse msgid Content$Rock/Pop -msgstr +msgstr Rock/Pop msgid Content$Serious/Classical Music -msgstr +msgstr Averti/Musique Classique msgid Content$Folk/Tradional Music -msgstr +msgstr Folk/Musique Traditionnelle msgid Content$Jazz -msgstr +msgstr Jazz msgid Content$Musical/Opera -msgstr +msgstr Com�die Musicale/Op�ra msgid Content$Ballet -msgstr +msgstr Ballet msgid Content$Arts/Culture -msgstr +msgstr Arts/Culture msgid Content$Performing Arts -msgstr +msgstr Performances artistiques msgid Content$Fine Arts -msgstr +msgstr Beaux Arts msgid Content$Religion -msgstr +msgstr Religion msgid Content$Popular Culture/Traditional Arts -msgstr +msgstr Culture Populaire/Arts Traditionnels msgid Content$Literature -msgstr +msgstr Litt�rature msgid Content$Film/Cinema -msgstr +msgstr Film/Cinema msgid Content$Experimental Film/Video -msgstr +msgstr Film Exp�rimental/Vid�o msgid Content$Broadcasting/Press -msgstr +msgstr
Re: [vdr] Reserve device for Live-Tv
You should try the Primary DVB interface parameter. From the wiki : Defines the primary DVB interface (i.e. the one that will display the menus and will react on input through the remote control). Valid values range from '1' to the number of installed DVB cards.* If more than one DVB card is installed and a recording is to be started, the program will try to use a free DVB card that is different from the primary DVB interface, so that the viewer will be disturbed as little as possible. * Marc. On 19/12/2012 09:54, Ingo Prochaska wrote: Hello, I would like to have one dvb-device dedicated for live tv. Or in other words: I want vdr to record on all-dvb-devices - 1, so that one device is still available for viewing via the output-front-end or streamdev. Perhaps its possible to configure vdr to behave like this - but I have no clue how to accomblish this... Regards, Ingo ___ 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] How to manually add a new transponder ?
Hi, I have some new channels but they are on a new transponder. I have set vdr to add new transponder (in DVB card configuration) but nothing happens, only channels on known transponders are added. Is there a way to manually add a transponder so vdr can finds these new channels ? Thanks, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How to manually add a new transponder ?
On 15/12/2012 14:18, Klaus Schmidinger wrote: On 15.12.2012 13:03, Marc wrote: Hi, I have some new channels but they are on a new transponder. I have set vdr to add new transponder (in DVB card configuration) but nothing happens, only channels on known transponders are added. Is there a way to manually add a transponder so vdr can finds these new channels ? In the Channels menu select New (green button) and enter the necessary data. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Thanks, I just have to configure a fake channel with the correct frequency and vdr makes all the job ! Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recent breakage of DVB subtitles with dxr3
On 01/04/2012 13:15, Mika Iisakkila wrote: Well, I googled a bit more, and it seems the actual problem is in dxr3-plugin, not the drivers. The plugin is only able to use OSS (as of Dec.2008, anyway). I'm not willing to waste time fighting with semi-functional compatibility layers, so I'll just keep using my own kernel. Next time I'll configure out all the unneeded junk before compiling, though :D Why don't you cross-compile your kernel on a faster computer ? Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] problems with playback and plugins with vdr-1.7.22
On 08/01/2012 08:43, René wrote: On 07.01.2012 23:23 , René wrote: The patch compiles now fine, but when activating livebuffer, vdr crashes with the following in the logs: I realized that i forgot to turn back a couple Gentoo-useflags that i had active til now: cutterlimit ddepgentry hardlinkcutter mainmenuhooks pinplugin timerinfo wareagleicon yaepg lircsettings Putting these back seems to have fixed the crash.. Still having trouble with playback/rewind/forwad of Regards, René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Yes, it works like this but it's a temporary workaround. I checked what Udo say and this is the real problem, the USE_LIVEBUFFER flag is not in use when the plugins are compiled. I don't know how to propagate this flag with portage. This would be a better solution. Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] problems with playback and plugins with vdr-1.7.22
On 08/01/2012 13:26, René wrote: On 08.01.2012 10:44 , Marc wrote: Yes, it works like this but it's a temporary workaround. I checked what Udo say and this is the real problem, the USE_LIVEBUFFER flag is not in use when the plugins are compiled. I don't know how to propagate this flag with portage. This would be a better solution. Hi Marc, I have USE_LIVEBUFFER=1 in /etc/make.conf, but this then does not seem to work correctly? The problem is to know how to tell portage to add this flag to gcc. With the others flags, this is done automatically, probably by the scripts launched in the ebuilds. I don't know how to do the same thing for local patches. Is the forwads/backward feature also part of this problem, or is it just me who has this problem.. I don't have this problem, I can't tell. I can use forward/backward on records and livebuffer. Has vdr-1.7 btw more resource-requirements than vdr-1.6? I still run my vdr on an epia mii 12000 board with 1gb memory. The 1.7 version of vdr has much more problem in keeping the palyback in sync. Also live-tv has problems keeping in sync. The sound is very often seconds behind the image... vdr itself take very low resources, it's the rendering witch require some resources. I use a nvidia card so all this part is handled by vdpau and, even in hd, my cpu has almost no load. Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] problems with playback and plugins with vdr-1.7.22
On 07/01/2012 10:59, René wrote: On 07.01.2012 3:44 , Udo Richter wrote: The cryptic symbol decodes to cTimer::cTimer(bool, bool, cChannel*), found in timers.h, line 46. The actual code is in timers.c, line 28. This function exists in this form since 1.3.38. VDR itself seems to be fine, so your VDR seems to have a different function instead. However, the plugins rely on the original function because they somehow compiled against the original definition in the timers.h. My guess is that one of the patches is optionally modifying this, and the plugins were somehow compiled with different versions of the timers.h, or with different compiler flags that cause some #ifdef to flip. Ok, i'll check if this would would work without any patches.. I doubt that I would be the only one with this issue if it would be the patches.. But again i would'nt surprise me if my system is messed up because of this big jump from 1.6.x to 1.7.22. Til now VDR has been a set and forget installation that just works, and works, and works and wo... :-) Regards, René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr The problem come from the livebuffer patch. It redefines cTimer::cTimer to add the length of the already buffered stream so when the instant recording start, it records the buffer too : +#ifdef USE_LIVEBUFFER + cTimer(bool Instant = false, bool Pause = false, cChannel *Channel = NULL, int Forerun = 0); +#else cTimer(bool Instant = false, bool Pause = false, cChannel *Channel = NULL); +#endif /*USE_LIVEBUFFER*/ This feature can be removed easily (it's not really useful), I attach a modified version of the livebuffer patch. Thanks Udo for pointing to the right direction. Regards, Marc. diff -Naur vdr-1.7.22/Makefile vdr-1.7.22-livebuffer/Makefile --- vdr-1.7.22/Makefile 2011-12-04 15:41:00.0 +0100 +++ vdr-1.7.22-livebuffer/Makefile 2011-12-31 11:16:23.0 +0100 @@ -62,6 +62,9 @@ LIBS += $(shell pkg-config --libs fribidi) endif +DEFINES += -DUSE_LIVEBUFFER +OBJS += livebuffer.o + LIRC_DEVICE ?= /var/run/lirc/lircd RCU_DEVICE ?= /dev/ttyS1 diff -Naur vdr-1.7.22/config.c vdr-1.7.22-livebuffer/config.c --- vdr-1.7.22/config.c 2011-12-03 16:21:30.0 +0100 +++ vdr-1.7.22-livebuffer/config.c 2011-12-31 11:16:23.0 +0100 @@ -461,6 +461,10 @@ InitialChannel = ; DeviceBondings = ; InitialVolume = -1; +#ifdef USE_LIVEBUFFER + LiveBufferSize = 30; + LiveBufferMaxFileSize = 100; +#endif /*USE_LIVEBUFFER*/ ChannelsWrap = 0; EmergencyExit = 1; } @@ -655,6 +659,10 @@ else if (!strcasecmp(Name, InitialChannel)) InitialChannel = Value; else if (!strcasecmp(Name, InitialVolume)) InitialVolume = atoi(Value); else if (!strcasecmp(Name, DeviceBondings)) DeviceBondings = Value; +#ifdef USE_LIVEBUFFER + else if (!strcasecmp(Name, LiveBufferSize))LiveBufferSize= atoi(Value); + else if (!strcasecmp(Name, LiveBufferMaxFileSize)) LiveBufferMaxFileSize = atoi(Value); +#endif /*USE_LIVEBUFFER*/ else if (!strcasecmp(Name, ChannelsWrap))ChannelsWrap = atoi(Value); else if (!strcasecmp(Name, EmergencyExit)) EmergencyExit = atoi(Value); else @@ -752,6 +760,9 @@ Store(InitialChannel, InitialChannel); Store(InitialVolume, InitialVolume); Store(DeviceBondings, DeviceBondings); +#ifdef USE_LIVEBUFFER + Store(LiveBufferSize, LiveBufferSize); +#endif /* LIVEBUFFER */ Store(ChannelsWrap, ChannelsWrap); Store(EmergencyExit, EmergencyExit); diff -Naur vdr-1.7.22/config.h vdr-1.7.22-livebuffer/config.h --- vdr-1.7.22/config.h 2011-12-03 15:19:52.0 +0100 +++ vdr-1.7.22-livebuffer/config.h 2011-12-31 11:16:23.0 +0100 @@ -307,6 +307,10 @@ int CurrentVolume; int CurrentDolby; int InitialVolume; +#ifdef USE_LIVEBUFFER + int LiveBufferSize; + int LiveBufferMaxFileSize; +#endif /*USE_LIVEBUFFER*/ int ChannelsWrap; int EmergencyExit; int __EndData__; diff -Naur vdr-1.7.22/device.c vdr-1.7.22-livebuffer/device.c --- vdr-1.7.22/device.c 2011-10-16 16:36:43.0 +0200 +++ vdr-1.7.22-livebuffer/device.c 2011-12-31 11:16:23.0 +0100 @@ -18,6 +18,10 @@ #include receiver.h #include status.h #include transfer.h +#ifdef USE_LIVEBUFFER +#include menu.h +#include interface.h +#endif /*USE_LIVEBUFFER*/ // --- cLiveSubtitle - @@ -663,6 +667,14 @@ return false; case scrNoTransfer: Skins.Message(mtError, tr(Can't start Transfer Mode!)); return false; +#ifdef USE_LIVEBUFFER +case srcStillWritingLiveBuffer: + if(Interface-Confirm(tr(Still writing timeshift data to recording. Abort?))) + cRecordControls::CancelWritingBuffer(); + else + if(cRecordControls
Re: [vdr] Updated patch for vdr 1.7.22 in gentoo
On 04/01/2012 00:29, René wrote: On 03.01.2012 16:12 , René wrote: On 03.01.2012 10:29 , Marc wrote: * Unifdef sources ... [ ok ] * Applying local patches * Applying livebuffer-1.7.22.patch ... [ ok ] Source prepared. Ok, then i have something fishy going on.. I have the livebufer in the menu, but then as you said most likely it's not applied correctly. I have to check the build-log if it complains something Marc, The patch is now found by the ebuild, but it wont' get applied. The problem is just that it does not work. For some reasons it get's errors like can't find file to patch... No, it's still the same problem, the patch applies but you have more difference in your source tree when the local patches are applied. You can see what parts of the patch don't apply in the log at line 205. For me, I only have Makefile, config.c and config.h witch differ but you have more : patching file device.c Hunk #1 FAILED at 18. patching file dvbplayer.c Hunk #4 FAILED at 281. patching file menu.c Hunk #4 FAILED at 4169. Hunk #18 FAILED at 4998. ... I only use the noepg use flag, did you tried to compile vdr without any use flags ? If it works like this, try to add each use flag one by one to see where is the problem. Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Updated patch for vdr 1.7.22 in gentoo
On 03/01/2012 00:16, René wrote: On 03.01.2012 1:00 , Marc wrote: I don't have livebuffer in the menu. I activated the livebuffer by setting 'Pause key handling' to 'Timeshit'. Ok, is this something you have to manually edit in setup.conf? I don't have this option in the setup for recording.. Here i have only pause live video, do not pause live video and confirm pause live video.. It's probably because the patch is not applied, this option is added in the menu by it. You should have something like this when you compile vdr : ... * Unifdef sources ... [ ok ] * Applying local patches * Applying livebuffer-1.7.22.patch ... [ ok ] Source prepared. ... Do you btw have to press pause to activate livebuffer, or can you just press rewind in the middle of playback? In the 1.6.x patch i don't have to press pause, i just press rewind.. I checked and yes, the patch still works like this. I can either use pause or rewind. Regards, René ___ 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
Re: [vdr] Updated patch for vdr 1.7.22 in gentoo
On 02/01/2012 23:44, René wrote: On 02.01.2012 23:44 , René wrote: On 02.01.2012 19:11 , Marc wrote: The patch applies, portage try several levels with patch and it succeeded at p1 (log start at 255). The modifications I've made work but you have more files that fail than me. Perhaps you use more use flags. I don't know if the extension patches are applied all the time or only when you set the use flag for them. You could try to build vdr without any use flag and see if it compiles. I got this patch installed without any errors, but it does not work (pressing rewind does not do anything).. In the setup-menu i see the LiveBuffer settings, but i can't enter the settings. I just started a vdrplugin-rebuild -se rebuild, so let's see if it's some other plugin that's screwing things up.. To add this patch to the overlay, have you tried to contact the maintainer ? It could be interested, its address is in the changelog. If i get this to work, then i'll do my best to persuade him to add this back to the overlay!! :-) A quick update.. Pressing the LiveBUffer menu-item in the setupmenu gives me the following in my logfile: Jan 3 00:42:27 vdr vdr: [16766] ERROR: Gentoo-VDR-Setup: menu System=LiveBuffer not known Does anyone know what this error means? if someone knows what's messed up in the previous error-message, then i get the same error for BigPatch Jan 3 00:42:29 vdr vdr: [16766] ERROR: Gentoo-VDR-Setup: menu System=BigPatch not known Regards, René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr I don't have livebuffer in the menu. I activated the livebuffer by setting 'Pause key handling' to 'Timeshit'. Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LiveBuffer for vdr 1.7.x
On 01/01/2012 18:41, René wrote: On 23.12.2011 14:27 , Marc wrote: There is a typo error in vdr.c but that's all. For gentoo users, I attached the patches I use. I relocated some hunk of config.c and config.h and renamed USE_LIVEBUFFER to LIVEBUFFER in Makefile. Patch the ebuild and put the other patch in /etc/portage/patches/media-video/vdr-1.7.21 (I use the epatch_user tool instead of the script, see the ebuild patch). Hi Marc, I'm having trouble in getting the patch you posted to work in my setup. Could you please check if you find something that i screwed up? http://paste.me.uk/1484.html I have saved the patch as: 0001-opt-96-livebuffer12-rmm.dpatch-rebased-onto-1.7.21.patch What i did was that i deleted the message-headers etc from the file, and left the first row to be: diff --git a/Makefile b/Makefile Best Regards, René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi René, You can watch the output of the patch (/var/tmp/portage/media-video/vdr-1.7.21-r2/temp/0001-opt-96-livebuffer12-rmm.dpatch-rebased-onto-1.7.21.patch.out) and see where it fails. vdr 1.7.22 is out now on vdr-devel overlay. I'll post an updated patch for it tomorrow. It could work better on your configuration. Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LiveBuffer for vdr 1.7.x
On 22/12/2011 23:07, René wrote: On 22.12.2011 23:32 , Marc wrote: It's a patch from yaVDR and it doesn't apply to the vdr source tree as is (at least for me). The second patch works on gentoo ebuild with small changes (It conflicts with other patches and need some changes for config.c config.h part). I tried the second too but it crashes vdr when I try to pause. I didn't tested a lot. Hi Marc, It's a shame that it did not work.. I wonder in which order the patches are added to VDR in a normal gentoo compilation-processs. Is the VDR_LOCAL_PATCHES_DIR applied as last in the row of patches, or is this first? I assume that if eg. this patch comes in as the last patch, I need to adjust this patch to match possible changes in the source made by other patches.. It would be great if this patch could be re-added into Gentoo as a default use-flag... This patch was (and still IS) a really great feature! :-) René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Yes, it's the way the ebuild works. Almost at the end of source_prepare, the local patches are applied after the others. But the second patch needs only few changes in config.c config.h to apply. Report back if you succeed with this patch. For me, with the patch, I have the option available but when I try to pause, vdr crash. Perhaps the patch is to old (1.7.18 and I use 1.7.21). The first patch is for vdr-1.7.21 but I didn't succeeded to use it. Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LiveBuffer for vdr 1.7.x
On 22/12/2011 17:04, Artem Makhutov wrote: Hi, René schrieb: On 21.12.2011 13:34 , Norm Dressler wrote: On 12/21/2011 3:48 AM, René wrote: On 21.12.2011 24:12 , Lists wrote: I'm stuck to vdr 1.6.0-2 because i can't find a current LiveBuffer patch for any current vdr 1.7.x. Does anyone know if there is any work going on with this great patch? Here you go. I grabbed this from the yaVDR source. Norm Hi Norm, Thanks!! Do you know which vdr-build this patch is for? I'm running gentoo, so it should be pretty easy to update an ebuild to contain this patch! :-) René This is for vdr 1.7.21 :) Norm Oh yeah!! Great!! I have right away try to modify an ebuild for this :-) If i'm succesful, i'll post the ebuild back to this thread! You don't have to alter the ebuild for this. You can just place patch the file in a directory (I don't remember which) and it will automaticly applied when you compile vdr. Regards, Artem ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Here it is : VDR_LOCAL_PATCHES_DIR=/your/patch/directory emerge vdr You can put it in make.conf I tried but it doesn't work on the vdr-1.7.21 source tree (perhaps it needs some change ) Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LiveBuffer for vdr 1.7.x
On 22/12/2011 22:17, René wrote: On 22.12.2011 19:36 , Tim wrote: Am Dienstag, 20. Dezember 2011, um 23:12:39 schrieb Lists: On 11-12-20 05:08 PM, René wrote: Hi All, I'm stuck to vdr 1.6.0-2 because i can't find a current LiveBuffer patch for any current vdr 1.7.x. Does anyone know if there is any work going on with this great patch? look at http://www.vdr-portal.de/board17-developer/board25-patches/p1003452-livebuffer- patch-f%C3%BCr-vdr-1-7-16-aus-rmm-svn/#post1003452 in this thread there is a newer version available. But this version still is missing three important fixes from RMM svn repos. Could anyone update these, please? Is this patch hosted at for example github, or at vdr-developer.org? Github would be a good idea, because their frontend makes it easy to follow between revisions.. Also other people could just join by forking and do their own additions :-) So did i understand correct that the patch Norm sent does not work with 1.7.21? (i have not managed to recompile my vdr, cause had too much work.. Will definitively try the update during x-mas! :-) René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr It's a patch from yaVDR and it doesn't apply to the vdr source tree as is (at least for me). The second patch works on gentoo ebuild with small changes (It conflicts with other patches and need some changes for config.c config.h part). I tried the second too but it crashes vdr when I try to pause. I didn't tested a lot. Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No video with separate PCR PID and VPID
Hi, I have the same problem. Can you give me the values you use ? Regards. Le 12/12/2011 17:23, Dominique a écrit : Hi Something has change on stream few weeks ago .. the updated VPID is totally wrong For my part I set vdr setup to not update PID automatically and update manually VPID to PPID value and all is fine @+ Le lundi 12 décembre 2011 12:15:45, Guillaume a écrit : Hi, On my vdrbox : vdr 1.7.21 I've about 25 channels TNT SD an HD channels. But I can't get Video form 3 channels, this ones are the only ones with separate PCR PID and VPID. Audio is working, when waiting 10 seconds. All other channels are working fine, event in the same Frenquency : Working : France 3;Nat:49:I999B8C999D999M999T999G999Y999:T:27500:220=2:230=fra@3:0:0:274 :8442:1:0 TV7;Scopus Network Technologies:49:I999B8C999D999M999T999G999Y999:T:27500:720=2:730=@4:0:0 :368:8442:1:0 LCP;GR1:49:I999B8C999D999M999T999G999Y999:T:27500:620=2:630=fra@3:0;64 0=fra:0:262:8442:1:0 Video not working : France 2;GR1:49:I999B8C999D999M999T999G999Y999:T:27500:174+120=2:130=fra@3,131 =qad@3:0;140=fra:0:257:8442:1:0 France 5;GR1:49:I999B8C999D999M999T999G999Y999:T:27500:374+320=2:330=fra@3,331 =qad@3:0;340=fra:0:260:8442:1:0 France Ô;GR1:49:I999B8C999D999M999T999G999Y999:T:27500:574+520=2:530=fra@3:0;5 40=fra:0:261:8442:1:0 I've no luck with replacing 174+120 with 120 or 174 ... Is there a solution, for that ? Thx Guillaume D (Vdr user since 2002 ! / Thanks for your works !) ___ 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 mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No video with separate PCR PID and VPID
It works, many thanks (I just changed the 6th fields). But I have to set the channel updates to none. Is this possible to make vdr works with the new values ? Regards, Marc Le 12/12/2011 18:01, Dominique a écrit : Here are my channels entry (frequencies may be differents), I use VDR 1.7.20 @+ France 2;GR1:634166:B8D0M64T8Y0:T:27500:120=2:130=fra@3,131=qad@3:0:0:257:8442:1:0 France 5;GR1:634000:B8D0M64T8Y0:T:27500:320=2:330=fra@3,331=qad@3:0:0:260:8442:1:0 France �;GR1:634000:B8D0M64T8Y0:T:27500:520=2:530=fra@3:0:0:261:8442:1:0 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Unable to record 2 dvb-t channels
The problem is solved with the manual update of VPID to PPID value. Thank again Dominique ! Regards. Le 25/11/2011 12:53, Marc a écrit : Hi, I use vdr (1.7.21) with xvdr (git version). I can't record 2 channels, vdr start the recording but the file is empty and after 30 seconds, vdr throws an emergency exit : Nov 25 12:18:34 myhost vdr: [12866] recording thread started (pid=10925, tid=12866) Nov 25 12:18:34 myhost vdr: [10949] XVDR: Recordings state changed (6) Nov 25 12:18:34 myhost vdr: [10949] XVDR: Requesting clients to reload recordings list Nov 25 12:19:05 myhost vdr: [12866] ERROR: video data stream broken Nov 25 12:19:05 myhost vdr: [12866] emergency exit request ignored according to setup When I try to watch these streams with xineliboutput, the stream starts only after 30 seconds and I have only the sound : [19021] [input_vdr] control OSDCMD [19021] [input_vdr] control OSDCMD [19021] [input_vdr] control OSDCMD [19021] [input_vdr] control DISCARD 114940568 61162 [19022] [demux_vdr] input-read_block() was interrupted [19021] [input_vdr] control STILL 0 [19022] [input_vdr] control data DISCARD 114940568 61162 [19022] [input_vdr] wait_stream_sync: discard_index 114940568 != curpos 114869128 ! (diff 71440) [19022] [input_vdr] wait_stream_sync: streams synced at 114940568/114940568 [19021] [input_vdr] control LIVE 0 [19022] [input_vdr] control data BLANK prebuffer=14400 pts [19021] [input_vdr] control STILL 0 vdpau_set_property: property=0, value=0 vo_vdpau: deinterlace: none [19022] [input_vdr] wait_fifos_empty: video 0, audio 0 prebuffer=2000 pts prebuffer=14400 pts [19021] [input_vdr] control STILL 0 [19021] [input_vdr] control LIVE 1 prebuffer=14400 pts [19021] [input_vdr] control TRICKSPEED 1 [19021] [input_vdr] control STILL 0 [19022] [demux_vdr] PAT: program changed, flushing demuxer [19022] [demux_vdr] PMT changed, resetting demuxer [19022] [demux_vdr] New PTS: 7327138046 (AUDIO) [19022] [demux_vdr] audio stream changed: - 0301 *** The stream doesn't start [19021] [input_vdr] control OSDCMD [19021] [input_vdr] control OSDCMD *** After 30 seconds, the audio start but no picture An example with an other channel of the same provider (France Television Group, the 2 wrecked channels are from the same provider): [19021] [input_vdr] control OSDCMD [19021] [input_vdr] control OSDCMD [19021] [input_vdr] control OSDCMD [19021] [input_vdr] control DISCARD 56596648 30119 [19022] [demux_vdr] input-read_block() was interrupted [19021] [input_vdr] control STILL 0 [19021] [input_vdr] control LIVE 0 prebuffer=14400 pts [19021] [input_vdr] control STILL 0 vdpau_set_property: property=0, value=0 vo_vdpau: deinterlace: none [19022] [input_vdr] control data DISCARD 56596648 30119 [19022] [input_vdr] wait_stream_sync: streams synced at 56596648/56596648 [19022] [input_vdr] control data BLANK [19022] [input_vdr] wait_fifos_empty: video 0, audio 0 prebuffer=2000 pts prebuffer=14400 pts [19021] [input_vdr] control STILL 0 [19021] [input_vdr] control LIVE 1 prebuffer=14400 pts [19021] [input_vdr] control TRICKSPEED 1 [19021] [input_vdr] control STILL 0 [19022] [demux_vdr] PAT: program changed, flushing demuxer [19022] [demux_vdr] PMT changed, resetting demuxer [19022] [demux_vdr] New PTS: 6415996599 (VIDEO) [19022] [demux_vdr] audio stream changed: - 0341 [19021] [input_vdr] control HDMODE 1 [19021] [input_vdr] WARNING: xine-engine setting engine.buffers.video_num_frames:22 is too small for some HD channels vdpau_set_property: property=0, value=1 vo_vdpau: deinterlace: temporal_spatial Broken NAL, skip it. ffmpeg_audio_dec: increasing buffer to 98304 to avoid overflow. Allocate 4 reference frames Create decoder: vdp_device: 1, profile: 8, res: 1920x1080 vo_vdpau: deinterlace: temporal vo_vdpau: set_scaling_level=0 vo_vdpau: enabled features: inverse_telecine=1 vo_vdpau: disable noise reduction. vo_vdpau: disable sharpness. vo_vdpau: vdpau_update_csc: hue=0.00, saturation=1.00, contrast=1.00, brightness=0.00, color_standard=1 studio_levels=0 vo_vdpau: skip_chroma = 0 vo_vdpau: background_color = 0 [19021] [input_vdr] control OSDCMD [19021] [input_vdr] control OSDCMD Regards, Marc. ___ 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
Re: [vdr] [patch] compil vdr-1.7.4 against v4l-dvb hg as of today
some x-vdr users reported problems with compiling mplayer and some plug-ins like music too. We solved this by adding DEFINES += -D__KERNEL_STRICT_NAMES Why would this suddenly be necessary? I don't know, but it seems to work. Marc ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [patch] compil vdr-1.7.4 against v4l-dvb hg as of today
Hi, some x-vdr users reported problems with compiling mplayer and some plug-ins like music too. We solved this by adding DEFINES += -D__KERNEL_STRICT_NAMES to the VDR Makefile and patching the driver header files --- ./linux/include/linux/dvb/video.h.orig 2009-03-03 09:54:58.0 +0100 +++ ./linux/include/linux/dvb/video.h 2009-03-03 09:45:30.0 +0100 @@ -28,6 +28,7 @@ #ifdef __KERNEL__ #include linux/compiler.h #else +#include linux/compiler.h #include stdint.h #include time.h #endif ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
