vdr March 2008

vdr@linuxtv.org

108 participants
108 discussions

Problems with defining CA-field to allow devices to access channels
by Antti Hartikainen 22 Mar '08

22 Mar '08

Hello, list and Klaus. Is it possible to limit multiple DVB devices to access certain channel with CA-field? I have following setup: Card #1: DVB-S full-featured (only for mpeg decoding and tv-output) Card #2: DVB-T budget (connected to antenna 1) Card #3: DVB-T budget (connected to antenna 2) Card #4: DVB-T budget (connected to antenna 1) So different DVB-cards can receive different multiplexes. Problem is: VDR doesn't seem handle correctly multiple CA-entries, when it's saving channel config file. When defining CA field to 2,4 (editing config file by hand) to let both cards 2 and 4 to access channel, VDR sets CA-field to 2. But would be nice if both cards which are capable to receive channel, could do it. In this case only one card gets it. And it is not possible to limit encrypted channels, which in my opinion is most critical here; 1) When defining CA field to 3,B00 - VDR sets CA-field to 3, and this channel won't be decrypted as it's not identified as Conax. 2) When defining CA field to B00,3 - VDR sets CA-field to B00, and every card can access this channel. Anyway it would be nice to limit access for devices by frequency (DVB-T/C) and by source (DVB-S, SourceCaps does this, any similar for DVB-T?). Or atleast to get this CA-field limiting working ;) Testing done with vdr 1.5.15

1 1

[ANNOUNCE] vdr-sudoku-0.2.0
by Thomas Günther 22 Mar '08

22 Mar '08

Hi! There is a new version of the Sudoku plug-in. Download: http://toms-cafe.de/vdr/sudoku/vdr-sudoku-0.2.0.tgz Changes since version 0.1.3: - Added gettext support (VDR >= 1.5.7). - Fixed compiler warnings with gcc-4.1.2. - Updated FSF address in the license information. - Improved copyright and license information in the header of all source files. - Fixed (un)marking the cell on the bottom right. - Show possible numbers as pattern. - Show possible numbers as digits (VDR >= 1.5.4). - Paint numbers with a larger font (VDR >= 1.5.4). - Changed the background color of marked cells to darkgreen. - Added commands menu. - Added commands to load and save puzzles from/to the sudoku-list file. - Added setup to commands menu. - Fixed height of info window for spanish text. - Updated German language texts. - Added Italian language texts (thanks to Gringo). - Margined output of text into the info window. This plugin generates Number Place puzzles, so called Sudokus, and let you solve it. A Sudoku puzzle consists of 9 x 9 cells subdivided into 9 regions with 3 x 3 cells. The rules are simple. There have to be the numbers from 1 to 9 in every row, column and region. In the beginning some numbers are given. These cells are painted with cyan background color. The aim of the puzzle is to find the missing numbers. There is only one solution of a Sudoku puzzle. See the project's homepage for details: http://toms-cafe.de/vdr/sudoku Tom

2 1

[ANNOUNCE] vdr-xine-0.8.2 plugin
by Reinhard Nissl 22 Mar '08

22 Mar '08

Hi, I'm pleased to announce a the maintenance release 0.8.2. You can find it on my homepage as usual: http://home.vr-web.de/~rnissl Excerpt from HISTORY: 2008-03-10: Version 0.8.2 - Fixed optional parameter processing for parameter -p. As getopt() requires that optional arguments must follow the option switch without any delimiters, I've updated MANUAL accordingly, i. e. all options are documented without delimiters. Furthermore you'll get an error message when specifying the argument for -p incorrectly. - Fixed compilation of patched xine-lib-1.1 (thanks to Darren Salt and Fabian Foerg for contributing fixes for this issue). - Provided xine_get_current_frame_alloc() to xine-lib which allows retrieving the current frame image without the need to pause the stream for a second call to the function after allocating sufficient memory. - Fixed retrieving only valid PTS from xine. xine's metronom is now intercepted to monitor PTS changes after which PTS are considered to be valid. - Fixed handling VDR's clear command. Adding sync points to the stream makes sure that all data on the way to xine up to sync point gets properly dropped. - Added Russian translation (thanks to Oleg Roitburd for providing ru_RU.po). Enjoy. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

7 13

[ANNOUNCE] VDR developer version 1.5.18 - release candidate 3
by Klaus Schmidinger 22 Mar '08

22 Mar '08

