vdr September 2016

vdr@linuxtv.org

8 participants
10 discussions

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

[PATCH] cDevice::GetDeviceForTransponder(): fix a typo
by glenvt18 01 Jan '17

01 Jan '17

d->MaySwitchTransponder(Channel) is always false here Please review, Sergey Chernyavskiy. --- device.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/device.c b/device.c index 18867cd..542d120 100644 --- a/device.c +++ b/device.c @@ -342,7 +342,7 @@ cDevice *cDevice::GetDeviceForTransponder(const cChannel *Channel, int Priority) if (d->ProvidesTransponder(Channel)) { if (d->MaySwitchTransponder(Channel)) Device = d; // this device may switch to the transponder without disturbing any receiver or live view - else if (!d->Occupied() && d->MaySwitchTransponder(Channel)) { // MaySwitchTransponder() implicitly calls Occupied() + else if (!d->Occupied()) { // MaySwitchTransponder() implicitly calls Occupied() if (d->Priority() < Priority && (!Device || d->Priority() < Device->Priority())) Device = d; // use this one only if no other with less impact can be found } -- 1.9.1

2 5

Upnp plugin
by Jose Alberto Reguero 02 Oct '16

02 Oct '16

I am trying to use the upnp plugin, but I can’t find documentation. Do you know the format of the config file directories.conf ? Or how I can add a multimedia directory? Jose Alberto

4 3

Scrambling timeout issue
by glenvt18 26 Sep '16

26 Sep '16

Hi folks, The code in cDevice::Action() (device.c:1588) which checks whether a stream can be descrambled by a particular CAM relies on the hard-coded TS_SCRAMBLING_TIMEOUT value which is 3 seconds. That can be too low not only for dvbapi, but for some 'real' CAMs as well. When a CAM is unable to start descrabmling in 3 seconds, recordings and streamdev don't work, and VNSI plugin has for years been using hacks and workarounds to cope with it. We need a more flexible solution here. It can be a VDR option, which can be set to 0 to disable, or a virtual function cCamSlot::ScramblingTimeout() which can return 0. @Klaus, what is your opinion on that? More info on this issue: https://github.com/FernetMenta/vdr-plugin-vnsiserver/pull/74#issuecomment-2… -- glenvt18

2 2

Skinflatplus plugin Channel Logo Names
by Richard Scobie 17 Sep '16

17 Sep '16

Can anyone who uses the skinflatplus plugin please tell me what the filename format for channel logo icons is? I currently have them named the same as the channel name from channels.conf, but they do not display. Thanks, Richard

2 4

"TS packets to determine frame type"
by Richard F 11 Sep '16

11 Sep '16

Hi Klaus, I'm 99% of the way to finishing my H264 ffmpeg transcoding script, I'm just getting 2 of these warnings when reindexing transcoded files May 30 21:08:09 ha-server vdr: [31785] WARNING: required 5 video TS packets to determine frame type May 30 21:08:09 ha-server vdr: [31785] WARNING: required 5 video TS packets to determine frame type Sometimes the number is 4. Fortunately not over 6 yet. Is this a functional problem ? (files play in everything I need them to). I reduced the I-frame gap which also improves seeking performance, but that's not the issue. Looking at the code I'm not quite sure what it's looking for - can you help? I may be able to adjust codec / muxer to avoid warnings Thanks Richard

4 9

Re: [vdr] VDR 2.3.1 dvbhddevice plugin
by cedric.dewijs＠telfort.nl 09 Sep '16

09 Sep '16

>----Origineel Bericht---- >Van : r.scobie(a)clear.net.nz >Datum : 07/09/2016 08:04 >Aan : vdr(a)linuxtv.org >Onderwerp : [vdr] VDR 2.3.1 dvbhddevice plugin > >Does anyone have a vdr 2.3.1 modified version of the dvbhddevice plugin >(or a patch against 2.2.0), that they can let me have? > >I am not at all a coder, but with the help of the changes in the 2.3.1 >Release notes and looking at another plugin that had been updated to >2.3.1, I made a few changes to the 2.2.0 plugin and got it to compile >and it seems to work fine until I go to delete a recording, at which >point vdr crashes. > >This is vanilla vdr 2.3.1 and only my (probably incomplete) modified >2.2.0 dvbhddevice plugin. > >Thanks, > >Richard > >_______________________________________________ >vdr mailing list >vdr(a)linuxtv.org >https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > Hi Richard, Could you show the changes you made? Maybe we can see from that what you missed :-) Cheers, Cedric

3 7

Help debugging a segfault cause
by VDR User 08 Sep '16

08 Sep '16

