[vdr] Removing newline characters from EPG entries.
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', '|'); Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDRAdmin-AM-3.5.2: Autotimer missing
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
[vdr] VDRAdmin-AM-3.5.2: Autotimer missing
Hi, 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? Br, Pasi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDRAdmin and character mapping
Hi, I have a small annoying problem that most likely is quite trivial but can find the cause. All characters above ASCII 127 are converted to something else. E.g. 'ä' gets converted to ','. Funny thing is that on my server (FC4) the conversion is done like that but on windows computer they are converted to '?' chars. On the machine where VDRAdmin is running characters are shown correctly. It seems to be related to language setting but can't figure out how to fix this. Could someone with more knowledge help me? Br, Pasi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
I'm kind of surprised people even bother to shutdown vdr at all. Didn't really how big of an issue this was until reading this thread. That's all I have to offer the discussion at this point. My apologies. :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
> Christian Wieninger wrote: > > perhaps this is too trivial, but why not create a daily or whatever > > timer as you suggested before with a special name like '@epgscan' and > > react on that? > > This would be a dirty ugly hack. There must be some pseudo-recording > running so VDR does not restart the recording over and over again. And > then we'll end up with a recording hack that looks like a timer but does > not block devices and does not write to disk and has no recording folder > and and and... > > 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. 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. 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 for realy using a KISS principle. The only benefit of scripting is that more people tend to write and change scripts that writing plugin or extend VDR code. The second is 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. Of couse Klaus should be one deciding the way to implement it but he should be more open here to stimulate more people to contribute to VDR. It's like Linux and Linus, the first is a scaling system the second not. Same for VDR and Klaus ;-) 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. kind regards Peter ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
Matthias Schwarzott wrote: In gentoo vdr package we added a small hack (attached), which implements a svdrp call "down" to tell vdr it is inactive and will shutdown in X minutes. We call this from shutdown-scripts to let vdr retry shutdown in 5 min (or other value if needed). Question is: Is this still needed? VDR already retries after an acceptable time, and VDR probably knows better whether an user is currently active or not. The only reason I could think of is that VDR was started without a timer nearby, and the start script knows that this is not an user start. And sending a kPower key press will also let VDR go inactive. Things were different in old versions, where VDR retried shutdown after 3 hours or so, but that has changed. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
Matthias Schwarzott wrote: I think a much easier solution (implementable in runvdr/vdr-initscript) is: Write down wakeup-time when shutting down and comparing that to time when system/vdr starts (with some margin). That would be the way I would do it. Reconstructing the reason for shutdown after the restart is ok for just timers, but with different reasons this is way too complex and error-prone. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
Christian Wieninger wrote: perhaps this is too trivial, but why not create a daily or whatever timer as you suggested before with a special name like '@epgscan' and react on that? This would be a dirty ugly hack. There must be some pseudo-recording running so VDR does not restart the recording over and over again. And then we'll end up with a recording hack that looks like a timer but does not block devices and does not write to disk and has no recording folder and and and... The alternative would be to implement a generic task scheduler and make timers one special type of schedule. This would get REALLY big. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
