So i've understood, but I don't really see why these values are not available anymore. I realize that messing with the internals of various codecs is not why libav is made for, but these fields are calculated anyway, so why not propagate it to the AVFrame ?
2014-03-25 12:06 GMT+01:00 Tomas Härdin <[email protected]>: > > On 2014-03-25 11:29, cyril poulet wrote: > >> Hi all >> As others who already posted on this matter but got no answers, I'm >> trying to get motion vectors from h264 codec (P-frames). >> Before v2, they seemed to be available in AVFrame::motion_val, (along >> with motion_subsample_log2 and mb_type), which are now deprecated. >> >> Is there any way to get these values since v2 ? >> >> (I'm also interested in getting back the dct_coeff for I-frames, but >> something tells me that all these questions are linked) >> > I think the general direction nowadays is to hide such internals. If you > want access to this stuff in the future you'll have to fork and hack the > functionality in > > /Tomas > _______________________________________________ > Libav-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/libav-user >
_______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
