Re: vaapi h264 ts problem

Hello,

thanks to reply.


I make xine_crash.log with your advice
and hope that be usefull.

I do many test with older ffmpeg, video driver, libva (vaapi)...

For now again only ffmpeg-1.0.7 is the only one version working with 
h264 ts and vaapi.

See you




Le 06/07/2013 19:50, Torsten Jager a écrit :
> Hello,
>
>> vaapi is broken again for h264 ts (not for mpeg2)
>
> Oh dear.
>
> I do not have VAAPI hardware. I use opengl2 and sometimes VDPAU
> through the binary NVIDIA driver. Thus I cannot reproduce your
> issue here. I remember Petri once told me he is using Intel gfx
> but he also seems to be far away for weeks now.
>
> But we can at least try to get a crash report. Since XINE
> crashed with a classic segfault, running it inside the debugger
> should help:
>
>   $ gdb xine | tee xine_crash.log
>
> If that fails please install the GNU debugger.
> There should be some welcome info now followed by a list of
> loaded and missing debug symbols. XINE and xine-lib syms
> are probably present because you built these yourself from
> sources. For the VAAPI subsytem you depend on the kindness
> of your gfx driver (my NVIDIA one cloaks itself into silence
> there... ).
>
> Run xine:
>
>   (gdb) run --verbose=2 00001.ts
>
> Sooner or later that crash appears:
>
>   Program received signal SIGSEGV, Segmentation fault.
>   0xffffe430 in __kernel_vsyscall ()
>   (gdb) _
>
> Now request a so-called backtrace of all threads:
>
>   (gdb) thread apply all bt
>
> Maybe you need to hit ENTER a few times to get all output.
> And exit:
>
>   (gdb) q
>   A debugging session is active.
>
>         Inferior 1 [process 3036] will be killed.
>
>   Quit anyway? (y or n) y
>   $
>
> There should now be a usable xine_crash logfile.
>
> I'm not sure whether xine itself is the reason.
> You may test for that by replacing libs individually
> (not all at once), eg try previous gfx driver with
> new ffmpeg and vice versa.
>
>> libva info: VA-API version 0.34.0
>> libva info: va_getDriverName() returns 0
>> libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_0_34
>> libva info: va_openDriver() returns 0
>> video_out_vaapi vaapi_open: Vendor : Intel i965 driver - 1.2.1.pre1
>> video_out_vaapi vaapi_init : Context width 1920 height 1080
>> video_out_vaapi vaapi_init : guarded render : 1
>> video_out_vaapi vaapi_init : glxrender      : 0
>> video_out_vaapi vaapi_init : glxrender tfp  : 0
>> video_out_vaapi vaapi_init : is_bound       : 1
>> video_out_vaapi vaapi_init : scaling level  : name default value 
>> 0x00000000
>> video_out_vaapi vaapi_open: Deinterlace : 0
>> video_out_vaapi vaapi_open: Render surfaces : 50
>> video_out_vaapi vaapi_open: Opengl render : 0
>> video_out: thread created
>
>> demux_ts: PAT transport_stream_id changed
>> demux_ts: found ISO 639 lang: fra
>> demux_ts: found ISO 639 lang: qaa
>> demux_ts: found ISO 639 lang: qad
>> load_plugins: plugin spudvb will be used for spu streamtype 03.
>
> Do samples _without_ subtitles work?
> Rendering those means tweaking the video out surfaces which is a
> potential hazard.
>
>> ffmpeg_video_dec: vaapi_mpeg_softdec 0
>> ffmpeg_video_dec: VAAPI Enabled in config.
>> load_plugins: plugin ffmpegvideo will be used for video streamtype 4d.
>> ffmpeg_video_dec: force AVDISCARD_DEFAULT for VAAPI
>> ffmpeg_video_dec: direct rendering enabled
>> ffmpeg_video_dec: direct rendering enabled
>> ffmpeg_audio_dec: augmentation du buffer à 98304 pour éviter sa 
>> saturation.
>> ffmpeg_video_dec: augmentation du buffer à 206359 pour éviter sa 
>> saturation.
>
>> libva info: VA-API version 0.34.0
>> libva info: va_getDriverName() returns 0
>> libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_0_34
>> libva info: va_openDriver() returns 0
>> video_out_vaapi VAAPI Supported Profiles : VAProfileMPEG2Simple
>> VAProfileMPEG2Main VAProfileH264Baseline VAProfileH264Main
>> VAProfileH264High VAProfileVC1Simple VAProfileVC1Main
>> VAProfileVC1Advanced <unknown> <unknown>
>> video_out_vaapi VAAPI Profile VAProfileH264High supported by your 
>> hardware
>> libva info: VA-API version 0.34.0
>> libva info: va_getDriverName() returns 0
>> libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so
>> libva info: Found init function __vaDriverInit_0_34
>> libva info: va_openDriver() returns 0
>> video_out_vaapi vaapi_open: Vendor : Intel i965 driver - 1.2.1.pre1
>> video_out_vaapi vaapi_init : Context width 0 height 0
>> video_out_vaapi vaapi_init : Profile: 7 (VAProfileH264High) Entrypoint 1
>> (VAEntrypointVLD) Surfaces 50
>> xiTK received SIGSEGV signal, RIP.
>> Abandon
>>
>
> Well ...
>
> Torsten
>
>
>

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

_______________________________________________
xine-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xine-devel