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.

 

Go Back   Doom9's Forum > Video Encoding > High Efficiency Video Coding (HEVC)

Reply
 
Thread Tools Search this Thread Display Modes
Old 10th November 2019, 13:49   #7181  |  Link
redbtn
Registered User
 
redbtn's Avatar
 
Join Date: Jan 2019
Location: Russia
Posts: 105
Thank you HolyWu
Can I find somewhere information how to build x265 with gcc or clang? I tried google it, but I fail.

Last edited by redbtn; 10th November 2019 at 14:23.
redbtn is offline   Reply With Quote
Old 10th November 2019, 15:53   #7182  |  Link
agressiv
Registered Loser
 
agressiv's Avatar
 
Join Date: Dec 2004
Posts: 117
Yes, thanks HolyWu for the lavf-enabled new build! Any chance you can upload a non-upx packed EXE? Or maybe even your source and compile script?
agressiv is offline   Reply With Quote
Old 11th November 2019, 02:03   #7183  |  Link
fauxreaper
Registered User
 
Join Date: Oct 2014
Posts: 23
HME is nondeterministic? Using --hme hex, I got slightly different file sizes on multiple encodes with same input file and x265 config.
fauxreaper is offline   Reply With Quote
Old 11th November 2019, 05:38   #7184  |  Link
microchip8
ffx264/ffhevc author
 
microchip8's Avatar
 
Join Date: May 2007
Location: /dev/video0
Posts: 1,843
Quote:
Originally Posted by fauxreaper View Post
HME is nondeterministic? Using --hme hex, I got slightly different file sizes on multiple encodes with same input file and x265 config.
--hme does not accept any parameters
--hme-search does (where you set the motion estimation algo, such as hex)
__________________
ffx264 || ffhevc || ffxvid || microenc
microchip8 is offline   Reply With Quote
Old 13th November 2019, 16:20   #7185  |  Link
nghiabeo20
Registered User
 
Join Date: Jun 2013
Posts: 32
I encode my clip in 5 parts, using -ss and -t to seek to cut position. Now mkvmerge refuses to merge the file, warning that "codec private data doesn't match". After checking the encoding settings, I found that only the --numa-pool change in the first 2 file. How can I edit SPS/PPS data to fool mkvmerge into merging my files? Thanks!
nghiabeo20 is offline   Reply With Quote
Old 13th November 2019, 16:57   #7186  |  Link
MeteorRain
結城有紀
 
Join Date: Dec 2003
Location: NJ; OR; Shanghai
Posts: 894
If you don't mind, join files using MP4Box on MP4s.

Other option is to strip the SEI/VPS/SPS/PPS data for part 2-5 and simply join the raw bitstream. (Stripping is optional.)

If you really want to join using mkvmerge, try using a binary editor to change the text inside SEI, however to be honest I don't think that text should make a difference.
__________________
Projects
x265 - Yuuki-Asuna-mod Download / GitHub
TS - ADTS AAC Splitter | LATM AAC Splitter | BS4K-ASS
Neo AviSynth+ filters - F3KDB | FFT3D | DFTTest | MiniDeen | Temporal Median
MeteorRain is offline   Reply With Quote
Old 13th November 2019, 21:19   #7187  |  Link
stax76
Registered User
 
stax76's Avatar
 
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
Is the estimated file size feature an official feature or a patch? It gets requested frequently, somebody needs to make an official feature request.
stax76 is offline   Reply With Quote
Old 13th November 2019, 22:45   #7188  |  Link
sneaker_ger
Registered User
 
Join Date: Dec 2002
Posts: 5,565
Quote:
Originally Posted by nghiabeo20 View Post
Now mkvmerge refuses to merge the file, warning that "codec private data doesn't match".
I don't think mkvmerge actually refuses to append the files. It is merely displaying a warning message, saying "there may (or may not) be problems".
sneaker_ger is offline   Reply With Quote
Old 14th November 2019, 02:53   #7189  |  Link
foxyshadis
ангел смерти
 
foxyshadis's Avatar
 
Join Date: Nov 2004
Location: Lost
Posts: 9,558
Quote:
Originally Posted by K.i.N.G View Post
The danger of that is that many people/companies will use that as an excuse to apply exagerated loss of detail information and 'mask' it with some added synthetic film grain applied to give the false illusion of detail retention (while the information that 'makes sense' is gone). If you know what i mean...
Lets hope they use a good implementation that prevents this as good as possible.
How is that any different from physical film grain on actual film stock? That x264 and x265 completely neglected it because it was hard to test doesn't mean a little noise generation isn't valuable.
foxyshadis is offline   Reply With Quote
Old 14th November 2019, 12:46   #7190  |  Link
Barough
Registered User
 
Barough's Avatar
 
Join Date: Feb 2007
Location: Sweden
Posts: 480
x265 v3.2+15-04db2bfee5d6 (32 & 64-bit 8/10/12bit Multilib Windows Binaries) (GCC 9.2.0)
Code:
https://bitbucket.org/multicoreware/x265/commits/branch/default
Barough is offline   Reply With Quote
Old 14th November 2019, 13:26   #7191  |  Link
Forteen88
Herr
 
