The maximum video buffer size was increased from 1920x1088 to
2500x2500, and 2500*2500*3 is roughly thrice 1920*1088*3. That's
probably where the size difference comes from. (It would be much
cleverer of transcode to allocate only as much space as was actually
needed for processing, but there's currently no way to propogate size
changes through the processing pipeline, so that'll have to wait for a
future version.)
<brainstorm>
There is a quite clean solution using NMS:
just return from configure() the module memory requirements, collect
them, pick the worst (highest requisites); compare with core requirements
(i.e., -Z), pick the worst again: so we have our numbers.
I don't think there is a way to do equal or better using OMS (and that's
why it _IS NOT_ done in OMS).
That looks like a post-1.1.0 task, anyway.
</brainstorm>
I defintively must figure out how to live without sleeping :^)
--
Francesco Romani
