It depends on the complexity of your project and the used encoder.
You can read more about this here: Voukoder Performance Analysis
It depends on the complexity of your project and the used encoder.
You can read more about this here: Voukoder Performance Analysis
Please make sure you have a proper framerate set in the video tab in the premiere export settings.
Glad to hear that!
Please update to premiere connector 1.3.0 and you'll have 36fps support.
Okay, looks like there is something wrong with your settings.
[10:03:09] - Video -------------------------------------
[10:03:09] Frame size: 1920x1080
[10:03:09] Pixel aspect: 1:1
[10:03:09] Timebase: 65536/1966080 (30.00 fps)
[10:03:09] Interlaced: No
[10:03:09] Encoder:
[10:03:09] Options: <none>
[10:03:09] Side data: ТAA= ТAA
[10:03:09] Filters: <none>
[10:03:09] Passes: 1
[10:03:09] Color range: unknown
[10:03:09] Color space: unknown
[10:03:09] Color primaries: unknown
[10:03:09] Color transfer: unknown
[10:03:09] - Audio -------------------------------------
[10:03:09] Timebase: 1/48000
[10:03:09] Channels: 2
[10:03:09] Encoder:
[10:03:09] Options: <none>
[10:03:09] Side data: P=P
[10:03:09] Filters: #
Alles anzeigen
Can you go into voukoders configuration dialog, check the settings and click okay again to save valid settings?
If you do a sequencial export (one after another) with Media Encoder or After Effects this should be fine. Voukoder can't be used for a parallel export.
You might send me the voukoder logfile so i can take a look into it.
I agree, sounds like a bug.
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)
That is the classic approach you are describing here.
x264 for example supports multipass (or n-pass) where the 1st pass is doing what you described above... the other passes are just about fine tuning the data and the last pass is actually encoding the data. It could be even a 10 pass process (but mostly makes no sense).
btw. NVENC handles it differently: It does 2-pass encoding in actually 1 encoding pass. I just have to send the data once. Not sure about the details though.
I'm not sure why you are targeting file size instead of quality for a project output though
Fully agree. Filesizes, bitrates, etc only make sense if you are limited by the filesize of a physical media e.g. BluRay or USB drive. For YouTube and similar just think about quality (~ quantizer values) and find a good compromise between quality and upload speed)
But back to topic: I am not sure what the benefit of a 3-pass, 4-pass or even more is. I highly doubt the decrease of filesize would be that big.
Yes, i will add that.
If you like Voukoder and especially if it helps saving time and money in your business - please consider supporting the project by paypal or on patreon. Thank you.
I am also looking for sponsors and partners. Please contact me if you are interested.
Make sure you are using the latest connector for your application(s)!
For using NVENC encoders driver version 436.15 or newer is required.
Thanks to my all supporters - especially the platinum tier patrons ValnirÆsirsson and Gronkh!
Okay, found it and fixed the issue.
btw: I configured the presets for around 60 fps output without any post processing (rescaling, etc)
Zitat[23:29:38] Timebase: 846556583/-368203776 (-0.43 fps)
Autodetecting the source framerate failed. So you need to set the frame rate or just click "match source".
Yes, it's included there.
For using NVENC encoders driver version 436.15 or newer is required.
The Adobe SDK actually limits the path to 255 characters.
Again, please provide a log file.
Not really.
So 0.7 is not working, but 0.6.1 works?