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. |
5th April 2020, 23:28 | #7501 | Link | |
Registered User
Join Date: Apr 2017
Posts: 63
|
Quote:
I noticed with other files they are all correct. It seems that this one was different. Is this common? |
|
6th April 2020, 19:20 | #7505 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,770
|
Quote:
You need to use the values that are appropriate to the mastering monitor, which isn't something you can know from anything in the source other than this metadata. So, copy it if you have it. Otherwise leave it blank rather than specifying an incorrect value. |
|
6th April 2020, 23:15 | #7508 | Link | |
Registered User
Join Date: Apr 2017
Posts: 63
|
Quote:
to add: If so, is that also true for --max-cll ? Last edited by _kermit; 6th April 2020 at 23:29. |
|
7th April 2020, 10:31 | #7510 | Link | |
Registered User
Join Date: Jan 2019
Location: Antarctica
Posts: 74
|
I suppose it's as somebody wrote few posts ago about things breaking when grabbing the latest as I tried the latest build Barough shares x265 v3.3+17-gdf2ac512d https://forum.doom9.org/showthread.p...30#post1905930 appears both --profile main444-12 --input-csp i444 and --profile main444-10 --input-csp i444 are broken (if somebody else can also confirm) and may include 4:2:0 10 bit equivalent. 8 bit works fine.
Hope Barough will see this post. ---------------------------------------------- I don't know if it's related but as of far as I've tested x265 v3.3+2-gbe2d82093 has stopped working telling me Error message for your references: System exception - Access violation when Prefetch(1) is in the end of the script of AviSynth+ 3.5 but runs when (I think its disabled) Prefetch(0) is set. No issues with x265 v3.2+22-a8a2c4c37267. I'm just writing this in case they may be related or not. I really do not know if Prefetch is even worth using since the AviSynth thread is of no help neither the documentation. ---------------------------------------------- Another question in regards to an interest in figuring out if a speed in my encoding with AviSynth+ is possible. As I recall the settings for slow and veryslow were changed sometime ago and prior my encodes were a bit faster with my settings which have hardly changed since that implementation (likewise with my AviSynth filtering) but I dunno if choosing slower is the same as veryslow as I cannot tell just doing several encode tests at my end. These are my current settings: Quote:
Wish the developers would give why the encoder stops to work on some settings instead of just stopping it with no explanation. Well, thanks if anybody gives any suggestions or critique. Last edited by dREV; 7th April 2020 at 11:18. Reason: stuff |
|
7th April 2020, 13:13 | #7511 | Link | |
Registered User
Join Date: Apr 2017
Posts: 63
|
Quote:
if used, the correct values must be provided or it doesn't matter and they should not be provided? (for both) Actually there is more to it: If I don't provide in particular max-cll, that metadata is missing in the mkv and that data is for example used by the Radiance Pro. So I think this should be in the new, at least, file since it was in the original? Last edited by _kermit; 7th April 2020 at 13:16. |
|
7th April 2020, 13:42 | #7512 | Link | |
Registered User
Join Date: Dec 2007
Location: Beijing,China
Posts: 92
|
Quote:
and for the last question, to be honest, I don't know if I need those preferences, why export a new file or something else instead of set them in command line?
__________________
Ryzen 7 3700X GTX1660S Ryzen 7 5800X RTX2060S |
|
7th April 2020, 18:28 | #7513 | Link | |
Registered User
Join Date: Apr 2017
Posts: 63
|
Quote:
If that information isn't there, the Radiance Pro is using default values (AFAIK), so they are rather important and can not be provided otherwise. And since I provide max-cll in the command line as parameters, that is fine. The primaries seem only to have two variants so far: R: x=0.708000 y=0.292000, G: x=0.170000 y=0.797000, B: x=0.131000 y=0.046000, White point: x=0.312700 y=0.329000 and R: x=0.680000 y=0.320000, G: x=0.265000 y=0.690000, B: x=0.150000 y=0.060000, White point: x=0.312700 y=0.329000 thank you all! |
|
10th April 2020, 21:29 | #7517 | Link | |
SuperVirus
Join Date: Jun 2012
Location: Antarctic Japan
Posts: 1,351
|
Quote:
https://bitbucket.org/multicoreware/...a725d4fa84a084 |
|
11th April 2020, 06:13 | #7518 | Link |
Registered User
Join Date: Oct 2016
Posts: 111
|
Unable to finish encode after using x265 version 3.3+19 and 3.3+21 on http://msystem.waw.pl/x265/
So i have to turn back on version 3.3+10 I got stuck after they encode to last frame |
12th April 2020, 15:04 | #7519 | Link | |
SuperVirus
Join Date: Jun 2012
Location: Antarctic Japan
Posts: 1,351
|
Quote:
I have just reported the latest-and-greatest problem to the x265 devils. |
|
13th April 2020, 02:30 | #7520 | Link |
Registered User
Join Date: Dec 2007
Location: Beijing,China
Posts: 92
|
My encoding work stuck on 3.3.19 & 3.3.21 too. It won't stuck on 3.3.10 with exact same settings, video and compiler. And it doesn't matter what compiler is, GCC or VS stuck on 3.3.19 and all goes well on 3.3.10. So the problem has to be in those commits between 3.3.19 and 3.3.10.
vspipe 2>NUL "RAW.vpy" - | C:\Encoder\x265_64_10bpp.exe --input-res 1280x720 --fps 29.970 --input-depth 16 --force-flush 0 --ctu 32 --no-strong-intra-smoothing --selective-sao 0 --no-sao --bframes 8 --weightb --no-open-gop --ref 6 --rc-lookahead 48 --aq-strength 1.0 --psy-rd 2.5 --rd 6 --aq-mode 1 --aq-motion --hme --hme-search "2,2,3" --hme-range "24,24,36" --me star --subme 6 --merange 64 --crf 18 --output “RAW.hevc" - here's the command line that I'm using.
__________________
Ryzen 7 3700X GTX1660S Ryzen 7 5800X RTX2060S |
Thread Tools | Search this Thread |
Display Modes | |
|
|