Re: [vdr] [ANNOUNCE] VDR developer version 1.7.21
On 09/09/2011 10:19 PM, Reinhard Nissl wrote: Hi, Am 09.09.2011 16:54, schrieb Klaus Schmidinger: Since you're saying that the problem is related to the dxr3 plugin I guess I won't see any error with my TT-S2 6400. I switch to 1.7.21 from 1.7.17 and see that teletext subtitles appear now for example on Das Erste HD. No matter which OSD size I setup in vdr-xine (e. g. 720x576, 1280x720 or 1920x1080), the subtitles are never positioned correctly and vdr-xine complains very often like that: vdr-xine: new OSD(-152, 0) requested with coordinates out of range I noticed a little different problem with vdr-sxfe (from xineliboutput). If I first watch some channel on vdr-sxfe client from the small window, the subtitles are positioned ok for me. But once I click the window for full screen mode, the subtitle position and size are not re-calculated and this causes that subtitles are shown in the middle of the screen. To fix this, I need to switch for another channel and then switch back to original channel. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.21
Hi, Am 09.09.2011 16:54, schrieb Klaus Schmidinger: Since you're saying that the problem is related to the dxr3 plugin I guess I won't see any error with my TT-S2 6400. I switch to 1.7.21 from 1.7.17 and see that teletext subtitles appear now for example on Das Erste HD. No matter which OSD size I setup in vdr-xine (e. g. 720x576, 1280x720 or 1920x1080), the subtitles are never positioned correctly and vdr-xine complains very often like that: vdr-xine: new OSD(-152, 0) requested with coordinates out of range Do these subtitles work correctly on your TT-S2 6400? Which OSD size do you use on your TT-S2 6400? Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rni...@gmx.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.21
Al 09/09/11 16:54, En/na Klaus Schmidinger ha escrit: >> I think this is still needed for output plugins that don't implement the >> method, >> so that they should at least work as before this modification. > > Can you please point out exactly which modificaton you are > referring to? I'm referring to the modification that changed GetVideoSize from being purely informational to being used for something. In case you're interested, with the patch below, output plugins that don't implement GetVideoSize will have the subtitles working as before. I know that the proper fix is to implement GetVideoSize and GetOsdSize (I actually did afterwards), but at least it doesn't break what was working before. --- dvbsubtitle.c.orig 2011-09-04 19:11:12.426133000 +0200 +++ dvbsubtitle.c 2011-09-09 19:27:46.064725000 +0200 @@ -887,7 +887,7 @@ double VideoAspect; cDevice::PrimaryDevice()->GetOsdSize(OsdWidth, OsdHeight, OsdAspect); cDevice::PrimaryDevice()->GetVideoSize(VideoWidth, VideoHeight, VideoAspect); - if (OsdWidth == displayWidth && OsdHeight == displayHeight) { + if ((OsdWidth == displayWidth && OsdHeight == displayHeight) || VideoWidth == 0) { osdFactorX = osdFactorY = 1.0; osdDeltaX = osdDeltaY = 0; } Bye -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.21
On 05.09.2011 19:52, Luca Olivetti wrote: Al 05/09/11 19:43, En/na Luca Olivetti ha escrit: Ok, I got confused, but why do you use VideoAspect * OsdHeight instead of OsdWidth? Most probably the problem is caused because the dxr3 plugin doesn't implement the GetOsdSize and GetVideoSize method, but the xine plugin does implement them. Ok, I had to setup the osd extents in xine to 1920x1080 to fix the issue. Anyway, since the cDevice::GetVideoSize returns 0 if not overridden, I put a check VideoWidth == 0 in SetOsdData. I think this is still needed for output plugins that don't implement the method, so that they should at least work as before this modification. Can you please point out exactly which modificaton you are referring to? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.21
On 05.09.2011 19:43, Luca Olivetti wrote: Al 05/09/11 18:15, En/na Klaus Schmidinger ha escrit: On 05.09.2011 00:08, Luca Olivetti wrote: Al 04/09/11 23:53, En/na Luca Olivetti ha escrit: Al 04/09/11 23:05, En/na Klaus Schmidinger ha escrit: Ok, I couldn't resist and I tried. I don't know if it solves the issue because now the subtitles are "whacky": they only appear from time to time and they're in the middle of the screen, both with my trusty dxr3 and with the xine plugin (in the latter case it happens both with sd and hd channels). Oh well, back to vdr-1.7.16 until I can investigate what's wrong :-( I tested this with several old recordings and also live (in HD) and the subtitles always worked just fine. I'm using a TT-S2 6400 as output device, if that matters. Well, I disabled the scaling/offset (in cDvbSubtitleConverter::SetOsdData) It still works better with the above "fix", but maybe there's a typo in there: shouldn't osdFactorX = VideoAspect * OsdHeight / displayWidth; be instead osdFactorX = VideoAspect * OsdHeight / displayHeight; I don't think so. 'VideoAspect * OsdHeight' is the width of a full screen subtitle display, using the entire OSD height, according to the aspect ratio of the video material. Dividing this by displayWidth (i.e. the actual width of the subtitle display) results in the osdFactorX, which is used to convert coordinates in the subtitle display to the OSD coordinate system. Ok, I got confused, but why do you use VideoAspect * OsdHeight instead of OsdWidth? Assume the OSD aspect is 16:9 and the currently displayed video material is 4:3. To properly map the subtitles on the 16:9 OSD you need to do VideoAspect * OsdHeight to get the proper width, assuming that the full height shall be used. Most probably the problem is caused because the dxr3 plugin doesn't implement the GetOsdSize and GetVideoSize method, but the xine plugin does implement them. Anyway, since the cDevice::GetVideoSize returns 0 if not overridden, I put a check VideoWidth == 0 in SetOsdData. Can you provide me with some sample recording that demonstrates the problem you are seeing? I think you can check by yourself: I tested with the bbc channels at 28.2E. Since you're saying that the problem is related to the dxr3 plugin I guess I won't see any error with my TT-S2 6400. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Only getting partial EPG data with 1.7.21?
On 06.09.2011 16:42, John Klimek wrote: Did anything change with VDR 1.7.21 regarding EIT? For some reason I'm only getting partial EIT data (ie. lots of channels are missing EIT data). For my provider, the 7 day EPG guide is sent on one specific transponder and it contains EPG information for all satellites and services on the entire network. This worked fine in 1.7.20 but for some reason it's not updating lots of channels in 1.7.21. 2011-09-04: Version 1.7.21 ... - The new function cDevice::ProvidesEIT() is used to determine whether a device can provide EIT data and will thus be used in cEITScanner::Process() to receive EIT data from the channels it can receive (suggested by Rolf Ahrenberg). Note that by default it is assumed that a device can't provide EIT data, and only the builtin cDvbDevice returns true from this function. If your receiving device is not a cDvbDevice then it will have to implement that function and return true. Other than that I don't see anything that changed in that area. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] perfect little vdr client hardware
On 9 September 2011 14:25, Henning Pingel wrote: > > Am Freitag, den 09.09.2011, 14:11 +0200 schrieb Torgeir Veimo > : >> >> The netv from chumby seems to be perfect as a hardware client to VDR, >> if it can decode mpeg2/h.264. Does anyone here know any more about >> this product? It seems to be fairly open, and based on an embedded >> linux distro. >> >> http://wiki.chumby.com/index.php/NeTV_developer_info > > Hi, > > From what I read about it yesterday I had the impression that it can be used > for displaying "anything but videos" on top of the external sources picture > (that - by the way - can't come from an internal tuner integrated in the TV). > "Anything but videos" IMHO means: Web pages, photos, rss news, its own OSD. > > So IMHO it's not meant to be used as a video player / video streaming device > like - for example these upcoming devices: > http://dune-hd.com/news/183-dune-hd-tv-101-301.html > > Cheers, > hepi > http://wiki.chumby.com/index.php/NeTV_FPGA_architecture somebody needs to write an output device plugin for the hardware? Unless you want to write a chrome application for the device and go through the user interface http://wiki.chumby.com/index.php/NeTV_local_UI ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] perfect little vdr client hardware
Am Freitag, den 09.09.2011, 14:11 +0200 schrieb Torgeir Veimo : The netv from chumby seems to be perfect as a hardware client to VDR, if it can decode mpeg2/h.264. Does anyone here know any more about this product? It seems to be fairly open, and based on an embedded linux distro. http://wiki.chumby.com/index.php/NeTV_developer_info Hi, From what I read about it yesterday I had the impression that it can be used for displaying "anything but videos" on top of the external sources picture (that - by the way - can't come from an internal tuner integrated in the TV). "Anything but videos" IMHO means: Web pages, photos, rss news, its own OSD. So IMHO it's not meant to be used as a video player / video streaming device like - for example these upcoming devices: http://dune-hd.com/news/183-dune-hd-tv-101-301.html Cheers, hepi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] perfect little vdr client hardware
The netv from chumby seems to be perfect as a hardware client to VDR, if it can decode mpeg2/h.264. Does anyone here know any more about this product? It seems to be fairly open, and based on an embedded linux distro. http://wiki.chumby.com/index.php/NeTV_developer_info -- -Tor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr