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. |
18th March 2019, 14:14 | #141 | Link | |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Quote:
https://forum.doom9.org/showthread.p...94#post1869094 I get consistent results on serial testing. He get's these dodgy inconsistent results. How so ?
__________________
Nostalgia's not what it used to be |
|
18th March 2019, 16:05 | #142 | Link | |||
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Quote:
Quote:
Code:
<ffmpeg path> -i "/path/to/crowd_run_1080p50.y4m" -c:v libx265 -preset slow -crf 28 -pix_fmt yuv420p -x265-params "keyint=100:min-keyint=100:colorprim=1:transfer=1:colormatrix=1" -r 50/1 "/path/to/encode.mp4" Code:
LWLibavSource: stop 435.99385609567906 83.19534706841786 stop 435.99385609567906 83.19534706841786 stop 435.99385609567906 83.19534706841786 stop 435.99385609567906 83.19534706841786 stop 435.99385609567906 83.19534706841786 ffms2- Wolfberry (default, i.e. seekmode=1) stop 435.99385609567906 83.19534706841786 stop 435.99385609567906 83.19534706841786 stop 435.99385609567906 83.19534706841786 stop 435.99385609567906 83.19534706841786 stop 435.99385609567906 83.19534706841786 Compare that to your results. Quote:
Also, as before, I extracted the log file data into LibreOffice Calc to run difference checks on the per-frame scores and I could find zero differences at all between the serial tests and between the LWLibavSource and ffms2 test series. And the frames were listed in correct sequence (0-499) in the log files. Go figure.
__________________
Nostalgia's not what it used to be Last edited by WorBry; 18th March 2019 at 16:27. |
|||
18th March 2019, 16:48 | #143 | Link |
Registered User
Join Date: Sep 2007
Posts: 5,374
|
What hardware were you guys running on ?
It might partially have to do with threads and cores ; The more threads, the more requests, the higher chance of frame mismatches and seek errors if you're not using a robust seek method or indexing like dgsource or seekmode=0, threads=1 CK's seektest is like wild random seeks to simulate very bad case; but usually "normal" encoding scenarios , "normal scripts", even "normal" metric testing occurs in linear order . But small inconsistencies, like 7th decimal place etc... suggest something else wrong. Unless you have duplicate frames in the test sequence (and the mild variation is just lossy encoding differences of duplicate frames), there is something else going on. I would start to look at other things, hardware issues, run memory diagnostics Last edited by poisondeathray; 18th March 2019 at 17:00. |
18th March 2019, 17:26 | #144 | Link | |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Actually, I've been running these tests on an older PC (6-core AMD FX-6300 Vishera 3500 Mhz, NVidia GeForce GT730, Win10 x64) that I keep for grunt encoding/processing and linux stuff (dual boot). A bit sluggish with 4K , but it gets there. For the metric tests I've let it run on 6 threads.
Quote:
__________________
Nostalgia's not what it used to be Last edited by WorBry; 18th March 2019 at 17:39. |
|
18th March 2019, 17:36 | #145 | Link |
Registered User
Join Date: Sep 2007
Posts: 5,374
|
Note the files you guys encoded are going to be slightly different too. Even with the same commandline . Because of encoding threads. Unless you guys have the same core and thread count on your hardware, or you explictly set threads
|
18th March 2019, 20:02 | #146 | Link |
Registered User
Join Date: Dec 2005
Location: Germany
Posts: 1,795
|
I added Decimal() for testing purposes https://github.com/theChaosCoder/zoptilib
The metric values are now much longer, sum should always be the same between runs. Please test.
__________________
AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK || VapourSynth Database |
18th March 2019, 21:05 | #147 | Link | |
Registered User
Join Date: Jul 2010
Posts: 132
|
Quote:
if you followed exactly the commands I posted and used the exact same sw packages I posted and linked to, then it may be a system difference, as poisondeathray pointed to. I asked you pages ago, what OS you're using... But, point remains: I can consistently repeat the problem w/ seekmode=1 (and the keyframes encode). CK, who repeated the procedure from my post, ended up experiencing the exact same issues on his system. So there is an issue, and clearly this is of interest for others, who may run into the same problems... btw, this is not a ffmpeg specific version problem, I tested w/ three different ffmpeg versions.. Last edited by Iron_Mike; 18th March 2019 at 21:26. |
|
18th March 2019, 21:44 | #150 | Link | ||
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Quote:
Quote:
Not denying there is an issue, but I'm not seeing it.
__________________
Nostalgia's not what it used to be Last edited by WorBry; 18th March 2019 at 21:54. |
||
18th March 2019, 21:51 | #152 | Link |
Registered User
Join Date: Mar 2018
Posts: 447
|
Mike, can you take a look at what the log files look like when you get the inconsistent results (like below)?
Code:
FFMS2 (Wolfberry) - seekmode=1 (default): stop 123.93944837285996 227.9372376995322 stop 123.74699115224307 228.86426005799092 stop 82.89543157743563 436.641839735243 stop 121.66415998563879 239.07092253508384 stop 122.1422683865401 236.40679167570886 |
18th March 2019, 21:56 | #153 | Link |
Registered User
Join Date: Jul 2010
Posts: 132
|
another pointer is that, on my end, when running CK's test script option #1 and option #5 showed both success if the file was NOT encoded w/ keyframes setting... if it was encoded w/ keyframes, then option #1 (seekmode=0) showed seek errors, always 3 frames off...
meaning: seek errors on my system are repeatable (if triggered), and are both confirmed by CK's test script and the inconsistent GMSD/SSIM results. you posted that you also had seek errors w/ option #1, yet when specifically setting seekmode=1 when running the GMSD/SSIM tests you get no errors... |
18th March 2019, 22:00 | #154 | Link | |
Registered User
Join Date: Jul 2010
Posts: 132
|
Quote:
where do I pass in the showstats parameter ? when I create an instance of the class, e.g. Code:
zopti = Zopti(log_fp, metrics=metrics_list, showstats=True) |
|
18th March 2019, 22:47 | #155 | Link | |
Registered User
Join Date: Dec 2005
Location: Germany
Posts: 1,795
|
@Iron_Mike, yes it's correct.
Quote:
Code:
alt_clip = muv.SSIM(alt_clip, clip, **filter_args).text.FrameProps() The values are much shorter. That means Decimal() is also totally unnecessary!? And we need to round even more? Or is FrameProps() rounding them?
__________________
AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK || VapourSynth Database Last edited by ChaosKing; 18th March 2019 at 22:53. |
|
18th March 2019, 23:07 | #156 | Link |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Correct. The seek-test script reported errors (the 3 frame off thing) with ffms2 - Wolfberry's and the version included with VS Fatpack portable. But I see no score inconsistencies running GMSD/SSIM with the same.
__________________
Nostalgia's not what it used to be |
18th March 2019, 23:48 | #159 | Link | ||
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Quote:
Quote:
stop 435.9938560956790122302706430 83.19534706841788751496835637 stop 435.9938560956790122302706430 83.19534706841788751496835637 stop 435.9938560956790122302706430 83.19534706841788751496835637 stop 435.9938560956790122302706430 83.19534706841788751496835637 stop 435.9938560956790122302706430 83.19534706841788751496835637 Consistent results on consecutive testing (still), but slightly different scores to previous results when rounded up to 14 decimal places.....not that it really matters.
__________________
Nostalgia's not what it used to be Last edited by WorBry; 18th March 2019 at 23:51. |
||
18th March 2019, 23:49 | #160 | Link | |
Registered User
Join Date: Dec 2005
Location: Germany
Posts: 1,795
|
Quote:
I mean your log is always in perfect order... I tested vspipe with 3 frames, and even then sometimes the output is 0 2 1 (before the update)
__________________
AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK || VapourSynth Database Last edited by ChaosKing; 18th March 2019 at 23:52. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|