******************************************************************** ** THIS IS AN ANNOUNCEMENT - PLEASE DO NOT REPLY TO THIS MESSAGE! ** ** SEND BUG REPORTS ETC. AS A NEW MESSAGE, WITH A PROPER SUBJECT! ** ********************************************************************
VDR developer version 1.3.32 is now available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.32.tar.bz2
A 'diff' against the previous version is available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.31-32.diff
The changes since version 1.3.31:
- Added some missing braces in remux.c (thanks to Wayne Keer for reporting this one). - Removed unused MAINMENUENTRY from svdrpdemo.c (thanks to Udo Richter for reporting this one). - Fixed appending sequence end code in cDvbPlayer::Goto() (thanks to Reinhard Nissl). - Fixed syncing in cRepacker (thanks to Reinhard Nissl). - Now always using stream id 0xE0 for the video stream, to avoid problems with post processing tools that choke on different ids (suggested by Reinhard Nissl). - Updated the Estonian OSD texts (thanks to Arthur Konovalov). - Fixed cDvbPlayer::SkipFrames() to properly handle radio recordings (thanks to Reinhard Nissl). - Updated the Swedish OSD texts (thanks to Tomas Prybil). - Updated the Slovenian OSD texts (thanks to Matjaz Thaler). - Updated the Danish OSD texts (thanks to Mogens Elneff). - Made LIRC command parsing more robust (thanks to Ville Skyttä). - Introduced a separate 'plugins-install' target in the Makefile (thanks to Daniel Thompson). - Re-introduced the code that waits for a tuner lock in VDR/device.c, since apparently some users actually need it. It's not active by default, you'll have to define the WAIT_FOR_TUNER_LOCK macro in that file if you need it (suggested by Malcolm Caldwell). - Adjusted the Makefile to the dvb-kernel driver on kernel 2.6 and up (thanks to Lauri Tischler). - Repeat keys are now ignored when waiting for a keypress to cancel an operation (thanks to Marko Mäkelä). - The main menu function of a plugin can now be activated through a key macro of the form "@plugin" even if that plugin doesn't have a main menu entry (using part of a patch by Hardy Flor, which originally implemented calling plugins from SVDRP). - The menu timeout handling is now done centrally in the main program loop. - Added missing help for the 'help' keyword in the SVDRP command PLUG. - The main menu function of a plugin can now be called programmatically through the static function cRemote::CallPlugin(). - The SVDRP command PLUG now has a new option 'main' which can be used to initiate a call to the main menu function of a plugin (using part of a patch by Hardy Flor). - The new command line option '--vfat' can be used to make VDR encode special characters in recording file names, even if it wasn't compiled with VFAT=1 (suggested by Peter Bieringer). The compile time option VFAT still exists and creates a VDR that always behaves as if it were called with '--vfat'. - Replaced the ':' delimiter between hour and minute in recording file names with a '.' under Linux, too. Existing recordings with ':' as delimiter will still work. - Implemented the SVDRP command MOVC (thanks to Andreas Brachold). - Added support for multiple audio language codes in ISO639LanguageDescriptors to 'libsi' (thanks to Marcel Wiesweg). - Changed the audio PID language codes to hold up to two 3 letter codes, separated by '+', to store separate languages broadcast in two channel audio mode. - If the preferred audio language is broadcast on a PID that has two different languages in the two stereo channels, the audio channel is now properly set when switching to such a channel (thanks to Mogens Elneff for his help in testing this). - Fixed some typos in MANUAL (thanks to Ville Skyttä). - Fixed the default value for "Setup/EPG bugfix level" (thanks to Ville Skyttä for reporting this one). - Fixed defining timers that only differ in the day of week (thanks to Patrick Rother for reporting this one). - Fixed converting summary.vdr files that would result in a very long 'short text' (thanks to Carsten Koch). - Implemented a hash for the channels to reduce the system load in the EIT scanning thread (based on a patch by Georg Acher).
Have fun!
Klaus
Dominique Simon wrote:
- Implemented the SVDRP command MOVC (thanks to Andreas Brachold).
What does this command do? Move Recordings?
kls@hawk:/home/kls/vdr/VDR > telnet video 2001 Trying 192.168.100.3... Connected to video. Escape character is '^]'. 220 video SVDRP VideoDiskRecorder 1.3.32; Sun Sep 11 17:00:26 2005 help movc 214-MOVC <number> <to> 214 Move a channel to a new position. 214 End of HELP info
Klaus
PS: so much for telling people not to reply to announcements... :-(
Klaus.Schmidinger@cadsoft.de(Klaus Schmidinger) 11.09.05 17:02
Dominique Simon wrote:
- Implemented the SVDRP command MOVC (thanks to Andreas Brachold).
What does this command do? Move Recordings?
kls@hawk:/home/kls/vdr/VDR > telnet video 2001 Trying 192.168.100.3... Connected to video. Escape character is '^]'. 220 video SVDRP VideoDiskRecorder 1.3.32; Sun Sep 11 17:00:26 2005 help movc 214-MOVC <number> <to> 214 Move a channel to a new position. 214 End of HELP info
Klaus
PS: so much for telling people not to reply to announcements... :-(
Text in capitals is hard to read. That's the reason why EULAs etc. are written in all capitals: The customer should not read it.
Try your self, what's easier to read?
** THIS IS AN ANNOUNCEMENT - PLEASE DO NOT REPLY TO THIS MESSAGE! ** ** SEND BUG REPORTS ETC. AS A NEW MESSAGE, WITH A PROPER SUBJECT! **
**************************************************************************** ** This is an announcement - please do not reply to this message! ** ** Send comments, questions etc. as a new message, with a proper subject! ** ****************************************************************************
Too:
Maybe a subject change would help?
The convention is: Subject: New topic (was: old topic)
"(was:" is a token detected be better readers so that further "Re" will not repete it again and again...
Rainer
Rainer Zocholl wrote:
Klaus.Schmidinger@cadsoft.de(Klaus Schmidinger) 11.09.05 17:02 ...
PS: so much for telling people not to reply to announcements... :-(
Text in capitals is hard to read. That's the reason why EULAs etc. are written in all capitals: The customer should not read it.
Funny idea...
Try your self, what's easier to read?
** THIS IS AN ANNOUNCEMENT - PLEASE DO NOT REPLY TO THIS MESSAGE! ** ** SEND BUG REPORTS ETC. AS A NEW MESSAGE, WITH A PROPER SUBJECT! **
** This is an announcement - please do not reply to this message! ** ** Send comments, questions etc. as a new message, with a proper subject! **
I was under the impression that it is common practice to write something important in capitals.
Too:
Maybe a subject change would help?
The convention is: Subject: New topic (was: old topic)
"(was:" is a token detected be better readers so that further "Re" will not repete it again and again...
Just changing the subject isn't doing the trick. You _have_ to write a _new_ message to start a new thread.
Well, this was an apparently feeble attempt to make people aware that they should start a new thread for a new problem. I guess I just have to give up and accept that there will always be somebody who just doesn't give a sh*t...
Klaus
Am 12.09.2005 um 18:22 schrieb Klaus Schmidinger:
just have to give up and accept that there will always be somebody who just doesn't give a sh*t...
As it was me: I just haven't seen it, if i had, i would have respected that. I am sorry.
Ciao, Dominique