vdr January 2013

vdr@linuxtv.org

42 participants
38 discussions

UPnP/DLNA media server plugin for the VDR
by Brian-Imap 05 Jan '13

05 Jan '13

Hi, this looks to be pretty interesting. So where exactly does it fit in between XVDR, VNSI, streamdev, etc. I just bought a Samsung smart TV, haven't found a single DLNA music server that it could receive music from (sure I've heard about updating the headers that are sent from the server), still none of them worked with the TV. Seems I could watch VDR directly on the TV without any kind of Set-Top box inbetween with this plugin. Cheers Brian

3 2

test - please ignore
by Leo Márquez 04 Jan '13

04 Jan '13

this is a test

1 0

tvguide 0.0.1
by syrius.ml＠no-log.org 04 Jan '13

04 Jan '13

Hi, I've just discovered tvguide on vdr-developper.org. I'm running vdr 1.7.31. i followed the instructions, copied the themes files to $VDRCONF/themes. When i try to use the plugin I get nothing (osd goes away). vdr control doesn't work anymore so i guess the plugin is activated. And vdr segfaults when i press OK. I don't have any channellogos or epgimages, the plugin is run with no option. The README file doesn't tell much about theses images anyway. (format, filename, examples files, etc... nothing) vdr-tvguide-0.0.1.tgz seems to date from september, is there a public repo for this plugin ? logs: vdr: [7439] tvguide: Rendering took 0 ms vdr[7439]: segfault at 20 ip 00007f494f59254e sp 00007fff4b73be80 error 4 in libvdr-tvguide.so.1.7.31[7f494f581000+1b000] config: OSDSkin = sttng OSDTheme = default tvguide.bigStepHours = 3 tvguide.channelCols = 5 tvguide.displayTime = 160 tvguide.epgImageHeight = 240 tvguide.epgImageWidth = 315 tvguide.fontButtonSize = 33 tvguide.fontDetailHeaderSize = 40 tvguide.fontDetailViewSize = 33 tvguide.fontGridSize = 27 tvguide.fontGridSmallSize = 24 tvguide.fontHeaderSize = 33 tvguide.fontIndex = 0 tvguide.fontMessageBoxLargeSize = 40 tvguide.fontMessageBoxSize = 33 tvguide.fontTimeLineDateSize = 33 tvguide.fontTimeLineTimeSize = 0 tvguide.fontTimeLineWeekdaySize = 40 tvguide.footerHeight = 80 tvguide.headerHeight = 120 tvguide.hideChannelLogos = 1 tvguide.hideEpgImages = 1 tvguide.hugeStepHours = 24 tvguide.jumpChannels = 5 tvguide.logoExtension = 0 tvguide.logoHeight = 73 tvguide.logoWidth = 130 tvguide.roundedCorners = 0 tvguide.themeIndex = 1 tvguide.timeColWidth = 120 tvguide.timeFormat = 1 tvguide.useBlending = 1 --

2 1

[PATCH] vdr-xine-0.9.4 vdr-1.7.33 video scaling API (YAEPG-Hack now obsolete)
by Lucian Muresan 03 Jan '13

03 Jan '13

Hi, attached you'll find a patch against vdr-xine-0.9.4 that makes use of the new video scaling API introduced in vdr-1.7.33, yielding correct aspect ratio when scaling. How can it be used? Well, have a look at yaepg-hd patched with [1], but even more exciting when the video output plugin supports true color OSD (unfortunately vdr-xine can do this only in non-X11-overlay mode) is the new true color skin nOpacity [2]. BTW, Reinhard, do you still plan on maintaining vdr-xine? I was wondering because the homepage of the plugin is no longer accessible... [1] https://github.com/lucianm/gen2ovl-googoo2/tree/master/media-plugins/vdr-ya… [2] http://www.vdr-portal.de/board16-video-disk-recorder/board55-vdr-plugins/p1… Regards & Happy Christmas, Lucian P.S. Just for convenience, I also attached the obligatory PmtParser Patch.

3 3

