vdr June 2009

vdr@linuxtv.org

71 participants
75 discussions

TeVii S650 missing remote keys PATCH
by gimli 13 Jun '09

13 Jun '09

Hi, the attached patch is against : http://mercurial.intuxication.org/hg/s2-liplianin It adds the missing remote keys found on the TeVii Remote for the S650 usb device. Now i have the remote fully working ;) cu Edgar (gimli) Hucek

2 7

vdr Digest, Vol 53, Issue 17
by Mr. Tux 13 Jun '09

13 Jun '09

What if the broadcaster does not send RST signal 2? I never see any other status signal in syslog than status 4 with this broadcaster. > Message: 7 > Date: Sat, 13 Jun 2009 11:47:59 +0200 > From: Klaus Schmidinger <Klaus.Schmidinger(a)cadsoft.de> > Subject: Re: [vdr] howto change time of epg grap? > > If a channel is recorded using "VPS" (which is implemented by using the > PDC descriptors), a particular event has its official broadcast time > encoded in the PDC descriptor, and that's how VDR assigns an event to > the timer. Whatever that event's data is at the time the recording starts > (which happens when the "running status" of the event goes to 2) will be > stored as the recording's info. > I don't see how "waiting a few minutes" would do any good here. > > Klaus

2 1

howto change time of epg grap?
by Mr. Tux 13 Jun '09

13 Jun '09

hello >From what I observe vdr is waiting to grap the epg content of a timed recording until this recording starts. There are a bunch of channels where this leads to unwelcome side effects: - Take a channel that is using place holder events in the "now" section of epg during commerical breaks between two events. - Take a channel that is broadcasting only one status signal, timed to the ending of each event. So you have the whole comerical break recorded as well. Vdr will start the recording with the status signal - this one bumps right into the beginning of the placeholder event. Thus the epg data vdr grabs is from the placeholder event, thus it is empty. I know it is the broadcasters fault, not vdr - I assume broadcasters using digital vps should *never* switch now/next epg events before the next event is indeed running. They sure can use place holder events between two scheduled events, but if they decide to do so, they should wait switching now/next event until the next event starts. If my broadcaster only could stick to this rule of thumb, there couldn't be a problem, sadly he never does. What can I do? I'd like vdr to wait a few minutes until he grabs epg data - or vdr could grab the epg data right away when I add the timer. Both ways sould be working. _________________________________________________________________ http://redirect.gimas.net/?n=M0906xWLM2009 Neu: Messenger 2009! Hier kostenlos downloaden!

2 1

making VDR ext4-ready
by Marcel Witte 13 Jun '09

13 Jun '09

Hi, today I've read an interesting article about ext4: http://www.heise.de/open/Das-Linux-Dateisystem-Ext4--/artikel/138431 (german, but there is also an english version). The new file system seems to be better for large files, as VDR-recordings are. Files up to 512 MB can be saved with just 1 inode, instead of a half Megabyte of inodes in ext3. So ext4 seems to be perfect for a video-partition, but to make it more perfect, it would be nice if VDR could use the fallocate()-systemcall as mentioned in the article. This would prevent fragmentation in the file system. For more information you should read the article ;) Greets, Marcel

8 10

Wrong OSD values in setup.conf (was: Re: vdr-xine-0.9.2 - ERROR: cOsd::SetAreas returned 5)
by Andreas Mair 13 Jun '09

13 Jun '09

Hi, check your setup.conf. Mine has invalid sizes: FontFix = Courier:Bold FontFixSize = 0 FontFixSizeP = 0,000000 FontOsd = VDRSymbols Sans:Bold FontOsdSize = 0 FontOsdSizeP = 0,000000 FontSml = VDRSymbols Sans:Book FontSmlSize = 0 FontSmlSizeP = 0,000000 OSDHeight = 0 OSDHeightP = 0,000000 OSDLanguage = de_DE OSDLeft = 0 OSDLeftP = 0,000000 OSDTop = 0 OSDTopP = 0,000000 OSDWidth = 0 OSDWidthP = 0,000000 As you can see they are are all "0". I don't know how that could happen, but I already had that on two VDR instances. Both upgraded from VDR 1.6.0. After setting them once in VDR 1.7 they are fine. What skin do you use? My own EnigmaNG skin (CVS release) takes care of invalid values ;) Regards, Andreas 2009/6/9 Reinhard Nissl <rnissl(a)gmx.de>: > Hi, > > Goga777 schrieb: > >> how can I fix my problem with ERROR: cOsd::SetAreas returned 5 > > This number matches the enum value oeWrongAlignment. In VDR's > code excerpt you can see the condition for this error: > > if (Areas[i].x1 > Areas[i].x2 || Areas[i].y1 > Areas[i].y2 || > Areas[i].x1 < 0 || Areas[i].y1 < 0) > return oeWrongAlignment; > >> Jun 9 21:25:39 arvdr vdr: [12294] vdr-xine: new OSD(0, -108) requested with coordinates out of range >> Jun 9 21:25:39 arvdr vdr: [12294] ERROR: cOsd::SetAreas returned 5 > > I've no idea why a vanilla VDR-1.7.7 should produce such an > incorrect OSD setup. > > Bye. > -- > Dipl.-Inform. (FH) Reinhard Nissl > mailto:rnissl@gmx.de > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > -- http://andreas.vdr-developer.org --- VDRAdmin-AM & EnigmaNG & VDRSymbols VDR user #303

3 4

Can't compile vdr. Error in recording.c [SOLVED]
by krzychp 10 Jun '09

10 Jun '09

Sorry, this was trouble with gcc 4.4 solution is here http://www.linuxtv.org/pipermail/vdr/2009-June/020743.html

1 0

Can't compile vdr. Error in recording.c
by krzychp 10 Jun '09

10 Jun '09

Hi! I have kernel 2.6.30 (but on 2.6.29 it happen to). I use driver for skystar hd s2-liplianin witch patch v4l-dvb-header-fix.diff and conpile break like here. Can somebody help me? g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DUSE_CMDRECCMDI18N -DUSE_CMDSUBMENU -DUSE_CUTTIME -DUSE_DDEPGENTRY -DUSE_DOLBYINREC -DUSE_LIEMIEXT -DUSE_PLUGINMISSING -DUSE_SETTIME -DUSE_WAREAGLEICON -DREMOTE_KBD -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVIDEODIR=\"/LMC/PLIKI/VDR\" -DCONFDIR=\"/LMC/CONF/vdrconfig\" -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"/usr/share/locale\" -DUSE_PLUGINAPI -I/usr/include/freetype2 -I/usr/src/s2-liplianin/linux/include recording.c recording.c: In constructor ‘cRecording::cRecording(cTimer*, const cEvent*)’: recording.c:664: error: invalid conversion from ‘const char*’ to ‘char*’ recording.c:665: error: invalid conversion from ‘const char*’ to ‘char*’ recording.c: In constructor ‘cRecording::cRecording(const char*)’: recording.c:730: error: invalid conversion from ‘const char*’ to ‘char*’ recording.c: In member function ‘void cRecordings::DelByName(const char*)’: recording.c:1789: error: invalid conversion from ‘const char*’ to ‘char*’ make: *** [recording.o] Error 1

1 0

vdr-xine-0.9.2 - ERROR: cOsd::SetAreas returned 5
by Goga777 09 Jun '09

09 Jun '09

Hi how can I fix my problem with ERROR: cOsd::SetAreas returned 5 Jun 9 21:25:26 arvdr vdr: [12294] VDR version 1.7.7 started Jun 9 21:25:26 arvdr vdr: [12294] codeset is 'UTF-8' - known Jun 9 21:25:26 arvdr vdr: [12294] found 23 locales in ./locale Jun 9 21:25:26 arvdr vdr: [12294] loading plugin: ./PLUGINS/lib/libvdr-xine.so.1.7.7 Jun 9 21:25:26 arvdr vdr: [12294] loading /video/setup.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/sources.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/diseqc.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/channels.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/timers.conf Jun 9 21:25:26 arvdr vdr: [12294] loading /video/svdrphosts.conf Jun 9 21:25:26 arvdr vdr: [12295] video directory scanner thread started (pid=12294, tid=12295) Jun 9 21:25:26 arvdr vdr: [12295] video directory scanner thread ended (pid=12294, tid=12295) Jun 9 21:25:26 arvdr vdr: [12296] video directory scanner thread started (pid=12294, tid=12296) Jun 9 21:25:26 arvdr vdr: [12296] video directory scanner thread ended (pid=12294, tid=12296) Jun 9 21:25:26 arvdr vdr: [12294] reading EPG data from /video/epg.data Jun 9 21:25:26 arvdr vdr: [12294] probing /dev/dvb/adapter0/frontend0 Jun 9 21:25:26 arvdr vdr: [12294] device 1 provides DVB-S2 ("Conexant CX24116/CX24118") Jun 9 21:25:26 arvdr vdr: [12298] tuner on device 1 thread started (pid=12294, tid=12298) Jun 9 21:25:26 arvdr vdr: [12299] section handler thread started (pid=12294, tid=12299) Jun 9 21:25:26 arvdr vdr: [12294] found 1 video device Jun 9 21:25:26 arvdr vdr: [12294] initializing plugin: xine (0.9.2): Software based playback using xine Jun 9 21:25:26 arvdr vdr: [12300] XineRemote control thread started (pid=12294, tid=12300) Jun 9 21:25:26 arvdr vdr: [12300] Entering cXineRemote thread Jun 9 21:25:26 arvdr vdr: [12294] setting primary device to 2 Jun 9 21:25:26 arvdr vdr: [12294] assuming manual start of VDR Jun 9 21:25:26 arvdr vdr: [12294] SVDRP listening on port 2001 Jun 9 21:25:26 arvdr vdr: [12294] setting current skin to "sttng" Jun 9 21:25:26 arvdr vdr: [12294] loading /video/themes/sttng-default.theme Jun 9 21:25:26 arvdr vdr: [12294] starting plugin: xine Jun 9 21:25:28 arvdr vdr: [12303] KBD remote control thread started (pid=12294, tid=12303) Jun 9 21:25:28 arvdr vdr: [12294] ERROR: remote control XineRemote not ready! Jun 9 21:25:28 arvdr vdr: [12294] remote control KBD - learning keys Jun 9 21:25:28 arvdr vdr: [12294] ERROR: cOsd::SetAreas returned 5 Jun 9 21:25:38 arvdr vdr: [12294] switching to channel 3 Jun 9 21:25:39 arvdr vdr: [12311] receiver on device 1 thread started (pid=12294, tid=12311) Jun 9 21:25:39 arvdr vdr: [12312] TS buffer on device 1 thread started (pid=12294, tid=12312) Jun 9 21:25:39 arvdr vdr: [12294] OSD size changed to 720x576 @ 4:3 Jun 9 21:25:39 arvdr vdr: [12294] vdr-xine: new OSD(0, -108) requested with coordinates out of range Jun 9 21:25:39 arvdr vdr: [12294] ERROR: cOsd::SetAreas returned 5 Jun 9 21:25:48 arvdr vdr: [12298] frontend 0 timed out while tuning to channel 3, tp 110744