VDR developer version 1.5.18 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.18.tar.bz2 A 'diff' against the previous developer version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.17-1.5.18.diff NOTE: ===== The originally planned release of version 1.6.0 has been postponed, because there have been a few small changes that need to be properly tested first. Please report any bugs as soon as possible. If nothing unexpected happens, I plan to release version 1.6.0 on March 23. The following translation files still have untranslated texts: el_GR.po hr_HR.po nn_NO.po pt_PT.po It would be nice if somebody could finish these before the 1.6.0 release. To avoid duplicate work, please announce your activity here in this thread. WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment, I strongly recommend that you only use it under controlled conditions and for testing and debugging. The changes since version 1.5.17: - Added a missing reset of maxNumber in cChannels::Renumber() (reported by Sundararaj Reel). - Revoked the fixed change of the default character set for SI data and introduced an environment variable to control it (thanks to Ales Jurik for reporting broken SI data on the Czech/Slovak channels, which actually do follow the standard). Users who want to set the default character set to something different can do this by setting the environment variable VDR_CHARSET_OVERRIDE to something like ISO-8859-9. - Fixed a signed character used as index in cBase64Encoder::NextLine() (thanks to Tobias Grimm). - Updated the Spanish and Catalanian OSD texts (thanks to Luca Olivetti). - Fixed automatically selecting the preferred subtitle language (based on a patch from Rolf Ahrenberg). - Updated the Ukrainian OSD texts (thanks to Yarema Aka Knedlyk). - Updated the Italian OSD texts (thanks to Diego Pierotto). - Updated the Polish OSD texts (thanks to Michael Rakowski). - Fixed formatting the name section in the VDR man pages (thanks to Tobias Grimm). - Updated the Swedish OSD texts (thanks to Magnus Andersson). - Added Russian translations to the 'skincurses' and 'pictures' plugins (thanks to Alexander Gross). - Fixed displaying the free disk space when entering the recordings menu where the last replayed recording was in a subdirectory, and pressing Back (thanks to Rolf Ahrenberg). - Fixed tuning to a live channel after a recording has been stopped using the 'Back' key. - Resetting a timer's 'pending' flag when it has ended. *When reporting problems, please don't reply to this message!* Create a new thread instead, using a descriptive subject! Have fun! Klaus

2 2

vdr-xine - screen size and resolution
by serge pecher 21 Mar '08

21 Mar '08

Hello, I am making some test with vdr-xine 0.8.2, libxine en xine-ui from Reinhard's site (kubuntu 7.10) It is on a laptop without dvb device. For the moment I just try to replay recordings from an other vdr box, and dvd with dvdswitch. I use a Sony bravia 32" TV screen connected at the vga output of the laptop. The resolution configured in xorg.conf is 1280x720. I achieve to have the "no-signal" in full screen. When I replay recordings, most of them are with wide black bands left & right and for some of them also small bands up&down. Some recordings (most movies) have wide bands on the four sides. The most dvd's also have wide bands L&R. One of them plays in full screen but the image is stretched. I was playing around with some settings of the plugin, but don't see how to get a good result. In the past I made some test, I believed, with vdr-xine (or maybe xineliboutput ?), and I can remember something in the settings that achieved auto-scaling. I had at that time almost everything in full screen, but sometimes also with wrong stretching. I tried to start xine, just by typing xine in a terminal box and choosinf "vdr" and I also tried xine -V xv --post vdr_video --post vdr_audio --post upmix_mono "vdr:/tmp/vdr-xine/stream#demux:mpeg_pes", but can't really see a difference. As I understand, I have different sources, with different resolutions. Is there a manner to tell vdr-xine or xine to adapt the output as good as possible to my tv screen ? Thanks, sp

3 5

Re: [vdr] xineliboutput and ubuntu 7.10 (Gutsy)
by Timo Laitinen 20 Mar '08

20 Mar '08