Hi, I recently had to update packages on a Debian testing box. Afterwards I recompiled fresh VDR + plugins. Now when I start VDR, it crashes with a segfault. I know the versions of everything are fine as I'm running the same versions on other VDR boxes. Does this look like a linkage problem? Any ideas/help is appreciated! ===== Thread 1 (Thread 0xb71df700 (LWP 25684)): #0 0x00000000 in ?? () #1 0xb771b13e in futex_wake (private=0, processes_to_wake=2147483647, futex_word=0xb64e5604) at ../sysdeps/unix/sysv/linux/futex-internal.h:231 #2 __pthread_once_slow (once_control=0xb64e5604, init_routine=0xb6463ea0) at pthread_once.c:127 #3 0xb6464c95 in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1 #4 0xb642e96b in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1 #5 0xb77bf341 in call_init (l=0x888b5b0, argc=argc@entry=1, argv=argv@entry=0xbfba6da4, env=0xbfba6dac) at dl-init.c:58 #6 0xb77bf4ae in call_init (env=0xbfba6dac, argv=0xbfba6da4, argc=1, l=<optimized out>) at dl-init.c:30 #7 _dl_init (main_map=main_map@entry=0x888a9e0, argc=1, argv=0xbfba6da4, env=0xbfba6dac) at dl-init.c:120 #8 0xb77c3767 in dl_open_worker (a=0xbfba58bc) at dl-open.c:575 #9 0xb77bf224 in _dl_catch_error (objname=objname@entry=0xbfba58b4, errstring=errstring@entry=0xbfba58b8, mallocedp=mallocedp@entry=0xbfba58b3, operate=0xb77c3390 <dl_open_worker>, args=0xbfba58bc) at dl-error.c:187 #10 0xb77c2f22 in _dl_open (file=0x8889168 "/usr/local/dvb/vdr.source/vdr-2.2.0/PLUGINS/lib/libvdr-softhddevice.so.2.2.0", mode=-2147483646, caller_dlopen=0x811d099 <cDll::Load(bool)+41>, nsid=<optimized out>, argc=1, argv=0xbfba6da4, env=0xbfba6dac) at dl-open.c:660 #11 0xb7708bf5 in dlopen_doit (a=0xbfba5a70) at dlopen.c:66 #12 0xb77bf224 in _dl_catch_error (objname=0x8888c84, errstring=0x8888c88, mallocedp=0x8888c80, operate=0xb7708b80 <dlopen_doit>, args=0xbfba5a70) at dl-error.c:187 #13 0xb770930d in _dlerror_run (operate=operate@entry=0xb7708b80 <dlopen_doit>, args=args@entry=0xbfba5a70) at dlerror.c:163 #14 0xb7708c9e in __dlopen (file=0x8889168 "/usr/local/dvb/vdr.source/vdr-2.2.0/PLUGINS/lib/libvdr-softhddevice.so.2.2.0", mode=2) at dlopen.c:87 #15 0x0811d099 in cDll::Load (this=0x8888ef8, Log=<optimized out>) at plugin.c:223 #16 0x0811df01 in cPluginManager::LoadPlugins (this=0xbfba6c50, Log=true) at plugin.c:351 #17 0x080a3820 in main (argc=<optimized out>, argv=<optimized out>) at vdr.c:732 (gdb)

1 0

VDR 2.3.1 dvbhddevice plugin
by Richard Scobie 07 Sep '16

07 Sep '16

Does anyone have a vdr 2.3.1 modified version of the dvbhddevice plugin (or a patch against 2.2.0), that they can let me have? I am not at all a coder, but with the help of the changes in the 2.3.1 Release notes and looking at another plugin that had been updated to 2.3.1, I made a few changes to the 2.2.0 plugin and got it to compile and it seems to work fine until I go to delete a recording, at which point vdr crashes. This is vanilla vdr 2.3.1 and only my (probably incomplete) modified 2.2.0 dvbhddevice plugin. Thanks, Richard

1 0

vdr-convert released
by Richard F 04 Sep '16

04 Sep '16

I'd like to announce the release of vdr-convert at https://projects.vdr-developer.org/projects/vdr-convert One of two people asked me to release it when ready, and after converting / testing most of my 4TB archive with it, I think it's about ready for the VDR community to use. What is it? A shell script with associated tools to transcode the content of VDR1.x and VDR2.x recordings as accurately as possible, including all streams, audio, AD, subtitles, and metadata into more compressed format, while maintaining perceived quality. H264 and AAC are the chosen codecs for the main streams. SD recordings are reduced to anywhere from 35% - 90% of original size depending on content and compression settings. On average, you can expect to save 1/3 of the disk space used for SD recordings. The USP is that this tool may be the only tool capable of converting/compressing old VDR1.x recordings with dvb subtitles into VDR2 compatible .ts files playable on VDR2 and 3rd party players such as Kodi, MPC-HC and VLC. The script also has ongoing use to automatically compress recordings once complete, or for automatic export, optionally by FTP (I use it this way). I created a comprehensive WIKI documenting the various usage scenarios and issues found during test. The files are in the Git repository. For VDR1.x conversion, a couple of tools need compiling from source. Have fun! Richard

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr September 2016