Re: [vdr] VDRAdmin-AM-3.5.2: Autotimer missing
Hi, you can also set AT_OFFER=2 in vdradmind.conf. Regards, Andreas On Monday 01 January 2007 22:41, Ville Skyttä wrote: On Monday 01 January 2007 23:14, Pasi Juppo wrote: Upgraded to the most recent version of VDRAdmin (previous was 3.4.5a). Now AutoTimer menu item is missing and can't get it visible. There seems to be option for this (at least vdradmind.pl has reference to it) but does not matter if I change the status in vdradmind.pl or vdradmind.conf file (AUTOTIMER is missing from conf file - if it even should be there). How can I fix the problem? Try removing AT_OFFER from vdradmind.conf and changing -s $AT_FILENAME to -f $AT_FILENAME around line 3000 in vdradmind.pl. Note also that the builtin autotimer functionality is deprecated in favour of using epgsearch, see HISTORY entries from 3.5.0beta onwards. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- http://andreas.vdr-developer.org --- VDRAdmin-AM VDR user #303 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Removing newline characters from EPG entries.
Carsten Koch wrote: Hi, I found the following code in epg.c lines 633-636: // VDR can't usefully handle newline characters in the title and shortText of EPG // data, so let's always convert them to blanks (independent of the setting of EPGBugfixLevel): strreplace(title, '\n', ' '); strreplace(shortText, '\n', ' '); AFAIK, VDR _can_ handle newlines in the title and shortText, as long as they are represented as '|'. So I wonder if it would not be an improvement to change the above code into // Change newline characters into '|', which will be displayed as newline. strreplace(title, '\n', '|'); strreplace(shortText, '\n', '|'); By VDR can't usefully handle newline characters in the title and shortText I meant that the title and short text are always used in a single line context. There's no point in having newlines in there. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] Maintenance update - image-0.2.7
Hi folks, There are a simple maintenance release available for vdr-image-plugin. Thanks to all supporters! -- image-0.2.7 -- This plugin allows the display of digital images, like jpeg, tiff, png, bmp and some more, on the TV screen, using the DVB out device from vdr. Changes: - Add checks for sanity of memory buffers - Create LIBDIR if'nt exist - Updated some i18n text - Updated french translations. (Thanks to NIVAL Michaël) - Updated finnish translations. (Thanks to Rolf Ahrenberg) - Warn if wrong APIVERSION used Details: http://vdr-image.berlios.de/ Download: https://developer.berlios.de/project/showfiles.php?group_id=4286 -- Happy new year, Andreas ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
[EMAIL PROTECTED] wrote: The alternative would be to implement a generic task scheduler and make timers one special type of schedule. This would get REALLY big. Yes, but it will be the much better design. It will open the option to do VDR related timed and maintainance tasks. There must be some limit. IMHO VDR is a video recorder, not a task scheduler. And I think that Klaus probably agrees with that. Don't reply this should be external scripts, as there is no way external scripts know what state VDR currently has without a lot more complexity. What additional internal state info do you need? Providing interfaces to cooperate with external schedulers should be no problem. These are EPG scans (internal, infosatepg, nextview), sleeptimers, switchonly timers, cleanup tasks of plugins and so on. Think about external EPGs, especilly the ones that need VDR to tune to a channel, like infosatepg or nextview. This is painfull hack doing his outside VDR as these tasks mutually collide with VDRs internal activities and need to be integrated Do you suggest to put all these EPG collectors as integral schedule events into core VDR??? At most, such things may be done as plugin. And for plugins, the ability to wake up at a non-timer time was already suggested. for realy using a KISS principle. In my eyes, KISS also applies to VDR itself. Meaning, why add a full-featured scheduler to VDR that VDR doesn't need? also cause by Klaus's reluctance to take over patches. Where there are patches there is need to change some VDR behaviour, so this behaviour should be changed. In limits, yes. But Klaus being very conservative on integrating patches and features is one of the reasons why VDR is still a very stable and easy to use program. What sounds like a nice enhancement now may soon turn into a dead end, a burden kept for compatibility. There are lots of programs that are overloaded with features that no one really knows, with an user interface to get lost in it. The idea to create now a external Shutdown class by a second person seems like a good starter. It should be done for other functionalities too. This is not the first bigger chunk of work contributed by others, and definitely not the first smaller feature that was contributed. Its also a matter of engagement: If you start off with I'll do it as independent patch, Klaus wont add it anyway, then you'll get what you want. The reason I am working on this is that AFAIK Klaus doesn't use the shutdown mechanisms, and the code really needed an overhaul by someone who's interested in it. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDRAdmin and character mapping
On Tue, 2007-01-02 at 18:46 +, Harald Milz wrote: I'm using the UTF-8 patch (because I'm using Russian and German EPGs), and German umlauts are displayed incorrectly unless I tell the browser explicitly to use UTF-8. Are debian packages with incorporated UTF-8 patchs available some where? BRGD, Vladimir ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
Udo Richter wrote: [EMAIL PROTECTED] wrote: The alternative would be to implement a generic task scheduler and make timers one special type of schedule. This would get REALLY big. Yes, but it will be the much better design. It will open the option to do VDR related timed and maintainance tasks. There must be some limit. IMHO VDR is a video recorder, not a task scheduler. And I think that Klaus probably agrees with that. I do. However, (don't know exactly if this has already been suggested as such) maybe a simple feature in the new shutdown code could be to allow the user to specify *one* time at which VDR shall be guaranteed to be up, along with a time period for which it shall stay up. That way external tools could be scheduled using cron, and they could rely on VDR being up at that time. But that's about as far as I'd go. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