On Mon, 17 Mar 2008 22:41:15 +0100 Darren Salt <linux(a)youmustbejoking.demon.co.uk> wrote: > I demand that Timo Laitinen may or may not have written... > > > Aaargh, forgot to change the vdr Digest from the subject to > > something reasonable... sorry about the noise... Here's the same > > with a bit more identifiable subject. > > You forgot to correct the In-Reply-To header. ;-) ... > > I'm inclined to believe the latter: you keep forgetting. :-) Well, I'd put the header problem somewhere between "didn't even think of it" and "can't do it with my emailer" (at least after a quick check and a couple of attempts), sorry... > > although not perfectly (rapid motion, such as news tickers, are > > jumpy with xxmc on openchrome when HW acceleration is on, not sure > > why) > > Sounds like an X problem to me, though it could just possibly be to > do with xine-lib's xxmc support. Yes, could be an X (openchrome) problem, could be xxmc or the HW decoding, I'm a bit at loss with it at the moment. With Xv the quality is just fine (but CPU at around 60-70%, a bit too touchy for other activity). The xxmc is somewhat blurry and jumping a bit with the tickers, with CPU at 30%. Any similar experience/solutions anyone? The hardware is CN700 (EPIA EN-12000). Well, maybe I should actually start another thread on this (with proper headers on the replys :-) ), or maybe at openchrome or xine... > > So (wrote he hoping), would things get better (regarding my quality > > problems) if I changed to 1.1.2? > > Hopefully not ? unless you mean 1.2, in which case you'll see much > the same as 1.1 hg wrt xxmc. I was (not really that optimistically) thinking that maybe the <<1.1.3 meant something horrible happens at higher versions... but I wasn't really expecting a positive answer on that. And it does seem that not much has happened with xine xxmc recently. > Basically, if you upgrade xine-lib to a newer ABI-compatible version, > you won't need to rebuild plugins (except just the once to get them > using the new plugin directory naming scheme when you upgrade past > 1.1.10.1). Ok, thanks for the info, maybe I'll try a newer version at some stage... -- Best Regards, Timo ------------ timo.laitinen(a)utu.fi FABRICATI DIEM, PVNK.

2 1

Which is the best firmware for ADV7170
by Kartsa 19 Mar '08

19 Mar '08

I have DXR3 card with ADV7170. I have quite bad audio sync problems with it and was wondering if there is some fw which is better over others. The problem is that I must every once and a while pause replay for a second or so or when watching live TV change the channel back and forthto get the sync back. I.e. I have a timer that causes vdr to start every morning to record the morning show which I start to playback as soon as I get up. During the next hour or so I must use pause at least five time or more. This happens every morning. I have: vdr (1.4.6-1/1.4.5) - The Video Disk Recorder dxr3 (0.2.7) - Hardware MPEG decoder and in case it matters burn (0.1.0-pre21) - Versatile convert-and-burn plugin dvd (0.3.6-b03) - turn VDR into an (almost) full featured DVD player wapd (0.8) - Remote control by WAP ttxtsubs (0.0.5-RRE) - Teletext subtitles text2skin (1.1-cvs) - Loader for text-based skins subtitles (0.5.0) - DVB subtitles decoder epgsearch (0.9.22) - search the EPG for repeats and more osdteletext (0.5.1) - Displays teletext on the OSD mp3 (0.10.0) - A versatile audio player mplayer (0.10.0) - Media replay via MPlayer quickepgsearch (0.0.1) - Quick search for broadcasts femon (1.1.3) - DVB Signal Information Monitor (OSD) vompserver (0.2.6) - VDR on MVP plugin by Chris Tallon epgsearchonly (0.0.1) - Direct access to epgsearch's search menu conflictcheckonly (0.0.1) - Direct access to epgsearch's conflict check menu thanks in advance \\Kartsa

4 5

compile error vdr-xine 0.8.2
by serge pecher 18 Mar '08

18 Mar '08

Hello, I am trying to compile vdr 0.8.2 I did download with hg libxine 1.2. and installed it with ./autogen.sh and make, make install. I did the same (cvs) with xine-ui When I make plugins, I have this error : make[1]: entrant dans le rÃ©pertoire Â« /usr/local/src/vdr-1.5.17-br/PLUGINS/src/xine-0.8.2 Â» g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -DUSE_CHANNELSCAN -DUSE_CMDSUBMENU -DUSE_CUTTERLIMIT -DUSE_CUTTERQUEUE -DUSE_CUTTIME -DUSE_DELTIMESHIFTREC -DUSE_DDEPGENTRY -DUSE_DOLBYINREC -DUSE_DVBPLAYER -DUSE_DVBSETUP -DUSE_DVDARCHIVE -DUSE_DVLRECSCRIPTADDON -DUSE_DVLVIDPREFER -DUSE_DVLFRIENDLYFNAMES -DUSE_HARDLINKCUTTER -DUSE_IPTV -DUSE_JUMPPLAY -DUSE_LIEMIKUUTIO -DUSE_MAINMENUHOOKS -DUSE_SETUP -DUSE_OSDMAXITEMS -DUSE_PINPLUGIN -DUSE_PLUGINMISSING -DUSE_ROTOR -DUSE_SETTIME -DUSE_SOURCECAPS -DUSE_SORTRECORDS -DUSE_SYNCEARLY -DUSE_TIMERCMD -DUSE_TIMERINFO -DUSE_TTXTSUBS -DUSE_VALIDINPUT -DUSE_VOLCTRL -DUSE_WAREAGLEICON -DUSE_YAEPG -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' -DFIFO_DIR=\"/tmp/vdr-xine\" -DVERIFY_BITMAP_DIRTY=0 `pkg-config --cflags libxine` -I../../../include xine.c Dans le fichier inclus Ã partir de xine.c:9: xineCommon.h:20:2: erreur: #error xine/vdr.h does not match. Please solve this issue by reading section XINE VDR VERSION MISMATCH in INSTALL! make[1]: *** [xine.o] Erreur 1 When I look at VDR VERSION MISMATCH in INSTALL, I have the right answer with pkg-config cflags libxine (/usr/local/include) In /usr/local/include I have the file xine.h and a directory xine. In xine I have vdr.h When I type pkg-config modversion libxine I get 1.1.90 (is that correct for 1.2 ?) I use kubuntu 7.10 Any Idea ? Thanks, sp

1 0

Re: [vdr] xineliboutput and ubuntu 7.10 (Gutsy)
by Timo Laitinen 17 Mar '08

17 Mar '08

Aaargh, forgot to change the vdr Digest from the subject to something reasonable... sorry about the noise... Here's the same with a bit more identifiable subject. br, Timo ----------- On Mon, 17 Mar 2008 12:00:02 +0100 Darren Salt <linux(a)youmustbejoking.demon.co.uk> wrote: > > I demand that Timo Laitinen may or may not have written... > > [snip] > > Just tackled with this one myself... at least if you used the e-tobi > > repositories. There was a strange requirement for the library > > version, I think it was something like libxine => 1.1.12 libxine << > > 1.1.13. > > Highly unlikely. ... > > Compilation went well with libxine 1.1.17 and the plugin and the > > frontends work fine. > > 1.1.17? Did you get that from... I don't know, probably late next > year? :-) > Oops, it seems my time machine had a programming glitch... Or, alternatively, I still haven't learned NOT to trust my memory... So, actually looking at it, it had Build-Depends libxine-dev (<< 1.1.3), libxine-dev (>= 1.1.2) , I removed all version requirements, compiled it against libxine 1.1.7. (in Ubuntu Gutsy) But, still, it works, although not perfectly (rapid motion, such as news tickers, are jumpy with xxmc on openchrome when HW acceleration is on, not sure why) > That *is* the general form, though, and it's to do with the name of > xine-lib's plugins directory and how the plugin build scripts get the > directory name. So (wrote he hoping), would things get better (regarding my quality problems) if I changed to 1.1.2? or to 1.1.11? Or is it just so that if it works at all, it's ok? -- Best Regards, Timo ------------ timo.laitinen(a)utu.fi FABRICATI DIEM, PVNK.

2 1

Re: [vdr] vdr Digest, Vol 38, Issue 36
by Timo Laitinen 17 Mar '08

17 Mar '08

On Mon, 17 Mar 2008 12:00:02 +0100 Darren Salt <linux(a)youmustbejoking.demon.co.uk> wrote: > > I demand that Timo Laitinen may or may not have written... > > [snip] > > Just tackled with this one myself... at least if you used the e-tobi > > repositories. There was a strange requirement for the library > > version, I think it was something like libxine => 1.1.12 libxine << > > 1.1.13. > > Highly unlikely. ... > > Compilation went well with libxine 1.1.17 and the plugin and the > > frontends work fine. > > 1.1.17? Did you get that from... I don't know, probably late next > year? :-) > Oops, it seems my time machine had a programming glitch... Or, alternatively, I still haven't learned NOT to trust my memory... So, actually looking at it, it had Build-Depends libxine-dev (<< 1.1.3), libxine-dev (>= 1.1.2) , I removed all version requirements, compiled it against libxine 1.1.7. (in Ubuntu Gutsy) But, still, it works, although not perfectly (rapid motion, such as news tickers, are jumpy with xxmc on openchrome when HW acceleration is on, not sure why) > That *is* the general form, though, and it's to do with the name of > xine-lib's plugins directory and how the plugin build scripts get the > directory name. So (wrote he hoping), would things get better (regarding my quality problems) if I changed to 1.1.2? or to 1.1.11? Or is it just so that if it works at all, it's ok? -- Best Regards, Timo ------------ timo.laitinen(a)utu.fi FABRICATI DIEM, PVNK.

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr March 2008