Re: [vdr] vdr-satip, Digibit R1 and 2 satellites
Hi Torsten, long time no hear! Good you're still around! On Tue, Sep 19, 2023 at 10:43:01AM +0200, Torsten Duwe wrote: > There is an alternative firmware for this box In fact I tried to boot satip-axe from a USB stick but for unknown reasons the box stuck to the original FW. :-( After digging a bit more, it seems that the signal on the two cables coming from the Hotbird LNB is dead. Also, my other DVB-S2 card refuses to tune in on these cables. :-( No idea why. But this would definitely explain these messages. > > Sep 17 19:22:34 seneca vdr: [5170] SATIP-ERROR: Tuning timeout - retuning > > [device 2] > > Sep 17 19:22:34 seneca vdr: [5173] SATIP-ERROR: Tuning timeout - retuning > > [device 3] Ciao, Harald ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-satip, Digibit R1 and 2 satellites
Hi all, I recently got a stone-aged Digibit R1 to replace an even older PCI-E card. My satellite antenna points at Astra S19.2E and Hotbird S13E, 2 Dual LNBs in Quad configuration. However, the Digibit device seems not to find anything on S13E. Not sure if I need DiSeQC with SATIP but I set: in sources.conf S19.2E 1 Astra 1KR/1L/1M/2C S19.2E 2 Astra 1KR/1L/1M/2C S13E3 Eutelsat Hot Bird 13B/13C/13D S13E4 Eutelsat Hot Bird 13B/13C/13D and in diseqc.conf 1 2: S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t S19.2E 9 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W15 A W15 t S19.2E 9 H 10600 t V W15 [E0 10 38 F3] W15 A W15 T 3 4: S13.0E 11700 V 9750 t v W15 [E0 10 38 F4] W15 B W15 t S13.0E 9 V 10600 t v W15 [E0 10 38 F5] W15 B W15 T S13.0E 11700 H 9750 t V W15 [E0 10 38 F6] W15 B W15 t S13.0E 9 H 10600 t V W15 [E0 10 38 F7] W15 B W15 T This has worked with a DD Cine S2 V6.5 PCI-E card earlier. conf.d/50-satip.conf goes like, [satip] -d 4 # -s 192.168.20.4|DVBS2-4:S19.2E,S13E|DIGIBIT in order to detect 4 tuners. The -s line is apparently not needed and the params are autodetected. syslog says, Sep 17 19:21:12 seneca vdr: [5163] SATIP discover thread started (pid=5159, tid=5163, prio=high) Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=0 DeviceNumber=0 [device 0] Sep 17 19:21:12 seneca vdr: [5164] SATIP#0 tuner thread started (pid=5159, tid=5164, prio=high) Sep 17 19:21:12 seneca vdr: [5159] new device number 2 (card index 2) Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=1 DeviceNumber=1 [device 1] Sep 17 19:21:12 seneca vdr: [5166] device 1 section handler thread started (pid=5159, tid=5166, prio=low) Sep 17 19:21:12 seneca vdr: [5165] SATIP#0 section handler thread started (pid=5159, tid=5165, prio=high) Sep 17 19:21:12 seneca vdr: [5167] SATIP#1 tuner thread started (pid=5159, tid=5167, prio=high) Sep 17 19:21:12 seneca vdr: [5159] new device number 3 (card index 3) Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=2 DeviceNumber=2 [device 2] Sep 17 19:21:12 seneca vdr: [5170] SATIP#2 tuner thread started (pid=5159, tid=5170, prio=high) Sep 17 19:21:12 seneca vdr: [5159] new device number 4 (card index 4) Sep 17 19:21:12 seneca vdr: [5159] SATIP: Creating device CardIndex=3 DeviceNumber=3 [device 3] Sep 17 19:21:12 seneca vdr: [5173] SATIP#3 tuner thread started (pid=5159, tid=5173, prio=high) Sep 17 19:21:12 seneca vdr: [5169] device 2 section handler thread started (pid=5159, tid=5169, prio=low) Sep 17 19:21:12 seneca vdr: [5174] SATIP#3 section handler thread started (pid=5159, tid=5174, prio=high) Sep 17 19:21:12 seneca vdr: [5171] SATIP#2 section handler thread started (pid=5159, tid=5171, prio=high) Sep 17 19:21:12 seneca vdr: [5172] device 3 section handler thread started (pid=5159, tid=5172, prio=low) Sep 17 19:21:12 seneca vdr: [5175] device 4 section handler thread started (pid=5159, tid=5175, prio=low) ... other stuff Sep 17 19:21:12 seneca vdr: [5168] SATIP#1 section handler thread started (pid=5159, tid=5168, prio=high) Sep 17 19:21:13 seneca vdr: [5163] SATIP: Adding server '192.168.20.4|DVBS2-4|DIGIBIT-002F2A:SAT>IP' Bind: default Filters: none CI: no Quirks: SessionId,ForcePilot However, when I set UpdateChannels = 5 to run channel full scan, all I get on devices 2 and 3 is Sep 17 19:22:34 seneca vdr: [5170] SATIP-ERROR: Tuning timeout - retuning [device 2] Sep 17 19:22:34 seneca vdr: [5173] SATIP-ERROR: Tuning timeout - retuning [device 3] over and over. What am I missing? TIA! Ciao, hm ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wake-on-timer rtcwake experiments on various PC hardware
Reminds me of the nvram-wakeup lotto back in the day.
Am 16. April 2023 19:54:03 MESZ schrieb "Marko Mäkelä" :
>Today, I tested rtcwake on several x86 or x86-64 based computers.
>
>The outcome:
>
>(1) Suspend to RAM (say, "rtcwake -m mem -s 10"):
>* Success: Every system.
>(2) Wake-on-timer ("rtcwake -m no -s 120 && shutdown -h now" or "rtcwake -m
>off -s 120"):
>* Success: Lenovo Thinkpad X220 (2012?), and a 5-year-old desktop system
>* Fail: IBM Thinkpad X60 (Core Duo from 2006), a HP Zbook from 2016.
>(3) Suspend to disk ("rtcwake -m disk -s 120") had no chance of working,
>because I never configure any swap partition. I would assume that this could
>only work if (2) worked in the first place. On the Debian systems that I
>tried, the command would fail as expected. On one Arch Linux system (Lenovo
>Thinkpad X220), it forcibly power off the computer and fail to start
>automatically; a file system check ran on the manual power-on.
>
>GNU/Linux is the only operating system on each computer, and apart from the
>32-bit Thinkpad X60, everything boots up via UEFI.
>
>In the BIOS setup of both the Thinkpad X60 and the HP laptop there are some
>settings related to powering up on timer. Maybe with something like
>nvram-wakeup (which was the only working option for a 2001 Intel Celeron
>machine) they could be made to work.
>
>Moral of the story: You can't expect wake-on-timer to "just work" even on
>relatively recent hardware. Possibly the chances are better with desktop or
>small-form-factor systems than with laptops.
>
> Marko
>
>___
>vdr mailing list
>vdr@linuxtv.org
>https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Integartion with systemd and rtcwake
Let me put my unsolicited €0.02 in. My mindset is pretty hackerish as well, but I'm also an engineer thinking in efficiency terms. The raspi is what it is, and it is a nice building block for many jobs. If I wanted to build a vdr, I'd either let the raspi run permanently (given its low energy demand) or get a Pico PSU powered mini itx board with an embedded CPU, like one of the low-power (4.3-10W) celerons, and let it wake up and shut down when needed. But that's just me. Am 12. April 2023 08:00:27 MESZ schrieb "Marko Mäkelä" : >Tue, Apr 11, 2023 at 05:41:24PM +0200, Joerg Riechardt wrote: >> https://github.com/j1rie/IRMP_STM32 > >Thank you. This is a user space solution, with the benefit that it is not >limited to Linux. I think that it would be good to mention this at >https://www.linuxtv.org/vdrwiki/index.php/Raspberry_Pi and perhaps also add >some pictures. > >That page currently mentions a minimal IR receiver for the Raspberry Pi: a >3-pin IR receiver module connected to the GPIO header. Because the Linux >kernel already includes a number of IR protocol drivers, there is no need to >install any user-space lircd driver (or input plugin) if you are using a >recent enough version of VDR. > > Marko > >___ >vdr mailing list >vdr@linuxtv.org >https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Trying to run satip w/ Geniatech EyeTV Netstream 4Sat
Hi Martin, On Wed, Mar 29, 2023 at 08:21:21PM +0200, Martin Dummer wrote: > I miss lines like these: > > Mar 28 19:28:25 vdr vdr: [21100] SATIP: Adding server > '192.168.166.129|DVBC-4|FRITZ!Box 6490 Cable' Bind: default Filters: > none CI: no Quirks: n > one Oh, these were 30 or 40 lines further above, no problem. > For example, the "GSSBOX"Grundig Sat Systems GSS.box DSI 400 has a > "SessionID Bug" and there is a "quirk" to fix this. Thanks for your hint. I tried all quirks one by one but to no avail. In particular, 0x01 did not help at all so I think the comment can be removed from the source code ;-) I think I'll be going for a low-power Mini-ITX system using the existing DD card. An alternative would be two dual input USB devices attached to my current vdr dedicated system (which is a Raspi 4B running Ubuntu 22.04 LTS by the way) but I do not have encouraging experience using USB devices from the past - except if someone can point me to a known working device. Cheers, hm -- Nothing so needs reforming as other people's habits. -- Mark Twain, "Pudd'nhead Wilson's Calendar" ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [SOLVED] Looking for DVB-C channels conf for Kabel DE München
OK, disregard all after good morning. I found that you can download the full up-to-date channels list in various formats from https://helpdesk.vodafonekabelforum.de, including channels.conf. On Sat, Jan 01, 2022 at 11:28:26AM +0100, Harald Milz wrote: > Hi all, > > happy new year everyone! > > I would like to add my DVB-C channels to my existing setup but can't seem to > find a working channels.conf for Kabel Deutschland München anywhere. There are > only older versions around but I know that they changed their channel > assignments considerably in the last few years. > > Any help is appreciated! > > > -- > This night methinks is but the daylight sick. > -- William Shakespeare, "The Merchant of Venice" -- Q: Why do WASPs play golf ? A: So they can dress like pimps. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Looking for DVB-C channels conf for Kabel DE München
Hi all, happy new year everyone! I would like to add my DVB-C channels to my existing setup but can't seem to find a working channels.conf for Kabel Deutschland München anywhere. There are only older versions around but I know that they changed their channel assignments considerably in the last few years. Any help is appreciated! -- This night methinks is but the daylight sick. -- William Shakespeare, "The Merchant of Venice" ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] SOLVED Re: option parsing for --log still broken
Hi Klaus, On Tue, Nov 17, 2020 at 06:15:51PM +0100, Klaus Schmidinger wrote: > This should do, too: > > --- vdr.c 2020/05/18 16:47:29 4.33 > +++ vdr.c 2020/11/17 17:11:51 > @@ -422,6 +422,7 @@ >SysLogLevel = l; >if (!p) > break; > + *p = '.'; Yes, that's much better. Just tried it and I can confirm it works. The command line in ps now looks like /usr/bin/vdr -v /video ... --log=2.6 -P epgsearch ... Before, the respective part looked like "--log=2 6" and everything after it was ignored by vdr, ie plugins not loaded. And it logs to LOCAL6 just fine. Just building new Ubuntu focal vdr-2.4.1 package. I suggest to put this patch upstream because it will cure a couple of people's headaches ;-) Thank you! -- Tomorrow, this will be part of the unchangeable past but fortunately, it can still be changed today. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] option parsing for --log still broken
Hi Klaus and all,
it appears that option parsing for the --log option is still broken, as
described in this thread:
https://www.vdr-portal.de/forum/index.php?thread/108924-gel%C3%B6st-logging-von-yavdr-in-separaten-logfiles-anstelle-des-syslog-und-probleme/
Short version: vdr stops parsing the remainder of the command line at the
point of --log=2.6.
Long version:
The problem is in the getopt code in vdr.c:
case 'l': {
char *p = strchr(optarg, '.');
if (p)
*p = 0;
if (isnumber(optarg)) {
int l = atoi(optarg);
if (0 <= l && l <= 3) {
SysLogLevel = l;
if (!p)
break;
if (isnumber(p + 1)) {
int l = atoi(p + 1);
if (0 <= l && l <= 7) {
int targets[] = { LOG_LOCAL0, LOG_LOCAL1,
LOG_LOCAL2, LOG_LOCAL3, LOG_LOCAL4, LOG_LOCAL5, LOG_LOCAL6, LOG_LOCAL7 };
SysLogTarget = targets[l];
break;
}
}
}
}
if (p)
*p = '.';
fprintf(stderr, "vdr: invalid log level: %s\n", optarg);
return 2;
}
Initially, the point is replaced by a NULL byte in order to be able to atoi()
both numbers (if (p) *p = 0;). This replacing takes place _in place_. In
theory, the replace
should be reverted at the end of the code snippet (if (p) *p = '.';) BUT if
one of the branches involving a break is executed, the revert is never
invoked, and the original command line remains broken so that the remaining
command line options are not getting evaluated. Consequently, what used to be
vdr -w 60 -g -u vdr -l 2.6 -P plugin1 -P plugin2
becomes
vdr -w 60 -g -u vdr -l 2 6 -P plugin1 -P plugin2
and the modules will not get loaded. The thread mentioned above speaks of
upstart & co but I have the same issue in a docker container with explicit
program start in a shell script whithout any upstart or anything. I now helped
myself putting the -l at the end of the command line but I still cannot send
the vdr log to a different facility because the dangling 6 is not getting
evaluated.
My suggestion would be to not evaluate the optarg string directly but create a
copy
of optarg first, and work with the copy. This way, the original command line
is unchanged. Sample patch attached, untested but it should do the trick.
--
You are as I am with You.
diff -ur vdr-2.4.4-ORIG/vdr.c vdr-2.4.4/vdr.c
--- vdr-2.4.4-ORIG/vdr.c 2020-05-18 18:47:29.0 +0200
+++ vdr-2.4.4/vdr.c 2020-11-17 12:15:16.605470457 +0100
@@ -413,11 +413,14 @@
fprintf(stderr, "vdr: invalid instance id: %s\n", optarg);
return 2;
case 'l': {
-char *p = strchr(optarg, '.');
+ int len = strlen(optarg);
+ char copy[4];
+ strncpy (optarg, copy, len);
+char *p = strchr(copy, '.');
if (p)
*p = 0;
-if (isnumber(optarg)) {
- int l = atoi(optarg);
+if (isnumber(copy)) {
+ int l = atoi(copy);
if (0 <= l && l <= 3) {
SysLogLevel = l;
if (!p)
@@ -432,8 +435,6 @@
}
}
}
-if (p)
- *p = '.';
fprintf(stderr, "vdr: invalid log level: %s\n", optarg);
return 2;
}
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Many "Tuning timeout" messages and signal disruptions with minisatip and the satip plugin
Hi guys, I migrated my VDR and my KVM host to Ubuntu 20.04-latest lately. The KVM host has the sat card (Digital Devices Cine S2 V6.5 DVB adapter), the driver stack (0.9.33-integrated), plus minisatip-latest from git, and the vdr VM runs the normal Ubuntu stack with vdr-2.4.1 and satip-2.4.0 (plus xineliboutput and vnsiserver). I use two satellites, Astra 19.2E and Hotbird S13E, with 2 receivers each. The stack basically works, but after some time the messages "SATIP-ERROR: Tuning timeout" get more and more and the usual artifacts occur. The WAF factor is not that high as you can tell. Since everything else works nicely, I suspect a problem somewhere between the ddbridge driver, minisatip and the satip plugin. Question: is that the expected behaviour for such a setup? In the old days I used PCI passthrough but this is very inconvenient because the server (HP DL380G6) has a RMRR problem with the sat card, and I had to use custom built kernels all the time... potential solutions: - run VDR in a docker container instead of in a VM and pass /dev/dvb to the container - replace the KVM host, thus get rid of the RMRR issue and continue to use PCI passthrough - run the VDR on bare metal - others? What would you do if you were in my place, and why? TIA! -- Q: Why should you always serve a Southern Carolina football man soup in a plate? A: 'Cause if you give him a bowl, he'll throw it away. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR does not find S13E channels after upgrading (not quite solved yet)
Hi all, On Thu, Apr 30, 2020 at 05:46:44PM +0200, Harald Milz wrote: > Möglicherweise habe ich verpasst, weil ich sehr lange nicht danach geschaut > habe, dass sich an den diesbezüglichen Configs von vdr-2.2.0 nach -2.4.0 was > geändert hat. [Background: since my upgrade from 2.2.0 to yavdr-2.4.0, VDR has been confused about channel to device allocation. I have 2 dual LNBs pointing to Astra 19.2E and Hotbird 13E, respectively, attached to a 4-port Digital Devices V 6.5 card. I also upgraded dddvb-0.9.32 to 0.9.38 from git. With the old installation, all worked fine. Sorry for writing in German in my first post.] In order to bind the 13E channels to device 3, I modified the CAIDs for the affected channels to 3 now. Device 4 should be able to receive these channels as well, but I rarely need 2 of them at the same time, and VDR seems to ignore 2 channels written as x,y in the CAID field anyway. This seems to work for now, although I do not consider this a permanent fix. I will keep looking if VDR again attempts to use device 3 or 4 for Astra channels. I also suspected a broken disecq.conf although I had not changed it during the upgrade, and replaced it by an empty file, but this confused VDR even more. Also, last night I was watching ZDF (with Kodi), when a recording on ARD started, which killed the ZDF live stream and crashed VDR. :-/ That should not happen with 2 available receivers. Turned out, VDR had attempted to use device 3 for the ARD recording, resulting in a VDSB error. m( Very strange. It feels like a bug, but this would affect everyone with 2.4.0 using 2 sats and 4 receivers, or the yavdr-2.4.0 build would be buggy, which I cannot imagine (why would they patch something here?). I think it's more plausible that there is something foul in the state of configs, something subtle and not obvious (to me). Any further idea where to look is appreciated! THX! -- Your lucky color has faded. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR findet S13E nicht mehr nach Upgrade
Servus, ich brauche ausnahmsweise mal Hilfe ;-) Nach längerem habe ich mich endlich aufgerafft, meinen VDR von Ubuntu 14.04 / Kernel 4.4.0 / vdr-2.2.0 / dddvb-0.9.32 hochzuziehen auf Ubuntu 18.04 / Kernel 4.15.0 / yavdr-2.4.0 / dddvb-0.9.38 (latest aus git). An den Configs habe ich nichts geändert. Die Karte ist eine DDBridge V 6.5 mit 4 Tunern. 1 und 2 liegen auf Astra S19.2E, die beiden anderen auf Hotbird S13E. Die LNBs sind zwei Quad von Kathrein, von denen jeweils nur die ersten beiden Ausgänge belegt sind. Die disecq.conf ist die Standardeinstellung dafür wie aus dem Wiki, was immer prima funktioniert hat. Aber jetzt nicht mehr: Kanäle auf Astra werden ohne weiteres gefunden, aber der VDR versucht nun S13E-Kanäle mit Tuner 1 oder 2 zu finden, was natürlich scheitert: Apr 30 17:41:47 vdr vdr: [16550] switching to channel 1 S19.2E-1-1019-10301 (Das Erste HD) Apr 30 17:41:47 vdr vdr: [16851] device 1 receiver thread started (pid=16550, tid=16851, prio=high) Apr 30 17:41:47 vdr vdr: [16852] device 1 TS buffer thread started (pid=16550, tid=16852, prio=high) ... Apr 30 17:42:10 vdr vdr: [16550] switching to channel 61 S13.0E-318-12400-8511 (Rai 1) Apr 30 17:42:10 vdr vdr: [16852] device 1 TS buffer thread ended (pid=16550, tid=16852) ... Apr 30 17:42:10 vdr vdr: [16851] device 1 receiver thread ended (pid=16550, tid=16851) Apr 30 17:42:10 vdr vdr: [16854] device 1 receiver thread started (pid=16550, tid=16854, prio=high) Apr 30 17:42:10 vdr vdr: [16855] device 1 TS buffer thread started (pid=16550, tid=16855, prio=high) Apr 30 17:42:19 vdr vdr: [16554] frontend 0/0 timed out while tuning to channel 61 (Rai 1), tp 210992 Ich hätte erwartet, dass er dafür frontend 2/0 oder 3/0 verwendet. Auf denen wirft er aber ständig Timeouts zu Channels von S19.2E. In /dev/dvb stehen alle 4 Adapter, und der VDR erkennt sie auch (found 4 DVB devices). Möglicherweise habe ich verpasst, weil ich sehr lange nicht danach geschaut habe, dass sich an den diesbezüglichen Configs von vdr-2.2.0 nach -2.4.0 was geändert hat. Wo muss ich hinschauen? Danke! -- You are only young once, but you can stay immature indefinitely. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Race condition when executing recording hook
Hi everyone, I finally managed to pull myself together and install markad-0.1.4 on Ubuntu 14.04.5 LTS and vdr-2.2.0. Not trivial for me because the markad sources needed patching in order to compile and link properly. Different story - if someone wants a clue just drop me a note. When playing around with markad last night, I noticed that there is a catch with the combination of an active recording, changing pids and a recording hook being configured. Look at the syslog snippet below. The recording is started, then all of a sudden the channel pids change, after which VDR stops the recording for a very short moment and restarts it accordingly. No problem for the recording itself because only a few frames will be missing. But when stopping, the recording hook is invoked with "after", upon which markad starts and tries to analyze the recording fragment. Now markad will handle this situation gracefully because it will be invoked with "after" again anyway when the recording is finished after a while, overwriting or renaming an existing marks file. But we cannot always be sure what a user does in the recording hook. I don't know how to handle this properly. My suggestion would be to ignore the channel pid change during an active recording on this channel, and defer the change until the recording is finished _if_ "-r something" is set on the command line. Ideas or insights anyone? Dec 13 21:55:00 vdr vdr: [3759] record /video/Tatort:_Wofür_es_sich_zu_leben_lohnt/2017-12-13.21.55.13-0.rec Dec 13 21:55:00 vdr vdr: [3759] creating directory /video/Tatort:_Wofür_es_sich_zu_leben_lohnt Dec 13 21:55:00 vdr vdr: [3759] creating directory /video/Tatort:_Wofür_es_sich_zu_leben_lohnt/2017-12-13.21.55.13-0.rec Dec 13 21:55:00 vdr vdr: [3759] recording to '/video/Tatort:_Wofür_es_sich_zu_leben_lohnt/2017-12-13.21.55.13-0.rec/1.ts' Dec 13 21:55:00 vdr vdr: [4035] recording thread started (pid=3759, tid=4035, prio=high) ... Dec 13 21:55:02 vdr vdr: [3768] changing pids of channel 13 (SWR RP HD) from 5121+5121=27:5122=deu@3,5123=mis@3;5126=deu@106:5135=deu:5134 to 5131+5131=27:5132=deu@3,5133=mis@3;5136=deu@106:5135=deu:5134 Dec 13 21:55:02 vdr vdr: [4035] executing '/usr/local/bin/markad.sh started "/video/Tatort:_Wofür_es_sich_zu_leben_lohnt/2017-12-13.21.55.13-0.rec"' Dec 13 21:55:02 vdr vdr: [3768] channel 13 (SWR RP HD) event Wed 13.12.2017 21:45-22:00 (VPS: 13.12. 21:45) 'SWR Aktuell Rheinland-Pfalz' status 4 ... Dec 13 21:55:06 vdr markad: [4032] detected logo stop (3892) Dec 13 21:55:06 vdr vdr: [3759] stopping recording due to modification of channel 13 (SWR RP HD) Dec 13 21:55:06 vdr vdr: [4035] recording thread ended (pid=3759, tid=4035) Dec 13 21:55:06 vdr vdr: [3759] timer 10 (13 2155- 'Tatort: Wofür es sich zu leben lohnt') stop Dec 13 21:55:06 vdr vdr: [3759] executing '/usr/local/bin/markad.sh after "/video/Tatort:_Wofür_es_sich_zu_leben_lohnt/2017-12-13.21.55.13-0.rec"' Dec 13 21:55:06 vdr markad: [4055] starting v0.1.6 (ea2e182) (64bit) Dec 13 21:55:06 vdr markad: [4055] on /video/Tatort:_Wofür_es_sich_zu_leben_lohnt/2017-12-13.21.55.13-0.rec Dec 13 21:55:06 vdr markad: [4055] broadcast aspectratio 16:9 (from info) Dec 13 21:55:06 vdr markad: [4055] getting broadcast start from info mtime Dec 13 21:55:06 vdr markad: [4055] no logo found, logo detection disabled Dec 13 21:55:06 vdr markad: [4055] marks can/will be weak! Dec 13 21:55:06 vdr markad: [4055] pre-timer 4m Dec 13 21:55:06 vdr markad: [4055] broadcast length 90m Dec 13 21:55:06 vdr vdr: [3759] switching device 2 to channel 13 (SWR RP HD) Dec 13 21:55:06 vdr vdr: [3759] timer 10 (13 2155- 'Tatort: Wofür es sich zu leben lohnt') start Dec 13 21:55:06 vdr vdr: [3759] Title: 'Tatort: Wofür es sich zu leben lohnt' Subtitle: 'Fernsehfilm Deutschland 2016' Dec 13 21:55:06 vdr vdr: [3759] executing '/usr/local/bin/markad.sh before "/video/Tatort:_Wofür_es_sich_zu_leben_lohnt/2017-12-13.21.55.13-0.rec"' Dec 13 21:55:06 vdr vdr: [3759] record /video/Tatort:_Wofür_es_sich_zu_leben_lohnt/2017-12-13.21.55.13-0.rec Dec 13 21:55:06 vdr vdr: [3759] recording to '/video/Tatort:_Wofür_es_sich_zu_leben_lohnt/2017-12-13.21.55.13-0.rec/2.ts' Dec 13 21:55:06 vdr markad: [4032] detected logo start (4384)* Dec 13 21:55:06 vdr vdr: [4058] recording thread started (pid=3759, tid=4058, prio=high) ... -- Don't feed the bats tonight. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR without PrimaryDVB but with xineliboutput ?
On Wed, Dec 21, 2016 at 03:14:29PM +0100, Niedermeier Günter wrote: > > I use these config parameters for xineliboutput plugin > > --local=none > --primary > --remote=0.0.0.0:37890 Yup, me too. In this case xineliboutput will be the primary display, and there will always be a channel running on it. Which is the root cause of my problem. If you omit --primary, xineliboutput will claim primary on its own if there is no other output device, which is the case when you have a receiver-only sat card. -- Q: Why did the germ cross the microscope? A: To get to the other slide. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR without PrimaryDVB but with xineliboutput ?
On Tue, Dec 20, 2016 at 06:09:46PM +0100, Stephan Loescher wrote: > Hi! > > I never tried it myself, but isn't vdr-dummydevice used for that? Hmmm, it seems xineliboutput doesn't like not being the primary: Dec 21 14:39:38 vdr vdr: [3419] [xine..put] Dropping client: xineliboutput is not the primary device ! I think I'll park the primary at a hotbird channel via SVDRP / cron for now. -- Hell is empty and all the devils are here. -- Wm. Shakespeare, "The Tempest" ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR without PrimaryDVB but with xineliboutput ?
Hi all, I would like to run my headless VDR without a primary DVB (or suspended output) but keep xineliboutput running. I can't figure out how. My VDR has 4 receivers (2x Astra, 2x Hotbird) without MPEG decoder. It runs vnsiserver (for my Kodi client), streamdev-server (for some browser / VLC clients) and xineliboutput (because it's sometimes useful to have access to the VDR console via remote). Alas, xineliboutput will always be the primary DVB device and block a receiver, which is nasty when VDR is recording on one bouquet, xineliboutput blocks another bouquet and I want to watch live TV on just another bouquet, all on the same satellite. Can I use the suspendoutput plugin while keeping xineliboutput active so that I can access it with vdr-sxfe when needed? TIA! (I could "park" xineliboutput on an arbitrary hotbird channel though but I'd like to have it automated ...) -- Keep emotionally active. Cater to your favorite neurosis. ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] NOW SOLVED!!! buffer overruns and sync probs after change of receivers
Hi all, I think I found the cause of the buffer overrun problem. My system has now been running for nearly 10 hours without a single problem, with occasional "buffer stats 0..3%" in the syslog. It appears that the problem relies with the Ubuntu-wily HWE kernel 4.2.0-something. I downgraded to 3.19.0-something today, and since then the problem hasn't occured again. I have been load testing the whole day, with up to 5 concurrent recordings on all 4 receivers plus up to 3 live streams (xine, vnsi, and streamdev). Smooth. Question: has anyone successfully run vdr-2.0.3 or -2.2.0 with the 4.2.0 kernel using a PCIe card? And while we're at it, a PCIe USB3 card with a harddisk attached? It seems that some kernel buffer starts choking after, like, 150 or more GB have been transferred. If that is a common problem (on any Ubuntu distro running the wily HWE kernel or on 15.10 itself) it should be mentioned somewhere - no idea where. vdr-wiki.de maybe. I also changed the motherboard inbetween. The new one has the ethernet chip attached via PCIe (RTL8111) but my old one had not (RTL8211 / NVidia MCP97), which might be the reason why the network didn't let me down on the old MoBo. But then, I am not a kernel expert. Phew. Thanks to Thomas who kept kicking me. (y) Does anyone need a K10N78 board with 4x 2 GB RAM? ;-) (I should start using ITIL-like change management. I might have noticed it earlier. It may well be that the problems with the old USB receivers started some time after upgrading the kernel to wily HWE). On Tue, Feb 09, 2016 at 03:15:09PM +0100, Thomas Netousek wrote: > Harald, > > if > - the problem surfaces only with a new DVBs hardware card (and not > with the old one) and > - it only appears when you have traffic both on the DVB card and on > the network interface and > - the problem only goes away when you cold boot > > then this makes me think that you have a problem with the PCIe bus. > > I trust you have updated the mainboard BIOS to the latest level, right ? > > Can you please elaborate on the hardware > * mainboard make and model > * schematic of the mainboard and how network card, disk controller > and DVB card are attached > > Please run an iperf test (bi-directional) to measure the network > performance when newly booted and when "the problem" has surfaced. > > And I would guess that you can trigger the problem more easily if > you run iperf, create disk activity (run a random access read-only > disk test ?) and run the remote video client at the same time. > > Btw, there are LEDs on the Digital Devices card, do they change > between the "good" and the "bad" state ? > > Thomas > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Q: What is purple and conquered the world? A: Alexander the Grape. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] NOT SOLVED!!! buffer overruns and sync probs after change of receivers
Hi folks, I hate to follow up on myself, but as it appears I cheered too soon. It now also happens reproducibly when recording, and independent of vnsiserver or anything else. The machine has been up for 4 days, and when starting a new recording, this is what happens after some seconds: Feb 9 11:41:37 seneca vdr: [624] i/o throttle activated, count = 1 (tid=624) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 60% (tid=623) Feb 9 11:41:46 seneca vdr: [624] buffer usage: 70% (tid=623) Feb 9 11:41:51 seneca vdr: [624] buffer usage: 80% (tid=623) Feb 9 11:41:55 seneca vdr: [624] buffer usage: 90% (tid=623) Feb 9 11:41:59 seneca vdr: [624] buffer usage: 100% (tid=623) Feb 9 11:41:59 seneca vdr: [624] ERROR: 1 ring buffer overflow (1 bytes dropped) Feb 9 11:42:05 seneca vdr: [624] ERROR: 31446 ring buffer overflows (5911848 bytes dropped) Feb 9 11:42:11 seneca vdr: [624] ERROR: 32635 ring buffer overflows (6135380 bytes dropped) (needless to say the recording is entirely crippled.) VDR is 2.2.0, plain but with PLAYERBUFSIZE and RECORDERBUFSIZE enlarged to 50 megs each. As I suspected earlier, enlarging the buffers only cures the symptom. It's only a matter of time. As if memory regions and pointers weren't cleanly free()'d but reused next time instead of malloc()ing new ones. Looking at the cRingBufferLinear class this seems to be the case. But how can this persist across VDR restarts? I'm puzzled. Restarting VDR, reloading the DVB drivers (dddvb-0.9.22 from Digital Devices) does not remedy the overruns. Only restarting the machine does. If anyone had an idea where to look, that would be great. e.g. were there any significant changes in the TS buffer code between 2.2.0 and devel-latest? I'm a bit reluctant to try 2.3.x because some plugins may not work with it. TIA! On Mon, Feb 08, 2016 at 08:17:08AM +0100, Harald Milz wrote: > Richard, > > On Sun, Feb 07, 2016 at 12:34:17PM +, Richard F wrote: > > One of the things that the vnsi developer said to do set this in the VDR > > config > > > > vnsiserver.AvoidEPGScan = 1 > > (http://forum.kodi.tv/showthread.php?tid=203396) > > Now that you mention it - I also see interruptions sometimes when Kodi appears > to update its timers. That is, when it scans through the timer list, > displaying the respective message windows bottom left. Sometimes, live > streaming just crashes, and needs to be restarted manually. > > I'll give AvoidEPGScan = 1 a try - thank you! > > > I don't know where PLAYERBUFSIZE is - Kodi config file - which one? > > No, that's in vdr: > > dvbplayer.c:#define PLAYERBUFSIZE MEGABYTE(1) > > and > > recorder.c:#define RECORDERBUFSIZE (MEGABYTE(10) / TS_SIZE * TS_SIZE) // > multiple of TS_SIZE > > Please not that it really cures only the symptom. If there is a problem with > filling any emptying the buffer, leading to an overrun, then it will > eventually happen, no matter what the size is. So far, I haven't seen this > yet with 50 megs each. > > -- > A gift of a flower will soon be made to you. -- Never be led astray onto the path of virtue. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] SOLVED??? buffer overruns and sync probs after change of receivers
Richard, On Sun, Feb 07, 2016 at 12:34:17PM +, Richard F wrote: > One of the things that the vnsi developer said to do set this in the VDR > config > > vnsiserver.AvoidEPGScan = 1 > (http://forum.kodi.tv/showthread.php?tid=203396) Now that you mention it - I also see interruptions sometimes when Kodi appears to update its timers. That is, when it scans through the timer list, displaying the respective message windows bottom left. Sometimes, live streaming just crashes, and needs to be restarted manually. I'll give AvoidEPGScan = 1 a try - thank you! > I don't know where PLAYERBUFSIZE is - Kodi config file - which one? No, that's in vdr: dvbplayer.c:#define PLAYERBUFSIZE MEGABYTE(1) and recorder.c:#define RECORDERBUFSIZE (MEGABYTE(10) / TS_SIZE * TS_SIZE) // multiple of TS_SIZE Please not that it really cures only the symptom. If there is a problem with filling any emptying the buffer, leading to an overrun, then it will eventually happen, no matter what the size is. So far, I haven't seen this yet with 50 megs each. -- A gift of a flower will soon be made to you. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Using a rasberry pi as vdr client
On Mon, Feb 01, 2016 at 07:19:32PM +0100, Gerald Dachs wrote: > > > An IR receiver is usually not necessary. The HDMI-CEC support of the > raspberry pi is very good. > Mostly the remote of the TV is just enough. Yup. If only my 2004 TV set supported HDMI-CEC. -- The mind is its own place, and in itself Can make a Heav'n of Hell, a Hell of Heav'n. -- John Milton ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Using a rasberry pi as vdr client
Hi, a bit late maybe but vnsiverver on the VDR side and Openelec / kodi on the RPi side should be fine, that's what I am using, and the WAF is pretty high. I got a Hama MCE remote with USB IR receiver, which worked out of the box. HTH! On Thu, May 28, 2015 at 07:19:13PM +0200, Damien Bally wrote: > Hi > > I want to use raspberry pi as if it were a graphic card : I mean the > dvb devices on a PC style server, IR receiver preferably on the > server too (rpi and server in the same room) > > I don't know how to configure it, there is apparently 2 ways of > doing it (from what I understood) > > + xineliboutput with vdr-fbfe (rpi plugin is closed source ? the one > here : > http://www.vdr-portal.de/board18-vdr-hardware/board98-arm-co/118588-rasperry-pi-xine-plugin/) > > > + streamdev and rpihddevice (which additional plugins ?) > > The second way seems to be more complicated to configure, and I'm > not sure it suits my project, but the rpihddevice is well maintained > though. > > The first solution is perhaps much straightforward and includes a > media player (?) > > Could you tell me more please ? > > Damien > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- You will live to see your grandchildren. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] buffer overruns and sync probs after change of receivers
with OpenELEC-latest or on Android 5.1.1 using Kodi-latest as from Google Play). Every other combination (recording, watching recordings, watching live TV with xineliboutput / vdr-sxfe (on Ubuntu 14.04-x86)) does not exhibit the problem. I have no idea what I can do here. Any hint or help is appreciated. TIA! On Sat, Jan 30, 2016 at 10:40:19AM +0100, Harald Milz wrote: > Hi all, > > I recently changed the receivers of my VDR from two TeVii S660's to a Digital > Devices Cine S2 + Duoflex card. Everything else remained unchanged on the VDR > side of things. Since then, I encounter frequent (as in, once per day approx.) > buffer overruns and resync probs. As it seems from the thread IDs, the TS or > VNSI > buffer threads seem to cause the problem. But I may be wrong. > > Software versions: > - Ubuntu 14.04.3 LTS with Wily kernel (4.2.0-latest) > - vdr-2.0.3 (ubuntu) > - vnsiserver-latest from git (from a couple of days ago) > - Kodi 6.0 as in Openelec-current on RPi2 > - dddvb driver 0.9.21 or 0.9.22 from Digital Devices git (current). > > As shown by the kernel log, the DD card is initialized just fine: > > [ 14.704506] dvb_core: module verification failed: signature and/or > required key missing - tainting kernel > [ 14.744728] Digital Devices PCIE bridge driver 0.9.21, Copyright (C) > 2010-15 Digital Devices GmbH > [ 14.744921] DDBridge driver detected: Digital Devices Cine S2 V6.5 DVB > adapter > [ 14.744938] DDBridge: HW 0001000d REGMAP 00010004 > [ 14.744972] DDBridge: using 1 MSI interrupt(s) > [ 14.746272] Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-S2 > [ 14.858090] Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-S2 > [ 14.859048] Port 2: Link 0, Link Port 2 (TAB 3): NO MODULE > [ 14.860003] Port 3: Link 0, Link Port 3 (TAB 4): NO MODULE > [ 14.861739] 0 netstream channels > [ 14.861742] DVB: registering new adapter (DDBridge) > [ 14.861744] DVB: registering new adapter (DDBridge) > [ 14.861745] DVB: registering new adapter (DDBridge) > [ 14.861746] DVB: registering new adapter (DDBridge) > ... > [ 15.407636] LNBx2x attached on addr=a > [ 15.436794] stv6110x_attach: Attaching STV6110x > [ 15.436799] attach tuner input 0 adr 60 > [ 15.436871] ddbridge :05:00.0: DVB: registering adapter 0 frontend 0 > (STV090x Multistandard)... > ... > [ 15.472168] LNBx2x attached on addr=8 > [ 15.472174] stv6110x_attach: Attaching STV6110x > [ 15.472176] attach tuner input 1 adr 63 > [ 15.472256] ddbridge :05:00.0: DVB: registering adapter 1 frontend 0 > (STV090x Multistandard)... > ... > [ 15.491106] LNB25 on 0c > [ 15.640527] ddbridge :05:00.0: DVB: registering adapter 2 frontend 0 > (STV0910)... > [ 15.642001] LNB25 on 0d > [ 15.645682] ddbridge :05:00.0: DVB: registering adapter 3 frontend 0 > (STV0910)... > > When running, after a while these error messages can be seen: > > Jan 23 11:15:46 seneca vdr: [7888] VNSI: Successfully switched to channel 14 > - KiKA HD > Jan 23 11:15:46 seneca vdr: [7888] VNSI: Started streaming of channel KiKA HD > (timeout 10 seconds) > Jan 23 11:15:46 seneca vdr: [7891] cLiveStreamer stream processor thread > started (pid=2593, tid=7891, prio=high) > Jan 23 11:15:46 seneca vdr: [7892] TS buffer on device 2 thread started > (pid=2593, tid=7892, prio=high) > Jan 23 11:15:46 seneca vdr: [7890] VNSI: VideoInput: no pat/pmt within > timeout, falling back to channel pids > Jan 23 11:15:46 seneca vdr: [7890] VNSI: Video Input - new pmt, attaching > receiver > Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6610 and > type=8 > Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6622 and > type=1 > Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6620 and > type=2 > Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6621 and > type=2 > Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6631 and > type=9 > Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6630 and > type=11 > Jan 23 11:15:49 seneca vdr: [7892] i/o throttle activated, count = 1 > (tid=7892) > Jan 23 11:15:50 seneca vdr: [7892] buffer usage: 70% (tid=7889) > Jan 23 11:15:50 seneca vdr: [7892] buffer usage: 80% (tid=7889) > Jan 23 11:15:50 seneca vdr: [7892] buffer usage: 60% (tid=7889) > Jan 23 11:15:50 seneca vdr: [2746] VNSI: Timers state changed (13) > Jan 23 11:15:50 seneca vdr: [2746] VNSI: Requesting clients to reload timers > Jan 23 11:15:52 seneca vdr: [7892] buffer usage: 70% (tid=7889) > Jan 23 11:15:52 seneca vdr: [7892] buffer usage: 80% (tid=7889) > Jan 23 11:15:52 seneca vdr: [7892] buffer usage: 90% (tid=7889) > Jan 23 11:15:53 seneca vdr: [7892] buffer usage: 100%
Re: [vdr] buffer overruns and sync probs after change of receivers
On Sat, Jan 30, 2016 at 12:35:49PM +0100, Thomas Netousek wrote: > Try disabling MSI interrupts in the ddbridge driver. Thank you for the hint... 17: 0 02317734690 IO-APIC 17-fasteoi ddbridge but sadly: Jan 30 17:38:36 seneca vdr: [26112] buffer usage: 70% (tid=26111) Jan 30 17:38:36 seneca vdr: [26112] buffer usage: 80% (tid=26111) Jan 30 17:38:37 seneca vdr: [26112] buffer usage: 90% (tid=26111) Jan 30 17:38:37 seneca vdr: [26112] buffer usage: 100% (tid=26111) Jan 30 17:38:38 seneca vdr: [26111] ERROR: skipped 123 bytes to sync on TS packet on device 1 Jan 30 17:38:44 seneca vdr: [26112] ERROR: driver buffer overflow on device 1 Jan 30 17:38:46 seneca vdr: [26111] ERROR: skipped 123 bytes to sync on TS packet on device 1 Jan 30 17:38:46 seneca vdr: [26112] buffer usage: 60% (tid=26111) Jan 30 17:38:46 seneca vdr: [26112] i/o throttle released, count = 0 (tid=26112) tid=26111 is the vnsiserver. Am I out of options? -- Learn to pause -- or nothing worthwhile can catch up to you. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] buffer overruns and sync probs after change of receivers
Hi all, I recently changed the receivers of my VDR from two TeVii S660's to a Digital Devices Cine S2 + Duoflex card. Everything else remained unchanged on the VDR side of things. Since then, I encounter frequent (as in, once per day approx.) buffer overruns and resync probs. As it seems from the thread IDs, the TS or VNSI buffer threads seem to cause the problem. But I may be wrong. Software versions: - Ubuntu 14.04.3 LTS with Wily kernel (4.2.0-latest) - vdr-2.0.3 (ubuntu) - vnsiserver-latest from git (from a couple of days ago) - Kodi 6.0 as in Openelec-current on RPi2 - dddvb driver 0.9.21 or 0.9.22 from Digital Devices git (current). As shown by the kernel log, the DD card is initialized just fine: [ 14.704506] dvb_core: module verification failed: signature and/or required key missing - tainting kernel [ 14.744728] Digital Devices PCIE bridge driver 0.9.21, Copyright (C) 2010-15 Digital Devices GmbH [ 14.744921] DDBridge driver detected: Digital Devices Cine S2 V6.5 DVB adapter [ 14.744938] DDBridge: HW 0001000d REGMAP 00010004 [ 14.744972] DDBridge: using 1 MSI interrupt(s) [ 14.746272] Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-S2 [ 14.858090] Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-S2 [ 14.859048] Port 2: Link 0, Link Port 2 (TAB 3): NO MODULE [ 14.860003] Port 3: Link 0, Link Port 3 (TAB 4): NO MODULE [ 14.861739] 0 netstream channels [ 14.861742] DVB: registering new adapter (DDBridge) [ 14.861744] DVB: registering new adapter (DDBridge) [ 14.861745] DVB: registering new adapter (DDBridge) [ 14.861746] DVB: registering new adapter (DDBridge) ... [ 15.407636] LNBx2x attached on addr=a [ 15.436794] stv6110x_attach: Attaching STV6110x [ 15.436799] attach tuner input 0 adr 60 [ 15.436871] ddbridge :05:00.0: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)... ... [ 15.472168] LNBx2x attached on addr=8 [ 15.472174] stv6110x_attach: Attaching STV6110x [ 15.472176] attach tuner input 1 adr 63 [ 15.472256] ddbridge :05:00.0: DVB: registering adapter 1 frontend 0 (STV090x Multistandard)... ... [ 15.491106] LNB25 on 0c [ 15.640527] ddbridge :05:00.0: DVB: registering adapter 2 frontend 0 (STV0910)... [ 15.642001] LNB25 on 0d [ 15.645682] ddbridge :05:00.0: DVB: registering adapter 3 frontend 0 (STV0910)... When running, after a while these error messages can be seen: Jan 23 11:15:46 seneca vdr: [7888] VNSI: Successfully switched to channel 14 - KiKA HD Jan 23 11:15:46 seneca vdr: [7888] VNSI: Started streaming of channel KiKA HD (timeout 10 seconds) Jan 23 11:15:46 seneca vdr: [7891] cLiveStreamer stream processor thread started (pid=2593, tid=7891, prio=high) Jan 23 11:15:46 seneca vdr: [7892] TS buffer on device 2 thread started (pid=2593, tid=7892, prio=high) Jan 23 11:15:46 seneca vdr: [7890] VNSI: VideoInput: no pat/pmt within timeout, falling back to channel pids Jan 23 11:15:46 seneca vdr: [7890] VNSI: Video Input - new pmt, attaching receiver Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6610 and type=8 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6622 and type=1 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6620 and type=2 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6621 and type=2 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6631 and type=9 Jan 23 11:15:47 seneca vdr: [7891] VNSI: Created stream for pid=6630 and type=11 Jan 23 11:15:49 seneca vdr: [7892] i/o throttle activated, count = 1 (tid=7892) Jan 23 11:15:50 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:15:50 seneca vdr: [7892] buffer usage: 80% (tid=7889) Jan 23 11:15:50 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:15:50 seneca vdr: [2746] VNSI: Timers state changed (13) Jan 23 11:15:50 seneca vdr: [2746] VNSI: Requesting clients to reload timers Jan 23 11:15:52 seneca vdr: [7892] buffer usage: 70% (tid=7889) Jan 23 11:15:52 seneca vdr: [7892] buffer usage: 80% (tid=7889) Jan 23 11:15:52 seneca vdr: [7892] buffer usage: 90% (tid=7889) Jan 23 11:15:53 seneca vdr: [7892] buffer usage: 100% (tid=7889) Jan 23 11:15:54 seneca vdr: [2746] VNSI: Timers state changed (14) Jan 23 11:15:54 seneca vdr: [2746] VNSI: Requesting clients to reload timers Jan 23 11:15:54 seneca vdr: [7892] ERROR: driver buffer overflow on device 2 Jan 23 11:15:58 seneca vdr: message repeated 2 times: [ [7892] ERROR: driver buffer overflow on device 2] Jan 23 11:16:00 seneca vdr: [7889] ERROR: skipped 123 bytes to sync on TS packet on device 2 Jan 23 11:16:03 seneca vdr: [7892] ERROR: driver buffer overflow on device 2 Jan 23 11:16:04 seneca vdr: [7892] buffer usage: 60% (tid=7889) Jan 23 11:16:04 seneca vdr: [7889] ERROR: skipped 123 bytes to sync on TS packet on device 2 Jan 23 11:16:04 seneca vdr: [7892] i/o throttle released, count = 0 (tid=7892) Jan 23 11:16:05 seneca vdr: [7892] i/o throttle activated, count = 1 (tid=7892) Jan 23
Re: [vdr] xineliboutput and streamdev at the same time
On Mon, Apr 20, 2015 at 11:40:41AM +0200, Patrick Boettcher wrote:
On Mon, 20 Apr 2015 11:33:02 +0200 Torgeir Veimo
torgeir.ve...@gmail.com wrote:
Have you tried rpihddevice plugin with VDR on the rpi? It might work
even smoother than using xinelinboutput, but you'd have to find a
different setup for cec i suppose.
http://projects.vdr-developer.org/git/vdr-plugin-rpihddevice.git/
I think the big difference between rpihddevice and vdr-fbfe is that
the vdr-fbfe does not need a local vdr-instance running on the device.
vdr-fbfe is connecting over network to a vdr running on a full
machine. No need for streamdev.
I have been happily using vdr-sfxe on an NVidia ION board on Ubuntu 12.04 for
quite a while (with a sufficiently high WAF factor :-) ) . But I haven't seen
vdr-{sxfe,fbfe} in Raspbian lately. Are there any ready to consume packages
anywhere? Since the ION machine has been a bit unstable lately, I'd be more
than willing to throw in my RPi that idles on my desk.
TIA!
--
You will be held hostage by a radical group.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and streamdev at the same time
On Tue, Apr 21, 2015 at 10:25:48AM +0200, M. Fiegert wrote:
On 21.04.2015 07:41, Harald Milz wrote:
I have been happily using vdr-sfxe on an NVidia ION board on Ubuntu 12.04
for
quite a while (with a sufficiently high WAF factor :-) ) . But I haven't
seen
vdr-{sxfe,fbfe} in Raspbian lately. Are there any ready to consume packages
anywhere? Since the ION machine has been a bit unstable lately, I'd be more
than willing to throw in my RPi that idles on my desk.
dto
fanless Zotac ION, vdr-sxfe, recently updated from 10.4 to Ubuntu 14.4
Thinking of RPi
Which kind of instabilities?
This is hardware related in case of my ION board. I'm looking for a new HW
platform anyway. I tried rpihddevice but using another, local VDR instance
would reduce the WAF factor. If vdr-fbfe works nicely on the Pi, this will be
my platform.
--
You will pass away very quickly.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and streamdev at the same time
On Tue, Apr 21, 2015 at 12:41:57PM +0300, Petri Hintukainen wrote:
Do you mean setting the marks (and letting remote VDR to do the actual
editing) ? Or using VDR in RPi to cut recordings ? Cutting with RPi is
probably very slow and consumes lot of limited I/O resources.
For setting editing marks - probably, I'm not sure. I rarely edit
Yes sure. With vdr-{sxfe,fbfe} you get a remote OSD from the server VDR, i.e.
you work on the server, not the RPi. No data is transferred over the net
except the OSD when cutting.
Latency with 100Mbit/s ethernet is not noticeable. It can be even faster
For SD 100 MBit is fine. For HD it should be okay also. As far as Wifi, 54
MBit is okay-ish for SD but better go for 300 on 5 GHz (to make sure the
wifi is near-exclusively used for the VDR link).
One possible source of problems is audio decoding performance. I'm not
EAC3 ?). AC3 decoding uses ~ half of RPi CPU time. Here the additional
CPU power of RPi 2 would be useful.
Better use HDMI pass-through and have the AC3 receiver decode the stream. The Pi
has only a 2.0 analog output anyway, so there's little point in decoding on
the Pi.
--
You will be traveling and coming into a fortune.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Commercial detection and automatic cutting
On Wed, Sep 24, 2014 at 09:28:05AM -0400, Norm Dressler wrote: I searched for noad but could not find it. I have it installed now and am trying it out. How do you create a recording with the commercials cut out? Or do you just rely on VDR to do it on the fly? Hi Norm, you'll find noad at http://noad.net23.net/. In a nutshell, when a recording is finished, noad scans the recording for various markers, and sets (porposed) cut marks. In many cases, these will work out of the box, in some cases you will have to manually re-check them. Then, just ask VDR to cut the recording :-) HTH! -- You may worry about your hair-do today, but tomorrow much peanut butter will be sold. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Raspberry Pi, Streamdev + rpihddevice
On Tue, Jul 08, 2014 at 02:34:37PM +0300, Marko Mäkelä wrote: I guess that for the cheap ARM boards such as the Raspberry Pi, it is simplest to keep the base hardware always on (the base power consumption being so low, and because there is no battery-backed clock or wakeup timer). I'm using a switchable power strip for my xineliboutput player, the TV set and everything else. :-) -- Alas, how love can trifle with itself! -- William Shakespeare, The Two Gentlemen of Verona ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Minimum CPU requirement for xineliboutput + vdr-sxfe for HDTV
It might be even cheaper to get a cheap Nvidia card along with s power saving CPU. My player is an ION board with an Atom 230... On 27. Februar 2014 21:29:20 MEZ, Stephan Loescher loesc...@gmx.de wrote: Hi! I am interested in your experiences with xineliboutput-plugin and vdr-sxfe for HDTV and not using VDPAU but using the plain CPU-power. The plan would be to build a simple system without any special graphics-card and no special X11-configuration or driver, perhaps some cheap system like the one descibed in http://ct.de/-1375124 (German). (Celeron G1820, small case, low power consumption, about 180 EUR without disks.) I know from my own VDR-systems, that a Intel Core2 Duo @ 1.86GHz or a Core i3 540 @ 3.07GHz has far enough power to run VDR and vdr-sxfe for displaying HDTV. But I think even slower and thus cheaper CPUs could do the HDTV-decoding, too. What is you experience? Would it be possible to use these new Haswell-Celerons? TIA and best regards, Stephan. -- loesc...@gmx.de http://www.loescher-online.de/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Streaming DVD contents from VDR?
Hi Marko, have you tried the xineliboutput plugin together with vdr-sxfe on the headless box? It basically gives you a remote VDR display including the OSD. The downside is, the DVD needs to be in the VDR PC in the different room... which may not be what you want. (And yes, a simple headless solution that can access the headless VDR player's DVD or Blu-Ray drive would be nifty ... NBD comes to my mind.) On Sat, Feb 01, 2014 at 10:42:49PM +0200, Marko Mäkelä wrote: Hi, I have a minimal setup consisting of an old PC sitting in a different room, and a Samsung SmartTV in the living room. We rarely watch any DVDs in my family, so we do not have any dedicated DVD player. I used to use a DVD player plugin when the VDR PC was in the living room, attached to a TV, but I would prefer to have a mostly-headless setup (the VDR PC is only hooked to a VGA monitor, no sound output at the moment). I checked both the Streamdev plugin and the SmartTV plugin, but neither seem to support DVDs at the moment: http://projects.vdr-developer.org/projects/plg-streamdev/ http://projects.vdr-developer.org/projects/plg-smarttvweb/ I wonder if there is any easy solution to stream the contents of a disk in the DVD drive of the VDR PC over the local CAT5e cabling. I guess that an alternative solution could be to transcode the DVD into MPEG PS files, which could presumably be viewed on or streamed from VDR. Best regards, Marko ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- You have a truly strong individuality. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-fritzbox no longer working after FBF firmware upgrade
Hi all, I've been happily using vdr-fritzbox for a very long time. Since the last upgrade to Fritz!OS 5.50 and then to 5.53 (54.05.50 respectively 54.05.53) the plugin cannot connect to the FBF any more. The log: Jan 21 10:10:58 seneca vdr: [2393] [libfritz++/FritzClient.cpp:210] logging into fritz box using old scheme without SIDs. Jan 21 10:10:59 seneca vdr: [2393] [libfritz++/FritzClient.cpp:228] login successful. Jan 21 10:10:59 seneca vdr: [2393] [libfritz++/FritzClient.cpp:317] sending callList request. Jan 21 10:11:01 seneca vdr: [2393] [libfritz++/FritzClient.cpp:342] Exception in connection to 192.168.20.253 - Could not connect Jan 21 10:11:01 seneca vdr: [2393] [libfritz++/FritzClient.cpp:342] waiting 3600 seconds before retrying VDR and plugin are the standard versions in Ubuntu 12.04 LTS: ii vdr1.7.22-1 ii vdr-plugin-fritzbox1.4.1-4 didn't have an opportunity to check out later versions yet. Should that be fixed by now? THX! -- Do not overtax your powers. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xinelib / vdpau suddenly fails to detect Nvidia ION GPU
On Sun, Jan 05, 2014 at 12:01:50PM +0100, André Weidemann wrote: On 03.01.2014 22:01, Harald Milz wrote: On Wed, Jan 01, 2014 at 11:52:11AM +0100, Patrick Boettcher wrote: Hi, On Thursday 26 December 2013 19:13:05 Harald Milz wrote: Any idea where I should look? Why might xinelib or vdr-sxfe fail to correctly detect the ION (MCP79) chip when everything is unchanged? Yes I ran an apt-get upgrade on the underlying Ubuntu 12.04.3 OS but this didn't change anything, apparently. If this upgrade upgraded the xorg-stuff, most likely some of the xorg- libraries, which are normally overwritten by the NVIDIA-driver (assuming you are using the proprietary driver), have been re-overwritten. Hmmm, it's Ubuntu 12.04: ii nvidia-current 295.40-0ubuntu1.2 NVIDIA binary Xorg driver, kernel module and VDPAU library so it's supposed to provide the correct files. What's the output of: debsums -a nvidia-current ? 132 lines of OK. Ah OK, as of today, Ubuntu upgraded to nvidia-304, testing now ... -- Expect the worst, it's the least you can do. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xinelib / vdpau suddenly fails to detect Nvidia ION GPU
On Wed, Jan 01, 2014 at 11:52:11AM +0100, Patrick Boettcher wrote: Hi, On Thursday 26 December 2013 19:13:05 Harald Milz wrote: Any idea where I should look? Why might xinelib or vdr-sxfe fail to correctly detect the ION (MCP79) chip when everything is unchanged? Yes I ran an apt-get upgrade on the underlying Ubuntu 12.04.3 OS but this didn't change anything, apparently. If this upgrade upgraded the xorg-stuff, most likely some of the xorg- libraries, which are normally overwritten by the NVIDIA-driver (assuming you are using the proprietary driver), have been re-overwritten. Hmmm, it's Ubuntu 12.04: ii nvidia-current 295.40-0ubuntu1.2 NVIDIA binary Xorg driver, kernel module and VDPAU library so it's supposed to provide the correct files. -- Your talents will be recognized and suitably rewarded. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xinelib / vdpau suddenly fails to detect Nvidia ION GPU
Hi all, I've been using a Zotac ION board with Nvidia GPU as XINE player for SD and HD for quite a while. The player is vdr-sxfe with --video vdpau. This has worked fine until recently, when the combo started to throw spurious errors like (from the vdr-sxfe log): load_plugins: plugin /usr/lib/xine/plugins/2.0/xineplug_dmx_mngvo_vdpau: Can't create vdp device : unsupported GPU? [5837] [vdr-fe]fe_xine_init: xine_open_video_driver(vdpau) failed Error initializing xine Lately, this happens reproducibly every time I start vdr-sxfe. (I had to switch to xxmc which works fine for SD programs but gives me a bit of stutter for HD channels on the 1.6 GHz single core Atom.) Any idea where I should look? Why might xinelib or vdr-sxfe fail to correctly detect the ION (MCP79) chip when everything is unchanged? Yes I ran an apt-get upgrade on the underlying Ubuntu 12.04.3 OS but this didn't change anything, apparently. TIA! -- You will hear good news from one you thought unfriendly to you. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] probs with new ZDF HDchannels
On Tue, May 01, 2012 at 09:18:33PM +0200, Reinhard Nissl wrote: Hi, Am 01.05.2012 20:08, schrieb Harald Milz: I just added the new ZDF HD channels (ZDF, KIKA, ZDF neo, kultur and info) and I get strange effects like the ones described in http://www.heise.de/newsticker/meldung/Neue-HDTV-Sender-Ruckler-auf-bestimmten-Receivern-1564225.html. It looks as if the color pallette switched every 0.7 s. This didn't happen with the old ZDF HD channel. My setup is unchanged. Other HD channels are not affected. Did anyone else observe this, and what can we do to fix this? You didn't mention your setup in detail, but I assume you're using a xine-lib VDPAU based solution. Yes, it's (still) vdr 1.7.15 and xinelib 1.0.7 I'll give the alter decoder a try next weekend. Maybe I'll be upgrading my setup ;-) -- Ein Optimist ist ein Mensch, der ein Dutzend Austern bestellt, in der Hoffnung, sie mit einer Perle, die er darin findet, bezahlen zu können. -- Theodor Fontane ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] probs with new ZDF HDchannels
Hi guys, I just added the new ZDF HD channels (ZDF, KIKA, ZDF neo, kultur and info) and I get strange effects like the ones described in http://www.heise.de/newsticker/meldung/Neue-HDTV-Sender-Ruckler-auf-bestimmten-Receivern-1564225.html. It looks as if the color pallette switched every 0.7 s. This didn't happen with the old ZDF HD channel. My setup is unchanged. Other HD channels are not affected. Did anyone else observe this, and what can we do to fix this? -- Sitzt einer in der Wüste und läßt Sand durch die Finger gleiten, dabei sagt er immer: Boooaaar. Kommt ein Kameltreiber daher und fragt: Warum sitzt du denn im Sand und sagst immer 'Boooaaar'? Ja, Mensch, Boooaaar, kama hier viel Sand klauen! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Feature suggestion: @include in channels.conf
Hi guys, I'm currently working on integrating my VDR setup with the commercial kartina.tv offering (found no workable reference so I'm doing it myself - will be documented at http://vdr-wiki.de/wiki/index.php/Kartina.tv_mit_IPTV). Because the channel list may be modified by the provider every now and then, and VDR cannot know anything about it, the channels.conf file needs to be rebuilt frequently outside of VDR (and reloaded on the next VDR restart). Since I'd like to see the kartina.tv channels at, say, @201, I have to parse the channels.conf file and insert the kartina.tv channels inbetween. This is cumbersome at best. It would be far easier if channels.conf could include other channels.conf files. Any ideas? I figure with more IPTV offerings on the horizon this is going to become more and more useful. -- Tomorrow will be cancelled due to lack of interest. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Spare Reel eHD card for sale
Hi, I've got a spare Reel eHD card for sale. The retail price was €159. VDR geeks know what this is. I'll ship within Europe (e-mail me for a shipping quote). Make me an offer! Payment possible via EU SWIFT/IBAN bank wire (or standard bank wire if within Germany). Ciao, hm -- Entropy isn't what it used to be. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Q: How to use Multiswitch w/ 2 satellites
On Thu, Jan 15, 2009 at 09:10:17AM +0100, C.Scheeder wrote: replace your single LNB with a dual LNB, and buy 2 disec-c switches. then link them together this way: *--**---* ** | quad LNB || disec-c | || | |- | switch |--| Card 1 | | |- *| 1 | || | |---|* *---* ** *--* || || *--* || *---* ** | dual LNB |---**---| disec-c | || | || switch |--| Card 2 | | || 2 | || *--**---* ** Maybe a twin or quad monoblock is the better solution ... have to try. -- Meader's Law: Whatever happens to you, it will previously have happened to everyone you know, only more so. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Q: How to use Multiswitch w/ 2 satellites
On Thu, Jan 15, 2009 at 10:37:42AM +0200, Theunis Potgieter wrote: On 15/01/2009, C.Scheeder christ...@scheeder.de wrote: this way you can record with both cards both Sat-positions. Great, that should work. Thanks for the hint! So is the quad LNB now acting like dual LNB? a waste of a quad LNB? It's already there. A waste would be to actually replace it. It may need replacing by a quattro or dual, though, because a quad already contains a multiswitch. -- Ambition is a poor excuse for not having sense enough to be lazy. -- Charlie McCarthy ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Q: How to use Multiswitch w/ 2 satellites
Hi, at the moment I use 2 satellites (Astra1 @ 19.2E, Hotbird @ 13.0E) with 3 budget cards and cables (2x Astra from a quad LNB, 1x Hotbird from a single) with the capabilities patch. In the future I may need to cut down the 3 to 2 cards / cables. I know I will need to replace the quad LNB by a quattro, or maybe both LNBs by two duals. The question is, how can I use a 3/2 multiswitch, and how will VDR know where the 13.0E programs are, or the 19.2E, respectively. TIA! -- Real Programmers don't play tennis, or any other sport that requires you to change clothes. Mountain climbing is OK, and real programmers wear their climbing boots to work in case a mountain should suddenly spring up in the middle of the machine room. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] EPG for Hotbird / russian programmes
Hi, 2 years after my last question about russian EPGs I need to ask again. The tvgrabru set on free-x.de is out of date, and there seems to be no other source of information. Has anybody been working on this topic lately? TIA, and have a nice Xmas (in case you dou celebrate it) and a happy new year. On Wed, Nov 29, 2006 at 06:58:57PM +0100, Harald Milz wrote: now that my VDR works fine with 2 satellites thanks to the help of some kind folks here and the SourceCaps patch (did I mention it should be in the mainstream VDR?) I have now a couple of FTA programmes in russian language for my better half :-) The only problem is, none of these programmes carry -- If everybody minded their own business, the world would go around a deal faster. -- The Duchess, Through the Looking Glass ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problems building xine-lib on openSUSE 11.0 w/ gcc 4.3.1
On Wed, Oct 15, 2008 at 04:48:55PM +0100, Darren Salt wrote: I demand that Harald Milz may or may not have written... this seems to be a famous one, possibly a GCC bug according to some fora. I can't build vdr-xine-0.8.2 and the related xine-lib on openSUSE 11.0 with gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) - apparently an asm optimization thing: [snip] dsputil_mmx.c:636: error: can't find a register in class ‘GENERAL_REGS’ while reloading ‘asm’ [snip] Is that a known problem, and does somebody have a patch curing this? Known problem. Use newer xine-lib (if you're using what I think that you're using, it's old and unsupported) and external ffmpeg. That sounds as if the vdr-xine plugin were outdated and should no longer be used on recent distros. If this is so, this should be noted in the vdr-wiki and one should use xineliboutput instead. Is that so? -- Asked by reporters about his upcoming marriage to a forty-two-year-old woman, director Roman Polanski told reporters, `The way I look at it, she's the equivalent of three fourteen-year-olds.' -- David Letterman ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Problems building xine-lib on openSUSE 11.0 w/ gcc 4.3.1
Hi, this seems to be a famous one, possibly a GCC bug according to some fora. I can't build vdr-xine-0.8.2 and the related xine-lib on openSUSE 11.0 with gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) - apparently an asm optimization thing: gcc -DHAVE_CONFIG_H -I. -I../../../../include -I../../../.. -I../../../../include -I../../../../include -I../../../../src -I../../../../src/xine-engine -I../../../../src/xine-engine -I../../../../src/xine-utils -I../../../../src/input -I../../../../src/input -I../../../../lib -I../../../../lib -DHAVE_AV_CONFIG_H -DRUNTIME_CPUDETECT -DXINE_MPEG_ENCODER -D_ISOC9X_SOURCE -DCONFIG_DECODERS -I../../../../src/libffmpeg/libavutil -I../../../../src/libffmpeg -I../../../../src/libffmpeg -fomit-frame-pointer -fno-strict-aliasing -D_REENTRANT -D_FILE_OFFSET_BITS=64 -DXINE_COMPILE -Wformat=2 -Wno-format-zero-length -Wmissing-format-attribute -Werror-implicit-function-declaration -Wstrict-aliasing=2 -mtune=pentiumpro -O3 -pipe -fomit-frame-pointer -falign-functions=4 -falign-loops=4 -falign-jumps=4 -fexpensive-optimizations -fschedule-insns2 -ffast-math -finline-functions -Wall -Wpointer-arith -Wnested-externs -Wcast-align -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -g -O2 -DNDEBUG -Os -MT dsputil_mmx.lo -MD -MP -MF .deps/dsputil_mmx.Tpo -c dsputil_mmx.c -fPIC -DPIC -o .libs/dsputil_mmx.o dsputil_mmx.c: In function ‘gmc_mmx’: dsputil_mmx.c:2486: warning: suggest parentheses around arithmetic in operand of | dsputil_mmx.c:2486: warning: suggest parentheses around arithmetic in operand of | dsputil_mmx.c:2487: warning: suggest parentheses around arithmetic in operand of | dsputil_mmx.c:2487: warning: suggest parentheses around arithmetic in operand of | dsputil_mmx.c:2487: warning: suggest parentheses around arithmetic in operand of | dsputil_mmx.c: At top level: dsputil_mmx.c:2692: warning: no previous prototype for ‘ff_put_cavs_qpel8_mc00_mmx2’ dsputil_mmx.c:2695: warning: no previous prototype for ‘ff_avg_cavs_qpel8_mc00_mmx2’ dsputil_mmx.c:2698: warning: no previous prototype for ‘ff_put_cavs_qpel16_mc00_mmx2’ dsputil_mmx.c:2701: warning: no previous prototype for ‘ff_avg_cavs_qpel16_mc00_mmx2’ h264dsp_mmx.c: In function ‘h264_h_loop_filter_luma_mmx2’: dsputil_mmx.c:636: error: can't find a register in class ‘GENERAL_REGS’ while reloading ‘asm’ dsputil_mmx.c:636: error: ‘asm’ operand has impossible constraints dsputil_mmx.c:636: error: ‘asm’ operand has impossible constraints dsputil_mmx.c:636: error: ‘asm’ operand has impossible constraints dsputil_mmx.c:636: error: ‘asm’ operand has impossible constraints h264dsp_mmx.c:393: error: ‘asm’ operand has impossible constraints dsputil_mmx.c:636: error: ‘asm’ operand has impossible constraints dsputil_mmx.c:636: error: ‘asm’ operand has impossible constraints Is that a known problem, and does somebody have a patch curing this? -- Death to all fanatics! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problems building xine-lib on openSUSE 11.0 w/ gcc 4.3.1
On Wed, Oct 15, 2008 at 05:08:10PM +0200, Ludwig Nussel wrote: Harald Milz wrote: this seems to be a famous one, possibly a GCC bug according to some fora. I can't build vdr-xine-0.8.2 and the related xine-lib on openSUSE 11.0 with [...] gcc -O3 ... -O2 ... -Os Use -O2, that works for sure. See the xine backports (which include vdr-xine Nay, same problem. btw) in the build service: https://build.opensuse.org/project/show?project=multimedia%3Axine Packman also offers xine packages built with the same options. But without netvdr as it seems ... Reinhard, any idea? -- When love is gone, there's always justice. And when justice is gone, there's always force. And when force is gone, there's always Mom. Hi, Mom! -- Laurie Anderson ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problems building xine-lib on openSUSE 11.0 w/ gcc 4.3.1
On Wed, Oct 15, 2008 at 06:50:40PM +0200, Harald Milz wrote: On Wed, Oct 15, 2008 at 05:08:10PM +0200, Ludwig Nussel wrote: Packman also offers xine packages built with the same options. But without netvdr as it seems ... Disregard - it's in. But --enable-vdr-keys is not ... -- When more and more people are thrown out of work, unemployment results. -- Calvin Coolidge ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Which DVB-S Card to buy in Germany
Matthias Fechner [EMAIL PROTECTED] wrote: Lauri Tischler wrote: I think your dish has moved or coaxial is broken. no the second card is working fine and all other cards in the house too. And that the cable breaks when no one touch it is nearly impossible. If I were you I'd definitely re-check the cabling. The F plugs are the worst sh*t the industry ever invented when it comes to safe contacts. Had they only used BNC plugs but no ... Every other while I get VDSBs or machine freezes from bad F plug contacts. Corrosion, earth quakes, I don't know. After fixing it every works fine, usually. it is a Technotrend Rev 1.3. Getting hot ;-) You need only one full featured card per system. All other cards can be budgets. -- Systems have sub-systems and sub-systems have sub-systems and so on ad infinitum -- which is why we're always starting over. -- Epigrams in Programming, ACM SIGPLAN Sept. 1982 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.2 plugin
Reinhard Nissl [EMAIL PROTECTED] wrote: I'm pleased to announce a the maintenance release 0.8.2. You can find it on my homepage as usual: I'm trying to build a small playback-only box using vdr-xine based on a Via Epia-15000 board with the onboard video adapter. I don't try to scale images -- the X server is set to 1024x576 (16:9 PAL). (The TV set has a nice rescaler to blow images up to 1366x768). Whatever I do, the image shows lots of artifacts, especially when there's a lot of movement in a scene, visibly more than softdevice with DirectFB on my old Matrox G450. I'm actually thinking about buying a PCI Matrox card (mind you, I don't even use the BES since I also set the FB to 1024x576 and let the TV set rescale), plug it into the Via board and use softdevice again. I did a lot of reading in various fora, trying to find out what other people do but the image doesn't get significantly better... Any idea? Any information missing? (Just want to get rid of the loud old VDR and replace it by a small quiet network attached one) -- The road to hell is paved with good intentions. And littered with sloppy analysis! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HDTV future for VDR
Igor [EMAIL PROTECTED] wrote: Manu Abraham promised in DVB-linux list http://www.linuxtv.org/pipermail/linux-dvb/2007-August/019784.html that in September in hg repository will be Technotrend S2-3200's support if everything will br OK. It's great news. But which will be next step to HDTV-future for VDR project ? h264 and PAFF support ? And then there's the decryption issue ... At least in DE, only few or even no channels will be FTA. Any info on how the required smartcards will be supported? -- Hofstadter's Law: It always takes longer than you expect, even when you take Hofstadter's Law into account. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] HELP! vdr-1.4.1 and softdevice-0.4.0 aren't working any more
Hi, after having reinstalled my VDR with OpenSUSE 10.1 a couple of weeks ago (after which VDR was working happily for some time) some very strange things happened. At first, after a reboot, sound was gone, without any change in the configuration, only after rebooting. My setup is still as described in http://www.vdr-wiki.de/wiki/index.php/Softdevice-plugin#Matrox_G550_mit_DVI-Ausgang_und_DirectFB (in German, though). In particular, softdevice is invoked as softdevice -ao alsa:pcm=plug:spdif#ac3=plug:spdif# -vo dfb: No sound from VDR. Video was displayed fine. I could play testsounds with aplay just fine. I started to troubleshoot the system to no avail. After one more reboot with no apparent change in the configuration (I checked all settings in setup.conf), VDR started to crash reliably each time vdr starts. The crash happens so quick that no logs are written, except over the network. The relevant last lines are (I changed alsa:pcm=plug:spdif to alsa:pcm=default bit no change): (HW setup: 3 dumb cards, budget, budget-ci and b2c2). Jul 7 17:20:02 linvdr linvdr vdr: [3322] VDR version 1.4.1 started Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading plugin: ./PLUGINS/lib/libvdr-softdevice.so.1.4.1 Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/setup.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] ERROR: unknown config parameter: softdevice.AlsaAC3Device = plug:spdif Jul 7 17:20:02 linvdr linvdr vdr: [3322] ERROR: unknown config parameter: softdevice.AlsaDevice = default Jul 7 17:20:02 linvdr linvdr vdr: [3322] ERROR: unknown config parameter: softdevice.Postprocess Method = 0 Jul 7 17:20:02 linvdr linvdr vdr: [3322] ERROR: unknown config parameter: softdevice.Postprocess Quality = 0 Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/sources.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/diseqc.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/channels.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/timers.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/commands.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/reccmds.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/svdrphosts.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/remote.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] loading /etc/vdr/keymacros.conf Jul 7 17:20:02 linvdr linvdr vdr: [3322] reading EPG data from /etc/vdr/epg.data Jul 7 17:20:02 linvdr linvdr vdr: [3323] video directory scanner thread started (pid=3322, tid=3323) Jul 7 17:20:02 linvdr linvdr vdr: [3324] video directory scanner thread started (pid=3322, tid=3324) Jul 7 17:20:03 linvdr linvdr vdr: [3322] probing /dev/dvb/adapter0/frontend0 Jul 7 17:20:03 linvdr linvdr vdr: [3322] probing /dev/dvb/adapter1/frontend0 Jul 7 17:20:03 linvdr linvdr vdr: [3327] tuner on device 1 thread started (pid=3322, tid=3327) Jul 7 17:20:03 linvdr linvdr vdr: [3328] section handler thread started (pid=3322, tid=3328) Jul 7 17:20:03 linvdr linvdr vdr: [3322] probing /dev/dvb/adapter2/frontend0 Jul 7 17:20:03 linvdr linvdr vdr: [3330] tuner on device 2 thread started (pid=3322, tid=3330) Jul 7 17:20:03 linvdr linvdr vdr: [3331] section handler thread started (pid=3322, tid=3331) Jul 7 17:20:03 linvdr linvdr vdr: [3322] found 3 video devices Jul 7 17:20:03 linvdr linvdr vdr: [3322] initializing plugin: softdevice (0.4.0): A software emulated MPEG2 device Jul 7 17:20:03 linvdr linvdr vdr: [] tuner on device 3 thread started (pid=3322, tid=) Jul 7 17:20:03 linvdr linvdr vdr: [3334] section handler thread started (pid=3322, tid=3334) Jul 7 17:20:03 linvdr linvdr vdr: [3322] [dfb] init Jul 7 17:20:04 linvdr linvdr lircd-0.7.2[2067]: accepted new client on /dev/lircd Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] Supported video Modes are: Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] Enumerating display Layers Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] Configuring CooperativeLevel for OSD Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] (osdLayer): flags, options, pixelformat: 000f, 00418c04 Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] (osdLayer): width, height: 1280 720 Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] osdLayer without !! alpha channel Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] surface capabilities for (scrSurface): videoonly, double-buffered, flippi ng, PixelFormat = 0x00418c04 Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] width = 1280, height = 720 Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] got fmt = 0x00418c04 bpp = 32 Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] Using this layer for OSD: (FBDev Primary Layer - [1280x720]) Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] surface capabilities for (osdSurface): videoonly, double-buffered, flippi ng, PixelFormat = 0x00418c04 Jul 7 17:20:04 linvdr linvdr vdr: [3322] [dfb] Configuring CooperativeLevel for Overlay Jul 7
Re: [vdr] Q: no sound with dvd-plugin and softdevice
Hi,
does nobody have an idea concerning this one? The question appears to be
how do I use softdevice-audio with dvd-plugin.
Harald Milz [EMAIL PROTECTED] wrote:
Hi,
I would like to use the dvd plugin (CVS as of today) together with
softdevice-0.4.0. Plays DVDs fine but no sound. In the plugin's source code
there's in player-dvd.c:
BitStreamOutActive = false;
HasBitStreamOut = (cPluginManager::GetPlugin(bitstreamout) != NULL);
SoftDeviceOutActive = false;
HasSoftDeviceOut= (cPluginManager::GetPlugin(xine) != NULL);
Shouldn't the plugin also check for softdevice? player-dvd.h says
static bool SoftDeviceOutActive; // currently used to switch for xine
static bool HasSoftDeviceOut;// currently used to switch for xine
Hmmm -
However - this patch
--- player-dvd.c.ORIG 2006-04-09 20:35:53.0 +0200
+++ player-dvd.c2007-05-11 18:50:22.871312099 +0200
@@ -577,7 +577,8 @@
HasBitStreamOut = (cPluginManager::GetPlugin(bitstreamout) !=
NULL);
SoftDeviceOutActive = false;
-HasSoftDeviceOut = (cPluginManager::GetPlugin(xine) != NULL);
+HasSoftDeviceOut = (cPluginManager::GetPlugin(xine) != NULL) ||
+ (cPluginManager::GetPlugin(softdevice) != NULL);
cSetupLine *slBitStreamOutActive = NULL;
if(HasBitStreamOut) {
leads to
May 11 18:52:00 linvdr vdr: [3894] dvd-plugin: SoftDeviceOutActive=1,
HasSoftDeviceOut=1
but still no sound, but a whole lot of
May 11 18:52:20 linvdr vdr: [3894] ERROR: dvd-plugin iframeassembler full
524772
May 11 18:52:20 linvdr vdr: [3982] [softdevice-audio] samplerate: 22050Hz,
channels: #2
May 11 18:52:20 linvdr vdr: [3982] [softdevice-audio] Device 'spdif-48',
Samplerate 22050 Channels 2
May 11 18:52:20 linvdr vdr: [3982] [softdevice-audio] Period size 1152 Buffer
size 6915
May 11 18:52:20 linvdr vdr: [3982] [softdevice-audio] Hardware initialized
May 11 18:52:20 linvdr vdr: [3982] [softdevice-audio] samplerate: 48000Hz,
channels: #2
May 11 18:52:20 linvdr vdr: [3982] [softdevice-audio] Device 'spdif-48',
Samplerate 48000 Channels 2
May 11 18:52:20 linvdr vdr: [3982] [softdevice-audio] Period size 1152 Buffer
size 9216
May 11 18:52:20 linvdr vdr: [3982] [softdevice-audio] Hardware initialized
spdif-48 is a plug that resamples everything to 48 kHz:
pcm.spdif-48 {
type plug
slave.pcm spdif
slave.rate 48000
}
Seems softdevice-audio doesn't get any useful data from dvd:
[mp2 @ 0xb79e7148]header missing skiping one byte
and
libdvdnav: Using dvdnav version 0.1.10 from http://dvd.sf.net
libdvdnav: DVD Title: VDRCONVERT_11-05-2007
libdvdnav: DVD Serial Number: 464496BE
libdvdnav: DVD Title (Alternative):
libdvdnav: Unable to find map file '//.dvdnav/VDRCONVERT_11-05-2007.map'
libdvdnav: DVD disk reports itself with Region mask 0x. Regions: 1
2 3 4 5 6 7 8
libdvdnav: Language 'de' not found, using 'en' instead
libdvdnav: Menu Languages available: en
libdvdnav: Language 'de' not found, using 'en' instead
libdvdnav: Menu Languages available: en
libdvdnav: Language 'de' not found, using 'en' instead
libdvdnav: Menu Languages available: en
libdvdnav: Language 'de' not found, using 'en' instead
libdvdnav: Menu Languages available: en
libdvdnav: Language 'de' not found, using 'en' instead
libdvdnav: Menu Languages available: en
libdvdnav: Language 'de' not found, using 'en' instead
libdvdnav: Menu Languages available: en
[mpegdecoder] Error! Codec 86020 not supported by libavcodec
[mpegdecoder] Error! Codec 86020 not supported by libavcodec
The DVD was created using vdrconvert-CVS and plays fine on my standalone
DVD player, so no region code and the generic name. Is that vdrconvert's
error?
???
--
Blood is thicker than water, and much tastier.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
--
Software, n.:
Formal evening attire for female computer analysts.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDSB with m920x-2bfda2098748 and TT-Budget/WinTV-NOVA-CI PCI
Hi, I was trying to get my MSI Digivox Mini SL to run with m920x-2bfda2098748. Basically, the USB stick works fine but my TT-Budget/WinTV-NOVA-CI PCI seems to refuse work with the budget_ci driver contained therein. The setup is: frontend 1 Fujitsu Siemens Activy Budget-S PCI (Astra) frontend 2 TT-Budget/WinTV-NOVA-CI PCI (Astra; no CI attached) frontend 3 Sky2PC/SkyStar 2 DVB-S (Hotbird) frontend 4 MSI Digivox Mini SL DVB-T(DE-Munich, just to play with) Sourcecaps patch etc. work fine. Softdevice-0.4.0 used as the MPEG decoder. Whenever a recording starts, VDR crashes after some seconds: Apr 23 00:36:39 linvdr vdr: [7983] record /video/Die_Killerhand/2007-04-23.00.35.50.99.rec Apr 23 00:36:39 linvdr vdr: [7983] creating directory /video/Die_Killerhand Apr 23 00:36:45 linvdr vdr: [7983] creating directory /video/Die_Killerhand/2007-04-23.00.35.50.99.rec Apr 23 00:36:45 linvdr vdr: [7983] recording to '/video/Die_Killerhand/2007-04-23.00.35.50.99.rec/001.vdr' Apr 23 00:36:45 linvdr vdr: [7983] max. latency time 7 seconds Apr 23 00:36:45 linvdr vdr: [16815] file writer thread started (pid=7983, tid=16815) Apr 23 00:36:45 linvdr vdr: [16816] recording thread started (pid=7983, tid=16816) Apr 23 00:36:45 linvdr vdr: [16817] receiver on device 2 thread started (pid=7983, tid=16817) Apr 23 00:36:45 linvdr vdr: [16818] TS buffer on device 2 thread started (pid=7983, tid=16818) Apr 23 00:36:48 linvdr vdr: [7990] frontend 1 timed out while tuning to channel 9, tp 212480 Apr 23 00:37:09 linvdr vdr: [15727] [VideoOut] sync info: repF = 52493, drpF = 0, totF = 52500 Apr 23 00:37:16 linvdr vdr: [16815] ERROR: video data stream broken Apr 23 00:37:16 linvdr vdr: [16815] initiating emergency exit Apr 23 00:37:16 linvdr vdr: [7983] emergency exit requested - shutting down And then VDR restarts, the recording restarts, VDR crashes, restarts, etc. This does not happen with the DVB drivers supplied with OpenSUSE 10.1 (which doesn't support the DVB-T stick ...) Any help is welcome. It would also be nice if make insmod did not load *all* of the DVB drivers, just the ones that are actually needed. It's also interesting to see that even if a recording starts for a channel that is on the same bouquet as the one tuned in on receiver 1, the second receiver is used for the recording. Is that by chance or on purpose? -- Write-Protect Tab, n.: A small sticker created to cover the unsightly notch carelessly left by disk manufacturers. The use of the tab creates an error message once in a while, but its aesthetic value far outweighs the momentary inconvenience. -- Robb Russon ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDRAdmin-AM with UTF-8 support?
Hi, is anyone working on a UTF-8 version of VDRadmin-AM? I'm using vdr with the UTF8 patch (de and ru) and need to always select UTF8 manually in the browser to avoid seeing the à stuff. Looking at the html files in template/default/, I see everything is hardcoded in iso-8859-1, but that should be a configuration option. Setting LANG=de_DE.utf8 doesn't help, it is silently ignored. Anyone? THX. -- No, `Eureka' is Greek for `This bath is too hot.' -- Dr. Who ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Utf8-patch experiences, anyone?
Petri Helin [EMAIL PROTECTED] wrote: Now there are some problems that have come up with the HD OSD. Font rendering and the way fonts and OSD are used by plugins are the main distractions. I bumped in to this Utf8-patch (http://www.vdr-wiki.de/wiki/index.php/Utf8-patch) which looks Has somebody got a pointer to where the actual patch is located, especially v0.1.2 (I'm running vdr-1.4.1)? The link to the homepage at free-x.de seems to be gone, and http://www.free-x.de/vdr/ contains a lot of stuff except this patch (Oleg?). I'd like to give it a try because I need to support a mixed (Russian - German) environment. Having to set the OSD to rus in order to read the EPGs is really not an option. ;-) Alexander, are you there? Oleg, thanks for the xmltv files! Works just fine! -- Being disintegrated makes me ve-ry an-gry! huff, huff ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] EPG for Hotbird / russian programmes
Hi, now that my VDR works fine with 2 satellites thanks to the help of some kind folks here and the SourceCaps patch (did I mention it should be in the mainstream VDR?) I have now a couple of FTA programmes in russian language for my better half :-) The only problem is, none of these programmes carry any EPG information. The schedules are available on the web sites, mostly. Has somebody written a plugin that retrieves the schedules and creates proper EPG data from them? I might but not too soon... I understand this task can be a pain in pick your favourite body part because people use no SOA interfaces. TBNRussia provides an Excel file (yuck). TIA! -- Reader, suppose you were an idiot. And suppose you were a member of Congress. But I repeat myself. -- Mark Twain ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Hint needed: 3 budget cards and Astra / Hotbird
Hi, I recently added a third budget card to my VDR which contained 2 budgets pointing at Astra so far (using softdevice for decoding): 00:0a.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 00:0f.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 00:0a.0 Class 0480: 1131:7146 (rev 01) 00:0f.0 Class 0480: 1131:7146 (rev 01) /var/log/messages says DVB: registering new adapter (Fujitsu Siemens Activy Budget-S PCI (rev GR/grundig frontend)). DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI). During my first runs I had connected the third LNB to one of the budgets by just moving one sat cable to the new LNB. I could watch all channels from Astra and Hotbird O.K. The SkyStar2 was not connected so far. Now adding the SkyStar2 card: 00:0b.0 Class 0280: 13d0:2103 (rev 01) 00:0b.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card (rev 01) DVB: registering new adapter (FlexCop Digital TV device). This card is connected to a LNB pointing at Hotbird. dvbscan shows all the channels on the respecive cards just fine. I generated the channels.conf listing using dvbscan. But from then on, I could either see the Astra channels or the Hotbird channels within VDR, never both sets at the same time. It appears as if only card #0 is active (the Activy card), no matter which LNB is connected to which budget card. What am I missing? As far as I know there is no way (and no point) in telling VDR to use cards #0 and #1 for Astra and #2 for Hotbird. Is that a known problem between (certain versions of) budget/-ci and b2c2 cards / drivers? Versions: dvb-1.1.0_CVS20051019-17 (OpenSUSE 10.1) in kernel 2.6.16.13-4-default vdr-1.4.1 softdevice-0.3.1 w/ ffmpeg-0.4.9 / DirectFB-0.9.25.1 / DFB++-0.9.25 / linux-fusion-3.2 Any hint is appreciated! -- Every nonzero finite dimensional inner product space has an orthonormal basis. It makes sense, when you don't think about it. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Re: Hint needed: 3 budget cards and Astra / Hotbird
On Mon, Nov 27, 2006 at 07:22:10AM +0100, Harald Milz wrote: 00:0b.0 Class 0280: 13d0:2103 (rev 01) 00:0b.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card (rev 01) DVB: registering new adapter (FlexCop Digital TV device). This card is connected to a LNB pointing at Hotbird. dvbscan shows all the channels on the respecive cards just fine. I generated the channels.conf listing using dvbscan. But from then on, I could either see the Astra channels or the Hotbird channels within VDR, never both sets at the same time. It appears as if only card #0 is active (the Activy card), no matter which LNB is connected to which budget card. I removed the SS2 from the system today, and it seems something went seriously haywire. Only card #0 is usable for receiving data. When I connect an LNB (no matter which one) to card #1 with #0 open, no image is displayed. I can still scan the whole range using dvbscan just fine. With an Astra LNB connected to card #0 and Hotbird to #1, I get messages like Nov 27 21:38:11 linvdr vdr: [3269] frontend 1 timed out while tuning to channel 0, tp 212500 Nov 27 21:40:37 linvdr vdr: [3269] frontend 1 timed out while tuning to channel 1438, tp 110773 Nov 27 21:40:58 linvdr vdr: [3269] frontend 1 timed out while tuning to channel 1439, tp 110832 No matter which LNB I connect to card #0 (FSC Activy), the respective program is displayed just fine. No matter which LNB I connect to cards #1 (WinTV-CI) or #2 (SS2), nothing is displayed, and I get the tuning errors shown above. The SS2 is a rev 2.6C if that helps. Huh??? -- WARNING TO ALL PERSONNEL: Firings will continue until morale improves. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Hint needed: 3 budget cards and Astra / Hotbird
On Mon, Nov 27, 2006 at 05:16:55PM +0200, Antti Hartikainen wrote: What you're missing is soucecaps patch, it tells vdr which card can see which satellite. Wow this works great. It should be in the standard vdr distro! Thanks! Ciao, Harald PS: I missed your answer - sorry for the second inquiry. -- San Francisco, n.: Marcel Proust editing an issue of Penthouse. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.4.1 can't play old recordings???
Harald Milz [EMAIL PROTECTED] wrote: I've been upgrading to 1.4.1 last May, then rebuilt my VDR lately. It seems it can't playback older recordings (pre-1.4.1) any more. The sound is stuttering heavily, and it looks as if audio were entirely out of sync. The ... and way too fast. whole setup is identical to the old one (cause for the rebuild was a dying root disk). Audio is AC3 and PCM over ALSA via softdevice. Any takers? -- Teamwork is essential -- it allows you to blame someone else. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.4 and osdpip anyone?
Ville Skyttä [EMAIL PROTECTED] wrote: On Sat, 2006-10-14 at 14:00 +, Harald Milz wrote: receiver.h:32: error: extra qualification ‘cOsdPipReceiver::’ on member ‘cOsdPipReceiver’ make[1]: *** [osd.o] Fehler 1 http://koti.mbnet.fi/kurg/vdr/vdr-osdpip-0.0.8-extraqual.patch OMG ... OK, I'll put this up on the wiki as well. -- Trying to be happy is like trying to build a machine for which the only specification is that it should run noiselessly. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.4 and osdpip anyone?
Udo Richter [EMAIL PROTECTED] wrote:
osdpip requires a patch since 1.3.31. See wiki:
http://www.vdr-wiki.de/wiki/index.php/Osdpip-plugin#Patches
http://deela.cc.fh-lippe.de/files/vdr-osdpip/
Ooops I saw it bit missed to get it.
But it still cries for help:
receiver.h:32: error: extra qualification ‘cOsdPipReceiver::’ on member
‘cOsdPipReceiver’
make[1]: *** [osd.o] Fehler 1
?
Plus the usual patch for APIVERSION ...
diff -ur osdpip-0.0.8.ORIG/Makefile osdpip-0.0.8/Makefile
--- osdpip-0.0.8.ORIG/Makefile 2005-05-14 18:41:53.0 +0200
+++ osdpip-0.0.8/Makefile 2006-10-14 15:56:55.826701500 +0200
@@ -33,6 +33,11 @@
### The version number of VDR (taken from VDR's config.h):
VDRVERSION = $(shell grep 'define VDRVERSION ' $(VDRDIR)/config.h | awk '{
print $$3 }' | sed -e 's///g')
+APIVERSION = $(shell sed -ne '/define APIVERSION/ { s/^.*\(.*\).*$$/\1/; p
}' $(VDRDIR)/config.h)
+
+ifeq ($(APIVERSION),)
+APIVERSION = $(VDRVERSION)
+endif
### The name of the distribution archive:
@@ -74,7 +79,7 @@
libvdr-$(PLUGIN).so: $(OBJS)
$(CXX) $(CXXFLAGS) -shared -o $@ $^ $(LIBS)
- @cp $@ $(LIBDIR)/[EMAIL PROTECTED](VDRVERSION)
+ @cp $@ $(LIBDIR)/[EMAIL PROTECTED](APIVERSION)
dist: clean
@-rm -rf $(TMPDIR)/$(ARCHIVE)
--
Do you think what we're doing is wrong?
Of course it's wrong! It's illegal!
I've never done anything illegal before.
I thought you said you were an accountant!
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-1.4 and osdpip anyone?
Hi, I'm trying to compile osdpip-0.0.8 in vdr-1.4.1, and I get osd_info.c: In member function ‘eOSState cOsdInfoWindow::ProcessKey(eKeys)’: osd_info.c:233: error: ‘cDevice’ has not been declared osd_info.c:260: error: ‘cDevice’ has not been declared osd_info.c:260: error: invalid type in declaration before ‘(’ token osd_info.c:262: error: jump to case label osd_info.c:260: error: crosses initialization of ‘int SwitchChannel’ osd_info.c:263: error: jump to case label osd_info.c:260: error: crosses initialization of ‘int SwitchChannel’ osd_info.c:264: error: jump to case label osd_info.c:260: error: crosses initialization of ‘int SwitchChannel’ osd_info.c:265: error: jump to case label osd_info.c:260: error: crosses initialization of ‘int SwitchChannel’ osd_info.c:271: error: jump to case label osd_info.c:260: error: crosses initialization of ‘int SwitchChannel’ osd_info.c:290: error: ‘cDevice’ has not been declared osd_info.c:298: error: jump to case label osd_info.c:260: error: crosses initialization of ‘int SwitchChannel’ osd_info.c:312: error: ‘cDevice’ has not been declared osd_info.c:319: error: jump to case label osd_info.c:260: error: crosses initialization of ‘int SwitchChannel’ osd_info.c:260: warning: unused variable ‘SwitchChannel’ Anybody managed to port it to 1.4? 0.0.8 is from May 2005... -- Boys are beyond the range of anybody's sure understanding, at least when they are between the ages of 18 months and 90 years. -- James Thurber ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with Matrox G550 - console on analog head - VDR on DVI - how?
Anthony Hornby [EMAIL PROTECTED] wrote: What I want however is the console to be on the analog output only and VDR to be on the DVI exclusively. At th moment if VDR exits then I get the console output on the analog output. I'd like to know that too and asked this question when I installed a similar system. Back then the answer was, it doesn't work. Did you find anything else in the meantime? Also if anyone has a directfb fb.modes entry for [EMAIL PROTECTED] I'd love a look at that as well :-) No way because the G550 can't do more than 1280x1024 at the DVI port. Analog yes. BTW for 1080p/i you'll need a _real_ fast CPU because the GPU doesn't do a lot of decoding work... -- Cogito cogito ergo cogito sum -- I think that I think, therefore I think that I am. -- Ambrose Bierce, The Devil's Dictionary ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
