Hi Karthick,
>> >> Another approch might be to store the wallclock frame time as some kind of >> metadata (as it is done for "timecode") and then add the possiblity to >> f_select to drop based on this. However the evaluation engine has no concept >> of complex objects (like frame, or frame metadata) so this probably needs >> additional work. > This involves a lot of extra work for a feature that can be implemented very > easily on the capture plugin. And still other capture plugins will have to > add the relevant metadata/sidedata for this feature to work for them. If you > still think that decklink plugin is not the right place to add this feature, > then I respect that decision. I will live with the f_select solution with > extra restrictions on timestamping options ( > Thanks again for your valuable suggestions. > After further discussion of the alternatives, putting it directly in the decklink module does seem like the least invasive option. While it would be nice if this functionality could be shared with other realtime sources, the framework doesn’t really seem to lend itself to that and it seems like a good bit more trouble than it’s worth. I withdrawal any objections I had to the original patch. Devin --- Devin Heitmueller - LTN Global Communications dheitmuel...@ltnglobal.com _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
