This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[HELP] why the capacity is too big?
#9
Okay, here's what happens:
Calulcating file size with bitrate: 5577kbs, speed: 172.55fps
Updating progress (assumed length: 1442.11s): FPS: 172.55, Bitrate: 5577, Percent: 99.9341, RestTime: 00:00:00, EstimatedSize: 958.76
Length is correct, bitrate is read correct.
So the problem must be with the size calculation.
Hybrid assumes the bitrate is in kilo bit per second.
QString::number(bitrate * 1000.0 / 8.0 / 1024.0 / 1024.0 * m_currentLength, 'f', 2);
* 1000 to get to bit per second
/ 8 to get to byte per second
/1024 to get to kilo (=1024 since we want to go for file size not data rate) byte per second
/ 1024 to get to mega (=1024*1024) byte per second
* 1442.11s to get to mega byte.
this seems correct to me.

taking the file size 4618.59 MB
/ 1442.11s to get to mega byte per second
* 1024 to get to kilo byte per second
* 1024 to get to byte per second
* 8 to get to bit per second
/1000 8 to get to kilo (= 1000) bit per second
gives = 50 478 kBit/s

That's nearly a factor 10 away from what was reported.
So either I overlook something here or this isn't Hybrids fault by a bug in NVEncC.

Seeing that I thought may be NVEncC switched to reporting in 'kilo byte per second', but then it should be wrong on my system too.

So I just did another test here:
Updating progress (assumed length: 269.242s): FPS: 707.84, Bitrate: 7284, Percent: 99.0808, RestTime: 00:00:00, EstimatedSize: 233.79
is what Hybrid predicted and
encoded 32237 frames, 706.92 fps, 7269.07 kbps, 232.79 MB
encode time 0:00:45, CPU: 4.4, GPU: 28.0, VE: 64.8, GPUClock: 1837MHz, VEClock: 1664MHz
frame type IDR    27
frame type I      27,  total size    1.48 MB
frame type P   32210,  total size  231.31 MB
ist the output on my system.
-> The calculation of Hybrid is correct and matches the prediction of NVEnc.

I used the same settings as you:
NVEnc --y4m -i - --fps 120.000 --codec h265 --profile main10 --level auto --tier high --sar 1:1 --lookahead 16 --output-depth 10 --vbrhq 7200 --max-bitrate 240000 --gop-len 0 --ref 3 --bframes 0 --no-b-adapt --mv-precision Q-pel --preset default --colorrange limited --colormatrix bt470bg --cuda-schedule sync --keyfile GENERATED_KEY_FILE --output "E:\test.265"
I also double checked that the dev version comes with the same nvencc version I used.

No real clue why this is happening on your system.

My guess atm. is that something on your system is interfering with NVEncC bitrate reporting.
-> try whether this changes is you disable any antivirus&co software on your system.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Messages In This Thread
why the capacity is too big? - by kwan0220 - 22.10.2021, 10:51
RE: why the capacity is too big? - by Selur - 22.10.2021, 11:00
RE: why the capacity is too big? - by Selur - 22.10.2021, 11:09
RE: why the capacity is too big? - by Selur - 22.10.2021, 12:20
RE: why the capacity is too big? - by Selur - 22.10.2021, 13:11
RE: why the capacity is too big? - by Selur - 22.10.2021, 19:00
RE: why the capacity is too big? - by Selur - 22.10.2021, 22:49
RE: why the capacity is too big? - by Selur - 22.10.2021, 23:04

Forum Jump:


Users browsing this thread: 1 Guest(s)