[vdr] [ANNOUNCE] VDR developer version 1.7.42
VDR developer version 1.7.42 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.42.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.41-1.7.42.diff MD5 checksums: 5a9ec132781045061325162fe03c2763 vdr-1.7.42.tar.bz2 011f2838026f849f031c40b2f06d9181 vdr-1.7.41-1.7.42.diff Approaching version 2.0.0: == If there are no more serious bug reports, the final version 2.0.0 of VDR shall be released on March 31, 2013. So please test this developer version intensely and report any problems you might encounter as soon as possible. The following language files still have the given number of untranslated texts: da_DK.po: 134 el_GR.po: 197 hr_HR.po: 134 lt_LT.po: 1 nn_NO.po: 262 pt_PT.po: 28 sl_SI.po: 1 tr_TR.po: 134 If nobody takes care of these, they will remain untranslated in version 2.0.0. DEADLINE FOR SUBMITTING TRANSLATIONS IS SATURDAY, MARCH 30! The changes since version 1.7.41: - Updated the Serbian OSD texts (thanks to Zoran Turalija). - Added maximum SNR and signal strength value for TechniSat SkyStar HD2 (thanks to Zoran Turalija). - Renamed the language file sr_SR.po to sr_RS.po (pointed out by Zoran Turalija). - Fixed loading the setup.conf file in case a parameter contains the '#' character (thanks to Johann Friedrichs). - The Resume button in the main menu is now only active if the respective recording actually exists (reported by Johann Friedrichs). - The cutter now allocates its buffers on the heap to avoid problems on systems with limited stack space (suggested by Juergen Lock). - Fixed formatting the channel definition example in the vdr(5) man page (thanks to Dominic Evans). - Updated the default channels.conf file. Have fun! Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] 0.1.0
On 23.03.2013 1:20 , fnu wrote: René, well you could go the hard way and try a mix of repository based VDR plus any self-compiled Plugins, in that case I would rather suggest to do everything by yourself inkl. VDR ... Or a little easier Debian/Ubuntu way, look here: http://goo.gl/Xz7zm, usage: sudo apt-add-repository ppa:yavdr/testing-vdr Our packages do base closely on Tobi's work. === Kind regards fnu Hi Fnu, Thanks for the suggesting your repo. It looks to have an impressive list of plugins :-) I did a small test-ride, but for some reason it did not install an init-script. is it something i'm missing, or shall i use the init-script found under /usr/share/doc/vdr/examples ? Regards, René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] 0.1.0
Hi, Am 23.03.2013 12:28, schrieb René: On 23.03.2013 1:20 , fnu wrote: René, well you could go the hard way and try a mix of repository based VDR plus any self-compiled Plugins, in that case I would rather suggest to do everything by yourself inkl. VDR ... Or a little easier Debian/Ubuntu way, look here: http://goo.gl/Xz7zm, usage: sudo apt-add-repository ppa:yavdr/testing-vdr Our packages do base closely on Tobi's work. === Kind regards fnu Hi Fnu, Thanks for the suggesting your repo. It looks to have an impressive list of plugins :-) I did a small test-ride, but for some reason it did not install an init-script. is it something i'm missing, or shall i use the init-script found under /usr/share/doc/vdr/examples ? In the final version (coming with vdr 2.0) the package will again install an init.d-Script (or an upstart-job if your system uses that like Ubuntu). For now you have to use the one found in the examples directory. Lars. Regards, René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] MaxThemeName and MaxSkinName limit
Hi, thank you Klaus for holding up your release plan for 2.0! However, I hope this minor patch won't be too much trouble for you, as it only increases the limit of 16 to theme and skin names, letting them be NAME_MAX as almost any files, since these names can also be involved in file names. Was there a good reason to limit them at 16 only, perhaps the fear that the name won't fit on the OSD? I don't really think someone would really make use of as many as 255 characters for this. On the other hand, users just encountered crashes with plugins which (unfortunately, yet) have themes of their own, when just adding a new theme with a name longer than 16 and at the same time the original plugin author relied on MaxThemeName when allocating the string length. So, what do you think, easy to adopt? Regards, Lucian diff -Naur vdr-1.7.42_orig/config.h vdr-1.7.42/config.h --- vdr-1.7.42_orig/config.h2013-03-16 16:12:14.0 +0100 +++ vdr-1.7.42/config.h 2013-03-23 16:57:48.378701000 +0100 @@ -53,8 +53,8 @@ #define MAXOSDHEIGHT 1200 #define MaxFileName NAME_MAX // obsolete - use NAME_MAX directly instead! -#define MaxSkinName 16 -#define MaxThemeName 16 +#define MaxSkinName NAME_MAX // obsolete - use NAME_MAX directly instead! +#define MaxThemeName NAME_MAX // obsolete - use NAME_MAX directly instead! // Basically VDR works according to the DVB standard, but there are countries/providers // that use other standards, which in some details deviate from the DVB standard. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] NVOD feeds
Hi, recently I started to give some maintenance to a plugin [1] which seemed to be orphaned for a while and needed by several, as I knew from the German VDR-Portal, subscribers of Sky Germany. The plugin was called Arghdirector, it is a fork of an even older one, called director, possibly because of the marketing name used by Sky Germany and former Premiere for their NVOD feeds at that time. Nowadays they call this Sky select, so that's for now the new name of the plugin. We even had some discussion on vdr-portal on the new name, someone even suggested NVOD [2], others emphasized this would be only usable to german Sky subscribers, and I only recently found out that NVOD is actually established terminology [3]. Just by chance, I discovered that the plugin actually also triggers on several of the plethora of channels called NVOD which seems to be mostly if not all from Sky UK, so the plugin might even work with them, allowing to find on which of the feeds what show is just about to start. So my question to Sky UK subscribers, would you care to give it a try, would this plugin be of any use for you? Well, I do not know of any alternatives (in terms of VDR plugins) you might be using, please mention them if that's the case. If you find the plugin useful also for you, I'm considering yet again renaming it to something more generic, like NVOD Feeds and the german translation can still sound Sky Select as that's the current name of this feature at Sky DE... Regards, Lucian [1] http://linuxtv.org/vdrwiki/index.php/SkySelectFeeds-plugin [2] http://www.vdr-portal.de/board17-developer/board21-vdr-plugins/p1132335-arghdirector-noch-gepflegt/#post1132335 [3] http://en.wikipedia.org/wiki/Video_on_demand ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] MaxThemeName and MaxSkinName limit
On 23.03.2013 17:14, Lucian Muresan wrote: Hi, thank you Klaus for holding up your release plan for 2.0! However, I hope this minor patch won't be too much trouble for you, as it only increases the limit of 16 to theme and skin names, letting them be NAME_MAX as almost any files, since these names can also be involved in file names. Was there a good reason to limit them at 16 only, perhaps the fear that the name won't fit on the OSD? I don't really think someone would really make use of as many as 255 characters for this. On the other hand, users just encountered crashes with plugins which (unfortunately, yet) have themes of their own, when just adding a new theme with a name longer than 16 and at the same time the original plugin author relied on MaxThemeName when allocating the string length. Those are bugs in the plugins and should be fixed there. Or is this something that can also happen in the core VDR? So, what do you think, easy to adopt? Well, for one, now is definitely not the right time for a change like this! And furthermore, skin and theme names should be short. What sense does it make to call a theme something like This is the theme that implements a range of colors from 400 nanometers to 700 nanometers, when you could just plain simple call it rainbow? ;-) So I'd say the limit is there for a reason, and should stay there. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
