you mean draw_slice is called from huffyuv.c( I am not sure if this is called) as don't see draw_slice called from h264.c . In h264.c in decode_nal_units, I see a call ff_vdpau_add_data_chunk , . After this I don't see how the control is transferred to draw_slice . Or is draw_slice called before the ff_vdpau_add_data_chunk . Are they running in different threads ? Sorry I've just started looking at it , so had these basic questions . thanks, kumar. On Sun, Aug 30, 2009 at 2:13 PM, Reimar Döffinger <Reimar.Doeffinger@xxxxxx>wrote: > On Sun, Aug 30, 2009 at 09:05:14PM +0000, Carl Eugen Hoyos wrote: > > kkumar s <kumars2007 <at> gmail.com> writes: > > > > > I am trying to understand the code for the data flow when vdpau is > enabled. > > > I see that in libvo/vo_vdpau.c the vdp_device is created , and later > the > > > vdp_decoder is also > > > created. I see a function draw_slice which actually calls > > > vdo_decoder_render. I am not able to figure out how libavcodec calls > > > draw_slice > > > > put_image() in libmpcodecs/vf_vo.c calls draw_slice. > > You got the wrong one, that is just a compatibility wrapper (and > wouldn't work for VDPAU). > It's draw_slice calling draw_slice all the way through from > libavcodec over libmpcodecs to libvo. > _______________________________________________ > MPlayer-users mailing list > MPlayer-users@xxxxxxxxxxxx > https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users > _______________________________________________ MPlayer-users mailing list MPlayer-users@xxxxxxxxxxxx https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
