VDR developer version 1.3.34 is now available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.34.tar.bz2
A 'diff' against the previous version is available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.33-34.diff
The changes since version 1.3.33:
- Fixed a leftover 'summary.vdr' in vdr.5 (thanks to Peter Bieringer for reporting this one). - Fixed opening recording folders in case the last replayed recording no longer exists (reported by Udo Richter). - Fixed an unjustified "Error while accessing recording!" after deleting a recording from a subfolder. - Fixed handling the '.update' file in case the video directory is not at the default location (reported by Jon Burgess). - Fixed a crash in cConfig::Load() when compiling on the PPC (thanks to Sascha Volkenandt). - Fixed the FATALERRNO macro to check for a non-zero errno value (reported by Marco Schlüßler). - Added a check against MAXOSDAREAS in cOsd::CanHandleAreas() (reported by Udo Richter). - Fixed setting current menu item if the first one is non-selectable. - cOsdItem::cOsdItem() now has a 'Selectable' parameter. - Improved displaying 'sub-title' and 'bottom text' in the CAM menu. - Added status message "Resetting CAM..." for an immediate feedback when the CAM reset has been triggered. - The CAM menu now automatically updates itself in case of a progress display (as used, for instance, when updating the firmware via satellite). - Now skipping some funny characters sent by some CAMs at the beginning of strings. - The CAM menu is now completely closed when pressing the Menu key while inside a sub menu. - Reduced MAX_CONNECT_RETRIES in ci.c to 2 (waiting too long made the whole thing appear hanging). - Added status message "Opening CAM menu..." for an immediate feedback when the CAM menu has been requested. - Speeded up initial opening of the CAM menu. - Fixed handling of menus with no selectable items. - The character 0x8A in CAM menu strings is now mapped to a real newline. - The 'sub-title' and 'bottom text' in the CAM menu can now consist of several lines. - Improved the CAM enquiry menu.
Have fun!
Klaus
I demand that Klaus Schmidinger may or may not have written...
VDR developer version 1.3.34 is now available at
[snip]
Would you mind setting your wrap width to <= 80 columns?
Darren Salt wrote:
Would you mind setting your wrap width to <= 80 columns?
Actually, the mail is wrapped at 75 columns, but with format=flowed, so mail readers can remove wrapping line breaks again. The original text had additional hard line breaks at >85 columns, just like the HISTORY file has.
Cheers,
Udo
I demand that Udo Richter may or may not have written...
Darren Salt wrote:
Would you mind setting your wrap width to <= 80 columns?
Actually, the mail is wrapped at 75 columns,
After quoted-printable decoding, I find that the longest line in that message is 85 characters long. With your common or garden monospaced font, this exceeds 75 columns.
The encoded text has no lines longer than 74 columns, but many of those which are 74 columns wide end with '='... allowing for an assumed trailing space, is that from where you got your "75 columns"? If so, you've been measuring the wrong thing.
(I'm tempted to base64-encode this so that I can say that no line in this message exceeds 64 columns, but I won't.)
but with format=flowed,
That's there, yes, but uselessly: there are no trailing spaces.
so mail readers can remove wrapping line breaks again.
None to be removed, but some could certainly be inserted...
[snip]
Darren Salt wrote:
The encoded text has no lines longer than 74 columns, but many of those which are 74 columns wide end with '='... allowing for an assumed trailing space, is that from where you got your "75 columns"? If so, you've been measuring the wrong thing.
Thats it, and that is the wrap width you can adjust in the mailer.
The request to Klaus should be to wrap the HISTORY file at 74 characters too, so all would be happy.
but with format=flowed,
That's there, yes, but uselessly: there are no trailing spaces.
At least my mailer rewraps the body from 75 back to 85. Plus/minus one or two. ;)
Cheers,
Udo
I demand that Udo Richter may or may not have written...
Darren Salt wrote:
The encoded text has no lines longer than 74 columns, but many of those which are 74 columns wide end with '='... allowing for an assumed trailing space, is that from where you got your "75 columns"? If so, you've been measuring the wrong thing.
Thats it, and that is the wrap width you can adjust in the mailer.
Hmm? Surely it's the width *before* q-p encoding which is the important one...
The request to Klaus should be to wrap the HISTORY file at 74 characters too, so all would be happy.
Then consider that to be the request. :-)
but with format=flowed,
That's there, yes, but uselessly: there are no trailing spaces.
At least my mailer rewraps the body from 75 back to 85.
<AOL>. It then rewraps from 85 to 80 for display because it's configured to use an 80-column window and I *don't* want to change that because then it'd be obscuring rather more than I'd like of other windows...
Plus/minus one or two. ;)
Not, say, five? ;-)
(FWIW, the current vdr seems to be working happily here ATM.)
Hello Klaus,
i have a problem with mplayer, when playing with vs.h == 240, and vdr. If i want get eVideoSystem cDvbDevice::GetVideoSystem(void) defined in device.h (with a call "cDevice::PrimaryDevice()->GetVideoSystem()" in plugin) from vdr it returns vsPAL with writing an error in dvbdevice.h in logfile.
If plugin calls the driver direct it get the correct result, do you know, why the call to vdr will fail?
I need it to draw skin not to big for ntsc (maximal height is 480 (from 0))
Frank
Frank wrote:
Hello Klaus,
i have a problem with mplayer, when playing with vs.h == 240, and vdr. If i want get eVideoSystem cDvbDevice::GetVideoSystem(void) defined in device.h (with a call "cDevice::PrimaryDevice()->GetVideoSystem()" in plugin) from vdr it returns vsPAL with writing an error in dvbdevice.h in logfile.
If plugin calls the driver direct it get the correct result, do you know, why the call to vdr will fail?
I just tested this here and didn't get an error message.
What error message do you actually get?
Klaus
----- Original Message ----- From: "Klaus Schmidinger" Klaus.Schmidinger@cadsoft.de To: vdr@linuxtv.org Sent: Friday, November 04, 2005 4:24 PM Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.3.34
Frank wrote:
Hello Klaus,
i have a problem with mplayer, when playing with vs.h == 240, and vdr. If i want get eVideoSystem cDvbDevice::GetVideoSystem(void) defined in device.h (with a call "cDevice::PrimaryDevice()->GetVideoSystem()" in plugin) from vdr it returns vsPAL with writing an error in dvbdevice.h in logfile.
If plugin calls the driver direct it get the correct result, do you
know,
why the call to vdr will fail?
I just tested this here and didn't get an error message.
What error message do you actually get?
Hello Klaus,
thanks for the answer.
With following lines (only for test and with plain vdr 1.3.35):
bool NTSC = false; isyslog("skinelchi: ask for NTSC and OSD"); if (cDevice::PrimaryDevice()->GetVideoSystem() == vsNTSC) NTSC = true; isyslog("skinelchi: %s", NTSC ? "NTSC" : "PAL"); bool PAL = false; if (cDevice::PrimaryDevice()->GetVideoSystem() == vsPAL) PAL = true; isyslog("skinelchi: %s", PAL ? "PAL" : "NTSC"); if (fd_video >= 0) { /* fd_video is set before with this: char *dev = NULL; asprintf(&dev, DEV_DVB_VIDEO, cDevice::PrimaryDevice()->CardIndex(), 0); fd_video = open(dev, O_RDONLY | O_NONBLOCK); oldbm = NULL; free(dev);*/ if (ioctl(fd_video, VIDEO_GET_SIZE, &vs) == 0) { if (vs.h == 480 || vs.h == 240) PAL = false; } } isyslog("skinelchi: %s", PAL ? "PAL" : "NTSC");
i get the following lines after messages from mplayer in user.log
Nov 5 00:04:47 vdr logger: *** Starting mplayer.sh Version 0.8.4 Nov 5 00:04:47 vdr logger: *** DEBUG: Variable CFGFIL has value "/etc/vdr/plugins/vdrmplayer.sh.conf" Nov 5 00:04:47 vdr logger: *** Use Option USERDEF at your own risk! Nov 5 00:04:48 vdr logger: *** INFO: Source Video has Resolution of 352 x 240 ... Nov 5 00:04:48 vdr logger: *** INFO: For Sqare Pixels we would scale to 320 x 218 ... Nov 5 00:04:51 vdr vdr[5139]: skinelchi: ask for NTSC Nov 5 00:04:51 vdr vdr[5139]: ERROR (dvbdevice.c,658): Ungültiger Dateideskriptor Nov 5 00:04:51 vdr vdr[5139]: skinelchi: PAL Nov 5 00:04:51 vdr vdr[5139]: ERROR (dvbdevice.c,658): Ungültiger Dateideskriptor Nov 5 00:04:51 vdr vdr[5139]: skinelchi: PAL Nov 5 00:04:51 vdr vdr[5139]: skinelchi: NTSC
looks like the filedescriptor "fd_video" will not be valid, but with vs.h = 480 and if i ask the driver for myself it works.
Frank
-
Darren Salt -
Frank -
Klaus Schmidinger -
Lauri Tischler -
Udo Richter