Francesco Romani wrote:
For modules, main documentation is in docs/module-system-API.txt
Feel free to send any comment about that.
Sure.
About the issues that comes into my mind, the very first are
- timestamp preserving on frame sources
Yes. If the frame_buffer_t - which from my initial understanding is the
basis for Audio/Video Access unit Storage:
This structure could have various attributes filled up based upon the
processing stage the frame is in?
For example - Clock information,derived from container format could be
added to the frame_buffer_t . This tagged information would be retained
through the post/pre/encoding and be used in AV sync activities in the
final stage.
How is Av sync achieved currently?
I, Makes any sense?
- proper frame marking (based on above)
pray elaborate?
- dealing with missing/skipped/corrupted frames on source
could this be handled by having video Stream as the Master clock?
- frame rate conversions
- filter reordering (if any) or delay (if any)
- proper muxing decision based on all of above
hmmm...
And much, much more.
