vdr June 2006

vdr@linuxtv.org

109 participants
101 discussions

[ANNOUNCE] New plugin svdrpservice-0.0.1
by Frank Schmirler 06 Jun '06

06 Jun '06

This plugin is required by the remoteosd plugin. That's all you need to know about it unless you are a plugin developer. For developers: This plugin offers svdrp connections as service to other plugins. So if you want to develop a plugin which needs to talk to a remote SVDRP server, you might want to take a look at. The plugin offers two services: One to obtain a connection and the other to send commands. The reply is returned as a list of lines. Multiple plugins can share the same SVDRP connection which is nice as long as SVDRP cannot handle multiple connections at a time. Check the README or the remoteosd plugin for some sample code. The plugin is available at http://vdr.schmirler.de. Known issues: - Locking has not been implemented yet. Only the main loop should call the service yet unless you know what you are doing - Still have to take a closer look at error handling. If a connection is not closed properly it sometimes blocks the SVDRP port on the server until it times out. Enjoy, Frank

1 0

[ANNOUNCE] New plugins: remoteosd and svdrpext
by Frank Schmirler 06 Jun '06

06 Jun '06

I like to introduce a set of new plugins, especially useful for those running VDR in a client/server environment. With remoteosd the menu of a remote VDR becomes available as submenu of your local VDR menu. So you can e.g. edit timers or execute commands on the server. On the one hand this is more powerful than what has been offered by older versions of the streamdev plugin. However there are a few drawbacks: - as every key stroke has to be processed on the server, it is quite slow - the OSD menu pops up on the server - no concurrent access I will adress these issues with an other plugin, but I haven't started coding yet. I plan to include features like client-side editing of remote timers (just like the former streamdev feature), syncing of channels and syncing of epg in the background. Anyway, for the moment I hope the generic approach with remoteosd will help all those who miss the remote timers feature in streamdev. svdrpext, the other plugin, is currently no more than the server part of remoteosd. But most likely I will need some more svdrp commands for the other things I have on my TODO list. Both plugins and more detailed information is available on http://vdr.schmirler.de. But be warned: This is the first release. Although I have been running these plugins here without major problems it doesn't mean that there will be no problems in your environment! Enjoy, Frank

1 0

*** plugins without APIVERSION: streamdev text2skin
by foreveruni＠clix.pt 06 Jun '06

06 Jun '06

