vdr April 2008

vdr@linuxtv.org

106 participants
122 discussions

How can VDR record with timer if behind a decoder ?
by vroemm 09 Apr '08

09 Apr '08

Hi. There is something i do not understand. Here is how i though it works: My TV provider, Casema in the netherlands, delivers digital TV via a decoder with a sort of credit card. Normally you use the remote control of this decoder to choose the tv prog to watch. Thus decoder sends only the selected digital channel to the DVB-C TV card in the computer. This was told to me by a sales person today. If this is true, how then can VDR select the different digital programs with the timers in VDR set by you ? Then somehow all digital channels have to be send to the DVB-C TV card. Or does VDR not work with decoders with such a credit card restriction ? I hope someone can explain this to me. If feel a bit stupid right now, i hope this falls under the saying "There are no stupid questions" :-)

2 2

Looking for Medion MD4688 remote code for VDR
by Jean-Claude Repetto 09 Apr '08

09 Apr '08

Hi, My Medion MD 4688 remote (from Aldi) has lost its codes because the batteries were dead :-( Obviously, I had not written the codes on the back label of the remote control. I have looked at this ML archives and found some codes (308, 336), but they are not working. I am not using LIRC, but the RC input of a WinTV DVB-S REV 1.3, and this is my remote.conf file : remote-event0._Setup /proc/av7110_ir 00008000 20 remote-event0.Up 0000000100010003 remote-event0.Down 0000000100010009 remote-event0.Menu 0000000100010004 remote-event0.Ok 0000000100010006 remote-event0.Back 000000010001000A remote-event0.Left 0000000100010005 remote-event0.Right 0000000100010007 remote-event0.Red 0000000100010001 remote-event0.Green 0000000100010002 remote-event0.Yellow 0000000100010023 remote-event0.Blue 000000010001000E remote-event0.0 000000010001001E remote-event0.1 0000000100010026 remote-event0.2 0000000100010027 remote-event0.3 0000000100010028 remote-event0.4 000000010001001A remote-event0.5 000000010001003E remote-event0.6 0000000100010017 remote-event0.7 0000000100010018 remote-event0.8 0000000100010019 remote-event0.9 000000010001002C remote-event0.Play 0000000100010031 remote-event0.Pause 000000010001003D remote-event0.Stop 0000000100010021 remote-event0.Record 0000000100010024 remote-event0.FastFwd 0000000100010037 remote-event0.FastRew 0000000100010036 remote-event0.Power 000000010001000D remote-event0.Channel+ 0000000100010035 remote-event0.Channel- 0000000100010034 remote-event0.User1 000000010001000C remote-event0.User2 0000000100010015 remote-event0.User3 000000010001003B remote-event0.User4 000000010001000B Any suggestions for the MD4688 code ? Thanks, Jean-Claude

2 2

vdr-burn gcc 4.3 build fix
by Ville Skyttä 08 Apr '08

08 Apr '08

Hi, The attached patch fixes build of vdr-burn (current CVS HEAD) with gcc 4.3's cleaned up C++ headers.

1 0

[PATCH] Install headers, add pkgconfig file
by Ville Skyttä 08 Apr '08

08 Apr '08

Hello, As discussed in the freetype/fontconfig pkgconfig thread, here's a combined patch implementing installation of VDR's headers and generating a pkgconfig *.pc file. This patch is mostly just a discussion draft - I haven't tried installing the headers and the pkgconfig file isn't installed yet by any "make install*" (mostly because very ironically, there's no way to query pkg-config for its default search path, which is something I've intended to report a bug about since a long time ago, but failed so far - maybe I'll do it right now :)). Also, I don't know if all *.h are actually something that should be installed by "install-headers", but since they're all available in the current setup for plugins to use too, I suppose weeding through them is an orthogonal task to this patch if needed in the first place (and maybe better discussed in the "RFC: Makefile ravamp" [sic] thread from Sat 8th Mar).

4 8

[Announce] vdr-streamdev-0.3.4 and CVS branch
by Frank Schmirler 08 Apr '08

08 Apr '08

Hi there, streamdev-0.3.4 is finally available from http://streamdev.vdr-developer.org. It marks the end of the 0.3.x series. As such, it still contains lots of unused and legacy code. There has been a major cleanup in the meantime. Watch out for the upcoming releases 0.4.0 (for VDR 1.4.0 - 1.5.8) and 0.5.0 (for VDR > 1.5.9). Most of it has already been commited to CVS. Note that a branch has been opened for the 0.4 series. Special thanks go to: - Sascha Volkenandt, the original author of streamdev - Rolf Ahrenberg for many suggestions, patches and for helping a lot to prepare the upcoming releases - Petri Hintukainen for contributing the section streaming parts. Great work! - all the others on the CONTRIBUTORS list ;) Please check http://streamdev.vdr-developer.org for information on new features. Additional information can be found in the README file and the HISTORY log. Enjoy, Frank

2 1

Re: [vdr] xineliboutput: viewing 16:9 content on 4:3 output device
by Torgeir Veimo 08 Apr '08

08 Apr '08

On 8 Apr 2008, at 16:43, Ian Bates wrote: > What I would like is to maintain the stream 16:9 ratio but by by > cropping the left and right sections of the stream that fall 'outside' > the TV, so the full real estate of the TV is used, at the expense of > losing some stream information. This setting is most often called crop mode. The specific setting you're after is often called pan-and-scan. I can't say how to achieve the desired output with xineliboutput though, since I use softdevice. -- Torgeir Veimo torgeir(a)pobox.com

1 0

Femon and new API.
by lucian orasanu 08 Apr '08

08 Apr '08

Helo. I'am tring to port femon to new api and no succes. 1. Questions. Is all new api implemented iet in multiproto? New version of api is 3.3 pr 4.3? Is there any documentation ? 2. My tests and work. I put this code : enum dvbfe_status { DVBFE_HAS_SIGNAL = (1 << 0), /* something above noise floor */ DVBFE_HAS_CARRIER = (1 << 1), /* Signal found */ DVBFE_HAS_VITERBI = (1 << 2), /* FEC is stable */ DVBFE_HAS_SYNC = (1 << 3), /* SYNC found */ DVBFE_HAS_LOCK = (1 << 4), /* OK .. */ DVBFE_TIMEDOUT = (1 << 5), /* no lock in last ~2 s */ DVBFE_STATUS_DUMMY = (1 << 31) }; #define DVBFE_READ_STATUS _IOR('o', 87, enum dvbfe_status) enum dvbfe_statistics_avail { DVBFE_BER = (1 << 0), /*!< bit error rate */ DVBFE_SIGNAL_STRENGTH = (1 << 1), /*!< signal strength */ DVBFE_SNR = (1 << 2), /*!< signal to nois ratio */ DVBFE_UNCORRECTED_BLOCKS = (1 << 3) /*!< number of uncorrected blocks */ }; struct dvbfe_statistics { enum dvbfe_statistics_avail avail; /*!< describes the available information */ __u32 ber; /*!< bit error rate, if avaible */ __u16 signal_strength; /*!< signal strength, if available */ __u16 snr; /*!< signal to noise ratio, if avaible */ __u32 uncorrected_blocks; /*!< number of uncorrected blocks, if avaible */ }; #define DVBFE_READ_STATIISTICS _IOR('o', 88, struct dvbfe_statistics) in /linux/include/linux/dvb/frontend.h from multiproto. and then i modified femontools.c like this: return NULL; CHECK(ioctl(fe, DVBFE_GET_INFO, &value)); CHECK(ioctl(fe, DVBFE_READ_STATUS, &status)); CHECK(ioctl(fe, DVBFE_READ_STATIISTICS, &signal)); //CHECK(ioctl(fe, DVBFE_READ_SNR, &snr)); //CHECK(ioctl(fe, DVBFE_READ_BER, &ber)); //CHECK(ioctl(fe, DVBFE_READ_UNCORRECTED_BLOCKS, &unc)); close(fe); info = cString::sprintf("CARD:%d\nTYPE:%d\nNAME:%s\nSTAT:%02X\nSGNL:%04X\nSNRA:%04X\nBERA:%08X\nUNCB:%08X", cardIndex, value.type, value.name, status, signal, snr, ber, unc); if (cFemonOsd::Instance()) info = cString::sprintf("%s\nVIBR:%.0f\nAUBR:%.0f\nDDBR:%.0f", *info, cFemonOsd::Instance()->GetVideoBitrate(), cFemonOsd::Instance()->GetAudioBitrate(), cFemonOsd::Instance()->GetDolbyBitrate()); if (channel) info = cString::sprintf("%s\nCHAN:%s", *info, *channel->ToText()); return info; } cString getFrontendName(int cardIndex) { struct dvbfe_info value; cString dev = cString::sprintf(FRONTEND_DEVICE, cardIndex, 0); int fe = open(dev, O_RDONLY | O_NONBLOCK); if (fe < 0) return NULL; CHECK(ioctl(fe, DVBFE_GET_INFO, &value)); close(fe); return (cString::sprintf("%s on device #%d", value.name, cardIndex)); } cString getFrontendStatus(int cardIndex) { dvbfe_status value; cString dev = cString::sprintf(FRONTEND_DEVICE, cardIndex, 0); int fe = open(dev, O_RDONLY | O_NONBLOCK); if (fe < 0) return NULL; CHECK(ioctl(fe, DVBFE_READ_STATUS, &value)); close(fe); return (cString::sprintf("Status %s:%s:%s:%s:%s on device #%d", (value & DVBFE_HAS_LOCK) ? "LOCKED" : "-", (value & DVBFE_HAS_SIGNAL) ? "SIGNAL" : "-", (value & DVBFE_HAS_CARRIER) ? "CARRIER" : "-", (value & DVBFE_HAS_VITERBI) ? "VITERBI" : "-", (value & DVBFE_HAS_SYNC) ? "SYNC" : "-", cardIndex)); } uint16_t getSignal(int cardIndex) { uint16_t value = 0; cString dev = cString::sprintf(FRONTEND_DEVICE, cardIndex, 0); int fe = open(dev, O_RDONLY | O_NONBLOCK); if (fe < 0) return (value); CHECK(ioctl(fe, FE_READ_SIGNAL, &value)); close(fe); return (value); } is this ok? a litle bit of help? ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

1 0

Newbie: Pinnacle PCTV tuner kit rev 1.7 good for VDR ?
by vroemm 08 Apr '08

08 Apr '08

Hi. I am new to this vdr mailinglist. I have been admiring the VDR project for a long time. And now am looking seriously into building one. I am having trouble finding a DVB-C PCI card in the city where i live. There is this one: Pinnacle PCTV TUNER KIT I could not find a type number. On the card is the text "REV 1.7" It is a PCI card. On the box are two pictures of DVB-T and DVB-C And it has a TV input and TV output, according to the picture on the box. Its price has been marked of from 60 - 70 euro to 57 euro. Guess the model is on its way out. Can not find any useful info on it on the internet. What are the capabilities of this card ? Does anyone know if this card can be used with VDR ? Thanks :-)

1 1

Request: Pvrinput and cards without mpeg encoder - writing a user mode encoder/proxy
by Eddi De Pieri 07 Apr '08

07 Apr '08

Hi, I'd like to use pvrinput plugin with my saa7134 based card. This card lacks of mpeg encoder, so I think so... Why don't write a proxy that works like DV4Linux preloading a library before starting VDR. - In the library configuration should be written the stupid device driver name (environment). - The library should trap the open of v4l device. - It should be started a probe routine for looking for device driver match the environment variable. - On open(fd,file), if file match the device probed, then using libavcodec, start encoding mpeg stream into a buffer for mmap - on ioctl, rewrite driver name in v4l2_capability.driver [and so on] What about this approach? Any volunteer? Regards, Eddi

1 0

[ANNOUNCE] vdr-dxr3 0.2.8
by Ville Skyttä 07 Apr '08

07 Apr '08

vdr-dxr3 0.2.8 is out, the most noteworthy thing being compatibility with VDR 1.6.0. 2008-04-06: Version 0.2.8 - Fix build with ffmpeg >= ~2007-07 (Ville Skyttä) - Fix build with VDR >= 1.5.9 (Ville Skyttä) - Drop support for VDR < 1.4.0 (Ville Skyttä) - Implement OSD level for VDR >= 1.5.9 (Luca Olivetti) - Fix subtitles for VDR >= 1.5.11 (Luca Olivetti, Sami Sundell) - Include VDR 1.6+ subtitle hack patch in patches/ (Luca Olivetti) https://sourceforge.net/project/showfiles.php?group_id=112648

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr April 2008