This actually happened to me when I left a gap between video clips, make sure you don't have that
Beiträge von iAvoe
-
-
So, as the topic, and I've actually written a post here, but I would agree it is very tedious and there are lots of "do not touch" options
I tried with v6.2 and made sure [show advanced options] are checked, which it doesn't do anything, so that's the problem
-
Yes, I know about this. Unfortunately I did not find a good way to tick the checkbox automatically when loading the presets.
The presets are updated in the code.
well... maybe you could make [show advanced options] checked in default (or change to [hide advanced options]), that would work just the same lol
-
I'm here again XD, I've found out that x264 custom presets would not be there if this thing is not checked:
So make sure you have selected "show advanced options" first before you are applying a preset... I guess XD
It can be solved by adding a line to automatically enable this option if its not on.
And just saying that I've updated the preset thread, there are speed improvement, some other parameters are tuned, and added more presets
-
Maybe a heatsink clean up will do, I guess?
-
Should we expect purely quality or also speed improvements?
speed improvement, I've fixed an error on merange, tuned some other parameters, and added more presets
-
I just checked, Intel QSV h.264 does have that option, not sure why it's not in voukoder. If you are in a hurry, I guess stick to x264 for now...
-
because qpmax=22，I put it there to prevent quality loss by locked any compression from quantization higher than 22, thus preventing people who are not very familiar with encoding setting, turning the quality down too much
-
Really great! I will add them to the x264 preset lists in voukoder!
Hey, care to update the preset both for x264 and x265? I've made a plenty of changes and I promise this one is much better
-
I remember some denoise filters are gpu heavy, some are cpu, there are also f3kdb, SMDegrain, KNLMeansCL, QTGMC, MCTDenoise, --NR (in x264)... I'm not sure are they now loaded in voukoder, but there are way more options...
-
There's a function in ffmpeg (maybe x264 has it too?) to fake video frame rate, give it a try?
-
Here's how 2 pass works: encoder firstly run through the whole clip to get quality for each frame (or block in frame in more rencent encoders) called pass 1, then mass adjusts all the quality values to get the file size, called pass 2. Which your 3 pass doesn't make sense to me... (I might be wrong on this)
I'm not sure why you are targeting file size instead of quality for a project output though, and I don't think quicksync h265 is anywhere as good as official x265 (I maybe wrong on this too), maybe give a try on x264 in crf mode, it can be fast as well, and might give a better quality result
-
I don't think many people would be using it, because it's not designed for x86 platforms that is currently best for video editing, or I'm wrong...
-
Alles anzeigen
iAvoe I've also downloaded 5RC2 now to test your presets. High Quality, High Compression would run like 24 hrs for a 30min video? Is that normal? I'm on Ryzen 3700X and GTX 1070.
And the more interesting thing is that the high quality preset always fails. The lossless (fast) preset as well. Adobe Media Encoder logs this:
Adobe Premiere
Es war nicht möglich den Encoder zu initialisieren.
Dieser Fehler tritt meinstens bei einer ungültigen Parameterkonfiguration auf.
Which means that this parameterconfig isn't valid.
Did you tried this one Vouk ?
Yep, it is, this setting has maxed high cost parameters. However there are even slower modes that are less effective. I uses this only for ~5min videos though
I'm not sure why it's not working though
-
Damn, I forgot to push my latest changes to GIT so the build server did not include this changes.
But it will look like this:
Hahaha ok I see, but just saying the lossless mode actually won't be fast or slower though
-
Really great! I will add them to the x264 preset lists in voukoder!
Hey I've just checked, the v5 actually didn't add those settings, is there anything wrong?
-
iAvoe okay thank you! I wasn't able to set denoise and GPU acc. Is that also in Voukoder on the settings page? And with --no-psy for example you mean no-psy=yes or no-psy=1 in boolean, right?
When I start to render a 30 min 1080p/60fps video with the given settings the rest time just increases and increases to more than 10 hrs but there is no progress. I think something is wrong or does it really need so much time?
Yeah I didn't see that setting either, but it's a x264 built-in function, it could be added in later version? I guess
Yes, it is no-psy here
I'm not sure why you are going this slow, x264 is a pretty fast encoder unless you maxed out motion search, I think it's due to some effect, you can try pre-render the sequence
-
I think NVENC is not designed for this use at first, so it would be better to use other encoders?
-
Sorry, that might be an idiotic question, but how can I configure the preset you give us in Voukoder (for me Premiere Pro)? I can just select the 3 given presets for x264.
Thats fine for me, its in the options page menu above the presets. The downside is you have to input every setting manually in every video project for current version (mouse select), I think the later updates than this comment would just add more presets, but you probably still have to do the calculation, and especially HDR info related parameters manually
-
x265 Common (all situation should apply, but still very slow)
[
Note: all unlisted settings are default
Warning: laptop users, remember connect to power
Warning: probably nerdy/hardcore content... though I'm not willing to admit... lol
Split Block: --ctu <less than 1600x900=16; 1600x900~2080x1170=32; more than 2080x1170=64> --rect --min-cu-size 16 --limit-tu 1 --tu-intra-depth 2 --tu-inter-depth 2 --tskip-fast
Motion search: --me umh --subme 5 --merange <ctu minus 4 and minus subme> --analyze-src-pics
*Alternative M. Search*: --hme-search umh --subme 5 --hme-range <Cm4mS÷4,Cm4mS÷2,ctu minus 4 minus subme>
Intra-frame Search: --max-merge 2 --limit-modes --limit-refs 3 --early-skip --rskip 1 --rc-lookahead <fps×3> --fast-intra --b-intra
Rate Control: --no-open-gop --min-keyint 5 --ref 3 --fades --pbratio <1.2 for waifu-anime only, other situation keep default> --bframes 14 --b-adapt 2 --no-strong-intra-smoothing
Transitions: --scenecut-aware-qp --max-qp-delta 6
Quantization: --crf 17 --crqpoffs -3 --cbqpoffs -1
Adaptive Quantize: --aq-mode 1 --aq-strength <waifu-anime=0.8, film=1> --qg-size 16
Rate Distort Optimize: --rd 3 --rdpenalty 1 --splitrd-skip --rdoq-level 2 --psy-rdoq <film=3.4, wf-anime=2.3, *add or minus 0.2 if ctu is 64 or ctu is 16*> --psy-rd <film=1.6, wf-anime=0.6 *add or minus 0.6 if ctu is 64 or ctu is 16*>
Deblock: <as default>
Sample Accommodating Offset: --limit-sao --sao-non-deblock
Data Perspective Lossless: <as default>
Picture/Sequence/Rate Parameter Set: --opt-qp-pps --opt-ref-list-length-pps --repeat-headers <for playing unmultiplexed h.265 video normally>
Input and Output (maybe consistency?): --hash crc --frame-dup --dup-threshold 59 --allow-non-conformance <use when writing custom parameters like here> --idr-recovery-sei <use when playing through network like from nas>
Processor Workload: --pools <select a single processor-ramsticks combination for multi-cpu setup ONLY, don't use more than 1 processor at same time as it slows everything down without improve. e.g. -,+ specifies 2 cpu-ram group, use the 2nd cpu, as premiere/FX/vegas is taking the 1st processor already>
Multi-thread referencing: <as default>
HDR Video: --master-display <tells decoder which color space to use :
DCI-P3: G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(?,1)
bt709: G(15000,30000)B(7500,3000)R(32000,16500)WP(15635,16450)L(?,1)
bt2020: G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(?,1)
CHECK SOURCE HDR VIDEO INFORMATION, MATCH WITH ONE BELOW, AND USE AN ACCORDING VALUE ABOVE:
L(?,1) COULD BE L(10000000,1), L(400,1)... CHECK THE SOURCE VIDEO
DCI-P3: G(x0.265, y0.690), B(x0.150, y0.060), R(x0.680, y0.320), WP(x0.3127, y0.329)
bt709: G(x0.30, y0.60), B(x0.150, y0.060), R(x0.640, y0.330), WP(x0.3127,y0.329)
bt2020: G(x0.170, y0.797), B(x0.131, y0.046), R(x0.708, y0.292), WP(x0.3127,y0.329)
> --max-cll <maximum content light level,maximum frame average light level> (use only when source video is specified, or found by ffprobe eventhough source video did not specify) --hdr10 <increase bitrate for HDR10 videos> --colormatrix <choose one according to source video INFO: GBR bt709 fcc bt470bg smpte170m smpte240m YCgCo
bt2020nc bt2020c smpte2085 ictcp> --transfer <transfer characteristics, choose one or keep unspecified as the source video: GBR bt709 fcc bt470bg smpte170m smpte240m YCgCo
bt2020nc bt2020c smpte2085 ictcp>
Windows export log: 2>D:\folder\log.txt
Linux export log: 2>&1 | tee D:\folder\log.txt
]
