Good question, I don't know for certain, but I'm afraid not.
The patches are not completely finished, so I'd be very surprised if upstream accepted them.
Maybe we should look into this and make it a goal: to get (some) patches accepted upstream as soon as possible.
An action plan would be (just brainstorming here):
1- gather information on the current state of the patches
2- determine what code changes are minimally required to get the patches accepted upstream
3- divide the work over the people willing to contribute
4- wait for SVN commits to be made to our repository
5- repeat 1-4 until we've got a candidate to submit upstream
6- submit the patches upstream
7- then we'll see what feedback we get from the FFmpeg developers....
So the very next action is "to gather information on the current state of the patches".
Our project page (
http://code.google.com/p/amv-codec-tools/) already has a wealth of details on the current state, but not from the perspective. of going upstream.
Who wants to help (a little) by:
- starting a new page on the wiki on "going upstream", to list this action plan and all related details on going upstream
- perhaps also changing the roadmap to include going upstream as a goal
- making a list what patches we have (multiplexer, demultiplexer, audio codec,...) ?
- diffing our repository to ffmeg's to see what changes we have
- compiling our binary, making an AMV and testing it to provide feedback
Best regards,
Tom Van Braeckel.