vdr June 2009

vdr@linuxtv.org

71 participants
75 discussions

[ANNOUNCE] vdr-text2skin-1.2
by Thomas Günther 08 Jun '09

08 Jun '09

Hello! This is the first release of the VDR Text2skin plugin from http://projects.vdr-developer.org. New develpment site: http://projects.vdr-developer.org/projects/show/plg-text2skin Downloads: http://projects.vdr-developer.org/projects/list_files/plg-text2skin Git-Web: http://projects.vdr-developer.org/git/?p=vdr-plugin-text2skin.git Anonymous Git-access : git://projects.vdr-developer.org/vdr-plugin-text2skin.git This is now intended to be a community maintained project! Please report any bugs, ideas or feature requests to the project site (no registration required for this!). If you want to contribute patches, new features or whatever, post an issue or patch to the projects issue tracker or request to join the project. I would happily add everyone as a project member, who would like to contribute to the project! Recent Changes: - Moved to http://projects.vdr-developer.org/projects/show/plg-text2skin as community maintained project using a GIT archive - adopted to newer VDR >= 1.3.38 - fixed possible buffer overflow in xml reading - Fix build with gcc 4.3's cleaned up C++ headers - Make compatible with VDR >= 1.5.4 - Added gettext support (VDR >= 1.5.7) The skins have to be patched, too. The patches for DeepBlue, Enigma and enElchi are ready for download from http://toms-cafe.de/vdr/download/. To patch other skins the Makefile from these patches could be used without any changes, missing translation entries should be added to the *.skin file (e.g. as comments ) - Fix font problems with libfreetype6 >= 2.2.1 - Replaced 'uint64' with 'uint64_t' to avoid problems on 64-bit machines - Quick fix for VDR >= 1.7.3 - Use pkg-config - Convert docs to UTF-8 - Updated project homepage url in README Tom

2 1

Build failures with gcc 4.4
by Ville Skyttä 08 Jun '09

08 Jun '09

Hello, I'm trying to build VDR 1.6.0-2 for the upcoming Fedora 11 release which has gcc 4.4. There are a bunch of compilation errors as gcc has again become less forgiving for C++ than it used to be. One very common source of problems is explained here: http://markmail.org/message/e5y6atneqztuvpw6#query: +page:1+mid:hdkehz7bgl5b6vgc+state:results There are quite a few of these problems in VDR 1.6.0-2 ("error: invalid conversion from 'const char*' to 'char*'"). I started patching but quickly realized that this is a job for someone who actually knows what he's doing. Anyway, attached is a patch against VDR 1.6.0-2 that fixes the first few of these errors. Approach with caution: I'm fairly confident that for example the changes to cRecordings::DelByName are not the right thing to do but then again I might not understand what it's doing anyway (changing the extension of the filename to .del but not actually renaming the file accordingly?). In addition to these errors, similar ones exist at least in StatNearestDir (videodir.c) cSVDRP::CmdGRAB. Help appreciated! By the way, in case someone runs into it, some recent changes in DVB headers (as in current Fedora devel) have caused other unrelated compilation issues, -D__KERNEL_STRICT_NAMES appears to be needed to get compilation past dvbdevice.c. See https://bugzilla.redhat.com/show_bug.cgi?id=483644

3 4

repeat Vol key
by martinez＠embl.de 08 Jun '09

08 Jun '09

