Re: [vdr] tvguide 0.0.1
Don't you have following error in the log? vdr: [8343] ERROR: cOsd::SetAreas returned 3 (bpp not supported) I'm experiencing the same crash. I'm using xineliboutput and there seems to be some problem with truecolor OSD support. Michal On 01/03/2013 03:55 PM, syrius...@no-log.org wrote: Hi, I've just discovered tvguide on vdr-developper.org. I'm running vdr 1.7.31. i followed the instructions, copied the themes files to $VDRCONF/themes. When i try to use the plugin I get nothing (osd goes away). vdr control doesn't work anymore so i guess the plugin is activated. And vdr segfaults when i press OK. I don't have any channellogos or epgimages, the plugin is run with no option. The README file doesn't tell much about theses images anyway. (format, filename, examples files, etc... nothing) vdr-tvguide-0.0.1.tgz seems to date from september, is there a public repo for this plugin ? logs: vdr: [7439] tvguide: Rendering took 0 ms vdr[7439]: segfault at 20 ip 7f494f59254e sp 7fff4b73be80 error 4 in libvdr-tvguide.so.1.7.31[7f494f581000+1b000] config: OSDSkin = sttng OSDTheme = default tvguide.bigStepHours = 3 tvguide.channelCols = 5 tvguide.displayTime = 160 tvguide.epgImageHeight = 240 tvguide.epgImageWidth = 315 tvguide.fontButtonSize = 33 tvguide.fontDetailHeaderSize = 40 tvguide.fontDetailViewSize = 33 tvguide.fontGridSize = 27 tvguide.fontGridSmallSize = 24 tvguide.fontHeaderSize = 33 tvguide.fontIndex = 0 tvguide.fontMessageBoxLargeSize = 40 tvguide.fontMessageBoxSize = 33 tvguide.fontTimeLineDateSize = 33 tvguide.fontTimeLineTimeSize = 0 tvguide.fontTimeLineWeekdaySize = 40 tvguide.footerHeight = 80 tvguide.headerHeight = 120 tvguide.hideChannelLogos = 1 tvguide.hideEpgImages = 1 tvguide.hugeStepHours = 24 tvguide.jumpChannels = 5 tvguide.logoExtension = 0 tvguide.logoHeight = 73 tvguide.logoWidth = 130 tvguide.roundedCorners = 0 tvguide.themeIndex = 1 tvguide.timeColWidth = 120 tvguide.timeFormat = 1 tvguide.useBlending = 1 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] (v2) vdr-xine-0.9.4 vdr-1.7.33 video scaling API (YAEPG-Hack now obsolete)
Hello,
On 12/25/2012 09:02 PM, Reinhard Nissl wrote:
Hi,
[..]
I appreciate your patches and will have a look at it during the next days.
after some clarifications of the new API, thanks to Klaus and "Johns"
the author of the softhddevice output device plugin, here is a new
version of the scaling API patch for vdr-xine.
Regards,
Lucian
diff -Naur xine-0.9.4_orig/xineDevice.c xine-0.9.4/xineDevice.c
--- xine-0.9.4_orig/xineDevice.c 2011-02-27 19:14:19.0 +0100
+++ xine-0.9.4/xineDevice.c 2013-01-03 21:54:57.585874032 +0100
@@ -4405,5 +4405,83 @@
{
return theXineDevice;
}
+#if APIVERSNUM >= 10733
+ ///< Asks the output device whether it can scale the currently shown video in
+ ///< such a way that it fits into the given Rect, while retaining its proper
+ ///< aspect ratio. If the scaled video doesn't exactly fit into Rect, Alignment
+ ///< is used to determine how to align the actual rectangle with the requested
+ ///< one. The actual rectangle can be smaller, larger or the same size as the
+ ///< given Rect, and its location may differ, depending on the capabilities of
+ ///< the output device, which may not be able to display a scaled video at
+ ///< arbitrary sizes and locations. The device shall, however, do its best to
+ ///< match the requested Rect as closely as possible, preferring a size and
+ ///< location that fits completely into the requested Rect if possible.
+ ///< Returns the rectangle that can actually be used when scaling the video.
+ ///< A skin plugin using this function should rearrange its content according
+ ///< to the rectangle returned from calling this function, and should especially
+ ///< be prepared for cases where the returned rectangle is way off the requested
+ ///< Rect, or even Null. In such cases, the skin may want to fall back to
+ ///< working with full screen video.
+ ///< If this device can't scale the video, a Null rectangle is returned (this
+ ///< is also the default implementation).
+ cRect cXineDevice::CanScaleVideo(const cRect &Rect, int Alignment/* = taCenter*/)
+ {
+// first implementation: we can always scale, we're a soft device ;-), ignore alignment for now
+
+// we need to store the value for the case we have to call ScaleVideo ourselves in vdr-xine
+vidWinRect = Rect;
+return vidWinRect;
+ }
+
+ ///< Scales the currently shown video in such a way that it fits into the given
+ ///< Rect. Rect should be one retrieved through a previous call to
+ ///< CanScaleVideo() (otherwise results may be undefined).
+ ///< Even if video output is scaled, the functions GetVideoSize() and
+ ///< GetOsdSize() must still return the same values as if in full screen mode!
+ ///< If this device can't scale the video, nothing happens.
+ ///< To restore full screen video, call this function with a Null rectangle.
+ void cXineDevice::ScaleVideo(const cRect &Rect/* = cRect::Null*/)
+ {
+// refresh stored value
+vidWinRect = Rect;
+// let our specialized code do the actual resizing / repositioning, get accurate parameters first
+int videoLeft, videoTop, videoWidth, videoHeight, videoZoomX, videoZoomY, osdWidth, osdHeight;
+double videoAspect, pixelAspect;
+m_xineLib.execFuncVideoSize(videoLeft, videoTop, videoWidth, videoHeight, videoZoomX, videoZoomY, &videoAspect);
+GetOsdSize(osdWidth, osdHeight, pixelAspect);
+tArea vidWinArea;
+vidWinArea.x1 = vidWinRect.X();
+vidWinArea.y1 = vidWinRect.Y();
+vidWinArea.x2 = vidWinRect.X() + vidWinRect.Width();
+vidWinArea.y2 = vidWinRect.Y() + vidWinRect.Height();
+if (vidWinRect == cRect::Null) {
+// will just resize to full size
+vidWinArea.bpp = 0;
+} else {
+vidWinArea.bpp = 12;
+// make corrections
+double aspectFactor = (double(osdWidth) / double(osdHeight)) / videoAspect;
+int output_width = vidWinRect.Height() * (videoAspect * aspectFactor);
+int output_height = vidWinRect.Width() / (videoAspect * aspectFactor);
+if (double(vidWinRect.Width())/double(vidWinRect.Height()) > videoAspect * aspectFactor) {
+output_height = vidWinRect.Height();
+vidWinArea.x1 += (vidWinRect.Width() - output_width) / 2;
+}
+else if (double(vidWinRect.Width())/double(vidWinRect.Height()) < videoAspect * aspectFactor) {
+output_width = vidWinRect.Width();
+vidWinArea.y1 += (vidWinRect.Height() - output_height) / 2;
+}
+vidWinArea.x2 = vidWinArea.x1 + output_width;
+vidWinArea.y2 = vidWinArea.y1 + output_height;
+}
+m_xineLib.SetVideoWindow(videoWidth, videoHeight, vidWinArea);
+ }
+
+ const cRect & cXineDevice::GetScaleRect()
+ {
+// just return the stored value
+return vidWinRect;
+ }
+#endif // APIVERSNUM >= 10733
};
diff -Naur xine-0.9.4_orig/xineDevice.h xine-0.9.4/xineDevice.h
--- xine-0.9.4_orig/xineDevice.h 2011-02-27 15:28:58.0 +0100
+++ xine-
[vdr] [ANNOUNCE] vdr-upnp 1.0.0
Hi all, I want to release a new version of the UPnP/DLNA media server plugin for the VDR: Version 1.0.0 Major changes: - usage of sub plugins to make extensibility easier. - usage of tntnet for http communication (no patch for additional headers in libupnp required) - usage of streamdev-server for live tv streaming Project website: http://projects.vdr-developer.org/projects/plg-upnp Git: http://projects.vdr-developer.org/git/vdr-plugin-upnp.git If you face any issues, please report bugs on the project web site. Thank you! Denis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Permissions in vdr-1.7.35 tarball
The directories in the vdr-1.7.35 tarball are set to mode 700. If, like me, you run vdr directly from the source tree but under a different user to the one you use for compiling, your plugins will not load. Dave ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] tvguide 0.0.1
Hi, I've just discovered tvguide on vdr-developper.org. I'm running vdr 1.7.31. i followed the instructions, copied the themes files to $VDRCONF/themes. When i try to use the plugin I get nothing (osd goes away). vdr control doesn't work anymore so i guess the plugin is activated. And vdr segfaults when i press OK. I don't have any channellogos or epgimages, the plugin is run with no option. The README file doesn't tell much about theses images anyway. (format, filename, examples files, etc... nothing) vdr-tvguide-0.0.1.tgz seems to date from september, is there a public repo for this plugin ? logs: vdr: [7439] tvguide: Rendering took 0 ms vdr[7439]: segfault at 20 ip 7f494f59254e sp 7fff4b73be80 error 4 in libvdr-tvguide.so.1.7.31[7f494f581000+1b000] config: OSDSkin = sttng OSDTheme = default tvguide.bigStepHours = 3 tvguide.channelCols = 5 tvguide.displayTime = 160 tvguide.epgImageHeight = 240 tvguide.epgImageWidth = 315 tvguide.fontButtonSize = 33 tvguide.fontDetailHeaderSize = 40 tvguide.fontDetailViewSize = 33 tvguide.fontGridSize = 27 tvguide.fontGridSmallSize = 24 tvguide.fontHeaderSize = 33 tvguide.fontIndex = 0 tvguide.fontMessageBoxLargeSize = 40 tvguide.fontMessageBoxSize = 33 tvguide.fontTimeLineDateSize = 33 tvguide.fontTimeLineTimeSize = 0 tvguide.fontTimeLineWeekdaySize = 40 tvguide.footerHeight = 80 tvguide.headerHeight = 120 tvguide.hideChannelLogos = 1 tvguide.hideEpgImages = 1 tvguide.hugeStepHours = 24 tvguide.jumpChannels = 5 tvguide.logoExtension = 0 tvguide.logoHeight = 73 tvguide.logoWidth = 130 tvguide.roundedCorners = 0 tvguide.themeIndex = 1 tvguide.timeColWidth = 120 tvguide.timeFormat = 1 tvguide.useBlending = 1 -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Tuning timeouts blocks the other adapter
Mariusz Bialonczyk writes: > On 01/03/2013 02:09 PM, syrius...@no-log.org wrote: >> I'm not using the xvdr plugin, what would be the equivalent workaround >> for vdr itself ? > > The equivalent in VDR should be this: > http://pastebin.com/raw.php?i=RnW6p5gt Thanks Mariusz ! Giving it a try right now. -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Tuning timeouts blocks the other adapter
On 01/03/2013 02:09 PM, syrius...@no-log.org wrote: > I'm not using the xvdr plugin, what would be the equivalent workaround > for vdr itself ? The equivalent in VDR should be this: http://pastebin.com/raw.php?i=RnW6p5gt regards, -- Mariusz Białończyk jabber/e-mail: ma...@skyboo.net http://manio.skyboo.net ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Tuning timeouts blocks the other adapter
Mariusz Bialonczyk writes: > On 11/10/2012 12:12 AM, Mariusz Bialonczyk wrote: >> Is it possible that it is caused by some global lock or mutexes >> in VDR? > > Hello > It seems the cause of the problem has been located by Alex Pipelka. > > The vdr freezes occurs when obtaining the signal strength/quality > with functions SignalStrength() and/or SignalQuality() > and when non-busy adapter has tunining issues > (frontend x/x timed out while tuning to channel ...). > It occurs only on multi adapters systems (one adapter is doing > EIT scan and the other is used, eg for a live-tv). > > Guys, any thoughts on this? > I think it may be even kernel/drivers related issue. > > some details in commit discussion: > https://github.com/pipelka/vdr-plugin-xvdr/commit/d3982714 Hi, I'm experiencing a similar issue, i have 3 dvb-s cards. I'm not using the xvdr plugin, what would be the equivalent workaround for vdr itself ? -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35
On 01/01/2013 09:52 PM, Lars Hanisch wrote: [...] I must confess that normally threads at a forum are easier to read and understand as mailing list threads in any mail-archive. First you have to found such an archive (or have to know that something like that even exists) and then it's complicated to search or even browse the archive (monthly indexes etc.). Just FYI, even if many ML readers may do something similar already. One can actually disable email delivery of this ML and read it through nntp at news.gmane.org, this way one can more easily have an overview of threads, and even with email delivery disabled, still post directly to the ML instead of nntp. Lucian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multistream support in VDR
> > Recently in kernel was added full multistream support (DTV_STREAM_ID) > > https://patchwork.kernel.org/patch/1351421/ > > > > is there any plans to implement multistream support in vdr ? > > DTV_STREAM_ID is already used in VDR for DVB-T2. > >>> > >>> what about DTV_STREAM_ID for dvb-s2 ? > >> > >> Which parameter would go in there, and where would it come from? > > > > parameter "P" in channels.conf for identification of sub-stream > > > > WeddingTV;Tivuitalia:11914:HM5S1P2:S31.5E:27500:1026:1027=ita:0:0:4:8572:972:0 > > > > and small patch from crazycat for VDR 1.7.35 > > Have you tested this and does it actually work? no, I have not tested As Manu mentioned - my cx24116 based hvr4000 dvb-s2 card doesn't support multistream Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multistream support in VDR
On Thu, Jan 3, 2013 at 2:08 PM, Klaus Schmidinger
wrote:
> On 03.01.2013 08:22, Goga777 wrote:
>>
>> Recently in kernel was added full multistream support (DTV_STREAM_ID)
>> https://patchwork.kernel.org/patch/1351421/
>>
>> is there any plans to implement multistream support in vdr ?
>
>
> DTV_STREAM_ID is already used in VDR for DVB-T2.
what about DTV_STREAM_ID for dvb-s2 ?
>>>
>>>
>>> Which parameter would go in there, and where would it come from?
>>
>>
>> parameter "P" in channels.conf for identification of sub-stream
>>
>>
>> WeddingTV;Tivuitalia:11914:HM5S1P2:S31.5E:27500:1026:1027=ita:0:0:4:8572:972:0
>>
>> and small patch from crazycat for VDR 1.7.35
>
>
> Have you tested this and does it actually work?
> I can hardly imagine that, because in
>
> + if (frontendType == SYS_DVBT2 || frontendType == SYS_DVBS2) {
> +// DVB-T2/DVB-S2
> SETCMD(DTV_STREAM_ID, dtp.PlpId());
> }
>
> "frontendType" will never be SYS_DVBS2 because in line 816 this is
> already limited to SYS_DVBT or SYS_DVBT2:
>
> else if (frontendType == SYS_DVBT || frontendType == SYS_DVBT2) {
>
DTV_STREAM_ID is supposed to work with the following:
- DVB-S2 (the only current user as of now. Also to be noted
is that, for any other current S2 demodulator in
the kernel, this will not work)
- DVB-T2
- ISDB-T/S
- DVB-C2
so, it shouldn't be restricted to DVB-T/T2 alone.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multistream support in VDR
On 03.01.2013 08:22, Goga777 wrote:
Recently in kernel was added full multistream support (DTV_STREAM_ID)
https://patchwork.kernel.org/patch/1351421/
is there any plans to implement multistream support in vdr ?
DTV_STREAM_ID is already used in VDR for DVB-T2.
what about DTV_STREAM_ID for dvb-s2 ?
Which parameter would go in there, and where would it come from?
parameter "P" in channels.conf for identification of sub-stream
WeddingTV;Tivuitalia:11914:HM5S1P2:S31.5E:27500:1026:1027=ita:0:0:4:8572:972:0
and small patch from crazycat for VDR 1.7.35
Have you tested this and does it actually work?
I can hardly imagine that, because in
+ if (frontendType == SYS_DVBT2 || frontendType == SYS_DVBS2) {
+// DVB-T2/DVB-S2
SETCMD(DTV_STREAM_ID, dtp.PlpId());
}
"frontendType" will never be SYS_DVBS2 because in line 816 this is
already limited to SYS_DVBT or SYS_DVBT2:
else if (frontendType == SYS_DVBT || frontendType == SYS_DVBT2) {
I would assume that this also requires some additional code in VDR's nit.c
in order to store the "PlpId" in the transponder parameters of DVB-S2
transponders (see case case SI::T2DeliverySystemDescriptorTag).
Klaus
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
