On Sun, Jun 30, 2013 at 9:20 AM, Tomas Neme <lacrymol...@gmail.com> wrote: >> Yes. MLT itself is not absolutely dependent on libavcodec. Libavcodec >> is only a dependency of the avformat module, and "yuv422p" appears to >> be a libavcodec pixel format name. > > I see, but I'm the function called mlt_image_format_name in > framework/mlt_frame.c does format_enum >> name translation, having to > do the inverse by hand in every producer / consumer in order to read > parameters seemed a little unnatural.
It has rarely been needed thus far because producers should dictate the format or react to the format parameter of its get_image function. And all consumers have access to the so-called base class (mlt_consumer) mlt_image_format property wherein it does this reverse mapping. Look for info about that property on this page: http://www.mltframework.org/doxygen/properties.html Yeah, maybe someday I will refactor the code behind it into a framework function. I saw you have a _format property in your code, and maybe you want to instead use the existing mlt_image_format property to sync the format of both the rendering thread and the consumer. -- +-DRD-+ ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
