x265 HEVC Encoder

[benwaggoner]

Originally Posted by tormento

HW decoders rarely can process 8 bit HEVC.

You mean can rarely process 8-bit HEVC without also supporting 10-bit HEVC, right?

Moreover, 10 bit encoding has (since the infamous Hi10P days) proven to increase compression with additional benefits regarding banding and no disadvantages (at least HEVC files).

The benefit of 10-bit encoding for 8-bit sources is less with HEVC than with H.264, as 8-bit internal precision was improved. But it can still give a few percentage improvement and can reduce banding artifacts.

[tormento]

Originally Posted by benwaggoner

You mean can rarely process 8-bit HEVC without also supporting 10-bit HEVC, right?.

So picky you are.

[mister_no]

Originally Posted by jpsdr

For those interested, made a new build of my x265_mod version.
-------------------------------------------------------------------------
Will wait the results of "classic" vs "histogram" to see if i change my encoding scripts, as i'm only doing 10 bits video / main10 encodes.

Can you please make a build without the extanded progress bar? My GUI doesn't show progress with the extanded progress bar.

[jpsdr]

Euh... Sorry but no, don't have time to try (don't even know if i would be able to) to build specific for X, Y, Z, etc...

[jpsdr]

About "histogram" vs "classic", what about hrd-pq ? If Boulder's video is 8 bit, i assume it sdr, so the "issue" is maybe main10 / 10 bits sdr video...
Has someone made tests to see if "histogram" behaves better than "classic" with main10 / 10 bits video in hdr-pq ?

[Boulder]

Originally Posted by jpsdr

About "histogram" vs "classic", what about hrd-pq ? If Boulder's video is 8 bit, i assume it sdr, so the "issue" is maybe main10 / 10 bits sdr video...
Has someone made tests to see if "histogram" behaves better than "classic" with main10 / 10 bits video in hdr-pq ?

It looks like the histogram mode works quite well with PQ sources. I tested a 3000-frame part from Harry Potter and the Philosopher's Stone, and classic produced 10 scene changes while the histogram mode found 24, which should be very close to the real value. There are some difficult parts with slo-mo in the clip which confuses the tool I use for creating a QP file.

So the issue is probably seen with SDR sources encoded with the Main10 profile.

[jpsdr]

Ok, thanks for the feedback. In that case, i'll change my encode scripts to use histogram mode.

[benwaggoner]

Wow, that's big news if the new histogram mode is good enough to be the default.

Anyone test --mctf or the new segment based rate control?

[vpupkind]

Originally Posted by benwaggoner

Wow, that's big news if the new histogram mode is good enough to be the default.

Anyone test --mctf or the new segment based rate control?

SBRC is a bit of a misnomer right now. It does some aq-related stuff, hopefully some actual rate control stuff will follow.

[Barough]

x265 v3.5+69
https://www.mediafire.com/file/kuh2ekbo2p6a7rf/

[ShortKatz]

Originally Posted by benwaggoner

Wow, that's big news if the new histogram mode is good enough to be the default.

Anyone test --mctf or the new segment based rate control?

Tested --mctf just once. It increased my encoding time 7-fold. So I did not do any further tests.

[LeXXuz]

Originally Posted by jpsdr

Ok, thanks for the feedback. In that case, i'll change my encode scripts to use histogram mode.

Could you possibly add 8-bit support to your version? I'd like to do some comparisons with aq5-mode between 8 and 10bit output.

[jpsdr]

.... There is not...? I ran cmake to create a VS projet and checked all possible options, i thought all the supports were enabled.
Setting --profile main, -D 8 (and all others related stuff saying that video is 8 bits) on the command line is not working ?

If not, for now, unfortunately i don't know what to do for...

[quietvoid]

If you enabled HIGH_BIT_DEPTH when configuring the build, it only builds 10 bit.
12 bit if you do MAIN12 too.

There's a multilib script to get a statically linked executable with all bit depths.
I can't really help for Windows/VS though.

[LeXXuz]

Originally Posted by jpsdr

.... There is not...? I ran cmake to create a VS projet and checked all possible options, i thought all the supports were enabled.
Setting --profile main, -D 8 (and all others related stuff saying that video is 8 bits) on the command line is not working ?

No there isn't. x265 exits with this error if forced to work in 8-bit:

x265 [FLAW]: main profile not supported, internal bit depth 10.

[jpsdr]

Ah.... Don't know how to do it for now, don't realy have time for now, sorry. Try to see if i can figure out something when there will be the need for a new build.
Otherwise, anyone can also make a build from my repo.

[quietvoid]

I just noticed that the new histogram scene cut commit removed the logging of consecutive B frames %, seemingly for no reason.
If anyone had a use for it, here's a diff: https://github.com/quietvoid/x265/co...a35be4377e390e

Should probably be renamed from m_histogram now but I just copied the old code back.

[Boulder]

Here's a very crude tool written in Python to get those average figures out of the csv log file written with csv-log-level 2 set. It expects that SSIM or PSNR is not enabled as those change the column structure. Only tested with two csv files I had on my HDD

Usage: "python logtool.py filename.csv". It will then write a .log file to the path where the csv file is and output the same information in the command prompt window.

import pandas as pd
import os
import sys

filename = os.path.abspath(sys.argv[1])

log_content = pd.read_csv(filename, sep=",", decimal=".", header=0)
log_content = log_content.iloc[:-4,11:-9]
log_content.columns = log_content.columns.str.replace('.1', '', regex=True)
log_content.columns = log_content.columns.str.replace('66', ' 16x16', regex=True)
log_content.columns = log_content.columns.str.replace('326', ' 32x16', regex=True)
log_content.columns = log_content.columns.str.replace('6x32', ' 16x32', regex=True)
log_content.columns = log_content.columns.str.replace('6x8', ' 16x8', regex=True)
log_content.columns = log_content.columns.str.replace('86', ' 8x16', regex=True)
log_content.columns = log_content.columns.str.replace('AMP6', 'AMP 16', regex=True)
log_content = log_content.replace('%', '', regex=True).astype(float)
average = log_content.describe().loc['mean'].to_string()

print (average)
with open(filename+str('.log'), mode='w') as outputfile:
    outputfile.write(str(average))
    outputfile.close()

[_kermit]

piping to x265 with powershell

sorry if that is too off-topic...

this works just fine in a command prompt:

ffmpeg.exe -i FILE -pix_fmt yuv420p10le -strict -1 -f yuv4mpegpipe - | x265.exe - --y4m .....etc.

Now I wanted to use Powershell for that and the piping isn't working, the x265 process doesn't even start, while ffpmpeg is running:

It seems that using the pipe character isn't working here.
Does anyone have an idea?

[excellentswordfight]

Originally Posted by _kermit

piping to x265 with powershell

sorry if that is too off-topic...

this works just fine in a command prompt:

ffmpeg.exe -i FILE -pix_fmt yuv420p10le -strict -1 -f yuv4mpegpipe - | x265.exe - --y4m .....etc.

Now I wanted to use Powershell for that and the piping isn't working, the x265 process doesn't even start, while ffpmpeg is running:

It seems that using the pipe character isn't working here.
Does anyone have an idea?

There is nothing "wrong" with the pipe command, but piping does not work in the same way in powershell as in cmd so you cannot pipe raw data in the same way.

There are some workaround and more info here https://stackoverflow.com/questions/...-in-powershell