vdr

vdr@linuxtv.org

2 participants
6731 discussions

Re: Re: [vdr] epgsearch, timeline, and streamdev-client timer patches?
by peter_weber69 04 Apr '05

04 Apr '05

Hi, 1) use my patched plugin streamdev-plugin for VDR-1.3.19, VDR-1.3.20 on http://mitglied.lycos.de/peterweber69/ 2) then change line (ca. 143) in .........../PLUGINS/src/streamdev/client/menu.c from Add(new cMenuEditDayItem( tr("Day"), &m_Data.m_Day)); to // Add(new cMenuEditDayItem( tr("Day"), &m_Data.m_Day)); bye > Von :: Luis Palacios <luis(a)luispa.com> > An :: "Klaus Schmidinger's VDR" <vdr(a)linuxtv.org> > Betreff: Re: [vdr] epgsearch, timeline, and streamdev-client timer patches? > Datum: Mon, 4 Apr 2005 12:51:44 +0200 > <pre>On Mon, 04 Apr 2005 12:30:26 +0200 > syrius.ml(a)no-log.org wrote: > > > > Hi, any news on streamdev and vdr-1.3.23 ? > > > > > > It used to work, with vdr-1.3.22: > > > vdr-streamdev-0.3.3-pre4.tgz > > > patch for streamdev: vdr-streamdev-patch-for-vdr-1.3.19.diff > > > > how about trying streamdev cvs ? > > I'm not sure it will work for 1.3.23, but at least it works here for > > 1.3.22. > > > > cvs -d:pserver:anoncvs@vdr-developer.org:/var/cvsroot login > > cvs -d:pserver:anoncvs@vdr-developer.org:/var/cvsroot co streamdev > > Thanks for the recomendation, however didn't work with 1.3.23. Same error. I > didn't apply vdr-streamdev-patch-for-vdr-1.3.19.diff though, so looks it's > not needed anymore. > > Unfortunately, same error: > > g++ -g -O2 -Wall -Woverloaded-virtual -O2 -c -D_GNU_SOURCE -DHAVE_AUTOPID > -I../../../include -I../DVB/include -I. -o client/menu.o client/menu.c > client/menu.c: In constructor ` > cStreamdevMenuEditTimer::cStreamdevMenuEditTimer(cRemoteTimer*, bool)': > client/menu.c:141: error: parse error before `(' token > > > > > > -- > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > <a href=http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr>http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr</a> > </pre> Benachrichtigung bei E-Mail Empfang! - http://mail.lycos.de/app/lycosinside/setupLI.exe

2 1

event-id in epg.data
by Matthias Schniedermeyer 04 Apr '05

04 Apr '05

Hi Currently i'm thinking about (finally) implementing a function in Master-Timer to watch for changes in the epg.data and modify/delete/add it's timers accordingly. But first i need a way to "bind" a specific timer to it's epg-entry. As it seem there is a "event-id" in the epg.data which could/should be usable for this. As it seems i could do the following with the event-id: - Data changes(*) for a given event-id can be (if applicable like time/duration) mirrored to the timer - When a event-id "vanishes" the timer can also be deleted(*4) As i haven't observed the event-ids in the past (until recently i considered the event-id as "junk"-data i don't need) i don't know how "good(tm)" this data is or how good the tv-station fill out this data. Has anyone already used the event-id and can tell me if i'm guessing correctly? (I intend to use the event-id as THE linchpin(Dreh- und Angelpunkt) for the epg-data-handling in Master-Timer) *: Like: - A change in time/duration/title/subtitle/... can be mirrored to the timer(*2) and/or - It can be checked if the entry still matches (a/the) torecord-entry and be deleted if it doesn't match anymore. e.x. this should be the case when the originally scheduled show is switch with a totally different one for which no torecord-entry matches. *2: But i guess with a change in time a new/changed event-id is more likely, but that wouldn't be a problem because the original timer would be deleted and a new one programmed instead. *3: It also wouldn't be a problem if a show is "inserted" somewhere between and all entries following after would be renumbered (seen *4) *4: When a specific show/event would get a "randomly" new event-id(*4), the old timer would be deleted, but a new timer one would be programmed too. So in worst-case Master-Timer should/would reprogram affected timers if the event-id is "missused" by tv-stations. -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.

1 0

no OSD provider available - using dummy OSD!
by Rainer Zocholl 04 Apr '05

04 Apr '05

Sorry if this is solved with a newer version, but i did not find a hint. (I still run 1.3.18) if found a very strange and "unnice" behavior of when trying to record TV6;X-Gate:12610:vC56:S19.2E:22000:100:101=deu:4201:0:12301:1:1112:0 After one hour of recording (in the background!) the TV screen of the running replay(!) becomes black and the remote control does not work any more. A reboot does not help. That's reproducible! Nearer investitgation shows, that for a few second "ARD" channel is displayed and then the screen becomes black again. /var/log/syslog fills with vdr[19538]: info: Channel not available! vdr[19538]: ERROR: no OSD provider available - using dummy OSD! vdr[19538]: switching to channel 4 vdr[19538]: info: Channel not available! A cold reboot shows that VDR runs into "panic" and tries to do a restart of itself a few second after it resumes the recording. 55:03 vdr[18461]: non blocking file reader thread started(pid=18461, tid=3375120) 03:01 vdr[12923]: ERROR: video data stream broken 03:01 vdr[12923]: initiating emergency exit 03:02 vdr[1659]: emergency exit requested - shutting down 03:02 vdr[12924]: recording thread ended (pid=12924, tid=3178513) 03:02 vdr[12923]: file writer thread ended (pid=12923,tid=3162126) 03:02 vdr[1659]: cTS2PES got 0 TS errors, 2 TS continuity errors 03:02 vdr[1659]: cTS2PES got 1 TS errors, 4 TS continuity errors 03:02 vdr[1659]: buffer stats: 65988 (1%) used 03:02 vdr[1659]: timer 114 (...) stop 03:02 vdr[18461]: non blocking file reader thread ended (pid=18461, tid=3375120) 03:02 vdr[18460]: dvbplayer thread ended (pid=18460,tid=3358733) 03:02 vdr[1659]: saved setup to /video0/setup.conf 03:02 vdr[1663]: tuner on device 1 thread ended (pid=1663, tid=16386) 03:21 vdr[19538]: VDR version 1.3.18 started 03:31 vdr[19538]: no free DVB device to record channel 108! I assume the channel is alternating between encrypted and not (without signaling it?). VDR missinterprets the encryption as "data stream broken" :-( I can reproduce the dying vdr simply by starting a recording on that channel. (Remember: EPG data is present!) Question: Why is it still required that VDRs reaction is so hard? I remember 4 years back: at that time it was OK, as too many problems existed. But today? Why can't VDR display a begign on screen message "Videos data stream broken during recording, OK=restart, all other suspends recording for today?" for say 5 minutes (If there were really a "stream broken", it would not matter if restarting now or in 5 minutes! The recording is bad anyway. But would matter a lot if the instant restart would break other recordings)! Or just record the black screen as it was told by the user? Rainer

2 1

mp3: how to remove track from playlist during play?
by Markku Tavasti 04 Apr '05

04 Apr '05

Is there some easy way to remove track from playlist during play. For me it is very common to find some particular track worthless during listening music, and therefore remove it from playlist permanently. However, I don't see any possibility for it, can this be true? For me it is the most often needed function on mp3player! -- M. Tavasti / tavasti(a)tavastisolutions.com / +358-40-5078254

3 6

ANNOUNCE: patches for graphlcd-0.1.2-pre5 freetype2 runtime rendering + complete romanian i18n
by Lucian Muresan 03 Apr '05

03 Apr '05

Hi, I finished reworking my FT2 patches against the latest pre-release of graphlcd. Of course, you must have a freetype-2.1.x library installed, and some TTF fonts if you want to try this. Those who want to try this, please: 1. Download the library patch from http://www.muresan.de/graphlcd/vdr/graphlcd-base-0.1.2-pre5_FT2.diff.bz2 and patch graphlcd-base after running a dos2unix over ./graphlcd-base-0.1.2-pre5/glcddrivers/serdisp.c ./graphlcd-base-0.1.2-pre5/glcddrivers/serdisp.h first. 2. After patching, HAVE_FREETYPE2=1 is already defined in Make.config so there is no need to enable it by yourself. Follow the normal instructions provided in the package to build & install. 3. Download the plugin patch from http://www.muresan.de/graphlcd/vdr/vdr-graphlcd-0.1.2-pre5_FT2.diff.bz2 and patch the original plugin vdr-graphlcd-0.1.2-pre5.tgz 4. Before proceeding with building and installing as you normally would, mkdir ./graphlcd-0.1.2-pre5/graphlcd/fonts/ttf and then make 3 symlinks in that newly created directory (in the source tree of the plugin, then they will be copied upon installing) pointing to actual TTF files on your machine (it could even be the same file if you wish, you will play with the size and the actual symlinks to different fonts later), with these names: ./graphlcd-0.1.2-pre5/graphlcd/fonts/ttf/fLarge.ttf -> /usr/share/fonts/corefonts/trebucbd.ttf ./graphlcd-0.1.2-pre5/graphlcd/fonts/ttf/fNormal.ttf -> /usr/share/fonts/corefonts/trebuc.ttf ./graphlcd-0.1.2-pre5/graphlcd/fonts/ttf/fSmall.ttf -> /usr/share/fonts/corefonts/trebuc.ttf 5. Install & build like you normally would Notes about usage ================= - Start VDR with the graphlcd plugin (you should still see the native fonts on your display at this time if you didn't mess with VDR's setup.conf already), go to it's configuration menu and enable true type fonts, then you have to close and start again (I hope this won't be necessary in future versions, I already took first steps in preparing the cFont class in the library for this). After restarting you will hopefully already see the TTF you've symlinked to on your display. You now may go again to the graphlcd configuration menu and adjust the sizes of the three fonts (theese options appear only when the plugin is started with graphlcd.UseFreeType2Fonts = 1 which is reated after your first run), unfortunately you have to restart every time to see the results of the size modification. You may also manually alter the entries in VDR's setup.conf while VDR is not running, that might be quicker, here are my settings I use with the symlinked fonts above on a 128x64 display (almost perfect results) graphlcd.UseFreeType2Fonts = 1 graphlcd.FreeType2SizeLarge = 11 graphlcd.FreeType2SizeNormal = 10 graphlcd.FreeType2SizeSmall = 9 If you want to revert to the native bitmap fonts, just set UseFreeType2Fonts = 0 in the file or in the configuration menu. - the character encoding is automatically selected according to VDR's OSD language, there is no separate option right now. - I only tested the FT2 stuff on my 128x64 display and it's not perfect even there, so expect strange layouts, but please try it and report. Have phun! Lucian Muresan P.S. @Andreas, I'll post another more technical one.

2 3

Motorised dish tuning delays and vdr
by Seppo Ingalsuo 03 Apr '05

03 Apr '05

Hi, Have you seen problems in getting picture after first channel change which requires dish movement? I'm controlling motorized dish directly trough diseqc.conf without rotor or actuator plugins. I didn't have problems with earlier VDR 1.3.x versions. Since upgrading from linux 2.6.9 to 2.6.11 I have seen occassionally similar problems even with DVB-T when new channel is on different frequency (multiplexes A, B, C). What is the corrent place to experiment with VDR tuning timeout values? BR, Seppo

2 6

Re: [vdr] Compiling VDR 1.3.20 in LinEspa0.30&In-Reply-to=&In-Reply-To=424EB117.6090302@tiscali.es
by ElChef 03 Apr '05

03 Apr '05

HGM.bg (GMX) escribió: >ElChef wrote: > > > >>I deleted it from osd.h >>Lines: >>106 // void __user *data; >>107 void *data; >> >>And from video.h >>Lines: >>105 // char __user *iFrame; /* pointer to a single >>iframe >>in memory */ >>106 char *iFrame; >> >> > >That's what i always do. > > > >>In Makefile: >>CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual -D__user >> >> > >I don't use that define -> -D__user > > > >>And now: >>In file included from ../DVB/include/linux/videodev.h:8, >> from dvbdevice.c:20: >>../DVB/include/linux/videodev2.h:436: error: error de decodificación >> before numeric constant >>../DVB/include/linux/videodev2.h:438: error: la declaración no >>declara nada} ../DVB/include/linux/videodev2.h:438: error: error de >> decodificación before numeric constant >> >> > >I don't have a videodev2.h ! My problem is that i don't understand the >spanish errors, you might do a 'export LANG=EN_en' or something similiar >to get english error-messages. > > > >>In file included from dvbdevice.c:20: >>../DVB/include/linux/videodev.h:225: error: error de decodificación >> before numeric constant >>En el fichero incluído de ../DVB/include/linux/dvb/video.h:27, >> de dvbdevice.c:24: >>../DVB/include/linux/compiler.h:11:1: aviso: se redefinió "__user" >><línea de orden>:5:1: aviso: esta es la ubicación de la definición >>previa In file included from dvbdevice.c:24: >> ../DVB/include/linux/dvb/video.h:106: error: error de >>decodificación before `*' token >>dvbdevice.c: En member function `virtual void >> cDvbDevice::StillPicture(const uchar*, int)': >>dvbdevice.c:1103: error: conversión inválida de `char*' a `char' >>dvbdevice.c:1109: error: conversión inválida de `char*' a `char' >>make: *** [dvbdevice.o] Error 1 >> >> > >Please tell me, which dvb-drivers you are using ? Which kernel etc.pp. > >I use the dvb-drivers from cvs that might be a difference. Please >describe to the list your software-config, so anyone else can help :) > > > >>I'm a newbie in C++ and in compilation errors... what I'm doing wrong? >> >> > >You are not that far away from success :) > >/hgm.bg > > > > The DVBDIR of the Makefile is the clue, I change it to: DVBDIR = ../DVB/include/linux or the same, remove the DVB symlink and remake it with: root@LinEspa:/usr/src# ln -s /usr/src/linux/include/linux DVB and let the DVBDIR = ../DVB and anything goes, with or without deleting __user from osd.h and video.h Thanks a lot!

1 0

Re: [vdr] Compiling VDR 1.3.20 in LinEspa0.30&In-Reply-to=&In-Reply-To=424EB117.6090302@tiscali.es
by ElChef 03 Apr '05

03 Apr '05

HGM.bg (GMX) escribió: >ElChef wrote: > > > >>I deleted it from osd.h >>Lines: >>106 // void __user *data; >>107 void *data; >> >>And from video.h >>Lines: >>105 // char __user *iFrame; /* pointer to a single >>iframe >>in memory */ >>106 char *iFrame; >> >> > >That's what i always do. > > > >>In Makefile: >>CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual -D__user >> >> > >I don't use that define -> -D__user > > > >>And now: >>In file included from ../DVB/include/linux/videodev.h:8, >> from dvbdevice.c:20: >>../DVB/include/linux/videodev2.h:436: error: error de decodificación >> before numeric constant >>../DVB/include/linux/videodev2.h:438: error: la declaración no >>declara nada} ../DVB/include/linux/videodev2.h:438: error: error de >> decodificación before numeric constant >> >> > >I don't have a videodev2.h ! My problem is that i don't understand the >spanish errors, you might do a 'export LANG=EN_en' or something similiar >to get english error-messages. > > > >>In file included from dvbdevice.c:20: >>../DVB/include/linux/videodev.h:225: error: error de decodificación >> before numeric constant >>En el fichero incluído de ../DVB/include/linux/dvb/video.h:27, >> de dvbdevice.c:24: >>../DVB/include/linux/compiler.h:11:1: aviso: se redefinió "__user" >><línea de orden>:5:1: aviso: esta es la ubicación de la definición >>previa In file included from dvbdevice.c:24: >> ../DVB/include/linux/dvb/video.h:106: error: error de >>decodificación before `*' token >>dvbdevice.c: En member function `virtual void >> cDvbDevice::StillPicture(const uchar*, int)': >>dvbdevice.c:1103: error: conversión inválida de `char*' a `char' >>dvbdevice.c:1109: error: conversión inválida de `char*' a `char' >>make: *** [dvbdevice.o] Error 1 >> >> > >Please tell me, which dvb-drivers you are using ? Which kernel etc.pp. > >I use the dvb-drivers from cvs that might be a difference. Please >describe to the list your software-config, so anyone else can help :) > > > >>I'm a newbie in C++ and in compilation errors... what I'm doing wrong? >> >> > >You are not that far away from success :) > >/hgm.bg > > > > Well, now the erros in english: Makefile now have: CXXFLAG = osd.h and video.h without __user Errors: In file included from ../DVB/include/linux/videodev.h:8, from dvbdevice.c:20: ../DVB/include/linux/videodev2.h:436: error: parse error before `*' token ../DVB/include/linux/videodev2.h:438: error: variable or field `__user' declared void ../DVB/include/linux/videodev2.h:438: error: declaration of `int v4l2_window::__user' ../DVB/include/linux/videodev2.h:436: error: conflicts with previous declaration `v4l2_clip v4l2_window::__user' ../DVB/include/linux/videodev2.h:438: error: parse error before `*' token In file included from dvbdevice.c:20: ../DVB/include/linux/videodev.h:225: error: parse error before `*' token make: *** [dvbdevice.o] Error 1 I got kernel 2.6.8.1 of a Debian distro, LinEspa, as I said in my first post, I think I must update to kernel 2.6.8.11 and apply patches from http://dl.bytesex.org/patches/ and pray for luck! don't?

1 0

Compiling VDR 1.3.20 in LinEspa 0.30&In-Reply-to=
by ElChef 03 Apr '05

03 Apr '05

I don't find __user in osd.h, don't find video.h, and suppose that it was videodir.h but I can't find __user in it. I search also only for "user" and I found nothing... Which version of vdr are using? I'm trying vdr 1.3.20

3 4

Out of Office replies
by Johannes Stezenbach 02 Apr '05

02 Apr '05

FYI: If you get Out-of-Office replies or similar from someone's auto-replier when posting to the list, and it annoys you, you can tell vdr-owner(a)linuxtv.org about it. Mail delivery to those people will then be suspended. Johannes

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr