vdr March 2007

vdr@linuxtv.org

83 participants
70 discussions

[ANNOUNCE] vdr-filebrowser-0.0.6b
by Holger Brunn 19 Mar '07

19 Mar '07

Hello list, I'm glad to announce a new version of the filebrowser plugin, you can get it from http://www.stud.uni-karlsruhe.de/~uqg8/vdr/filebrowser/vdr-filebrowser-0.0.… This version fixes a really stupid mistake that might freeze your vdr after executing commands in the background, so feel encouraged to upgrade. Changelog: - Now allowing comments and empty lines in config files (thanks to Tobias Grimm for providing a patch) - Fixed possible lockup while doing housekeeping (thanks to Christian Jacobsen) - Fixed crash on malformed entries in config files - Fixed crash on huge output strings - now the buffer is emptied if its size exeeds 1MB, more renders vdr unresponsive (pointed out by Ronny Kornexl) Your comments, bug reports and patches would be appreciated, regards Holger

1 0

Mailing List Etiquette
by Clemens Kirchgatterer 19 Mar '07

19 Mar '07

This is the 'official' and updated vdr-mailing-list-etiquette-reminder. Please take this as a serious advice. Take the time to read it, especially if you are new to mailinglists in general. E-mail formatting ================= Mailing list email should fit the following criteria: DO == * Trim quoted material to the minimum needed to clarify what you're talking about. * Add a blank line _before_ and _after_ each quote for better readability. * Make sure you are attributing material to the correct person (i.e. make sure the "On 19/07/2002, Joe Bloggs said:" is correct) * Write your responses _after_ the quoted text, not before. If your mail client makes it difficult to do this, get a new one. * Make sure lines are wrapped at maximum 76 characters (to fit an 80 character wide screen), even if the text had been quotet several times. * Use the correct number of ">" characters at the start of each quoted line. * Set your mail client to "english headers" to avoid subjects like: "AW: Antwort: Re: AW: AW: AW: Re: Some Topic allready trunkated" If you see one, don't just add another "Re:" but remove all "AW:" and other chained "Re:". * Use a descriptive subject! A message titled "A small wish" doesn't tell what it is about. Better use something like "should do xyz" or "crashes when doing xyz". * If the topic of the thread changed/degrades meanwhile, change the subject too. That means: Before you start to answer, have a look into the subject your are going to reply to. For example use: New topic [WAS] old topic * Always write one separate message per topic. some people (especially those who matter) might not read mixed-up and lengthy threads. * Start a new thread when posting a new subject. * Make emails as short as possible whilst keeping them comprehensible. Don't ===== * Don't post in either HTML-only or in Text and HTML. If your mail client doesn't support this, change it. * Don't top post. * Don't give a one line answer having quoted the whole post. * Don't use a too long signature. Approx. 4 lines should always be enought. * Don't reply where you should have started a new thread. This means, make sure that you're not responding to an existing posting. Just changing the subject header and deleting any quoted text is NOT enough, because the message's header will still contain references to other messages. * Don't break threads by sending a new mail, where you should have replied. * Don't test post. Send your test posts to "echo(a)fu-berlin.de" or similar reply machines. * Don't use lengthly disclaimers. If not possible, use a freemail account. * Don't quote disclaimers and other footers. General Etiquette ================= This can really be summed up in one phrase - 'be polite'. Allways use your 'Real Name' when posting to mailinglists or newsgroups. If you think something is off-topic, don't reply to the list although you may want to send a short and *polite* note to the person privately telling them which list would be more appropriate; don't just say - "that is OT here". Before asking a question, please Have a look at the mailing list archives at http://www.linuxtv.org/pipermail/vdr/ If someone flames or trolls the list, don't reply - it wastes everyones bandwidth and time. Don't reply to spam which gets through to the list - just ignore it when it does. Resources ========= * The ultimate guide to most matters to do with email etiquette is RFC-2822 which can be found at: ftp://ftp.isi.edu/in-notes/rfc2822.txt * A german site set up by some usenet-people, who take it even more serious with netiquette. http://learn.to/quote

1 0

Is GrabImage only for PAL resolution when using FF cards?
by Stone 19 Mar '07

19 Mar '07

I noticed that when the screenshot plugin starts, it grabs a PNM image to /dev/null, but the resolution is not right. Fory my system, everything should be in NTSC resolution. How is vdr getting 768x576 for the capture screen resolution? I would like this to be 720x480 instead. Mar 18 21:04:26 sid vdr: [4336] starting plugin: screenshot Mar 18 21:04:26 sid vdr: [4336] grabbing to PNM 100 768 576 Mar 18 21:04:26 sid vdr: [4336] grabbed image to /dev/null Best Regards.

2 2

plugin errors with vdr 1.5.1
by anthony kelly 18 Mar '07

18 Mar '07

Hi I don't know if this is useful. I could not compile many plugins with 1.5.1 until I made the following change in ./include/vdr/osdbase.h, in "class cOsdObject" I moved "bool needsFastResponse;" from private to public scope. Then most of my plugin probs went away. Don't have the faintest idea what I am doing so you can ignore/use if you wish. cheers Anthony Kelly

2 1

vdr-1.5.1: Interface race
by s.huelswitt＠gmx.de 18 Mar '07

18 Mar '07

Hi, there is a race condition while terminating vdr. Early in the shutdown process the Interface class is deleted. If a signal is raised after that point, the signal handler will call Interface->Interrupt() which is allready deleted. Regards. -- Stefan Huelswitt s.huelswitt(a)gmx.de | http://www.muempf.de/

2 1

softplay problem with ffmpeg [rev 8428] (Was: softdevice audio problem. audio repacker issue?)
by Stefan Lucke 18 Mar '07

18 Mar '07

On Sunday 18 March 2007 10:34, Martin Wache wrote: > Stefan Lucke schrieb: > > But there is still one drawback. > > It is still not playable with softplay. > > > > Neither audio nor video. > > There are only some accustic fragments and no video frame. > > > > For me softplay works fine with vdr recordings. Did you make sure that > you compiled softplay with the same ffmpeg version like the softdevice? Yes. just did a make clean-plugins, make plugins. This is with old (vdr-1.2.1) and new recordings. My current ffmpeg revision is 8428. Will test some older like 7852 too. -- Stefan Lucke

1 0

vdr doesn't recognise some remote keys when using LIRC
by Torgeir Veimo 18 Mar '07

18 Mar '07

I'm using a lirc setup with inputlircd daemon with a hauppauge remote on a dvb card. Everything works with the remote plugins using /dev/ input/eventX, but I'm trying to share the remote with several applications. For some reason when trying to learn keys with LIRC, when I'm running the inputlircd daemon, VDR refuses to react to them. I can see the keys being interpreted properly with irw. Does anyone know why this can be? -- Torgeir Veimo torgeir(a)pobox.com

3 6

(OFFTOPIC) "EFF reveals plot to cripple European television"
by Erik Tjernlund 16 Mar '07

16 Mar '07

<http://www.boingboing.net/2007/03/13/eff_reveals_plot_to_.html> <http://www.eff.org/IP/DVB/dvb_briefing_paper.php> /Erik

8 10

Scanning and channels.conf problems
by anthony kelly 15 Mar '07

15 Mar '07

