xineliboutput-devel

[xineliboutput-devel] Still no joy with xineliboutput and xine-lib-1.2

[Chris R. <ran...@ya...>]

Hi,

I've cloned the git repository at git://projects.vdr-developer.org/xineliboutput and compiled it against xine-lib-1.2. (Like xine-lib-1.2, I needed to patch the Makefile before xineliboutput would compile:

diff --git a/Makefile b/Makefile
index 47ffdec..84f6e41 100644
--- a/Makefile
+++ b/Makefile
@@ -179,7 +179,7 @@ endif
 ### Includes and Defines (add further entries here):
 ###

-INCLUDES  += -I$(VDRINCDIR)
+INCLUDES  += -I$(VDRINCDIR) -I/usr/include/ffmpeg

 ifeq ($(ARCH_APPLE_DARWIN), yes)
     INCLUDES  += -I/sw/include


I'm thinking no-one else is using Fedora, or these build breakages would have been noticed already!)

Unfortunately, xine still refuses to talk to VDR. This time, it says:=0A=0A=0A"There is no input plugin available to handle 'vdr://tmp/vdr-xine/stream#demux:mpeg_pes'.


Yeah, right.

Is anyone actually *testing* xine or xineliboutput any more? Because I've tested xinelibout against both xine-lib-1.1 and xine-lib-1.2 and it has utterly failed to do anything with either!


Cheers,
Chris

Re: [xineliboutput-devel] Still no joy with xineliboutput and xine-lib-1.2

[Petri H. <phi...@us...>]

On la, 2012-07-28 at 14:44 -0700, Chris Rankin wrote:
> Hi,
>
> I've cloned the git repository at git://projects.vdr-developer.org/xineliboutput and 
> compiled it against xine-lib-1.2. (Like xine-lib-1.2, I needed to patch the Makefile 
> before xineliboutput would compile:
> 
> diff --git a/Makefile b/Makefile
> index 47ffdec..84f6e41 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -179,7 +179,7 @@ endif
>  ### Includes and Defines (add further entries here):
>  ###
> 
> -INCLUDES  += -I$(VDRINCDIR)
> +INCLUDES  += -I$(VDRINCDIR) -I/usr/include/ffmpeg
> 
>  ifeq ($(ARCH_APPLE_DARWIN), yes)
>      INCLUDES  += -I/sw/include

That's expected if headers or libraries are installed to non-default
places. You can give the path to configure script as parameter or add it
to Make.config file.

Does pkg-config give correct include path for libavutil (pkg-config
libavutil --cflags) ? If yes, this should be fixed in CVS now.

> I'm thinking no-one else is using Fedora, or these build breakages would have been noticed already!)
> 
> Unfortunately, xine still refuses to talk to VDR. This time, it says:=0A=0A=0A"There is no input 
> plugin available to handle 'vdr://tmp/vdr-xine/stream#demux:mpeg_pes'.

Wrong mrl (xineliboutput uses xvdr:// ...)

> Yeah, right.
> 
> Is anyone actually *testing* xine or xineliboutput any more? Because I've tested xinelibout 
> against both xine-lib-1.1 and xine-lib-1.2 and it has utterly failed to do anything with either!

Yes, both xine-lib versions should work equally well with xineliboutput.

I've experienced some problems when both 1.1.x and 1.2.x are installed
at the same time. Also make sure you don't have loads of old xine
plugins in /usr/lib/xine/plugins/


- Petri

Re: [xineliboutput-devel] Still no joy with xineliboutput and xine-lib-1.2

[Chris R. <ran...@ya...>]

----- Original Message -----

> Does pkg-config give correct include path for libavutil (pkg-config
> libavutil --cflags) ? If yes, this should be fixed in CVS now.

It says:

# pkg-config libavutil --cflags
-I/usr/include/ffmpeg

So this is correct. However, anything checking for libavutil headers would need to include this during any autoconf step. (Which is probably where xine-lib-1.2 goes wrong...)

Cheers,
Chris

Re: [xineliboutput-devel] Still no joy with xineliboutput and xine-lib-1.2

[Chris R. <ran...@ya...>]

----- Original Message -----

>> Unfortunately, xine still refuses to talk to VDR. This time, it says:=0A=0A=0A"There is no input 
>> plugin available to handle 'vdr://tmp/vdr-xine/stream#demux:mpeg_pes'.
>
> Wrong mrl (xineliboutput uses xvdr:// ...)

Ah, xine-lib-1.2 contains another plugin: xineplug_vdr.so. When I remove this plugin, xine-ui has enough room to display the xvdr button.

Pressing the xvdr button results in the exact same spectacular failure as with xine-lib-1.1 where xine-ui displays nothing from VDR except "No Signal", if I'm lucky.

> Yes, both xine-lib versions should work equally well with xineliboutput.

Indeed - it fails equally with both...

Jul 29 13:57:34 endgame vdr: [20992] [xine..put] Detected video size 720x576
Jul 29 13:57:47 endgame vdr: [20984] [xine..put] Client 0 connected: 127.0.0.1:54423
Jul 29 13:57:47 endgame vdr: [20984] loading /etc/vdr/plugins/xineliboutput/allowed_hosts.conf
Jul 29 13:57:47 endgame vdr: [20984] creating directory /etc/vdr/plugins/xineliboutput/pipes.20976
Jul 29 13:57:47 endgame vdr: [20984] removing /etc/vdr/plugins/xineliboutput/pipes.20976
Jul 29 13:58:16 endgame vdr: [20976] switching to channel 2
Jul 29 13:58:17 endgame vdr: [20993] TS buffer on device 1 thread ended (pid=20976, tid=20993)
Jul 29 13:58:17 endgame vdr: [20992] buffer stats: 82156 (3%) used
Jul 29 13:58:17 endgame vdr: [20992] receiver on device 1 thread ended (pid=20976, tid=20992)
Jul 29 13:58:17 endgame vdr: [21023] receiver on device 1 thread started (pid=20976, tid=21023)
Jul 29 13:58:17 endgame vdr: [21024] TS buffer on device 1 thread started (pid=20976, tid=21024)
Jul 29 13:58:17 endgame vdr: [20984] [xine..put] Client connection 0 closed
Jul 29 13:58:17 endgame vdr: [20984] [xine..put] Closing connection 0
Jul 29 13:58:17 endgame vdr: [21023] [xine..put] Detected video size 720x576

Have you tested with VDR 1.7(.27)?

Cheers,
Chris

Re: [xineliboutput-devel] Still no joy with xineliboutput and xine-lib-1.2

[Chris R. <ran...@ya...>]

> Yes, both xine-lib versions should work equally well with xineliboutput.


For reference:
* I am using Fedora 17's VDR 1.7.27 RPM, and libxine1.2.2 RPMs compiled from the repository.
* xineliboutput is passed these parameters: --local=none --remote=37890
* xine-ui is my front-end.
* For some reason, xineliboutput's vdr_event_cb() function is receiving a XINE_EVENT_UI_PLAYBACK_FINISHED event, which sets this->control_running = 0.

Cheers,
Chris