vdr December 2017

vdr@linuxtv.org

10 participants
8 discussions

Trouble with DVB-T2 on frontend 1
by Marko Mäkelä 03 Jan '22

03 Jan '22

Hi all, I recently got a USB adapter "Astrometa DVB-T2" that I would like to use with VDR. It comprises two frontends: /dev/dvb/adapter0/frontend0: Realtek RTL2832 (DVB-T) /dev/dvb/adapter0/frontend1: Panasonic MN88473 (DVB-T2 and DVB-C) I guess it is similar to this one; just a slightly different plastic case with some more ventilation holes: http://blog.palosaari.fi/2014/09/naked-hardware-18-astrometa-amdvb-t2-v2.ht… The hardware appears to work fine, once I copied the /lib/firmware/dvb-demod-mn88473-01.fw from somewhere. The firmware upload has failed at least once on the Raspberry Pi 2 (using Linux 4.9.59), but never on another machine that runs a 4.13.0 kernel. I did not yet get the infrared remote control to produce anything in evtest. With dvbv5-zap (after running dvbv5-scan), I can tune into DVB-T2 channels like this: dvbv5-zap -a 0 -f 1 -c dvb_channel.conf 'Yle TV1 HD' -r After this, I can play the video and audio stream on the Raspberry Pi 2: omxplayer /dev/dvb/adapter0/dvr0 Unless I explicitly specify the options -a 0 -f 1, then dvbv5-zap will fail to find any DVB-T2 senders, because it apparently defaults to frontend0, which is DVB-T only. In VDR 2.3.8, I have only been able to view DVB-T from the first frontend. When I did a trick and renamed /dev/dvb/adapter0/frontend1 to frontend0 before starting VDR, VDR no longer complained that the DVB-T2 channels (which I converted from the dvb_channel.conf to channels.conf with dvb-format-convert) not being available, but it did not seem to receive anything from these channels either. Also, after using dvbv5-scan or dvbv5-zap, I sometimes have to invoke w_scan to "reset" the hardware so that VDR can receive DVB-T channels. I would like to receive and record DVB-T and DVB-T2 on this setup. I am willing to try patches or do some programming myself, but I would appreciate some hints to get started. Marko

2 7

VDR ISDB-T support
by Christian Rodriguez 14 Sep '18

14 Sep '18

Hello everyone! I'm from Argentina, and up to last month I've been using VDR 1.7.262 with an ISDB-T USB adapter. It works really good, but the last week I've been trying to upgrade to VDR 2.2 and I've found a problem with ISDB-T cards: they are not supported. As I'm really interested in using VDR, I was digging inside the code and found a partial solution for this problem: as ISDBT is the same as DVBT, I've changed the way delivery system is queried. My changes are applied in a cloned repo at github: https://github.com/chrodriguez/vdr/commit/dadbca57c2dc55c1c53b4fa8f68b56728… That's the only change I've made. Now I can enjoy my fresh upgraded VDR installation!! I think a better refactor should be made, but for now it's working perfectly deployed as a docker container: https://registry.hub.docker.com/u/chrodriguez/vdr Thanks for this wonderfull project! -- Lic. Christian A. Rodriguez @car_unlp

4 7

VDR locking up
by VDR User 29 Dec '17

29 Dec '17

