Since there are a lot of users complaining about crashes when exporting movie files (you should not do this anyway), I decided to start a list so we can remove the codecs which fail from the export settings.
Also thinking about limiting to only a few working codecs (@rodlie) ?
And a checker which checks if File ending is correct to Container selection ?!
Would be nice if other useres, especially (MacOSX/Windows) could also test and submit their results, so I can open a Github issue an report which codes shall be removed from the write node
(There are some formats breaking when the render gets paused…).
ProRes (MOV) 444/422 output works great (on all platforms), been using that for at least a year now (I have short deadlines, and mostly do motion graphics. So MOV’s fit my workflow better than sequences).
It should be
Codec + Containers (Containers are common in all o/s platform, since win7 support is dropped)
mp4 doesn’t support apple prores. Prores only supports mov container.
Is there any report link to see the problem deeply?
There is a built-in list integrated in write node which can verify Container+Codec compatibility. A mismatch gives warning in the viewport. So, I think it can be done to hide non compatible codecs from the codec dropdown according to the container. Possible hint? @rodlie
5. All image sequence codec should be UNTOUCHED with MOV. As it is required in studio environments. with quicktime/mov
So far only complaint I get before was with mp4 container. There is a error till now with mp4 container + avc1 codec family.
Instead it should use mp4 container+ cisco openh264 codec.
[Edit: it is fixed now. Only VLC won’t support avc1]
If there are crashes, then it’s a real issue. Please report that on github with a sample project file. Any valid codec/container combination should work. If it doesn’t, it’s a bug.
@cgvirus: its somehow possible to export prores in a mp4 container in Natorn, which I agree should not be possible.
@devernay
While testing all the codecs, I begin to realize that new users complaining about movie export, do not select the right container / codec combination.
So maybe I should write a section in the manual on how to use the write node and which combinations do work (question is: do they even read the docs?), or we just leave it as is and get used to have every month someone complaining here…
If a user has a container selected that can’t support a codec ideally that codec shouldn’t even be able to be selected in the first place if it won’t work. This is more of a UX issue than a “users should read the docs and tooltips to be informed” issue.
Actually this can also be considered bad UX, because the user doesn’t know how to get a given codec or a given container. And this can become impossible to select a codec, eg if a codec A only works with container B and container B only supports container A, they would never be selectable.
Believe me, we tried everything, and that’s the best we could get. It’s a very minor issue for users, since that codec/container choice usually happens when they create their first project, and the default is a reasonable one for every container.
The Red error message Fred mentions seems ok to me.
If we really want to add something to it, that could be:
“Hover the container box for a compatibility list”
and