[ANNOUNCE] vdr-upnp 1.0.0
by Denis Loh 03 Jan '13

03 Jan '13

Hi all, I want to release a new version of the UPnP/DLNA media server plugin for the VDR: Version 1.0.0 Major changes: - usage of sub plugins to make extensibility easier. - usage of tntnet for http communication (no patch for additional headers in libupnp required) - usage of streamdev-server for live tv streaming Project website: http://projects.vdr-developer.org/projects/plg-upnp Git: http://projects.vdr-developer.org/git/vdr-plugin-upnp.git If you face any issues, please report bugs on the project web site. Thank you! Denis

1 0

[DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35
by Reinhard Nissl 03 Jan '13

03 Jan '13

Hi, as mentioned in the VDR-1.7.34 announcement, Make.config is now gone for plugins. Make.config gave me the opportunity to control features or behavior of plugins and VDR at a central location without having the need to adjust each plugin's Makefile. For example, while developing vdr-xine, I could keep vdr-xine's Makefile in a distributable state and still control to enable some features I'd like to use in my local configuration. And when upgrading some other plugins at bugfix level (i. e. there are usually no new features and hence the config variables can stay the same), there was no need to adjust the Makefile due to the config entries in Make.config. Here is an excerpt of my Make.config for an example of the above mentioned configuration settings: > #xine > #VDR_XINE_VDR_HAS_TRUECOLOR_OSD = 1 > VDR_XINE_SET_VIDEO_WINDOW = 1 > VDR_XINE_VERIFY_BITMAP_DIRTY = 0 > > #burn > DVDDEV=/dev/hdd > ISODIR=/video > > #vdr > BIDI=1 > VFAT=1 > REMOTE=LIRC > LIRC_PUSHFREQ=64 # 1/s > LIRC_REPEATDELAY=250 # ms > LIRC_REPEATFREQ=32 # 1/s > #LIRC_REPEATTIMEOUT=500 # ms > #LIRC_RECONNECTDELAY=3000 # ms > LIRC_PRIORITYBOOST=1 > > #muggle > HAVE_ONLY_SERVER=1 As you can see, there is nothing like changing compiler or linker settings -- for that stuff, I really appreciate the way it is done now. In a private discussion with kls, he asked me to talk to other plugin developers too (so here we are) about that issue, so that any solution in that regard will be of broad agreement by all developers. To conclude: 1.) there is a need for a common make configuration file for both VDR and plugins. 2.) the file should be included in VDR's Makefile after including Make.config (maybe that idea should be dropped in favor of 5.a) as any VDR related option can be put into Make.config anyway). 3.) the file should be included into plugin Makefiles after having set PLUGIN and VERSION to be able to have some plugin-/version-dependent configuration. 4.) the file is optional -- maybe a template file like Make.config.template could indicate that there is something available for tuning. 5.) how do we name the file? 5.a) plugins.conf (doesn't fit perfectly for 2., to be a common file for VDR too) 5.b) Make.common 5.c) local.conf 5.d) Make.config.local 6.) where do we put the file? 6.a) kls suggested /etc/vdr at a random shot 6.b) I would like to put it next to Make.config 6.c) use pkg-config to determine path (defaults to VDRDIR) Please start sharing your ideas now ;-) Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

22 89

multistream support in VDR
by Goga777 03 Jan '13

03 Jan '13

Hi Recently in kernel was added full multistream support (DTV_STREAM_ID) https://patchwork.kernel.org/patch/1351421/ is there any plans to implement multistream support in vdr ? Goga

3 15

vdr-sxfe does only react to lowercase letters
by cedric.dewijs＠telfort.nl 02 Jan '13

02 Jan '13

Hi All, I use vdr-sxfe to watch TV. This works great, but when I acidently leave caps lock on, VDR does not react to keys anymore. VDR only reacts to keys not affected by caps lock, like space, esc F1 and so on. I use a wireless keyboard, so I don't have a caps lock light. Where in VDR are the keystrokes handled? Would you accept a patch that adds handling for upper case keys? Best regards, Cedric

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr January 2013