vdr October 2016

vdr@linuxtv.org

6 participants
8 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

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

[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

Large amount of logging with vdr on Fedora 24
by Richard Scobie 18 Oct '16

18 Oct '16

I have just updated the OS of my TT s2-6400 based vdr box from Fedora 16 to Fedora 24 Server and all is working fine except the log (both journald and rsyslog) fill up rapidly with the following type of entry. [ 1983.410546] demux_worker (0): dma buffer = 0 [ 1983.427146] demux_worker (0): dma buffer = 1 [ 1983.444525] demux_worker (0): dma buffer = 2 [ 1983.461113] demux_worker (0): dma buffer = 3 [ 1983.477710] demux_worker (0): dma buffer = 4 [ 1983.494305] demux_worker (0): dma buffer = 5 [ 1983.509629] stv090x_read_status: Status: Unlocked (Searching ..) [ 1983.511662] demux_worker (0): dma buffer = 6 [ 1983.528265] demux_worker (0): dma buffer = 7 [ 1983.544857] demux_worker (0): dma buffer = 0 [ 1983.562229] demux_worker (0): dma buffer = 1 [ 1983.578835] demux_worker (0): dma buffer = 2 I am using a custom kernel with a fork of the DVB drivers, as opposed to the stock versions of both on the Fedora 16 install, so am just wondering if anyone is running a standard late Fedora install and seeing this behaviour? Thanks, Richard

1 0

Re: [vdr] Upnp plugin
by Jose Alberto Reguero 04 Oct '16

04 Oct '16

Thanks, I give it a try. Jose Alberto. El 02/10/2016 14:52, Richard F <lists(a)keynet-technology.com> escribió: > > Have you looked at Minidlna? > I've been using it for a while now to provide upnp access to various media. It's lightweight and doesn't slow the server down noticeably, once it's scanned the directories. I normally access the VDR directory via SMB, but I added it to the minidlna config to test, and it worked OK. > > HTH Richard > > ----- On 28 Sep, 2016, at 14:26, Jose Alberto Reguero jareguero(a)telefonica.net wrote: > > > 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 > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

1 0

Re: [vdr] Upnp plugin
by Jose Alberto Reguero 04 Oct '16

04 Oct '16

El 01/10/2016 22:59, Lucian Muresan <lucianm(a)users.sourceforge.net> escribió: > > On 29.09.2016 14:59, Peer Oliver Schmidt wrote: > > Isn't the UPnP plugin solely for the purpose to use UPnP renderes with > > VDR recordings and stuff, and not outside media files?! > > The UPnP Plugin also has a "sub-plugin" for other media files, but I > never got that one working, maybe it isn't even finished. Accessing live > TV and recordings used to work, but I do not use it anymore due to > insanely heavy load it puts on my VDR machine... > > Greetings, > Lucian Thanks, for me it work with live tv, but don't work with the recordings. Jose Alberto.

1 0

Supertennis HD on 13°E, is it gone?
by Lucian Muresan 03 Oct '16

03 Oct '16

Hello folks, I thought I'd try to ask here, is it only me having problems to receive the italian FTA channel Supertennis HD from Hotbird 13°E, or did they just ceased broadcasting over sattelite lately? According to the Lyngsat list they should still be there: http://www.lyngsat.com/tvchannels/it/Super-Tennis.html They also seem to broadcast a SD variant on 12,5°W, for which I would have to redo the entire setup of my multifeed antenna, but first I would like to know if it's really worth trying that. Anybody knows something on what happened to them? Best regards, Lucian

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr October 2016