Skip to main content
kalamazandy
Known Participant
February 13, 2023
Open for Voting

Show source and output helpers with less technical Only information

  • February 13, 2023
  • 0 replies
  • 24 views

A great example is H.264 and H.265.

Profile: Main and Main 10 - currently the tooltip says "Constrains the bitrate range and controls other properties such as compression algorithm and chroma format."

You'll find similar things with level and tier. 

 

For artists, we care about a few things right? Does it look good, and is it a useable size? 

But if you're doing something like, making proxies, how much technical knowledge is expected? Sure, ProRes is Great and all, but it's HUGE! If you compare performance with H.265 Intra, you'll be pretty surprised. 

But lets say you want to set that up in AME. The source tells you the name, dimensions, fps, that it is progressive (because lets get real, you're not using interlaced anymore), and time. 

But what Could be there that is useful to artists? Chroma format. Is your original 4.2.0? Is it 4.2.2, 4.4.4? AME doesn't tell you. 

And it incorrectly has a checkbox next to it, that would lead you to believe it's matching the correct profile, level and tier to the source footage.

 

My current footage is 10 bit 4:2:2. My Output ends up being 10 bit 4:2:0. I lost resolution in chroma, but AME didn't tell me that. 

H.265 is an interesting example also, because there is Main, Main10, but also REXT profile. REXT is required for yuv444, and yuv422 might not be an option for hardware encoding? Now see, I'm not quite that technical. 

 

What most anyone can agree on, is the source has color information, and the output has color information. It is useful to Anyone, to understand what they might be changing. And to the same effect, there's likely not much point in taking 8bit 4:1:0 and converting that 12bit 4:4:4, because that's just going to take a bunch of space to handle, however, you Will find that moving 8bit to 10bit when reducing bit rate actually does a good job of reducing banding. 

 

Please address the tool tips with useful information. Add color information to the source and output summary. And If there is a checkbox next to encoding settings, they should Actually match the source right? If there is a mismatch and the closest value is used, then I would suggest to indicate that in some way so the users are aware. In the same area, if a user has hardware selected, and they change a setting that automatically changes that, I would recommend that it changes to software, but with a note attached like, "current hardware maximum width supported is 4096" or something like that. That way we know why our render is so slow, and what we might be able to do to fix it. 

The same kind of thing applies to "Render at Maximum Depth." Without seeing what that will effect in the output, it's really annoying. And you can't even check with AME! I've got to do a test file, then check by importing it into premiere, or checking with ffprobe.

 

Please give useability to encoding a little love. And also please realize the usefulness of H.265 intra format since you can hardware encode proxies with sources at 8k resolutions at 10bit, and I Think you can output YUV444 and premiere will still act nicely. I know the format supports it, but not sure if it would still be smooth. But H.265 is about 21 times smaller than ProRes LT at the same size, just as an example, scrubs just as smoothly, and gives fairly comparable results at that size. It seemed the only difference I noticed was in chroma, but that's because AME wouldn't let me get anything but 4:2:0