I've done that..but now: Plugin text2skin: make[1]: Entering directory `/home/antibody/Area51/vdr/vdr-1.4.0/PLUGINS/src/text2skin-1.0' g++ -Wall -Woverloaded-virtual -O2 -g -c -DHAVE_IMAGEMAGICK -DHAVE_FREETYPE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"text2skin"' -I/usr/include/freetype2 -I../../../include -I../../../../DVB/linux/include -I../../../../DVB/include -I. -o text2skin.o text2skin.c text2skin.c:16: error: expected unqualified-id before '<<' token text2skin.c:18: error: expected unqualified-id before '==' token text2skin.c:20: error: expected unqualified-id before '>>' token make[1]: *** [text2skin.o] Error 1 make[1]: Leaving directory `/home/antibody/Area51/vdr/vdr-1.4.0/PLUGINS/src/text2skin-1.0' AND Plugin streamdev: make[1]: Entering directory `/home/antibody/Area51/vdr/vdr-1.4.0/PLUGINS/src/str eamdev' g++ -W -Woverloaded-virtual -O2 -c -D_GNU_SOURCE -DHAVE_AUTOPID -I../../../inclu de -I../../../../DVB/include -I. -o streamdev-server.o streamdev-server.c make[1]: Leaving directory `/home/antibody/Area51/vdr/vdr-1.4.0/PLUGINS/src/stre amdev' *** failed plugins: streamdev text2skin Best Regards João Mamede On Friday 02 June 2006 19:58, foreveruni at clix.pt wrote: > *** plugins without APIVERSION: streamdev text2skin > when I try to compile these two plugins I have this problem my vdr version > is vdr-1.4.0 I'm crazy looking for patches..but I cannot find them :( Can > anyone help me? > Just do this to the plugin: # sed -i Makefile -e 's/VDRVERSION/APIVERSION/' Matthias -- Matthias Schwarzott *** plugins without APIVERSION: streamdev text2skin when I try to compile these two plugins I have this problem my vdr version is vdr-1.4.0 I'm crazy looking for patches..but I cannot find them :( Can anyone help me?

2 1

genindex 0.1.3
by s.huelswitt＠gmx.de 05 Jun '06

05 Jun '06

Hi, a new version of the genindex tool is availabel from my homepage. Genindex is usefull to create a VDR index file for downloaded/ ripped video files. <http://www.muempf.de/down/genindex-0.1.3.tar.gz> 05.06.2006 - Version 0.1.3 - Added mode to rewrite video files (including file splitting and removing of PES streams). - Allow a single input file >2GB in rewrite mode. -- Stefan Huelswitt s.huelswitt(a)gmx.de | http://www.muempf.de/

2 1

[OT] C't vdr dist
by Tomas Prybil 05 Jun '06

05 Jun '06

Hi list. Do any of you German readers have any idea if the C't version 5 will be released for download? The is a link to a crippled jigdo download.I guess you need the real CD image as a starting point. I would very much pay for the magazine but unfortenately my magazine stand doesn't carry C't :( BR /t

3 2

PremiereEPG plugin 0.0.6
by s.huelswitt＠gmx.de 05 Jun '06

05 Jun '06

Hi, a new version of the PremiereEPG plugin is available from my homepage. <http://www.muempf.de/down/vdr-premiereepg-0.0.6.tar.gz> 05.06.2006: Version 0.0.6 - Fixed and improved generation of EventId. You should delete your epg.data file to avoid duplicate entries. - Now using libsi code introduced in VDR 1.3.47 and fixed in 1.4.0-3. Obviously requires VDR with API version 1.4.1 or later. - Checking for broken PMT entries. - Setting event running status by looking at the start & end time. - Updated Makefile according to changes in VDR 1.3.47 (APIVERSION & DVBDIR). Regards. -- Stefan Huelswitt s.huelswitt(a)gmx.de | http://www.muempf.de/

1 0

[PATCH] jumpplay patch 0.9
by Thomas Günther 05 Jun '06

05 Jun '06

Hi! Here is a new version of the jumpplay patch: http://toms-cafe.de/vdr/download/vdr-jumpplay-0.9-1.4.0.diff (applicable to VDR >= 1.3.35) Changes since version 0.8: - New setup parameter "Pause at last mark" - Updated description in README.jumpplay - Moved parameters description to MANUAL This patch changes the replay behaviour for recordings that contain editing marks. It allows to immediately continue the replay after jumping forward to the next mark, and to automatically jump over the commercial break to the next "start" mark, if an "end" mark is reached. The features of this patch can be turned on or off in the replay setup. See README.jumpplay included in the patch for details, history and contributors. Tom

2 3

TV-out, softdevice
by Johan Linder 05 Jun '06

05 Jun '06

Hi! I've been trying for a while now to get the TV-out working smoothly. It feels like the TV-out is "computerized", like it's only 20fps or something. I've been searching the net for answers but haven't found any helping tips. Is it possible to get a smooth TV-out, or should I accept some studdering? I start vdr with: vdr -l 3 -P "softdevice -vo xv:" -P "subtitles" -P "osdteletext" vdr-1.4.0, softdevice-0.2.3 // Johan # lspci 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a2) 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev a2) 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a2) 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a2) 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a2) 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:07.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 01:07.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 05:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2) xorg.conf: Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" #HorizSync 30.0 - 70.0 HorizSync 30 - 50 #VertRefresh 50.0 - 120.0 VertRefresh 50 - 50 Modeline "720x576" 13.5 720 744 800 864 576 586 590 624 -hsync -vsync interlace EndSection Section "Device" Identifier "Card0" Driver "nvidia" VendorName "nVidia Corporation" BoardName "Unknown Board" Option "Connected Monitor" "TV" # Option "TwinView" "true" # Option "TwinViewOrientation" "Clone" Option "TVOutFormat" "SVIDEO" Option "TVStandard" "PAL-B" Option "TVOverScan" "0.6" Option "SecondMonitorHorizSync" "30-50" Option "SecondMonitorVertRefresh" "50" Option "MetaModes" "1024x768,1024x768;800x600,800x600;640x480,640x480;512x384,512x384" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 Option "dpms" Option "XvMC" Option "RenderAccel" "on" Option "Overlay" "on" Option "NoFlip" "off" Option "UBB" "on" Option "XvmcUsesTextures" "on" Option "MultisampleCompability" "on" Option "OverlayDefaultVisual" "on" Option "HWCursor" "on" Option "AllowGLXWithComposite" "on" SubSection "Display" Viewport 0 0 Depth 24 # Modes "1024x768" Modes "720x576" EndSubSection EndSection

8 13

CinergyT2 "frontend timed out" when switching to ARD
by Matthias Thomae 04 Jun '06

04 Jun '06

Hello, I've been trying to get my Cinergy T2 USB box working properly with VDR, but I get the "frontend timed out" error message sometimes when switching to ARD (or another channel in the same bouquet), and the screen remains blank (error message below). The 'sometimes' varies from 2 to maybe 20 times. After the error occurs, I can still view other channels, but none in the ARD bouquet. Restarting VDR doesn't help, neither unloading/loading the cinergyT2 kernel module. After unplugging the USB cable I can again view ARD until the error occurrs again. I tried with VDR 1.4.0-1 and 1.3.49 from e-tobi.net, kernel 2.6.17-rc4 and 2.6.15.5, on 2 different machines (one with the USB box only, one with an additional full-featured DVB-S card). The CinergyT2 is running firmware 1.08. There are similar reports on www.vdr-portal.de, one claims the problem vanished after doubling the CinergyT2 kernel tuning parameters and changing channels.conf entries from I0 to I999 (http://www.vdr-portal.de/board/thread.php?threadid=50153). I also tried this, but the problem remains. Any ideas? Regards. Matthias Jun 4 18:24:36 localhost vdr: [3760] switching to channel 19 Jun 4 18:24:36 localhost vdr: [4101] transfer thread ended (pid=4101, tid=4101) Jun 4 18:24:37 localhost vdr: [4103] TS buffer on device 1 thread ended (pid=4103, tid=4103) Jun 4 18:24:37 localhost vdr: [4102] buffer stats: 58844 (2%) used Jun 4 18:24:37 localhost vdr: [4102] receiver on device 1 thread ended (pid=4102, tid=4102) Jun 4 18:24:37 localhost vdr: [3760] buffer stats: 115996 (5%) used Jun 4 18:24:37 localhost vdr: [4106] transfer thread started (pid=4106, tid=4106) Jun 4 18:24:37 localhost vdr: [4107] receiver on device 1 thread started (pid=4107, tid=4107) Jun 4 18:24:37 localhost vdr: [4108] TS buffer on device 1 thread started (pid=4108, tid=4108) Jun 4 18:24:46 localhost vdr: [3860] frontend 0 timed out while tuning to channel 19, tp 184

1 0

[ANNOUNCE] VDR maintenance patch 1.4.0-3
by Klaus Schmidinger 04 Jun '06

04 Jun '06

VDR maintenance patch 1.4.0-3 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.0-3.diff This is a 'diff' against the official version 1.4.0 plus all previous 1.4.0-X maintenance patches (which means that you need to first apply any previously released patches before you can apply this one). Small fixes to the officially released VDR versions will be first made available as "maintenance patches" in the Developer directory, so that they can be reviewed and tested before a new official release is published. So please apply the patches ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.0-1.diff ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.0-2.diff ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.0-3.diff in the given sequence to the original VDR version 1.4.0 and report whether it works (or if it causes any new problems). If no bugs are reported, I'll release this as version 1.4.1 next weekend. The changes since version 1.4.0-2: - Fixed the PremiereContentTransmissionDescriptor in 'libsi' (thanks to Stefan Huelswitt). - Removed all the compatibility '#if APIVERSNUM...' stuff and instead increased the API version number - plugins will have to be recompiled. - Removed the call to pthread_setschedparam(childTid, SCHED_RR, 0) in thread.c, because it caused a compiler warning with g++ 4.1.1 (reported by Ville Skyttä). Since the third parameter has to be non-null to have any effect, the call was presumably a NOP, anyway. - Fixed the 'clean-plugins' target in the Makefile to also remove additional plugin libraries (thanks to Wayne Keer). - Applied the fixes to moving and deleting channels from version 1.4.0-2 to the SVDRP commands MOVC and DELC as well. - Fixed handling the display of the '*' indicator in the "What's on now/next?" menu, so that events that haven't been "seen" in the data stream within 30 seconds won't be shown as "running". - Fixed handling tabbed item display in 'skincurses'. - Increased the column spacing in the "Recordings" menu (was too small for the 'skincurses' plugin). - When the 'skincurses' plugin is loaded, it automatically sets the 'curses' skin as the current one. This doesn't modify the Setup.OSDSkin parameter, so that after using 'skincurses' (for instance for debugging) the previously selected skin will be used again. - Added some log messages when setting the current skin. - Only making a second attempt to set the current skin at startup if the first attempt has failed. - Now switching to non-VPS timers' channels 60 seconds before the timer starts (if a free device is available), to allow for the updating of EPG data and CA descriptors before the actual recording starts. Have fun! Klaus

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr June 2006