x265 HEVC Encoder

[Jamaika]

Hi elipse98
Maybe I shouldn't write, but also once had a problem with color XAVC.
Which did you use the decoder for codec H264?

Depending NLE editor may be different shades of decoding.
http://filmowiec.pl/forum/viewtopic....5255&start=195
Video Bitrate 5Mbps far too small for the dynamic films FullHD.

It is worth remembering about parameters XAVC.

Color primaries : BT.709
Transfer characteristics : IEC 61966-2-4
Matrix coefficients : BT.709

[eclipse98]

Originally Posted by Jamaika

Hi elipse98
Maybe I shouldn't write, but also once had a problem with color XAVC.
Which did you use the decoder for codec H264?

Depending NLE editor may be different shades of decoding.
http://filmowiec.pl/forum/viewtopic....5255&start=195
Video Bitrate 5Mbps far too small for the dynamic films FullHD.

It is worth remembering about parameters XAVC.

Color primaries : BT.709
Transfer characteristics : IEC 61966-2-4
Matrix coefficients : BT.709

Hi Jamaika,

I am not using any NLE editor, pretty much loading source XAVC video directly with StaxRip and choosing Automatic AviSynth+ filter, it picks LSMASHVideoSource, can this be an issue ? Do you think if I convert XAVC with some intermediate codec (Avid) it might help ?

For 264 I am using x264 r2692 8-Bit x64 'very slow' profile, 2 pass encoding using StaxRip (same LSMASHVideoSource filter, same 5mbps bit rate).

Yes, 5mbps is on low side, but this is a requirement for streaming, so not much choice here, it is accepted that I am not shooting for BD quality.

I would not necessarily call it far too small either, the reason I am using x265 is because it excels at low bit rate compared to x264. I made some incredible x265 encodes at 5mbps (same type of dynamic footage) - overall very happy until this problem appeared.

I uploaded a very short video to shared folder where you can see trailing color problem - I am not sure if it's a color issue - as you can see in the video the bushes in front of the car do not exhibit any artifacts, but you can clearly see them behind the car

Thanks for your help !

[fauxreaper]

Originally Posted by eclipse98

Hi Everybody,

I am getting some bad "color bleeding", that's what I think it is but I think a more accurate description is "color trailing". It gets pretty bad and mostly occurring when the object that leaves the color trail (car, road sign) passes in front of bare trees or dry grass.

Original footage is UHD, Sony AX53 Handycam, XAVC 100mbps shot from moving car (camera mounted outside) - resized to HD and encoded with x265 5mbps very slow preset (StaxRip, HEVC encoder version 1.9+150-00ea3784bd36). I tried different presets (medium-very slow) and problem occurs in each of them. It seems a bit better with SSIM tune, but still clearly present.

Attached is zoomed in image where a trail of blue/purple spots left by passing car can be clearly seen:
https://lh5.googleusercontent.com/Rw...eMw=w1896-h873

Tested with h264 and it does not have the same problem.

Link to shared folder that has screenshot from original footage (no spots), h264 video, x265 video and zoomed in x265 version:
https://drive.google.com/folderview?...Gs&usp=sharing

Would appreciate your help if there is any setting I can try that might help with getting rid of this issue.

Thanks for your help, Cheers !

Can you test a x265 encode with "--no-cutree" option? Maybe these spots are just ghosting.

[eclipse98]

Originally Posted by fauxreaper

Can you test a x265 encode with "--no-cutree" option? Maybe these spots are just ghosting.

Fauxreaper,

"--no-cutree" made it much worse, more spots and now they are glowing with every color of the rainbow

Here are encode settings:

x265 [info]: HEVC encoder version 1.9+150-00ea3784bd36
x265 [info]: build info [Windows][GCC 5.3.0][64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX LZCNT
x265 [info]: Main profile, Level-4 (Main tier)
x265 [info]: Thread pool created using 8 threads
x265 [info]: frame threads / pool features : 3 / wpp(17 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : star / 57 / 3 / 3
x265 [info]: Keyframe min / max / scenecut : 25 / 250 / 40
x265 [info]: Lookahead / bframes / badapt : 25 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 4 / on / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 1 / 1.0 / 32 / 0
x265 [info]: Rate Control / qCompress : ABR-5336 kbps / 0.60
x265 [info]: tools: rect limit-modes rd=4 psy-rd=2.00 rdoq=2 psy-rdoq=1.00
x265 [info]: tools: signhide tmvp strong-intra-smoothing lslices=4 deblock sao
x265 [info]: tools: stats-read

[Ma]

Originally Posted by eclipse98

"--no-cutree" made it much worse

You can try '--cbqpoffs -2 --crqpoffs -2'.

[eclipse98]

Originally Posted by Ma

You can try '--cbqpoffs -2 --crqpoffs -2'.

Ma, slightly better, maybe 20% or so, but still persists. I tried '--cbqpoffs -4 --crqpoffs -4' and it returned back to original. You think experimenting with different values might yield some improvements ?

Thanks !

[Ma]

Originally Posted by eclipse98

Ma, slightly better, maybe 20% or so, but still persists. I tried '--cbqpoffs -4 --crqpoffs -4' and it returned back to original. You think experimenting with different values might yield some improvements ?

You can try -1 or -3 values. You can also try '--aq-mode 3' option.

[Jamaika]

Originally Posted by eclipse98

Hi Jamaika,

I uploaded a very short video to shared folder where you can see trailing color problem - I am not sure if it's a color issue - as you can see in the video the bushes in front of the car do not exhibit any artifacts, but you can clearly see them behind the car

Add the original.

PS These are the ghosts. On my decoder MPC-BE the spots of color they are in other places.

[Ma]

For volunteers I have x265 build with Unicode support for input files to test (yuv and y4m) -- www.msystem.waw.pl/x265/utf-input.7z (diff file in archive)

Example (from Total Commander):

x265.exe "żółć-liść-będąc-23甜蜜的一天(玛丽亚.凯丽&男人男孩).y4m" -o o.hevc

[eclipse98]

Originally Posted by Jamaika

Add the original.

PS These are the ghosts. On my decoder MPC-BE the spots of color they are in other places.

Screenshots were taken from different encode, that is probably why spots of color are in different places.

I uploaded a 90 sec segment of original video (original.mp4, XAVC, 100mbps) as well as new encode from this segment (x265.mp4, slow preset, 3 pass, 5mbps). You can see color ghosts left by car at 0:13, 0:18, 0:35, 0:44, 0:57. By road signs at 01:20 (on left), 1:34 and 1:44 (on the right). None of those artifacts exist in original video.

https://drive.google.com/folderview?...Gs&usp=sharing

So, is it possible to get rid of them ?

Thanks !

btw. Sorry to hijack the thread, I thought it was relevant to x265 as a possible issue. If you think otherwise please let me know and I'll start a new thread specific to this issue.

[Motenai Yoda]

try raising qcomp to .75~.8 and cbqpoffs/crqpoffs to -2

[eclipse98]

Originally Posted by Motenai Yoda

try raising qcomp to .75~.8 and cbqpoffs/crqpoffs to -2

--bitrate 5000 --preset slow --qcomp 0.75 --cbqpoffs -2 --crqpoffs -2

Doesn't seem to make any difference.

Originally Posted by Ma

You can try -1 or -3 values. You can also try '--aq-mode 3' option.

Tried different values and aq-mode 3, didn't work either

[Jamaika]

The problems are with the SAO.

My attempt to film processing:
https://www.sendspace.com/filegroup/...9DbjYPMLX4LFOt

[eclipse98]

Originally Posted by Jamaika

The problems are with the SAO.

My attempt to film processing:
https://www.sendspace.com/filegroup/...9DbjYPMLX4LFOt

Jamaika,

Thank you so much for testing this, appreciate it. I am looking at your settings and will replicate them in my tests. In addition to no-sao, I see other settings that differ from mine - you also use a different scaler (Lanczos vs Bicubic), not sure if it makes any difference.

I'll update once I have some test results !

Cheers !

Some patches were just committed that address some of the issues reported here... especially with respect to tune grain. We look forward to your feedback.

[ndkamal]

I made some tests with x265 V19 R165 and tune grain, and the result is really impressive. This version retains more grain than x264 (at equivalent bitrate). Very good job. I hope there will be a significant progress in normal mode (without tune grain), in the next months.

[Magik Mark]

Originally Posted by ndkamal

I made some tests with x265 V19 R165 and tune grain, and the result is really impressive. This version retains more grain than x264 (at equivalent bitrate). Very good job. I hope there will be a significant progress in normal mode (without tune grain), in the next months.

Can you post a before & after image? Thanks

[nandaku2]

Originally Posted by Magik Mark

Guys,

Can you help me with my ghost problem. Maybe a missing switch? Doing x265 10bit 2pass via staxrip

Hi, is this clip a grainy one (heavy film grain, ie)? If so, you may want to check with the new tune grain setting.

[Jamaika]

The problem hasn't been solved.
To test, I used material from the drone. Cloudy sky, the sun's rays reflecting in the water. At some point drone changes its position and is another angle of sunlight. And here curiosity. Where are the frames B all is well. Next frame "I" and there are violets.
Excision of extra functions give nothing "--no-amp --no-temporal-mvp --no-signhide --no-strong-intra-smoothing --no-b-intros". The use of "open-gop" also doesn't give results.
As for the focus. It seems to me that better falls x264. There is no pulsation between sharp and blurred places between frames.

PS I realize that we are talking about cheap cameras with poor optics.

Edit: It isn't satisfied with the settings tune grain.
https://github.com/videolan/x265/com...99b95f2e37d46f
First, I have problems with:
*: Option: `--aq-mode` 0
*: Option: `--cutree` 0
*: Option: `--qpstep` 1
Here there are large pixels.
I don't know what's going on with recursion-skip` 1. The inclusion doesn't improve quality. For me it is worse.
Settings:
*: Option: `--sao` 0
*: Option: `--psy-rd` 4.0
*: Option: `--psy-rdoq` 10.0
They are better than mine --psy-rd` 2.0 --psy-rdoq` 50.0
Use of me = umh causes more blemishes. Therefore, the above badly written.
The advertised the function 'lanczos' is bullshit. How would I not configured and so is the 'bicubic'.
My best settings for version 1.9 + 167 (veryslow):
--psy-rd 4.00 --psy-rdoq 10.00 --no-sao --high-tier --no-recursion-skip --keyint 60 --bitrate 6000 --vbv-bufsize 10000 --vbv-maxrate 10000
PS These settings in version 1.9 + 168 already look worse for the same film.
https://www.sendspace.com/file/inmvs6

[LigH]

x265 1.9+167-bebae72f9db7 provides a few changes regarding the grain handling, and a new tweak:

   --[no-]recursion-skip         Enable early exit from recursion. Default enabled