Hello dear developers,
am I the only one to think that the output GUI interface doesn’t reflect what is/should be happening under the hood when blender outputs video?
I am not quite sure, but isn’t for example h.264 only a codec, not a container format? Why is it then offered under “Movie” output options??
I propose the following model for an interface streamlining pass:
Let user select the Output Container, based on if the output is an Image or Video:
Then let the user chose the codec for video and the codec for audio, along with settings, and a bit of logic behind it so only possible combinations under certain container formats are possible
After that, if possible, let the user select the encoding backend, for example ffmpeg, if the selected combination is offered by ffmepg.
Output Format: Image | Video
–Select streamout: to-file | frameserver
–Select Codecs:
----Video stream: MPG1, MPEG2, MPEG4, FLV, etc.
----Audio stream: PCM, MP2, MP3, AAC
–Select backend: internal, ffmpeg
I think it was more logical in 2.49, where you could select ffmpeg and then edit the suboptions passed to ffmpeg via this pipeline-branch. But to this date I couldn’t quite wrap my head around how the output is organized in 2.5…