GNOME Bugzilla – Bug 652261
xvidenc needs codec profiles in caps
Last modified: 2011-12-01 08:58:58 UTC
This is a mirror of the 651320 bug against ffenc_mpeg4, however I noticed that xvidenc actually got a lot more profiles set as properties so in terms of creating the profiles for mpeg4 video xvidenc is probably the best starting point and then moving onto enabling what can be enabled or ffenc_mpeg4.
xvidenc confuses profiles and levels. There are really only SP, ASP, ARTS, and unconstrained.
<slomo> cschalle: and xvidenc doesn't negotiate the profile via caps, it only has a property for that cschalle: so... something should still be done there and actually you're right, the profile needs to be on the caps then ;) cschalle: could you update the bug? it should say that xvidenc should put profile/level into the caps and that it should negotiate the profile with downstream via caps instead of a property <cschalle> slomo, yes, to me this is just like the aac encoders, which also used to use properties, but we added it also to the caps <slomo> cschalle: yes, it's exactly the same... and the same as for x264enc
commit b23d0790ce3d144719e9a68fa1ad4966a75f9285 Author: Sebastian Dröge <sebastian.droege@collabora.co.uk> Date: Thu Dec 1 09:54:08 2011 +0100 xvidenc: Add profile/level to the caps and negotiate them with downstream Still keep the profile property to select profile/level if there are no downstream constraints. Fixes bug #652261. commit 8c02dd5b6b2dd00a2b1b5a4a65c6dea7ac8b4980 Author: Sebastian Dröge <sebastian.droege@collabora.co.uk> Date: Thu Dec 1 09:39:11 2011 +0100 xvidenc: Add support for levels 4a/5/6 of the simple profile