vdr

vdr@linuxtv.org

6731 discussions

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

Croatian translation for VDR and hello plugin
by Adrian C. 17 Mar '08

17 Mar '08

Hello, I took hr_HR.po from latest VDR rc announcement - vdr-1.5.18, and finished the translation, as well as fixed/changed many strings to try and make the translation more consistent with all the other FOSS translated to Croatian (among others this is also useful http://open-tran.eu/). I've been a user of VDR for a long time now and felt that at least I can do this to thank all the developers for their hard work. I'm also a translator of several other applications like gajim and comix so I have some little experience. I was unable to find POTFILES.in in this snapshot, so I trusted that the provided po files are in sync with all the strings of the program and I worked directly on the po file provided (please advise me of any mistakes). % msgfmt -v hr_HR.po 322 translated messages. % msgfmt -v hello/hr_HR.po 6 translated messages. Tarball is here: http://sysphere.org/~anrxc/vdr/hr_HR-vdr.tar -- JID:anrxc|sysphere|org | sysphere.org/~anrxc/

1 0

FF card AV sync problems, possible fix to VDR (fwd)
by Ville Rannikko 17 Mar '08

17 Mar '08

> > Hi! > > > > The newest firmware for FF cards did not completely fix the AV desync > > problems > > for me. > Can you provide a sample recording where A/V sync fails with the current > firmware? Oh, well. Turns out that I had somehow failed to install the new firmware properly. My test patch is possibly not needed at all. Ville

8 38

Streaming service (UDP streamdev and DLNA plugin)
by alexw 17 Mar '08

17 Mar '08

Dear VDR users, I did try to get info about 2 projects discussed here and in dvb forum in the past. At the moment I did not find any good status information. 1) The UDP client/server implementation for the streamdev plugin. It was planned to reduce the number of ack sent by the client on a wifi link. 2) The UPNP (DLNA) plugin implementation to turn VDR into a full IPTV server. If someone has more information.... Cheers, Alex

1 0

VDR multiple cards, multi-recording vdr-1-5-15
by Simon Baxter 17 Mar '08

17 Mar '08

I have 2 DVB-C cards in my system, a TT-1500C budget card and a TT-2300C-FF card and run vdr-1.5.15. The intention was with 2 cards there should always be a DVB resource available to watch/record channels on different transponders. Tonight I had 2 recording events both start at 20:30, on the same transponder. For some reason, each recording event started on a different card - so all my DVB resources were tied up!! ONE;T:618000:C0M64:C:6900:5011:5012=eng:5014:606:501:182:5:0 TV2;T:618000:C0M64:C:6900:5021:5022=eng:5024:606:502:182:5:0 Any ideas why this happenned, and how to avoid this happenning again? Can I make one card preferred as the recording card? Thanks Simon

1 1

Re: [vdr] How to change font data?
by Martin Prochnow 17 Mar '08

17 Mar '08

>>>>> Is it possible to change font data directly in code or do I have to >>>>> create my own true type font containing the icons? >>> >>> the best aproach IMHO would be an API in VDR that allows you to "nail" >>> custom glyphs into the glyph cache. though this could lead to problems >>> if multiple plugins overwrite the same codepoints in the cache. using a >>> custom font would work too but you would force every user of your >>> plugin to use that font. making a ttf font is no fun either. maybe >>> there should be some way to mix cOsd::Bitmap with normal text? >> >> Messing with the fonts is not a good idea, IMHO. > > It works for VDR 1.4.x ;-) > >> I'll see about a method to add icons to the menu items. >> However, this has veeery low priority ;-) > > So my only option for now is a true type font containing the icons. Or > maybe to create a skin plugin that can displays the icons. > At the moment I try to solve the hole issue by using a true type font containing the icons. There was done some work at vdr-portal.de (thanks folks ;) ) But there comes the next problem. Until now, I use the space between 0x80 and 0x9f, which is marked as unused for ISO8859. But this does not work for UTF-8. Amair from vdr-portal.de suggests to use the position after 0xe000 for this case. So I need two different fonts and I have to check, if VDR is running in an UTF-8 environment and set the values for the icons accordingly. This hole TTF and UTF-8 crap makes the handling of the icons very complicated. Maybe it is the best for now to replace the icons with normal letters until VDR provides support icons. I don't want to dictate the users what font they have to use. Martin

3 2

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

16 Mar '08

> I have installed 1.5.17 (i think) of vdr (from the experimental apt > repository) however I can't get xineliboutput compiled as it's > complaining that it can't find a valid libxine. It looks like the > dependencies are quite specific in what they want. Hi, 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. If anyone knows what is so terribly wrong with later libxine, please let me know... What I did, was I just edited out the latter requirement from the debian/control file, and a couple of others (can't remember what they were, but there were about 4-5 files in the debian directory with the requirement setting). Compilation went well with libxine 1.1.17 and the plugin and the frontends work fine. -- Best Regards, Timo ------------ timo.laitinen(a)utu.fi FABRICATI DIEM, PVNK.

2 1

2GB file sizes and cutting recordings
by Florian Gleixner 16 Mar '08

16 Mar '08

Hi, i use dvbcut to cut my recordings. After cutting i can rename the resulting mpg file to 001.vdr, delete the index file and run genindex and then i have a perfect cutted recording. This works well for all recordings that are smaller than 2GB. If the file is > 2GB, i tried to concat the 001.vdr 002.vdr ... files and use dvbcut to make a new 001.vdr. Unfortunately vdr does not like files > 2GB. But i also canot use split -b 2097152000 to make new vdr files, because it would not split at GOP. Or is that not needed? It would be easier if vdr could handle files > 2GB - and tools like genindex too. Handling these files for playback would be enough for me. Or is there another preferred method cutting files? I dont want to use vdrs cutter because my remote does not really work well and i read that i can only cut every iframe. dvbcuts sliders are really easy to handle :-) Thanks! Flo

4 10

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr