Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
16th February 2018, 08:03 | #21 | Link | |
Registered User
Join Date: Sep 2005
Posts: 178
|
Quote:
Anyway, my understanding of the "multi-bit" builds was that was only for selectable depth output, and hasn't had any effect on what x264 will take in. As long as I've used it, x264 with lavf or y4m support supports all depths that lavf / y4m support for output, and you can even feed it a full 16 bit video if you like. Whether or not this is a good idea depends on other factors, but I usually try to feed it the same depth I'm outputting to (usually 10 bit). Theoretically 16 bit would be better if it had internal support for it, but I'm unsure without looking at the code base. The error that appears when I try to directly encode 10-bit output from avs scripts is vexing though: "avs [error]: not supported pixel type: YUV420P10"? I can only assume this is due to its avs demuxer not handling anything higher than 8 bit, while lavf/y4m handle it just fine. Last edited by `Orum; 16th February 2018 at 08:08. |
|
16th February 2018, 10:54 | #22 | Link |
Registered User
Join Date: Sep 2010
Location: Ukraine, Bohuslav
Posts: 377
|
10-bit y4m input is actually up-converted to 16-bit internally: http://git.videolan.org/?p=x264.git;...ds/master#l282
On my observations 16->10->16 will produce lesser bitrate (against direct 16 bits) with near the same quality. |
16th February 2018, 16:41 | #24 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
Quote:
The avs demuxer was only updated to accept the 16-bit high bit depth pix_fmts from AviSynth+. It'll downsample to 10-bit if you tell it to output 10-bit. |
|
16th February 2018, 19:32 | #25 | Link | |||
Registered User
Join Date: Sep 2005
Posts: 178
|
Quote:
Quote:
Quote:
Code:
src.ConvertBits(10, dither=0).ConvertBits(16) Last edited by `Orum; 16th February 2018 at 19:38. |
|||
17th February 2018, 01:21 | #26 | Link | |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
Quote:
10-bit avs script -> not using the -D option -> 8-bit output 10-bit avs script -> -D 10 -> 10-bit output and it's detected correctly when you look at the [lavf] info line. When you give it a 12-bit script, though, things go sideways. The script is incorrectly detected as 8-bit, and --input-depth does nothing to force it to behave (the output is bugged as well). That's going to have to be fixed in the LAVF patch, since it's completely isolated to that patch; libavformat itself is totally fine with 12-bit input from AviSynth+, and will pass it to libx265 correctly as 12-bit when it happens inside FFmpeg. |
|
Tags |
avs2yuv, avs2yuv64, x265 |
|
|