Hi I am not sure if I should post this to vdr or to v4l/dvb as I'm not sure where the problem lies. One of our local TV stations changed their broadcast configuration as follows: "Guard Interval will change from 1/8 to 1/16 The FEC will change from 2/3 to 3/4" To get this channel working again, I tried to scan a new channels.conf. I changed the transponder file au-Darwin appropriately. Before this the scan did not see the 2 channels from this station at all, after the change it did. However, neither vdr or tzap is able to lock onto the config output. The errors are respectively: VDR: frontend 0 timed out while tuning to channel 17, tp 557 TZAP: ERROR: error while parsing inversion (syntax error) The dvbscan I used is from csv in 19/12/2005, all other channels work fine with the channels config output. I got the latest DVBAPPS and found that dvbscan no longer exists, but "scan" seems to replace it. However, scan produces a different output again, and vdr will not tune to any channel from the resulting output. I have a friend in Darwin who changed his au-Darwin transponder file in the same way and scanned and got workable outputs for him. But his channels.conf entry for this particular channel doesn't work for me either. In the past I have noticed that both he and I have different channels.conf formats but they have both worked find so I never worried about it. He and I were both on VDR 1.4.X also. Sorry if I am wandering here, I have tried so many things that I don't know exactly where the problem lies. In summary: -the latest scan utility generates output my vdr cannot read (1.4.1 or 1.5.1) -the older dvbscan utility generates output that works for all channels but one -my friend does the same thing and gets channel configs that work for him on all channels, but not for me. My config is: Debian 2.6.14.4 vdr 1.5.1 Compro DVB300-T tuner (SAA7134) v4l/dvb from csv (I think) from 14/6/2006 My latest scan output is: ABC HDTV;ABC:543625:I999B7C34D999M64T8G16Y0:T:27500:2314+2309:0;2315:2316:0:640:0:0:0 ABC TV Darwin;ABC:543625:I999B7C34D999M64T8G16Y0:T:27500:512+128:650=eng;660=eng:576:0:641:0:0:0 ABC2;ABC:543625:I999B7C34D999M64T8G16Y0:T:27500:2307+2306:2308=eng:2310:0:642:0:0:0 ABC TV;ABC:543625:I999B7C34D999M64T8G16Y0:T:27500:512+128:650=eng:576:0:643:0:0:0 ABC DiG Radio;ABC:543625:I999B7C34D999M64T8G16Y0:T:27500:0:2317=eng:0:0:646:0:0:0 ABC DiG Jazz;ABC:543625:I999B7C34D999M64T8G16Y0:T:27500:0:2318=eng:0:0:647:0:0:0 Nine Darwin SD;NINE NETWORK:550500:I999C34D34M64B7T8G8Y0:T:27500:512+128:650=eng;651=eng:578:0:1793:12921:0:0 Nine Darwin HD;NINE NETWORK:550500:I999B7C34D34M64T8G16Y0:T:27500:514+130:0;671:578:0:1794:12921:0:0 SBS HD;SBS:536625:I999B7C23D23M64T8G8Y0:T:27500:102:103=eng:41:0:864:12802:0:0 SBS DIGITAL 1;SBS:536625:I999B7C23D23M64T8G8Y0:T:27500:161:81=eng:41:0:865:12802:0:0 SBS DIGITAL 2;SBS:536625:I999B7C23D23M64T8G8Y0:T:27500:162:83:0:0:866:12802:0:0 SBS DIGITAL;SBS:536625:I999B7C23D23M64T8G8Y0:T:27500:161:81=eng:41:0:867:12802:0:0 SBS RADIO 1;SBS:536625:I999B7C23D23M64T8G8Y0:T:27500:0:201:0:0:878:12802:0:0 SBS RADIO 2;SBS:536625:I999B7C23D23M64T8G8Y0:T:27500:0:202:0:0:879:12802:0:0 SCTV Darwin;SCTV:557625000:I999C23D23M64B7T8G8Y0:T:27500:609:610=eng:611:0:2305:12954:0:0 SCTV HD - Darwin;Southern Cross Television:557625:I999B7C23D23M64T8G8Y0:T:27500:3311:0;3312:611:0:2337:12954:0:0 The last 2 entries (SCTV*) are the ones that do not work. They differ from the rest in the order of the parameters (i.e all the others are IxBx whereas the onex that donw's work have the B* much later). I have tried to manipulate these manually to match the others with no success. Also interestingly the guard interval is scanned as 8 instead of the 16 it should be. Any ideas are welcome. I am at a complete loss. I have very old card drivers, could this make a difference (I tried new ones but couldn't get them compiled). Thanks in Advance Anthony Kelly

1 0

TV Standards option for vdr-1.5.x
by Stone 15 Mar '07

15 Mar '07

Hi, In all the prevous versions of VDR, I have had to patch the FRAMESPERSECOND and change the rest of the hardcoded PAL values in VDR for my NTSC television. Is making this an option in VDR on the TODO list? Best Regards.

7 17

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr March 2007