vdr March 2011

vdr@linuxtv.org

40 participants
32 discussions

[1.7.17][Patch] Program guide scroll
by Udo Richter 19 Mar '11

19 Mar '11

Hi list, In reference to [1], and to give this a push-up, I've attached an updated patch for program guide scroll for VDR-1.7.17. The patch also fixes the non-working scrolling in longer descriptions. If anyone needs this fixed for VDR < 1.7.17, let me know. Cheers, Udo [1] http://www.linuxtv.org/pipermail/vdr/2010-June/023122.html

1 0

Re: [vdr] xineliboutput subtitle crop
by jdobry＠centrum.cz 19 Mar '11

19 Mar '11

I can try only DVB subtitles. > From: Petri Hintukainen<phintuka(a)users.sourceforge.net> > Subject: Re: [vdr] xineliboutput subtitle crop > To: VDR Mailing List<vdr(a)linuxtv.org> > Message-ID:<1300468302.18383.4870.camel@ph-laptop> > Content-Type: text/plain; charset="UTF-8" > > pe, 2011-03-18 kello 16:13 +0100, jdobry(a)centrum.cz kirjoitti: > > Looks correct, at least for DVB subtitles. Did you test only with DVB > subtitles or also with teletext subtitles ?

1 0

xineliboutput subtitle crop
by jdobry＠centrum.cz 19 Mar '11

19 Mar '11

Hello, On vdr 1.7.17 I have problem with xineliboutput and subtitles. It's oversized and cropped. Problem is probably incompatibility to change OSD layer size on 1.7.17 Here is my hotfix. I am not sure, if it is correct because I don't know vdr/xineliboutput internals. But it siply works for me. Jiri PS: many thanks for nice piece of SW, specially thanks to Klaus. --- osd.c.old 2011-03-18 15:55:32.681879469 +0100 +++ osd.c 2011-03-18 16:02:54.111874506 +0100 @@ -393,10 +393,13 @@ #if VDRVERSNUM >= 10708 +#if VDRVERSNUM < 10717 if (xc.osd_spu_scaling && (m_Layer == OSD_LEVEL_SUBTITLES || m_Layer == OSD_LEVEL_TTXTSUBS)) { m_ExtentWidth = 720; m_ExtentHeight = 576; - } else { + } else +#endif + { double Aspect; int W, H; m_Device->GetOsdSize(W, H, Aspect);

3 2

Add support for [non-standard?] DiSEqC switch "MAXIMUM DiSEqC 4/1"
by Hans Petter Selasky 14 Mar '11

14 Mar '11

