vdr December 2011

vdr@linuxtv.org

42 participants
38 discussions

shouldn't a vdr recording pause during status 3 flag?
by Lou 14 Jan '12

14 Jan '12

I noticed one of my local broadcasters does actually flag a commercial break's starts and endings: Nov 3 16:48:37 channel 17 (TSR1) event Thu 03.11.2011 16:45-17:26 (VPS: 03.11 16:45) 'Hawaii Five-0' status 4 Nov 3 17:13:38 channel 17 (TSR1) event Thu 03.11.2011 16:45-17:26 (VPS: 03.11 16:45) 'Hawaii Five-0' status 3 Nov 3 17:16:08 channel 17 (TSR1) event Thu 03.11.2011 16:45-17:26 (VPS: 03.11 16:45) 'Hawaii Five-0' status 4 Nov 3 17:32:20 channel 17 (TSR1) event Thu 03.11.2011 17:26-17:35 '(null)' status 4 Nov 3 17:32:20 timer 8 (17 1645-1726 VPS 'Hawaii Five-0~Po'ipu') stop This looks legit to me, start and endings are always trimmed fine - so the question remains, why the recording does not pause during the commercial break? I'd love to avoid manual editing if possible.

7 12

Patch: Eliminate duplicate events when using xmltv2vdr
by Timo Eskola 12 Jan '12

12 Jan '12

Hi, I started to use xmltv2vdr for some channels with poor EPG data. I do not want to use xmltv2vdr for all channels so I modified xmltv2vdr.pl script to clear only the channels which will be grabbed with xmltv. The result was multiple EPG events for some programs. I found 2 issues in VDR code that caused this. 1. CLRE for a channel does not always clear all events. I compared CLRE for clearing all channels and noticed that it also clears events in timers. The patch will add this to CLRE for a channel. 2. Second problem was that for some reason there are small differences in events times in EPG and xmltv. The patch find events close to the current event during EPG scan. Now I have proper program data from EPG and xmltv. http://www.tolleri.net/vdr/vdr/vdr-1.7.21-clre-epgscan.patch Maybe Klaus can have a look if the changes can be implemented in VDR. Regards, Timo

2 1

[PATCH] GOTOXX patch for vdr-1.7.22
by Ales Jurik 11 Jan '12

11 Jan '12

Hi all, here is patch for using motor with vdr-1.7.22. As the diseqc subsystem changed quite a lot in 1.7.22 please report any problem. I'm using/testing it together with vtuner devices (NessieDVB) and cascade of diseqc switches: 1. DVB device: vtuner(PC) <-> LAN <-> NessieDVB <-> motor <-> uncomm.switch <-> comm. switch) 2. DVB device: vtuner(PC) <-> LAN <-> NessieDVB <-> uncomm.switch <-> comm. switch) I'm using it together with VDR capability of dedicated and undedicated sources to some cards and it works for me without problems. I do not have possibility to test it together with real DVB cards inside PC, so any remarks are welcomed. My diseqc.conf looks like: # ONLY SWITCHES 1 2: S19.2E 11700 V 9750 t v W30 [E0 10 39 F0] W30 [E0 10 38 F0] W30 t S19.2E 99999 V 10600 t v W30 [E0 10 39 F0] W30 [E0 10 38 F1] W30 T S19.2E 11700 H 9750 t V W30 [E0 10 39 F0] W30 [E0 10 38 F2] W30 t S19.2E 99999 H 10600 t V W30 [E0 10 39 F0] W30 [E0 10 38 F3] W30 T S13.0E 11700 V 9750 t v W30 [E0 10 39 F0] W30 [E0 10 38 F4] W30 t S13.0E 99999 V 10600 t v W30 [E0 10 39 F0] W30 [E0 10 38 F5] W30 T S13.0E 11700 H 9750 t V W30 [E0 10 39 F0] W30 [E0 10 38 F6] W30 t S13.0E 99999 H 10600 t V W30 [E0 10 39 F0] W30 [E0 10 38 F7] W30 T .... # MOTOR + SWITCHES 1: S1.0W 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t S1.0W 99999 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T S1.0W 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t S1.0W 99999 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T S9.0E 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t S9.0E 99999 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T S9.0E 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t S9.0E 99999 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T .... Enjoy, Ales

1 1

[PATCH v2] multi-frontend-support for vdr 1.7.21
by L. Hanisch 08 Jan '12

08 Jan '12