Date: Sun, 7 Jun 2009 19:30:34 +0200 From: Gerald Dachs <vdr(a)dachsweb.de> Subject: Re: [vdr] repeat vol key To: vdr(a)linuxtv.org Message-ID: <20090607193034.5ef1f902@master> Content-Type: text/plain; charset=US-ASCII I use the remote that comes with the Hauppagge S2-HD (and hence connected to the card itself) lirc connects to this remote vi/dev/input/by-path/pci-0000:01:0a.0--event-ir This is part of my /etc/lircd.conf name NOVA-HD-S2 bits 16 eps 30 aeps 100 one 0 0 zero 0 0 pre_data_bits 16 pre_data 0x1 gap 199999 min_repeat 1 toggle_bit 1 Am Sun, 7 Jun 2009 19:01:00 +0200 schrieb martinez(a)embl.de: in /etc/vdr/remote.conf I have (among others) these two entries: LIRC.Volume+ VolumeUp LIRC.Volume- VolumeDown My wife complains that to increase the volume she has to press many times VolumeUp rather than simply hold it down. Is there something I can do to make her happy? Recently I have read about some simple USB IR receivers that don't send the toggle bit that lirc needs to recognize the hold of a button. I suppose you use one of them, because normally it works like your wife expects. So I believe you should exchange the IR receiver.

1 0

Re: [vdr] vdr-sxfe doesn't work correctly with keyboard
by martinez＠embl.de 07 Jun '09

07 Jun '09

Hi Goga, remove XKeySym.Up >Up XKeySym.Down >Down does it fix up and down? then remove the numbers 2

2 1

repeat vol key
by martinez＠embl.de 07 Jun '09

07 Jun '09

in /etc/vdr/remote.conf I have (among others) these two entries: LIRC.Volume+ VolumeUp LIRC.Volume- VolumeDown My wife complains that to increase the volume she has to press many times VolumeUp rather than simply hold it down. Is there something I can do to make her happy?

2 1

vdr-sxfe doesn't work correctly with keyboard
by Goga777 06 Jun '09

06 Jun '09

