I agree, sounds like a bug.
Beiträge von Vouk
-
-
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.
-
I had it in for some time. But the logic was really messed up. It didn't work when you were using quantizer based rate control methods .
-
Release Notes
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.
Important
Make sure you are using the latest connector for your application(s)!
Fixes
- Closing the separate logfile properly
- Fixed atrim selection by sample count
- Fixed bwdif filter options matching their labels
- Fixed deinterlacing filters (Bobbing)
- Fixed audio stream bug
- Clearing options on encoder change
Changes
- (h264_amf, hevc_amf) Added "GOP size" option
- (x264,x265) Added more options (@Kleinrotti )
- (x264,x265) fixed loading of grouped parameters
- Added wavpack encoder (@Kleinrotti)
- Added SVT-AV1 encoder (experimental)
- Added iAvoe 's x264 presets
Notes
For using NVENC encoders driver version 436.15 or newer is required.
Credits
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.
-
-
Release Candidate 2
Fixes
- Closing the separate logfile properly
- Fixed atrim selection by sample count
- Fixed bwdif filter options matching their labels
- Fixed deinterlacing filters (Bobbing)
- Fixed audio stream bug
- Clearing options on encoder change
Changes
- (h264_amf, hevc_amf) Added "GOP size" option
- (x264,x265) Added more options (@Kleinrotti )
- (x264,x265) fixed loading of grouped parameters
- Added wavpack encoder (@Kleinrotti)
- Added SVT-AV1 encoder (experimental)
- Added iAvoe's x264 presets
Notes
For using NVENC encoders driver version 436.15 or newer is required.
Download
-
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?
-
Working on it.
-
First, their "plugin" has less options and thus they don't have a complex UI and everything.
Second, I guess they are doing all the pixel format conversion on the GPU.
Third, I use FFmpeg internally to have the same interface for all encoders. They have less glue code in between.
Premiere does not use x264, they use the man concept encoders.
-
Many of you use the Voukoder plugin to have NVENC or AMF GPU acceleration available in Premiere and/or Media. The good news is they will support it natively in the next version (tested it with the latest 14.2 beta version). It is even alot faster than Voukoder ever was: 1m50s vs. 3m00s with my test clip. I am glad I could help you out the last 3 years to provide are workaround. Of course I will continue to develop the plugin as it also supports many other codecs and encoders (and containers like MKV).
-
Kleinrotti AV1 is just extremely slow and needs a high performance processor. Otherwise it might seem as "not working".
-
Please try to click on the "(Use project settings)" first.
-
Your approach was correct. You decrease the quantizer value until you are happy with the quality.
What did youtube complain about?
-
Sorry, it took me a while to reply to this one.
Can you post your voukoder log file please?