Hi, The local guy over here mounted what he claimed is a fully standard 4/1 DiSEqC switch which works with every sat-receiver around. After some brief investigation, it appears this DiSEqC switch is using a non-standard? scheme, which is not supported by w_scan nor vdr. Correct me if I'm wrong. To get the switch working with VDR I need an option to turn off the switch power. This is part of the sequence to program the switch. I've attached patches for w_scan and VDR to work with the DiSEqC switch I've got. I don't have any documentation on the switch. All the programming was the result of two days of reverse engineering. And I did not open the switch either :-) Manufacturer homepage: http://www.kjaerulff1.com/en-gb/p/30_maximum_diseqc_41_switch Information needed for VDR's diseqc.conf # # Full sequence for LNB-A # LNB.A 11700 V 9750 t F W45 v W15 W45 F W45 v W15 W45 t W45 LNB.A 99999 V 10600 t F W45 v W15 W45 F W45 v W15 W45 T W45 LNB.A 11700 H 9750 t F W45 V W15 W45 F W45 V W15 W45 t W45 LNB.A 99999 H 10600 t F W45 V W15 W45 F W45 V W15 W45 T W45 # # Full sequence for LNB-B # LNB.B 11700 V 9750 t F W45 v W15 [E0 10 26] W45 F W45 v W15 [E0 10 26] W45 t W45 LNB.B 99999 V 10600 t F W45 v W15 [E0 10 26] W45 F W45 v W15 [E0 10 26] W45 T W45 LNB.B 11700 H 9750 t F W45 V W15 [E0 10 26] W45 F W45 V W15 [E0 10 26] W45 t W45 LNB.B 99999 H 10600 t F W45 V W15 [E0 10 26] W45 F W45 V W15 [E0 10 26] W45 T W45 # # Full sequence for LNB-C # LNB.C 11700 V 9750 t F W45 v W15 [E0 10 27] W45 F W45 v W15 [E0 10 27] W45 t W45 LNB.C 99999 V 10600 t F W45 v W15 [E0 10 27] W45 F W45 v W15 [E0 10 27] W45 T W45 LNB.C 11700 H 9750 t F W45 V W15 [E0 10 27] W45 F W45 V W15 [E0 10 27] W45 t W45 LNB.C 99999 H 10600 t F W45 V W15 [E0 10 27] W45 F W45 V W15 [E0 10 27] W45 T W45 # # Full sequence for LNB-D # LNB.D 11700 V 9750 t F W45 v W15 [E0 10 27] W45 F W45 v W15 [E0 10 26] W45 F W45 v W15 [E0 10 27] W45 F W45 v W15 [E0 10 26] W45 t W45 LNB.D 99999 V 10600 t F W45 v W15 [E0 10 27] W45 F W45 v W15 [E0 10 26] W45 F W45 v W15 [E0 10 27] W45 F W45 v W15 [E0 10 26] W45 T W45 LNB.D 11700 H 9750 t F W45 V W15 [E0 10 27] W45 F W45 V W15 [E0 10 26] W45 F W45 V W15 [E0 10 27] W45 F W45 V W15 [E0 10 26] W45 t W45 LNB.D 99999 H 10600 t F W45 V W15 [E0 10 27] W45 F W45 V W15 [E0 10 26] W45 F W45 V W15 [E0 10 27] W45 F W45 V W15 [E0 10 26] W45 T W45 Good luck! I hope the patches can be included into VDR and w_scan. Not sure if this is the right list to post the patches. --HPS

1 0

priorities in streamdev
by Rainer Blickle 13 Mar '11

13 Mar '11

Hi everybody, i have a question regarding the streamdev plugin. I have 2 tv cards, both gets accessed with the pvrinput plugin, but the problem i have would be the same with dvb devices. I also watch TV on the PC with the two cards. I have another pc (laptop) with vdr installed. There i installed the streamdev-client plugin. When switching the channel on the laptop with the up/down keys, the live picture gets interrupted with a black screen for about half a second. My wife doesn't like this very much. I had a look into the source code and found following: - The receiver of the pc has the priority 0, the receiver of the streamdev-server 1. - When switching with the up/down keys, the streamdev-client sends an "PROV"-Message to the streamdev-server. The streamdev-server tries to get a device (Method cServerConnection::GetDevice). The Receiver of the "old" streamdev-channel is still receiving. - The Method cServerConnection::GetDevice calls cDevice::GetDevice. The priority in the function call is 1. In the cDevice::GetDevice method the devices gets iterated, calling on each device the method cDevice::ProvidesChannel. Because the priority property of this call is 1, the "old" receiver of the streamdev-server has also a priority of 1 and the live-receiver has the priority of 0, the only device which can provide the channel is the device of the live-tv. - In the latter of the method cDevice::GetDevice the live-receiver gets detached via "d->DetachAllReceivers". Later in the code of cServerConnection::GetDevice, if the Method cDevice::GetDevice doesn't return a device, the current receiver gets detached. In my infrastructure this doesnt happend because the live receiver will nearly always gets detached ( The only exception is when a timer records). To prevent this, i changed the code in that way that the streamdev-receiver gets detached before calling cDevice::GetDevice). Is the detaching of live-tv an known issue or is this a feature ? Should have the live tv receiver a priority greather than streamdev-receiver ? If so, the live-tv wouldn't get detached ? Regards, Rainer

6 20

How's the 24 bit OSD VDR coming?
by Simon Baxter 09 Mar '11

09 Mar '11

Hi Klaus - et al How's the development on vdr-1.7.17 (?) coming? I wait with baited breath!!

5 6

channels.conf fr-Paris since analog switch-off
by Nicolas Huillard 09 Mar '11

09 Mar '11

Hi all, For some reason (API/kernel mismatch or so), I can't manage to run a working DVB scan with either scan, dvbscan or w_scan, and VDR itself don't seem to catch the new transponders, whatever I do... Since this is a family urgency, I can't wait to upgrade everything needed in my VDR server (which does a lot of other things, making an emergency upgrade a bit risky) before having all channels back. What I miss is apparently only multiplex R4 (Multi4, M6, W9, NT1, etc.). I can't find anywhere on the net what frequency it now uses in Paris (Tour Eiffel). Can someone in the area share his/her channel.conf, please ? For those who wonder: last Tuesday, they switched off analog TV in many locations in France, rearranging some transponders in the process. Most channels were correctly updated (or not actually changed) by my VDR instance, but some must have changed frequencies and are thus missing. TIA, -- NH

1 1

Messages from Lirc have to be longer than 21 chars, why?
by Gerald Dachs 08 Mar '11

08 Mar '11

Hi, during my tests with eventlircd I noticed that the up key of my remote didn't work with vdr, but with xbmc. I debugged vdr and stumbled above the line lirc.c:89 (not vanilla sources): if (ready && ret > 21) { Lirc sends this to vdr: "67 0 KEY_UP devinput" So this key gets ignored, all other key have longer names and are working. Solution seems to be easy. Instead of 21 I could use 19, but with inputlircd I get this string for the same key: "67 0 KEY_UP event7" It would get ignored again. What is the intention for this condition: ret > 21? Is it to make sure to not get garbage from lirc? But why 21 chars? What would be a better length, or a better check? Gerald

4 4

[announcement] Release 0.2.0 of vdr-plugin-dvdswitch
by Andreas Brachold 05 Mar '11

05 Mar '11

Hello, A new release of vdr-plugin-dvdswitch http://projects.vdr-developer.org/attachments/download/534/vdr-dvdswitch-0.… Changes: http://projects.vdr-developer.org/versions/show/169 * Read name of volume to prefill OSD-Entry with filename Fill OSD-field with capitalize volume name * Improve menu to read images * Rename image was'nt possible * used posix functions to parse commandline, create symbolic links, parse mountpoint * Improve handle of error messages * Update translations Add italian translation (Support #490) * refactoring MenuSetup Allow localized character at title of image menu * remove some unused code, typecast ... What's it --------- The dvdswitch plugin functions as a kind of a DVD changer. This plugin make it possible to select images and play them with the DVD plugin. But it's need too dvd-plugin See included file README for more details. http://projects.vdr-developer.org/projects/plg-dvdswitch/wiki Please report any bugs, ideas or feature requests to the project site If you want to contribute patches, new features or whatever, post an issue or patch to the projects issue tracker or request to join the project. I would happily add everyone as a project member, who would like to contribute to vdr-plugin-dvdswitch . Enjoy, Andreas

1 0

Two problems with vdr 1.7.16-1devel2
by Tony Houghton 01 Mar '11

01 Mar '11

I'm currently experiencing two problems with vdr 1.7.16-1devel2. The first problem is that if I fast forward or rewind, when I return to normal playback the stream resumes from wherever I started the ff/rew instead of where I stopped it. That's with vdr-sxfe on remote clients, I'm not sure whether it does the same if the client is on the same PC as vdr. The second problem is a memory leak. It's not too bad, but I have to restart VDR about twice a week to make sure there's no swapping and plenty of memory free for caching on a 2GB x86_64 system. As well as xineliboutput I'm also using the eepg and remote plugins. All from Tobias Grimm's debian repository. Are these known problems, perhaps fixed in a later release of "upstream" VDR?

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr March 2011