Hi my system is server - debian + kernel 2.6.29 + vdr 177 + s2-liplanin + hvr4000 + cvs xineliboutput + vdr-xine from hg remote client - debian + vdr-sxfe from cvs xineliboutput + xine-lib-1.2 from hg I have the problem with keyboard on remote frontend computer (vdr-sxfe) For example - If I press and after that release the any digital button ("2" or "5") I have the "22" or "55" results - not "2" or "5" as usual . Another example - If I press and release the button UP or DOWN the cursor will move on TWO lines to up or to down. The problem is when I released the button - after release of button I have second event - double figure or double moving. Also I couldn't use the pipe connection , rtp, udp protocols - only tcp connection Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Trying PIPE connection ... Jun 6 11:44:37 arvdr vdr: [17202] creating directory /video/plugins/xineliboutput/pipes.17195 Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Pipe not opened by client Jun 6 11:44:37 arvdr vdr: [17202] removing /video/plugins/xineliboutput/pipes.17195 Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Trying RTP connection ... Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] RTP transport not implemented for vdr-1.7.x Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Trying UDP connection ... Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] UDP transport not implemented for vdr-1.7.x logs from vdr 177 arvdr:/vdr# ./vdr -P"xineliboutput --local=none --remote=37890" Jun 6 11:43:45 arvdr vdr: [17195] cTimeMs: using monotonic clock (resolution is 1 ns) Jun 6 11:43:45 arvdr vdr: [17195] VDR version 1.7.7 started Jun 6 11:43:45 arvdr vdr: [17195] codeset is 'UTF-8' - known Jun 6 11:43:45 arvdr vdr: [17195] found 23 locales in ./locale Jun 6 11:43:45 arvdr vdr: [17195] loading plugin: ./PLUGINS/lib/libvdr-xineliboutput.so.1.7.7 Jun 6 11:43:45 arvdr vdr: [17195] loading /video/setup.conf Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] Skipping configuration entry Frontend=sxfe (overridden in command line) Jun 6 11:43:45 arvdr vdr: [17195] loading /video/sources.conf Jun 6 11:43:45 arvdr vdr: [17195] loading /video/diseqc.conf Jun 6 11:43:45 arvdr vdr: [17195] loading /video/channels.conf Jun 6 11:43:45 arvdr vdr: [17195] loading /video/svdrphosts.conf Jun 6 11:43:45 arvdr vdr: [17195] loading /video/remote.conf Jun 6 11:43:45 arvdr vdr: [17196] video directory scanner thread started (pid=17195, tid=17196) Jun 6 11:43:45 arvdr vdr: [17196] video directory scanner thread ended (pid=17195, tid=17196) Jun 6 11:43:45 arvdr vdr: [17197] video directory scanner thread started (pid=17195, tid=17197) Jun 6 11:43:45 arvdr vdr: [17197] video directory scanner thread ended (pid=17195, tid=17197) Jun 6 11:43:45 arvdr vdr: [17195] reading EPG data from /video/epg.data Jun 6 11:43:45 arvdr vdr: [17195] probing /dev/dvb/adapter0/frontend0 Jun 6 11:43:45 arvdr vdr: [17195] device 1 provides DVB-S2 ("Conexant CX24116/CX24118") Jun 6 11:43:45 arvdr vdr: [17199] tuner on device 1 thread started (pid=17195, tid=17199) Jun 6 11:43:45 arvdr vdr: [17200] section handler thread started (pid=17195, tid=17200) Jun 6 11:43:45 arvdr vdr: [17195] found 1 video device Jun 6 11:43:45 arvdr vdr: [17195] initializing plugin: xineliboutput (1.0.90-cvs): X11/xine-lib output plugin Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] cTimePts: clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] cTimePts: using monotonic clock Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] RTP SSRC: 0x27fae0fc Jun 6 11:43:45 arvdr vdr: [17195] setting primary device to 1 Jun 6 11:43:45 arvdr vdr: [17195] device 1 has no MPEG decoder Jun 6 11:43:45 arvdr vdr: [17195] trying device number 2 instead Jun 6 11:43:45 arvdr vdr: [17195] setting primary device to 2 Jun 6 11:43:45 arvdr vdr: [17195] assuming manual start of VDR Jun 6 11:43:45 arvdr vdr: [17195] SVDRP listening on port 2001 Jun 6 11:43:45 arvdr vdr: [17195] setting current skin to "sttng" Jun 6 11:43:45 arvdr vdr: [17195] loading /video/themes/sttng-default.theme Jun 6 11:43:45 arvdr vdr: [17195] starting plugin: xineliboutput Jun 6 11:43:45 arvdr vdr: [17202] Remote decoder/display server (cXinelibServer) thread started (pid=17195, tid=17202) Jun 6 11:43:45 arvdr vdr: [17202] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99] Jun 6 11:43:45 arvdr vdr: [17202] [xine..put] Listening on port 37890 Jun 6 11:43:45 arvdr vdr: [17202] [xine..put] Listening for UDP broadcasts on port 37890 Jun 6 11:43:45 arvdr vdr: [17202] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0^M Server port: 37890^M Server vers ion: xineliboutput-1.0.90-cvs^M ^M Jun 6 11:43:45 arvdr vdr: [17195] [xine..put] cXinelibDevice::StartDevice(): Device started Jun 6 11:43:45 arvdr vdr: [17203] KBD remote control thread started (pid=17195, tid=17203) Jun 6 11:43:45 arvdr vdr: [17195] remote control KBD - learning keys Jun 6 11:43:55 arvdr vdr: [17195] switching to channel 1 Jun 6 11:43:55 arvdr vdr: [17195] info: Channel not available! Jun 6 11:43:58 arvdr vdr: [17195] switching to channel 1 Jun 6 11:43:58 arvdr vdr: [17195] info: Channel not available! Jun 6 11:44:01 arvdr vdr: [17195] OSD size changed to 720x576 @ 4:3 Jun 6 11:44:09 arvdr vdr: [17195] switching to channel 1 Jun 6 11:44:09 arvdr vdr: [17195] info: Channel not available! Jun 6 11:44:20 arvdr vdr: [17195] switching to channel 1 Jun 6 11:44:20 arvdr vdr: [17195] info: Channel not available! Jun 6 11:44:31 arvdr vdr: [17195] switching to channel 1 Jun 6 11:44:31 arvdr vdr: [17195] info: Channel not available! Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Client 0 connected: 192.168.5.88:57886 Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 225280 bytes Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Trying PIPE connection ... Jun 6 11:44:37 arvdr vdr: [17202] creating directory /video/plugins/xineliboutput/pipes.17195 Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Pipe not opened by client Jun 6 11:44:37 arvdr vdr: [17202] removing /video/plugins/xineliboutput/pipes.17195 Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Trying RTP connection ... Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] RTP transport not implemented for vdr-1.7.x Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Trying UDP connection ... Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] UDP transport not implemented for vdr-1.7.x Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Client 1 connected: 192.168.5.88:57887 Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 225280 bytes Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] Data connection (TCP) requested Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] cBackgroundWriterI initialized (buffer 512 kb) Jun 6 11:44:37 arvdr vdr: [17202] [xine..put] cTcpWriter initialized (buffer 512 kb) Jun 6 11:44:42 arvdr vdr: [17195] switching to channel 1 Jun 6 11:44:42 arvdr vdr: [17195] info: Channel not available! Jun 6 11:44:53 arvdr vdr: [17195] switching to channel 1 Jun 6 11:44:53 arvdr vdr: [17195] info: Channel not available! Jun 6 11:44:55 arvdr vdr: [17199] frontend 0 timed out while tuning to channel 27, tp 211804 Jun 6 11:45:01 arvdr /USR/SBIN/CRON[17216]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Jun 6 11:45:04 arvdr vdr: [17195] switching to channel 1 Jun 6 11:45:04 arvdr vdr: [17195] info: Channel not available! Jun 6 11:45:15 arvdr vdr: [17195] switching to channel 1 Jun 6 11:45:15 arvdr vdr: [17195] info: Channel not available! Jun 6 11:45:17 arvdr vdr: [17199] frontend 0 timed out while tuning to channel 1, tp 211881 Jun 6 11:45:25 arvdr vdr: [17195] switching to channel 26 Jun 6 11:45:25 arvdr vdr: [17358] receiver on device 1 thread started (pid=17195, tid=17358) Jun 6 11:45:25 arvdr vdr: [17359] TS buffer on device 1 thread started (pid=17195, tid=17359) Jun 6 11:45:25 arvdr vdr: [17195] [xine..put] Got PAT: PMT pid = 132 Jun 6 11:45:25 arvdr vdr: [17195] [xine..put] Got PMT packet, h264 = 0 Jun 6 11:45:26 arvdr vdr: [17195] switching to channel 27 Jun 6 11:45:26 arvdr vdr: [17359] TS buffer on device 1 thread ended (pid=17195, tid=17359) logs from vdr-sxfe goga@goga:/usr/src/vdr/PLUGINS/src/xineliboutput$ vdr-sxfe xvdr://192.168.5.86 vdr-sxfe 1.0.90-cvs (build with xine-lib 1.1.90, using xine-lib 1.1.90) VDR Server: xvdr://192.168.5.86 [5366] [vdr-fe] Detected 2 CPUs [5366] [vdr-fe] Enabling FFmpeg multithreaded video decoding [5366] [input_vdr] Connecting (control) to tcp://192.168.5.86:37890 ... [5366] [input_vdr] Server greeting: VDR-1.7.7 xineliboutput-1.0.90-cvs READY [5366] [input_vdr] Connected (control) to tcp://192.168.5.86:37890 [5366] [input_vdr] connect_pipe_data_stream: client ip=0x5805a8c0 != server ip=0x5605a8c0 ! [5366] [input_vdr] Connecting (data) to pipe:///video/plugins/xineliboutput/pipes.17195/pipe.0 [5366] [input_vdr] Pipe not found [5366] [input_vdr] Data stream connection failed (PIPE) [5366] [input_vdr] Server does not support RTP ? (RTP: RTP transport not implemented for vdr-1.7.x.) [5366] [input_vdr] Data stream connection failed (RTP) [5366] [input_vdr] Connecting (data) to udp://192.168.5.86 ... [5366] [input_vdr] Server does not support UDP ? (UDP: UDP transport not implemented vor vdr-1.7.x.) [5366] [input_vdr] Data stream connection failed (UDP) [5366] [input_vdr] Connecting (data) to tcp://192.168.5.86:37890 ... [5366] [input_vdr] Data stream connected (TCP) [5366] [input_vdr] using custom "no signal" image /etc/vdr/plugins/xine/noSignal.mpg [5366] [demux_vdr] Using decoder "libmpeg2" for mpeg2 video [5366] [demux_vdr] Using decoder "FFmpeg" for H.264 video Press Esc to exit post_warp: warp_get_parameters post_warp: warp_get_parameters my remote.conf XKeySym.Up >Up XKeySym.Down >Down XKeySym.Menu >m XKeySym.Ok >Return XKeySym.Back >BackSpace XKeySym.Left >Left XKeySym.Right >Right XKeySym.Red >F1 XKeySym.Green >F2 XKeySym.Yellow >F3 XKeySym.Blue >F4 XKeySym.0 >0 XKeySym.1 >1 XKeySym.2 >2 XKeySym.3 >3 XKeySym.4 >4 XKeySym.5 >5 XKeySym.6 >6 XKeySym.7 >7 XKeySym.8 >8 XKeySym.9 >9 XKeySym.Info >i XKeySym.Pause >space XKeySym.FastFwd>F6 XKeySym.FastRew>F5 XKeySym.Power >p XKeySym.Volume+>F12 XKeySym.Volume->F11 XKeySym.Mute >F10 XKeySym.User7 >F7 XKeySym.User8 >F8 XKeySym.User9 >F Goga

1 0

Status of WinTV-HVR-4000 card!!
by lucian orasanu 05 Jun '09

05 Jun '09

Hello, I want to buy this card, but before I wnat to know if this card works fine under linux and with vdr. Can some one tell me if is using this card and is ok?

7 9

[OT] What about the VIA VX855?
by Paul Menzel 04 Jun '09

04 Jun '09

Dear list, there has been some talk about the new ION chipset from NVIDIA on this list [1]. Intel also published a board which is said to be very promising for SD (standard definition) material [2] (at least with the FRC (frame rate control) patches [3]. So what about the VIA VX855 chipset [4] as the basis for a multimedia platform? VIA publishes the docs and it looks like it will even be supported by coreboot [5][6]. I know it depends on what you need (SD or HD and so on). But I searched for »vx855 vdr«, »vx855 xbmc«, »vx855 mythtv« on the WWW and did not get meaningfull results. Or is the problem, that there are no boards available yet? What do you think? Thanks, Paul [1] http://linuxtv.org/pipermail/vdr/2009-May/020457.html [2] http://www.vdr-portal.de/board/thread.php?threadid=86810 [3] http://frc.easy-vdr.de/ [4] http://www.tomshardware.com/news/Via-VX855-chipset,7261.html [5] http://www.coreboot.org/ [6] http://www.coreboot.org/pipermail/coreboot/2009-May/048829.html

2 1

sysinfo 0.1.0a
by Scott Waye 03 Jun '09

03 Jun '09

Hi, I am trying to get this plugin working with vdr 1.7.7. When I bring it up from the menu it segmentation faults. The relevant sections from the backtrace are : #0 0x00000000004a4b2d in cBitmap::DrawText (this=0x2acb4e0, x=10, y=3, s=0x7fdb8302fb90 "SysInfo 0.1.0a", ColorFg=4278190080, ColorBg=2164260863, Font=0x754040, Width=0, Height=0, Alignment=5) at osd.c:454 454 int w = Font->Width(s); And the full thread bt is Thread 1 (process 31944): #0 0x00000000004a4b2d in cBitmap::DrawText (this=0x2acb4e0, x=10, y=3, s=0x7fdb8302fb90 "SysInfo 0.1.0a", ColorFg=4278190080, ColorBg=2164260863, Font=0x754040, Width=0, Height=0, Alignment=5) at osd.c:454 w = <value optimized out> limit = <value optimized out> cw = <value optimized out> h = <value optimized out> ch = <value optimized out> #1 0x00000000004a5b3a in cOsd::DrawText (this=0x12b5f80, x=10, y=3, s=0x7fdb8302fb90 "SysInfo 0.1.0a", ColorFg=4278190080, ColorBg=2164260863, Font=0x754040, Width=0, Height=0, Alignment=5) at osd.c:856 i = 1 #2 0x00007fdb8325a34e in PluginXine::cXineOsd::DrawText (this=0x12b5f80, x=10, y=3, s=0x7fdb8302fb90 "SysInfo 0.1.0a", ColorFg=4278190080, ---Type <return> to continue, or q <return> to quit--- ColorBg=2164260863, Font=0x754040, Width=0, Height=0, Alignment=5) at xineOsd.c:331 osdLock = {mutex = 0x7fdb85342f40, locked = true} #3 0x00007fdb8302cc33 in cSysInfoOsd::DrawMenu (this=0x2ad3f50) at sysinfoosd.c:204 No locals. #4 0x00007fdb8302cd33 in cSysInfoOsd::PleaseWait (this=0x754040) at sysinfoosd.c:96 cTemp = "\200_+\001\000\000\000\000\222pJ\000\000\000\000\000\006\000 \000\000\000\000\000\000\200_+\001\001\000\000\000\000\000\000\000\001 \000\000\000\001\000\000\000\000\000\000\000\006\000\000\000\000\000\000 \000\200_+\001\000\000\000\000\200�N\215�\177\000\00009\225\000\000\000 \000\000\001\000\000\000\000\000\000\000\226�%\203�\177\000\000@/4\205" #5 0x00007fdb8302ce71 in cSysInfoOsd::Show (this=0x2ad3f50) at sysinfoosd.c:87 Area = {x1 = 0, y1 = 0, x2 = 623, y2 = 483, bpp = 2} #6 0x00000000004dec52 in main (argc=<value optimized out>, argv=<value optimized out>) at vdr.c:1154 state = osPlugin Now = 1243887926 Interact = (class cOsdObject *) 0xe0caf0 key = kOk savedTm = {c_iflag = 7595072, c_oflag = 0, c_cflag = 1040, c_lflag = 0, c_line = 0 '\0', c_cc = "�\217\203�\177\000\000p\231L\205�\177\000\000 \004\000\000\000 \000\000\000��\000\000\000\000�", c_ispeed = 32731, c_ospeed = 7558488} HasStdin = false StartedAsRoot = <value optimized out> VdrUser = 0x0 UserDump = false SVDRPport = 2001 AudioCommand = 0x0 ConfigDirectory = 0x7fff8d4eee6f "/etc/vdr" EpgDataFileName = 0x504bd9 "epg.data" DisplayHelp = 48 DisplayVersion = false DaemonMode = false SysLogTarget = <value optimized out> MuteAudio = false WatchdogTimeout = 60 Terminal = 0x1 <Address 0x1 out of bounds> LocaleDir = 0x0 UseKbd = true LircDevice = 0x0 RcuDevice = 0x0 PluginManager = {_vptr.cPluginManager = 0x4fac10, static pluginManager = 0x7fff8d4ede70, directory = 0x74e0b0 "/etc/vdr/plugins/lib", lastHousekeeping = 1243887910, ---Type <return> to continue, or q <return> to quit--- nextHousekeeping = 0, dlls = {<cList<cDll>> = {<cListBase> = { _vptr.cListBase = 0x4fadb0, objects = 0x74e0f0, lastObject = 0x74e1e0, count = 2}, <No data fields>}, <No data fields>}} c = <value optimized out> CodeSet = <value optimized out> Menu = (class cOsdObject *) 0x754040 LastChannel = 6 LastTimerChannel = -1 PreviousChannel = {1, 6} PreviousChannelIndex = 1 LastChannelChanged = 1243887689 LastInteract = 1243887926 MaxLatencyTime = 1 InhibitEpgScan = false IsInfoMenu = false CheckHasProgramme = false CurrentSkin = <value optimized out> long_options = {{name = 0x4f1b2d "audio", has_arg = 1, flag = 0x0, val = 97}, {name = 0x504e9d "config", has_arg = 1, flag = 0x0, val = 99}, { name = 0x504ea4 "daemon", has_arg = 0, flag = 0x0, val = 100}, { name = 0x504eab "device", has_arg = 1, flag = 0x0, val = 68}, { name = 0x504eb2 "epgfile", has_arg = 1, flag = 0x0, val = 69}, { name = 0x504eba "grab", has_arg = 1, flag = 0x0, val = 103}, { name = 0x504ebf "help", has_arg = 0, flag = 0x0, val = 104}, { name = 0x504ec4 "instance", has_arg = 1, flag = 0x0, val = 105}, { name = 0x504bd5 "lib", has_arg = 1, flag = 0x0, val = 76}, { name = 0x504ecd "lirc", has_arg = 2, flag = 0x0, val = 364}, { name = 0x504ed2 "localedir", has_arg = 1, flag = 0x0, val = 620}, { name = 0x504edc "log", has_arg = 1, flag = 0x0, val = 108}, { name = 0x501208 "mute", has_arg = 0, flag = 0x0, val = 109}, { name = 0x504ee0 "no-kbd", has_arg = 0, flag = 0x0, val = 366}, { name = 0x504ee7 "plugin", has_arg = 1, flag = 0x0, val = 80}, { name = 0x504eee "port", has_arg = 1, flag = 0x0, val = 112}, { name = 0x504ef3 "rcu", has_arg = 2, flag = 0x0, val = 370}, { name = 0x504ef7 "record", has_arg = 1, flag = 0x0, val = 114}, { name = 0x504efe "shutdown", has_arg = 1, flag = 0x0, val = 115}, { name = 0x504f07 "terminal", has_arg = 1, flag = 0x0, val = 116}, { name = 0x504f10 "user", has_arg = 1, flag = 0x0, val = 117}, { name = 0x504f15 "userdump", has_arg = 0, flag = 0x0, val = 373}, { name = 0x4f65cc "version", has_arg = 0, flag = 0x0, val = 86}, { name = 0x504f1e "vfat", has_arg = 0, flag = 0x0, val = 374}, { name = 0x504c92 "video", has_arg = 1, flag = 0x0, val = 118}, { name = 0x504f23 "watchdog", has_arg = 1, flag = 0x0, val = 119}, { name = 0x0, has_arg = 0, flag = 0x0, val = 0}} lastTime = 0 ChannelSaveTimeout = 1243888290 TimerState = 0 ---Type <return> to continue, or q <return> to quit---# LastTimerCheck = 1243887920 DeviceUsed = {0 <repeats 16 times>} to me this looks like the Font passed into DrawText is invalid. This is set up in sysinfoosd.h thus: static const cFont *font = cFont::GetFont(fontOsd); Is there something obvious here that someone with more experience of the code can spot? Thanks, Scott

4 3

vdr-xine buffer values
by martinez＠embl.de 02 Jun '09

02 Jun '09

Hi Reinhard, I have undone the offending changeset in xine-lib as per your explanation there. http://sourceforge.net/mailarchive/message.php?msg_name=4A15672E.5090908%40… Now, zapping time better. What is in your opinion the optimum buffer settings for vdr-xine and for .xine/config ? (I have a Hauppage S2-HD) These are my current settings: vdr/setup.conf xine.modeLiveTV.prebufferFrames = 11 xine.modeLiveTV.prebufferHysteresis = 4 .xine/config # number of audio buffers engine.buffers.audio_num_buffers:460 # number of video buffers engine.buffers.video_num_buffers:250 # number of video frames engine.buffers.video_num_frames:22

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr June 2009