Re: xine drops most of the frames from deinterlaced video when using opengl output
Christophe Thommeret <[email protected]>
| Newsgroups | gmane.comp.video.xine.devel |
|---|---|
| Message-ID | <[email protected]> |
Le 17/04/2012 13:48, Michal a écrit : > Recently, I had to switch from xv output to opengl, because Intel's > sandybridge integrated graphics lacks vsync support for xv. > Unfortunately, there is some problem with opengl output when tvtime > deinterlacing is used. Most of the frames are dropped and the video is > unwatchable. > > Steps to reproduce are simple: > - download http://www.w6rz.net/vertrezmotion.zip > - run > xine -V opengl \ > --post > tvtime:method=Greedy2Frame,enable=1,cheap=0,chroma_filter=0,pulldown=none,framerate_mode=full,judder_correction=1,use_progressive_frame_flag=1 > \ > --post pp:quality=0 \ > vertrezmotion.ts > > If I use xv instead of opengl then everything works fine (except the > tearing caused by missing vsync). > > CPU usage is minimal. I've added a logging of frames_to_skip to function > vo_frame_draw() in video_out.c. In case of xv output it settles around > -14 after a while. And in case of opengl it oscillates between ca. -10 > and 24. Does anybody have an idea what could be wrong? > The old opengl output driver's FragProg method does not support yuy2. TVTime deinterlacer converts frames to yuy2 format, unless cheap_mode is set to 1. That might be the problem. ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev