Would it be possible to provide a static build of ffmpeg with the 10-bit version of x264?

I'd like to be able to use ffmpeg to encode using the libx264 high422 profile with a 10 bit depth — I'm investigating it as a way of storing 10-bit 422 (prores and dnxhd) camera footage, using less room, but keeping the grade-ability of the originals. But compiling two different versions of x264 and linking it to two different ffmpegs is way beyond my newb Windows user capabilities. Would this be do-able?

It's difficult to include 10-bit x264 support because then I would need to provide 4 different builds (Win32, Win64 in static and shared linking).

This would be a substantiation amount of extra work, but if there is enough demand for 10-bit support I would defiantly consider it. So far there have been very few requests for 10-bit support to warrant the extra complication it would cause.

You didn't say what you wanted to wanted to store the 10-bit AVC in. I just pipe to the VLC x264 builds and output as an MP4 without audio. I don't know if that will work for you. If you need audio, you can add it with MP4Box or FFMPEG on a post-encode command in a batch file (windows) or shell script (Linux/Mac).

Zeranoe wrote:It's difficult to include 10-bit x264 support because....a substantiation amount of extra work

I would like to see a 10bit-x264-static too. So here is my suggestion.

Only release a 10bit-x264 build once a month, and only in Win32 (which will still run on 64bit systems)

As of the original thread posting, only 20(10x2) extra builds would have been done, from then to now. To put that in perspective 300(75x4) builds have been done in that same time frame.

This would vastly reduce the work required, while still having some 10-bit x264 support that's only slightly off current.

If that's still a bit much, release only a linked-10bit-x264-win32 build. All the static users can use the linked version, it's just more files to keep track of. And that would only have been 10 extra builds since the original post, which at 1/30th additional amount of work, may not feel so substantiation(substantial).

Zeranoe wrote:It's difficult to include 10-bit x264 support because....a substantiation amount of extra work

I would like to see a 10bit-x264-static too. So here is my suggestion.

Only release a 10bit-x264 build once a month, and only in Win32 (which will still run on 64bit systems)

As of the original thread posting, only 20(10x2) extra builds would have been done, from then to now. To put that in perspective 300(75x4) builds have been done in that same time frame.

This would vastly reduce the work required, while still having some 10-bit x264 support that's only slightly off current.

If that's still a bit much, release only a linked-10bit-x264-win32 build. All the static users can use the linked version, it's just more files to keep track of. And that would only have been 10 extra builds since the original post, which at 1/30th additional amount of work, may not feel so substantiation(substantial).