Hi, Here's version 2 of my multi-frontend-patch. It's still "dirty", since it changes the constructor of cDvbDevice which will break compilation of some plugins. But I think it might be necessary to look at the relevant plugins since they might need to react on frontend changes. I haven't tested any of those plugins but will have a look at some that I'm using. Maybe there have to be some virtual functions like "BeforeFrontendSwitch" and "AfterFrontendSwitch" so the plugins are even able to know about it. Assumption for this patch: All frontends within one adapter have to be used mutually exclusive. All cards I know behave in this way. If there are cards with multiple frontends which can be used simultaneously I'd like to hear about it. Whenever the dvb-api-changes are upstream (the ENUM_DELSYS thingy) I think my patch can easily be converted to use that. I'm still working on this patch, it's not finished yet... :-) Have fun, Lars.

7 8

Rotor / Rotor-NG not working with latest VDR
by Morfsta 03 Jan '12

03 Jan '12

Hi, I have just upgraded my VDR system to yavdr 0.4.0 which uses VDR 1.7.21 and I notice that the Rotor plugin and my own Rotor-ng plugin no longer drive the rotor using any of the functions in the menu. Is anyone else seeing this too? I think that this could be because of recent changes to disecq handling code within VDR as part of the Unicable update. Klaus could you point me in the direction of what might have changed such that these plugins no longer work and I will do my best to implement a fix. Thanks very much for your help, Regards, Morfsta

5 11

sxfe and vsync
by Tony Houghton 26 Dec '11

26 Dec '11

When using NVidia graphics cards and the proprietary driver I find vdr-sxfe looks quite smooth even with a monitor that only supports 60Hz. I think it's been syncing to the vertical blank "automagically". But with other graphics cards I get a lot of tearing which is marring my viewing pleasure. This is happening both with Intel Sandy Bridge (normal monitor) and a Radeon 5450 with fglrx connected to a TV. The free ati driver isn't a practical option on that because the HDMI audio doesn't work with it. I'm using the xv output in each case. Is there a way to make vdr-sxfe sync to the vertical blank with these cards/drivers?

5 7

Re: [vdr] [PATCH] vdr-1.7.21 & DVB-T2 support
by Rolf Ahrenberg 22 Dec '11

22 Dec '11

On Thu, 22 Dec 2011, Stuart Morris wrote: > I'm running 1.7.21 with a DVB-T and DVB-T2. The only patch I have is for > decoding the compressed EPG for UK Freeview HD. Does DVB-T2 need special handling in VDR? That's not been my experience. > I suspect it depends on the tuner driver. I'm using a PCTV nanoStick 290e. Well, your T2 channels are most propably using PLP id 0 and your driver is defaulting to that one, so your working setup is pure luck until the broadcasting systems are getting more complex :) Also without the patch there's no mechanism to prevent your DVB-T cards tuning to DVB-T2 channels. BR, -- rofa

2 1

[PATCH] vdr-1.7.21 & DVB-T2 support
by Rolf Ahrenberg 22 Dec '11

22 Dec '11

Hi, here's my attempt to provide a native DVB-T2 support for VDR. - added initial libsi support for the required T2 delivery system descriptor - updated bandwidth, modulation, transmission, guard settings to match DVB-T2 specs - added a new PLP id to channel parameters and tuning mechanism - requires DVB API 5.3 - implementation is analog to the current DVB-S/S2 extending the existing delivery system field - shortcomings: PLP id can be found also in DVB-T channel configuration (but doesn't affect anything) and the new channels.conf values could be a bit more intuitive It seems to work here in Finland with my limited access to local DVB-T2 muxes, but no guarantees. :) BR, -- rofa

2 1

Re: [vdr] Rotor / Rotor-NG not working with latest VDR
by Jan. Med. 22 Dec '11

22 Dec '11

Hi, > That may be. Have you installed the latest updates? ># sudo apt-get update ># sudo apt-get dist-upgrade >There should at least be an update for vdr-plugin-dynamite. Sorry, I don't use yavdr. Rotorng works fine for me with the last 1.7.22 and the previous versions. The version 22 is patched only with rotor patch. The 21 with rotor+lnbsharing patches Regards, Jan

1 0

Re: [vdr] [PATCH] vdr-1.7.21 & DVB-T2 support
by Rolf Ahrenberg 22 Dec '11

22 Dec '11

No comments? Am I really the only one running such a DVB-T + DVB-T2 system? Anyway, this has worked quite nicely for a rather long time on my setup, and therefore I strongly suggest the integration of the patch into the official VDR tree before the next stable release. BR, -- rofa

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr December 2011