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. |
6th November 2019, 18:34 | #7162 | Link |
Registered User
Join Date: Jul 2016
Posts: 19
|
For the values, you can use anything you want, but I would recommend using values to meet a certain Tier and Level so you can get Hardware accelerated decoding. You can see those at https://en.wikipedia.org/wiki/High_E...y_Video_Coding, under Tiers and levels section.
I usually set bufsize and maxrate as the same. I cannot find anywhere that shows how high bufsize can be set to to maintain DXVA hardware decoding, so I use the following for all my encodes for x265. 480p:--vbv-bufsize 12000 --vbv-maxrate 12000 1080p:--vbv-bufsize 20000 --vbv-maxrate 20000 2160p:--vbv-bufsize 25000 --vbv-maxrate 25000 These have all resulted in DXVA compatible files. |
7th November 2019, 04:34 | #7163 | Link | |
Registered User
Join Date: May 2015
Posts: 68
|
Quote:
I'm trying to figure out if HME is worthwhile for me, given that the encoding is significantly slower. |
|
7th November 2019, 11:39 | #7164 | Link | |
Registered User
Join Date: Dec 2014
Posts: 240
|
Quote:
__________________
AMD Ryzen 9 5950X, 32GB DDR4-3200 CL16, RTX 3060, 2TB NVMe PCIE4.0, NAS with 8x16TB HDD |
|
7th November 2019, 13:18 | #7165 | Link | |
Lost my old account :(
Join Date: Jul 2017
Posts: 325
|
Quote:
If the only concern is level compatibility then I usually just set --level in the command line and x265 will automatically set the vbv and limit max ref frames etc to be compliant. But afaik some decoders will not handle such big bufsize even though they specification says that it supports a specific level, so there is viability to set custom (lower) values to ensure playback on an targeted device. But all my hevc level 5.1 devices have had no playback issues with encodes using the values in high teir though. Last edited by excellentswordfight; 7th November 2019 at 13:40. |
|
7th November 2019, 18:13 | #7166 | Link | |
ffx264/ffhevc author
Join Date: May 2007
Location: /dev/video0
Posts: 1,844
|
Quote:
In the end, I recommend doing your own tests and see if it's worthy |
|
7th November 2019, 23:29 | #7167 | Link | |
Registered User
Join Date: Jul 2016
Posts: 19
|
Quote:
So I try to make sure I am as compatible with all my encodes as I can possible be. I hope I read the specs correctly. Last edited by Majorlag; 7th November 2019 at 23:31. |
|
8th November 2019, 04:13 | #7168 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
Quote:
|
|
8th November 2019, 12:14 | #7169 | Link | |
Lost my old account :(
Join Date: Jul 2017
Posts: 325
|
Quote:
http://www.blu-raydisc.com/assets/Do...per_150724.pdf The different disctypes will then have different maximum ts bitrates though, I guess that the discs that allow for 81.7 Mbps are the most common. But when it comes to bufsize, is it common that that devices has a smaller buffer then the allowed maxrate for the supported level? If I remember it correctly HD blurays specified a smaller one (30 vs 40Mbps), and the same was true for PS3 and xbox360 compliant encodings. If I read the whitepaper correctly, it looks like this is the bufsize specificaiton for UHD-Bluray for the HEVC stream: "DPB1 Decoded picture buffer for HEVC stream: 93312000 [bytes]" Last edited by excellentswordfight; 8th November 2019 at 13:52. |
|
9th November 2019, 04:01 | #7171 | Link | |
Registered User
Join Date: May 2009
Posts: 331
|
Quote:
Unless it's magically gotten better since then. |
|
9th November 2019, 05:04 | #7172 | Link |
Derek Prestegard IRL
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,989
|
Depends on the intended use case. If you're going for total transparency you might have a harder time. If you're trying to get down to 10-15 Mbps for 1080p you'll probably get good results with the grain tuning and some nice slow settings, but it might be hard to get a reduction if you're coming from a BluRay source.
Getting down to a lower bitrate without blowing up and maintaining some of the grain texture is usually possible, but always difficult. Grain is hard no matter what. I'm hoping the film grain synthesis tools in AV1 get explored soon - I've always thought this was a great idea. I also wonder if the new MPEG-5 LC-EVC / enhancement layer systems could be used to encode a cleaner version of the video and then grain synthesis information as an enhancement layer / noise model, kind of like V-Nova Perseus but tuned for grain. |
9th November 2019, 06:18 | #7173 | Link | |
Registered User
Join Date: Apr 2015
Posts: 21
|
Quote:
|
|
9th November 2019, 09:51 | #7174 | Link | |
Lost my old account :(
Join Date: Jul 2017
Posts: 325
|
Quote:
With that said, is x264 better for 1080p sdr to achive near lossless quality at high bitrates? Sure, especialiy if speed also is concidered. But that is not the focus for x265 or most hevc encoders. Last edited by excellentswordfight; 9th November 2019 at 10:45. |
|
9th November 2019, 12:55 | #7175 | Link | |
Registered User
Join Date: Aug 2009
Posts: 90
|
Quote:
Lets hope they use a good implementation that prevents this as good as possible. Last edited by K.i.N.G; 9th November 2019 at 13:14. |
|
9th November 2019, 20:39 | #7176 | Link |
FishmanMod Android Dev
Join Date: Apr 2004
Location: Somewhere else, maybe Arizona Bay
Posts: 1,143
|
Odd there are no x265 3.2.1 builds around...
__________________
"Cinderella story, out of nowhere, former greenskeeper, now about to become the Masters champion. It looks like a mirac- it's in the hole!" |
9th November 2019, 21:49 | #7178 | Link |
Registered Loser
Join Date: Dec 2004
Posts: 117
|
LAVF Patch
Is there any guide to compiling x265 on Windows with an LAVF/Smash patch?
I grabbed the Yuuki source and threw it into my cross-compile script, but get a ton of errors lavf.cpp on and I'm not knowledgeable enough to troubleshoot. I had to hack apart the script as it was to not overwrite the Yuuki version with the current mercurial branch. One of 50+ errors: /home/agressiv/ffmpeg-windows-build-helpers/sandbox/cross_compilers/mingw-w64-x86_64/lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld: CMakeFiles/cli.dir/objects.a(lavf.cpp.obj):lavf.cpp.text+0x11): undefined reference to `avcodec_free_context' |
9th November 2019, 22:49 | #7179 | Link | |
Registered Loser
Join Date: Dec 2004
Posts: 117
|
Quote:
Here's one I compiled - 3.2.1, x64 bit MSVC compiled with 8/10/12 bit support. |
|
10th November 2019, 02:45 | #7180 | Link | |
結城有紀
Join Date: Dec 2003
Location: NJ; OR; Shanghai
Posts: 894
|
Quote:
You'll need windows gcc compiled ffmpeg being installed in your x86_64 include & lib. I have full rakefile to compile Yuuki and Asuna binaries. |
|
|
|