Join Date: Apr 2009
Location: North Europe
Posts: 556
Quote:
Originally Posted by Barough View Post
x265 v3.2+15-04db2bfee5d6 (32 & 64-bit 8/10/12bit Multilib Windows Binaries) (GCC 9.2.0)
Is this version newer than x265-3.2.1+1?
Forteen88 is offline   Reply With Quote
Old 14th November 2019, 13:28   #7192  |  Link
Barough
Registered User
 
Barough's Avatar
 
Join Date: Feb 2007
Location: Sweden
Posts: 480
Yes it is, this is compiled from the default branch and not the stable one.

Skickat från min SM-G975F 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.

Last edited by Barough; 15th November 2019 at 21:21.
Barough is offline   Reply With Quote
Old 15th November 2019, 20:51   #7193  |  Link
benwaggoner
Moderator
 
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
Quote:
Originally Posted by foxyshadis View Post
How is that any different from physical film grain on actual film stock? That x264 and x265 completely neglected it because it was hard to test doesn't mean a little noise generation isn't valuable.
The grain generation is often done in wrong ways that make it much harder to encode than real world grain. I especially see this in 4K and HDR, where grain gets rendered at the pixel level with SDR code values and so comes out way too bright and too fine-grained. I've seen synthetic film grain that made content impossible to encode at even vaguely acceptable quality at 40 Mbps.

We're also seeing silly amounts of film grain in restored rescans of movies. It isn't creative intent to preserve all kinds of noise that wouldn't have been visible on the perf screens and foot lamberts that the creatives actually approved the content on.
__________________
Ben Waggoner
Principal Video Specialist, Amazon Prime Video

My Compression Book
benwaggoner is offline   Reply With Quote
Old 15th November 2019, 20:55   #7194  |  Link
Blue_MiSfit
Derek Prestegard IRL
 
Blue_MiSfit's Avatar
 
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,988
I hear you on the remastering, Ben.

Home Alone is an astounding example of this.
Blue_MiSfit is offline   Reply With Quote
Old 15th November 2019, 20:57   #7195  |  Link
benwaggoner
Moderator
 
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
Quote:
Originally Posted by nghiabeo20 View Post
I encode my clip in 5 parts, using -ss and -t to seek to cut position. Now mkvmerge refuses to merge the file, warning that "codec private data doesn't match". After checking the encoding settings, I found that only the --numa-pool change in the first 2 file. How can I edit SPS/PPS data to fool mkvmerge into merging my files? Thanks!
Also maybe try --hrd-concat if you are using HRD?
__________________
Ben Waggoner
Principal Video Specialist, Amazon Prime Video

My Compression Book
benwaggoner is offline   Reply With Quote
Old 15th November 2019, 22:56   #7196  |  Link
Stereodude
Registered User
 
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
Watch the 4k77 UHD release of Star Wars if you want to see overdone grain. MCTD is calling its name when I build my new Zen 2 system in the next month or two.

Last edited by Stereodude; 15th November 2019 at 22:59.
Stereodude is offline   Reply With Quote
Old 17th November 2019, 15:59   #7197  |  Link
markiemarcus
Registered User
 
Join Date: May 2018
Posts: 49
Quote:
Originally Posted by Blue_MiSfit View Post
I hear you on the remastering, Ben.

Home Alone is an astounding example of this.
Something definitely looked off with Home Alone. The pitch of the grain was both far too fine and too bright; it didn't gel at all with the image.

I must say though, I like the way the UHD release of Predator looks and it's pretty damn grainy. It looks right to me. Was shaky film stock from the outset IIRC.
markiemarcus is offline   Reply With Quote
Old 18th November 2019, 04:07   #7198  |  Link
RanmaCanada
Registered User
 
Join Date: May 2009
Posts: 328
The original Predator, in my view, is the PERFECT example of what a transfer and remaster should look like. I'm old enough to have seen it in the cinema, and watching that 4k copy was everything I remembered. And we all know how we view the past with rose coloured glasses.
RanmaCanada is offline   Reply With Quote
Old 18th November 2019, 08:28   #7199  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
Film grain ... I witnessed an attempt to preserve a sensible amount of it while trying to remove the majority that only distracts the MPEG-2 encoder of a "Kinowelt" DVD production. Source: Die Feuerzangenbowle (1944) – too much denoising, and the trees on the schoolyard look like forged of concrete.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 19th November 2019, 14:45   #7200  |  Link
markiemarcus
Registered User
 
Join Date: May 2018
Posts: 49
Quote:
Originally Posted by RanmaCanada View Post
The original Predator, in my view, is the PERFECT example of what a transfer and remaster should look like. I'm old enough to have seen it in the cinema, and watching that 4k copy was everything I remembered. And we all know how we view the past with rose coloured glasses.
Was quite a treat to watch it again I must say. I wonder what the difference in process was, because it obviously wasn't an easy source to work with.

It's a nice encode too. I've noticed that a number of grainy UHD Blu-rays have issues from time-to-time in that regard. There are a handful of scenes in both Blade Runner and The Fog that completely fall apart. Seems inexcusable given how much space there is to play with. In the case of The Fog, the bit rate actually plummets in the affected scenes.
markiemarcus is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 12:35.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.