Occasionally my signal drops out (haven't looked into it yet), and it causes VDR to completely freeze and become defunct/zombie. That locks up the drivers and the only way to resolve it is by rebooting. No core file gets created. Does anyone know how to prevent the lock-up in the first place? Could it be some kind of leak from the looping (see log clip below)? Here's a clip of the log when it happens. You can see how the log gets filled with the same repeating lines until it crashes. 2016.Oct.28|12:08:55 video: slow down video, duping frame 2016.Oct.28|12:08:55 video: decoder buffer empty, duping frame (5656/167423) 7 v-buf 2016.Oct.28|12:09:29 video: slow down video, duping frame 2016.Oct.28|12:16:09 [1297] [softhddev]Clear: 2016.Oct.28|12:16:09 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:09 audio/alsa: using device 'default' 2016.Oct.28|12:16:09 audio/alsa: start delay 336ms 2016.Oct.28|12:16:09 [1297] [softhddev]Clear: 2016.Oct.28|12:16:10 audio/alsa: using device 'default' 2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:10 audio/alsa: start delay 336ms 2016.Oct.28|12:16:10 [1297] [softhddev]Clear: 2016.Oct.28|12:16:10 audio/alsa: using device 'default' 2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:10 audio/alsa: start delay 336ms 2016.Oct.28|12:16:10 [1297] [softhddev]Clear: 2016.Oct.28|12:16:10 audio/alsa: using device 'default' 2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:10 audio/alsa: start delay 336ms 2016.Oct.28|12:16:10 [1297] [softhddev]Clear: 2016.Oct.28|12:16:10 audio/alsa: using device 'default' 2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:10 audio/alsa: start delay 336ms 2016.Oct.28|12:16:10 [1297] [softhddev]Clear: 2016.Oct.28|12:16:10 audio/alsa: using device 'default' 2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:10 audio/alsa: start delay 336ms 2016.Oct.28|12:16:10 [1297] [softhddev]Clear: 2016.Oct.28|12:16:10 audio/alsa: using device 'default' 2016.Oct.28|12:16:10 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:11 audio/alsa: start delay 336ms 2016.Oct.28|12:16:11 [1297] [softhddev]Clear: 2016.Oct.28|12:16:11 audio/alsa: using device 'default' 2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:11 audio/alsa: start delay 336ms 2016.Oct.28|12:16:11 [1297] [softhddev]Clear: 2016.Oct.28|12:16:11 audio/alsa: using device 'default' 2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:11 audio/alsa: start delay 336ms 2016.Oct.28|12:16:11 [1297] [softhddev]Clear: 2016.Oct.28|12:16:11 audio/alsa: using device 'default' 2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:11 audio/alsa: start delay 336ms 2016.Oct.28|12:16:11 [1297] [softhddev]Clear: 2016.Oct.28|12:16:11 audio/alsa: using device 'default' 2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:11 audio/alsa: start delay 336ms 2016.Oct.28|12:16:11 [1297] [softhddev]Clear: 2016.Oct.28|12:16:11 audio/alsa: using device 'default' 2016.Oct.28|12:16:11 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:11 audio/alsa: start delay 336ms 2016.Oct.28|12:16:11 [1297] [softhddev]Clear: 2016.Oct.28|12:16:12 audio/alsa: using device 'default' 2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:12 audio/alsa: start delay 336ms 2016.Oct.28|12:16:12 [1297] [softhddev]Clear: 2016.Oct.28|12:16:12 audio/alsa: using device 'default' 2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:12 audio/alsa: start delay 336ms 2016.Oct.28|12:16:12 [1297] [softhddev]Clear: 2016.Oct.28|12:16:12 audio/alsa: using device 'default' 2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:12 audio/alsa: start delay 336ms 2016.Oct.28|12:16:12 [1297] [softhddev]Clear: 2016.Oct.28|12:16:12 audio/alsa: using device 'default' 2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:12 audio/alsa: start delay 336ms 2016.Oct.28|12:16:12 [1297] [softhddev]Clear: 2016.Oct.28|12:16:12 audio/alsa: using device 'default' 2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:12 audio/alsa: start delay 336ms 2016.Oct.28|12:16:12 [1297] [softhddev]Clear: 2016.Oct.28|12:16:12 audio/alsa: using device 'default' 2016.Oct.28|12:16:12 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:13 audio/alsa: start delay 336ms 2016.Oct.28|12:16:13 [1297] [softhddev]Clear: 2016.Oct.28|12:16:13 audio/alsa: using device 'default' 2016.Oct.28|12:16:13 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:13 audio/alsa: start delay 336ms 2016.Oct.28|12:16:13 [1297] [softhddev]Clear: 2016.Oct.28|12:16:13 audio/alsa: using device 'default' 2016.Oct.28|12:16:13 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:13 audio/alsa: start delay 336ms 2016.Oct.28|12:16:13 [1297] [softhddev]Clear: 2016.Oct.28|12:16:13 audio/alsa: using device 'default' 2016.Oct.28|12:16:13 [1297] ERROR: TS packet not accepted in Transfer Mode 2016.Oct.28|12:16:13 audio/alsa: start delay 336ms 2016.Oct.28|12:16:13 [1297] [softhddev]Clear:

4 12

Re: [vdr] xineliboutput '/usr/local/lib/vdr/' n'est pas un répertoire
by g.bruno 28 Dec '17

28 Dec '17

Hallo, I had the same problem some months ago. If I remember right, it was a question of permissions. Did you verify if you have all rights on the directory /usr/local/lib/vdr/ "read, write and execute -rwx-"? Regards GBruno Am 23.12.2017 um 22:53 schrieb Karim Afifi: > Hi ! > > I am trying to upgrade my VDR to 2.3.8, but I have a trouble... > > xine-lib 1.2.8 is installed, but xineliboutput doesn't compil. It seems to be a "simple" directory problem, but I didn't find what's wrong. > > Could you please help me to fix this issue ? > > Thank you. > Regards. > > > ... > -fvisibility=hidden -shared -shared xineliboutput.o device.o frontend.o osd.o config.o menu.o setup_menu.o menuitems.o media_player.o equalizer.o frontend_local.o frontend_svr.o tools/avahi.o tools/cxsocket.o tools/udp_pes_scheduler.o tools/backgroundwriter.o tools/playlist.o tools/http.o tools/vdrdiscovery.o tools/time_pts.o tools.o tools/metainfo_menu.o logdefs.o tools/rle.o black_720x576.o nosignal_720x576.o vdrlogo_720x576.o -lrt -L/lib64 -lcap -ldl -o libvdr-xineliboutput.so.2.3.8 > install libvdr-xineliboutput.so.2.3.8 /usr/local/lib/vdr/ > install: la cible '/usr/local/lib/vdr/' n'est pas un répertoire: Aucun fichier ou dossier de ce type > Makefile:341 : la recette pour la cible « libvdr-xineliboutput.so.2.3.8 » a échouée > make[1]: *** [libvdr-xineliboutput.so.2.3.8] Erreur 1 > > *** failed plugins: xineliboutput > > Makefile:225 : la recette pour la cible « plugins » a échouée > make: *** [plugins] Erreur 1 > > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >

2 1

Race condition when executing recording hook
by Harald Milz 23 Dec '17

23 Dec '17

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/00001.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-0000 '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-0000 '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/00002.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.

5 4

Re: [vdr] Trouble with DVB-T2 on frontend 1
by Karl-Heinz Volk 13 Dec '17

13 Dec '17

I own an Astrometa DVB-T2 stick like this and moving /dev/dvb/adapter0/frontend1 to /dev/dvb/adapter0/frontend0 makes my vdr 2.3.8 (arch linux) running. But I do not succeed scanning for channels here in Bremen in Germany without errors (I have a nice signal with my antenna under the roof). With w_scan version 20170107 I get only six lines: freenet.TV Info;MEDIA BROADCAST:482000:B8D0G16S1T32Y0P1:T:27500:1569=36:1570@15 :0:0:16974:8468:16497:0 ZDF HD;ZDFmobil:586000:B8D0G16S1T32Y0P0:T:27500:2110=36:0;2120,2121:2130;2131:0:2001:8468:16392:0 ZDFinfo HD;ZDFmobil:586000:B8D0G16S1T32Y0P0:T:27500:2210=36:0;2220,2221:2230;2231:0:2002:8468:16392:0 zdf_neo HD;ZDFmobil:586000:B8D0G16S1T32Y0P0:T:27500:2310=36:0;2320,2321:2330;2331:0:2003:8468:16392:0 3sat HD;ZDFmobil:586000:B8D0G16S1T32Y0P0:T:27500:2410=36:0;2420,2421:2430;2431:0:2004:8468:16392:0 KiKA HD;ZDFmobil:586000:B8D0G16S1T32Y0P0:T:27500:2510=36:0;2520,2521:2530;2531:0:2005:8468:16392:0 There is no EPG with this. I have tried to use dvbv5-scan like Marko described but I cannot find initial files for my location. Yours Karl-Heinz 2017-12-03 2:16 GMT+01:00 Jose Alberto Reguero <jareguero(a)telefonica.net>: > I have another card with the same problem, it has frontend0 and > frontend1and I modify vdr to open always demux0 dvr0 and net0 instead of > demux1, dvr1 and net1, and work well with my card. > > Jose Alberto > > Enviado desde mi Huawei > > > -------- Mensaje original -------- > Asunto: Re: [vdr] Trouble with DVB-T2 on frontend 1 > De: Marko M鋕el� > Para: VDR Mailing List > CC: > > > On Wed, Nov 29, 2017 at 11:13:24AM +0100, Klaus Schmidinger wrote: > >>The second startup is for a tweak where I removed > >>/dev/dvb/adapter0/frontend0 and renamed frontend1 to frontend0. On > >>this startup, VDR will not complain anything, but it will not find any > >>signal either. It properly detects the MN88473, but perhaps improperly > >>claims that it provides DVB-T along with DVB-T2 and DVB-C. > > > >Well, from the information that VDR gets from the driver, it does > >support DVB-T, -T2 and -C: > > > > frontend 0/0 provides DVB-T,DVB-T2,DVB-C with > > QPSK,QAM16,QAM32,QAM64,QAM128,QAM256 ("Panasonic MN88473") > > > >If this is not correct, I assume it's a driver problem. > > I made some further experiments today. It turns out that frontend1 > indeed supports both DVB-T and DVB-T2 (and presumably DVB-C). > > Furthermore, with the trick > sudo mv /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/frontend0 > I got VDR to display both DVB-T and DVB-T2 programs. The only difference > from my previous attempts was that this time, I did not rename the old > frontend0 to frontend2. The only frontend device descriptor that existed > in the file system was frontend0. > > The reception is not the best here (especially on windy or rainy days, > in particular with DVB-T2), and it is possible that during my previous > attempts, the DVB-T2 signal was too weak to get the tuner to lock on it > in reasonable time. Also, the USB stick might not have the best analog > signal path or the best tuner. > > So, the good news is that the device indeed works with this little > tweak. It probably is not worth the effort to implement something in > dvbdevice.c that would allow this device to work without tweaking > /dev/dvb/. > > Now I will only have to figure out how to get the remote control to > work. > > Best regards, > > Marko > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > -- Karl-Heinz Volk Pastorenweg 78 B 28237 Bremen

2 1

[ANNOUNCE] VDRfuse
by Teemu Suikki 13 Dec '17

13 Dec '17

VDRfuse -------- Fuse filesystem to "autoedit" VDR recordings! (c) Teemu Suikki 2017 Based on the fuse example "passthrough_fh.c" Latest version: https://github.com/Zuikkis/vdrfuse Using: --------- This filesystem can be used to mount the VDR recordings directory. All other file operations work normally, but every "00001.ts" file is replaced with edited version, according to "marks" file in the same directory! The translation is done "on the fly", reading the original file at correct positions. There are some limitations: - Directory must have "index", "info" and "marks" file. - "info" file must have F line (fps) - "marks" must have correct order. VDR does not require this.. - Recording must be single file, just 00001.ts! If any of these requirements is not met, the file will be served unedited. So it's not "fatal", you just need to watch commercials. :) "marks" is re-read every time file is opened, so you can edit marks in VDR and the change is instant when you re-open the video. VDRfuse works perfectly with Plex Media Server, especially if combined with VDR recordings scanner from my github. Also recommended is Comskip, http://www.kaashoek.com/comskip/ Testing: ---------- If you just want to test it, create an empty directory for mountpoint and: vdrfuse -o modules=subdir,subdir=/srv/vdr/video mntpoint You can use "-f" switch to view some debug output. Then it won't run in the background. The "subdir" parameter is the VDR recording directory. Installation: -------------- You can mount it permanently in /etc/fstab: vdrfuse /srv/vdr/edited fuse allow_other,modules=subdir,subdir=/srv/vdr/video 0 2

1 0

Re: [vdr] Trouble with DVB-T2 on frontend 1
by Jose Alberto Reguero 03 Dec '17

03 Dec '17

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr December 2017