2 1

Re: [vdr] need help with GOTOX patch.
by lucian orasanu 09 Jun '09

09 Jun '09

I did that, i took my position with an gps, putet ther in lnb config, and afther that changing channels.conf form diferent satelites, but i did something wrong because i did not manage to get signal, until i setup my antena manualy again (form left right switches of motor). My idea was to use this patch and stored position from my motor!! --- On Tue, 6/9/09, Ales Jurik <ajurik(a)quick.cz> wrote: > From: Ales Jurik <ajurik(a)quick.cz> > Subject: Re: [vdr] need help with GOTOX patch. > To: vdr(a)linuxtv.org > Cc: "lucian orasanu" <o_lucian(a)yahoo.com> > Date: Tuesday, June 9, 2009, 1:31 PM > On Tuesday 09 of June 2009, lucian > orasanu wrote: > > Hy, > > > > I want to use this patch, but i dont know how. Only > this is necesary to > > move the motor: > > > > S5.0W 11700 V 9750 G v t > > S5.0W 99999 V 10600 G v T > > S5.0W 11700 H 9750 G V t > > S5.0W 99999 H 10600 G V T > > > > > > or should be like this: > > > > S1.0W 11700 V 9750 G v t [e0 31 6e 01(this bite > should be positon in rotor > > ?] S1.0W 99999 V 10600 G v T [e0 31 6e 01] > > S1.0W 11700 H 9750 G V t [e0 31 6e 01] > > S1.0W 99999 H 10600 G V T [e0 31 6e 01] > > > > with settings like this my motor wont move! > The first config should be ok. > > > > And in lnb setup menu at degres what should i put > there, my position? > Yes, your position. > > > > How this pach works?? > Patch is originaly written by Seppo Ingalsuo > (http://www.linuxtv.org/pipermail/vdr/2008-March/016164.html). > > The patch uses algo from vdr-rotor patch to calculate angle > to which motor > should move and send then the gotox diseqc command [e0 31 > 6e p1 p2] where p1 > and p2 is calculated angle. If you have dish with closer > beam be sure to have > position of satellites in sources.conf and channels.conf > written in right way > (for example satellites at 1.0W are at 0.83W and 0.75W > exactly) to be able to > receive also weaker transponders. > > The patch send this command only when satellite is > changing. You should also > use it for motor behind diseqc switch. The next example is > for 4-input diseqc > switch which has diseqc motor connected to input 4. Please > be sure that in > such way your dvb card will not be overloaded with output > current (you should > use motor which disconnect LNB when moving and card with > electronically > limited output current to prevent damages). > > S0.8W 11700 V 9750 t v > W15 [E0 10 38 FC] W150 G v t > S0.8W 99999 V 10600 t v W15 > [E0 10 38 FD] W150 G v T > S0.8W 11700 H 9750 t V > W15 [E0 10 38 FE] W150 G V t > S0.8W 99999 H 10600 t V W15 > [E0 10 38 FF] W150 G V T > > BR, > > Ales > >

2 1

need help with GOTOX patch.
by lucian orasanu 09 Jun '09

09 Jun '09

Hy, I want to use this patch, but i dont know how. Only this is necesary to move the motor: S5.0W 11700 V 9750 G v t S5.0W 99999 V 10600 G v T S5.0W 11700 H 9750 G V t S5.0W 99999 H 10600 G V T or should be like this: S1.0W 11700 V 9750 G v t [e0 31 6e 01(this bite should be positon in rotor ?] S1.0W 99999 V 10600 G v T [e0 31 6e 01] S1.0W 11700 H 9750 G V t [e0 31 6e 01] S1.0W 99999 H 10600 G V T [e0 31 6e 01] with settings like this my motor wont move! And in lnb setup menu at degres what should i put there, my position? How this pach works??

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr June 2009