[RFC] autoparse element

[Tim Müller]

On Fri, 2013-12-06 at 00:24 +0200, Andrey Utkin wrote:

> The pain is that some parsers (aacparse, ac3parse) have caps property
> name "framed", others (h264parse, mpegvideoparse, mpeg4videoparse)
> have "parsed". Is that a special design (i see audio parsers have
> "framed", and video parsers have "parsed")? 

It's not by design, it's an oversight / inconsistency that we didn't get
around to fixing in the run-up to 1.0. It's not audio vs. video, just
"some audio formats" vs. the rest.

e.g. mpeg-1 audio (mp3 etc.) uses "parsed" not "framed".

 Cheers
  -Tim

-- 
Tim Müller, Centricular Ltd - http://www.centricular.com