![]() ![]() So you're saying that if the total data bitrate in my video is 12000 it could peak above that to 30000 how can that be ? I thought the data bitrate that is written on the video properties can't get higher than the number it has (12000). On the other hand, you are losing a little should the bitrate peak above that. Clamping this to 20000 shouldn't be a significant visual problem and should ensure compatibility with hardware players that can't cope with higher bitrates. If that 12000 is an average across a whole video then it's quite likely you have occasional bitrate peaks above 30000. Like h.264 you can encode without setting a level at all but you lose any guarantee that the settings you've chosen are within the capabilities of hardware decoders and will have to experiment. I don't know how well handbrake handles automatically setting the levels these days. Note that I oversimplified levels by only talking about resolution and frame rate - they also affect the maximum bitrate and reference frames/dpb size, so if your chosen bitrate or dpb size is relatively high for your chosen resolution, you may still need to bump up the level. If you're encoding multiple different things choose a level that will cover the ones with the highest frame rates and resolutions. For greatest compatibility, choose a suitable level for the material you're encoding. Again, this is based on the capabilities of the decoder - it's fine to encode at a higher level than you need, if you know the decoder can support it. Level 4 gets you 1080p video at 30fps, while level 4.1 gets you 1080p video at 60fps. Level 5 gets you 4k video at 30fps, while level 5.1 gets you 4k video at 60fps. Level is just like in h.264 and the actual levels are pretty much equivalent, too. Main 10 is fine to use for 8 or 10 bit color depths and its inclusion in version 1 of the standard means it will enjoy a high level of support as long as the decoder supports 10 bit. But then you have additional profiles for supporting additional decoder capabilities like higher colour depth (10, 12 or 16 bit), less subsampling (4:2:2 or 4:4:4) or intra-constrained (mainly for editing, as it's not efficient). All decoders which can decode h.265 will support it. I appreciate any help or insight and can provide more information if needed.Profile is a set of capabilities of a decoder. What can I check or alter to try fixing this?ฤก6GB RAM, though I forget the speed and the mobo, but I doubt those will be necessary info. ![]() So I'm inclined to believe it's an issue with my computer, whether software or hardware. I am using the most current version of Handbrake (checked for updates again and it says I'm up to date) and the issue persists when using DVDFab as well. I've attempted to alter the settings over the last few days (up the quality to lossless, turn on deinterlacing, deblocking, denoising, slowest optimization, render with CPU, render with GPU.) and tried multiple blurays, including ones that worked before. And it looks worse in motion than in stills. The image on the left is what it used to look like for me, and the image on the right is what it looks like now. (note: the image is 4K because my monitors are 4K, but the actual video is 1080P, same as the source) ![]() ![]() The entire image is noticeably pixelated, as you can see in this comparison shot: In Handbrake (and DVDFab 11) I'm suddenly having an issue wherein any bluray or DVD I rip has a persistent distorted image quality. So I can't seem to find a cause or solution for my issue because I'm having a hard time putting into a search engine what my exact issue is. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |