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. |
28th July 2016, 19:10 | #4062 | Link |
Registered User
Join Date: Jun 2016
Posts: 116
|
Thanks for the images. I don't argue that the quality of x265 has improved significantly from even a year ago. I'm still on the fence with the encoding time... All three systems I have are only AVX, none of them have AVX2 which gave a decent speed boost. |
28th July 2016, 19:15 | #4063 | Link | |
Registered User
Join Date: Jun 2016
Posts: 116
|
Quote:
|
|
28th July 2016, 19:34 | #4064 | Link |
Registered User
Join Date: Nov 2011
Posts: 66
|
While changing some random setting in Media Player Classic I noticed something awkward. My Output filter is set to "Enhanced Video Renderer", and below that is a setting for "resizer" where "Bilinear" was selected by default. After I changed it to one of "Bicubic" settings offered, image sharpness in full-screen mode improved dramatically (I use a Full-HD display and mostly play content encoded below that resolution)!
Could that be the stupid cause for "unexplainable" image softness most people notice with HEVC? When playing H.264 many systems (mine included) use built-in GPU decoders through DXVA, where software resize options might not have influence at all. Which software do you use for playing HEVC videos? Last edited by gamebox; 28th July 2016 at 19:48. |
28th July 2016, 20:14 | #4065 | Link |
Registered User
Join Date: Feb 2007
Location: Sweden
Posts: 480
|
I mainly use MPC-BE with default settings. Haven't bothered with tweaking the settings since im pleased with how it looks.
Sent from my Samsung Galaxy S7 edge via Tapatalk
__________________
Do NOT re-post any of my Mediafire links. Download & re-host the content(s) if you want to share it somewhere else. |
28th July 2016, 20:45 | #4066 | Link |
Registered User
Join Date: Jun 2016
Posts: 116
|
I have dual E5-2670 v1 which only have AVX. Anyone here with an equivalent setup with AVX2? What speeds are you averaging given your settings of course.
I use a slightly modified version of littlepox's settings. I'm trying to keep the bitrate down a bit for archival. I average 4.5 - 5.5 FPS with these settings. Code:
--profile main10 --output-depth 10 --ctu 32 --bframes 8 --rc-lookahead 80 --scenecut 40 --ref 5 --limit-refs 0 --me 1 --merange 25 --subme 3 --no-rect --no-amp --limit-modes --max-merge 4 --no-early-skip --b-intra --no-sao --signhide --weightp --weightb --aq-mode 3 --aq-strength 0.8 --cutree --rd 4 --tu-intra-depth 3 --tu-inter-depth 3 --psy-rd 2.0 --psy-rdoq 2.0 --rdoq-level 2 --lookahead-slices 4 --qcomp 0.65 --no-strong-intra-smoothing --deblock -1:-1 --qg-size 32 Last edited by brumsky; 28th July 2016 at 20:46. Reason: --rd 4 not 3 |
28th July 2016, 21:11 | #4067 | Link | |
Registered User
Join Date: May 2015
Posts: 68
|
Quote:
(For me, it's mostly high definition movies and HD home videos, all in x264, which I want to re-encode at about 30% of original bitrate.) |
|
29th July 2016, 10:43 | #4068 | Link |
Registered User
Join Date: Mar 2015
Location: New Zealand
Posts: 45
|
30% of the original bitrate? You wont get that, but you may get 30% reduction in bitrate. That is what I am seeing. I am currently reencoding ds9, and the latest x265 is excellent, but only with no-sao. Bitrate is about 60% of x264, and the quality is better. Admittedly some of that is that I now have run smdegrain over it.
Ok, now time for something weird. The ultimate x265 low bitrate test. As per previous posts, I have encoded sg1, 480p, low bitrate for mobile devices. I took a 1.36MB chunk of an episode, 1min 7 seconds, and copied it on to a FLOPPY DISK. And guess what, it played it no problem! buffered for 16 seconds and then played the remaining 51 seconds fine. In fact it finished reading the disk after it had played 30 seconds, so the floppy disk transfer rate was too fast! So a great testament to how good x265 is at low bitrates. What about bluray from floppy disk? lets see now... Last edited by divxmaster; 29th July 2016 at 10:46. |
29th July 2016, 11:10 | #4069 | Link | |
Registered User
Join Date: May 2015
Posts: 68
|
Quote:
About SAO that you mention, that's an aspect I'd like to know as well. Are others too experiencing noticeable loss of quality due to SAO? The developers have stated that SAO was improved in 2.0. |
|
29th July 2016, 11:51 | #4070 | Link |
Registered User
Join Date: Mar 2015
Location: New Zealand
Posts: 45
|
Yes, the testing of the 'new' SAO in 2.0 is one thing I have to get around to doing. But as far as fixed bitrate goes, for me I wouldn't do that. The bitrate required is way to variable. In crf mode, I have some 576p that uses a bitrate of 450-500, but other 576p uses a bitrate of 1000-1200! And the 450-500 looks better in this instance.
|
29th July 2016, 22:14 | #4073 | Link | |
Registered User
Join Date: Oct 2014
Posts: 268
|
Quote:
Does x264 have decent gpu acceleration after all those years?? . OpenCL lookaheads came eventually - very late - and contribute not much.. I don't expect much to change for x265. Pretty much accelerated hevc encoding already exist on the recent GPUs and there are commandline tools to use it, but you have to do with the quality it provides, not much to improve upon. |
|
30th July 2016, 03:50 | #4074 | Link | |
Registered User
Join Date: Mar 2008
Posts: 448
|
Quote:
|
|
30th July 2016, 06:46 | #4075 | Link | |
Registered User
Join Date: Apr 2009
Posts: 478
|
Quote:
I used to be on the same boat as you. But one thing that you have to understand is that the presets of x264 and x265 are not comparable. For me, x265's medium is roughly comparable in quality and speed as x264's slow, but with smaller file size of course. Last edited by aegisofrime; 30th July 2016 at 06:50. |
|
30th July 2016, 07:19 | #4076 | Link | |
Registered User
Join Date: Mar 2008
Posts: 448
|
Quote:
NVENC can be used as a hardware accelerator to perform motion search and generate motion vectors and mode information only. The resulting motion vectors or mode decisions can used, for example, in motion compensated filtering or for supporting other codecs not fully supported by NVENC or simply as motion vector hints for a custom encoder. Sample code from nvenc : /** * Motion vector structure per CU for HEVC motion estimation. */ typedef struct _NV_ENC_HEVC_MV_DATA { NV_ENC_MVECTOR mv[4]; /**< up to 4 vectors within a CU */ uint8_t cuType; /**< 0 (I), 1(P), 2 (Skip) */ uint8_t cuSize; /**< 0: 8x8, 1: 16x16, 2: 32x32, 3: 64x64 */ uint8_t partitionMode; /**< The CU partition mode 0 (2Nx2N), 1 (2NxN), 2(Nx2N), 3 (NxN), 4 (2NxnU), 5 (2NxnD), 6(nLx2N), 7 (nRx2N) */ uint8_t lastCUInCTB; /**< Marker to separate CUs in the current CTB from CUs in the next CTB */ } NV_ENC_HEVC_MV_DATA; /** * Creation parameters for output motion vector buffer for ME only mode. */ typedef struct _NV_ENC_CREATE_MV_BUFFER { uint32_t version; /**< [in]: Struct version. Must be set to NV_ENC_CREATE_MV_BUFFER_VER */ NV_ENC_OUTPUT_PTR mvBuffer; /**< [out]: Pointer to the output motion vector buffer */ uint32_t reserved1[255]; /**< [in]: Reserved and should be set to 0 */ void* reserved2[63]; /**< [in]: Reserved and should be set to NULL */ } NV_ENC_CREATE_MV_BUFFER; /** NV_ENC_CREATE_MV_BUFFER struct version*/ #define NV_ENC_CREATE_MV_BUFFER_VER NVENCAPI_STRUCT_VERSION(1) Of course, there are lotta lines of code before ME step, such as buffer creation + reference frame + buffer locking + buffer pointer location and finally the last step buffer destruction + release. Questions are.....how to port the code for x265 or can it be done in first place? Who will do it for free? Is there any licensing issue? Last edited by JohnLai; 30th July 2016 at 07:28. |
|
30th July 2016, 09:25 | #4077 | Link | |||
Registered User
Join Date: Aug 2006
Posts: 2,229
|
Quote:
Quote:
So: 480 ---- x 57 1080 Equals 25.33, which is why 25 seems to be optimal for 480P If you are doing 720P, likewise: 480 ---- x 57 1080 Equals 38. Now in effect, the 25 and 38 takes you to the equivalent point in the picture, since there are more pixels between the two points at 720P than 480P. For b-frames, I found around 6 is ideal for normal content, but maybe 8 for animation. Setting this too high just leads to more encode time with little efficiency benefit. In the stats at the end of the encode, you can see the percentages for the consecutive b-frames. The first number is 0, so if there are 7 numbers the seventh one relates to 6 consecutive b-frames. You will see the percentages can be quite low at the top end, any less than a few percent it wouldn't be worth the extra encode time. Instead of a B frame in that instance, a P frame would be used instead. For example, for a few recent recent encodes (x265 2.0+11) I got: Quote:
The other options are a balance of speed and quality. Also note I set --tu-intra-depth 3 as this shows benefits for little peformance cost, however I did not option --tu-inter-depth 3, as it didn't show any noticeable quality or compression improvements, and just slowed down the encode. The settings -early-skip --fast-intra --tskip --tskip-fast --limit-modes are all performance related, they noticeably improve speed when all used together but really don't impact the quality of the output. Give the settings I listed a go exactly as written apart from the --merange calculation (no other changes) and see how the speed compares to quality. EDIT: Forgot to mention, the above is solely the options on the command line. That is, not using any other preset as a basis. The crf (not stated) should be set to the desired amount. I would suggest maybe something a little lower than the default but within what would give you a desirable end file size. You can use decimals, so you could set it to 21.2 if you wanted (for example). Last edited by burfadel; 30th July 2016 at 18:36. |
|||
30th July 2016, 20:41 | #4079 | Link | |
Registered User
Join Date: Jun 2015
Posts: 5
|
Quote:
- benefit cost (quality + size) = x265 . |
|
31st July 2016, 03:43 | #4080 | Link | |
Registered User
Join Date: Mar 2015
Location: New Zealand
Posts: 45
|
Quote:
|
|
Thread Tools | Search this Thread |
Display Modes | |
|
|