I was reading this on wikipedia for years that only ac-3 and aac are supported. But ...
Also MPEG-4 Part 3 audio objects, such as Audio Lossless Coding (ALS), Scalable Lossless Coding (SLS), MP3, MPEG-1 Audio Layer II (MP2), MPEG-1 Audio Layer I (MP1), CELP, HVXC (speech), TwinVQ, Text To Speech Interface (TTSI) and Structured Audio Orchestra Language (SAOL)
... I might have been wrong. Strange.
Welcome to Voukoder 2.0!
This will now replace version 1 which should be considered as deprecated from now on. But version 2 is not finished yet (from a feature point of view), there is more to come soon. There has been alot of beta testing and from my point of view it is stable now and ready for a public release. If you still experience some issues report them to the forum please.
Attention! Users have been reporting some issues with Threadripper processors (or maybe other processors with high core counts). Although this seems to be more premiere related I'm still investigating this. Thus ...
I am looking for a collaboration / a sponsor with a company providing me with hardware to investigate and fix issues like the one mentioned above. Please contact me (vouk@mailbox.org) if you are interested or if you know someone who might be interested in such a partnership. Thanks!
Thanks to all beta-testers, translation providers, my patrons on patreon, all donors.
Special thanks to GRONKH for the continuing support and being the first top patron!
Changes:
MP3 is not officially supported in an MP4 container, but as it still works i have added this option again.
Previousely discussed here: H.265 HDR
Congratulations to > 400 fps.
Thats what I meant: There are so many variables that could affect the performance. Maybe on 4 core systems CUDA is even faster. Who knows?
There are some issues with your system, yes. I have no clue why it is like that. It could be many things:
Maybe ...
I did not get any hardware donations and I can't afford buying any test equipment. So I can just guess here.
But as you have a working Visual Studio IDE and the voukoder sources I'd recommend that you try to find the issue. Try to find that slow spot.
Try to profile it.
Edit:
My i7-4770 looks similar but still faster than your Threadripper:
[20:01:44] Video frame #2297: Render: 808 µs, Process: 6 µs, Encoding: 1884 µs
[20:01:44] Video frame #2298: Render: 56 µs, Process: 3 µs, Encoding: 2543 µs
[20:01:44] Video frame #2299: Render: 19 µs, Process: 4 µs, Encoding: 1799 µs
[20:01:44] Video frame #2300: Render: 16 µs, Process: 3 µs, Encoding: 1747 µs
[20:01:44] Video frame #2301: Render: 9 µs, Process: 3 µs, Encoding: 3062 µs
[20:01:44] Video frame #2302: Render: 17 µs, Process: 3 µs, Encoding: 2303 µs
[20:01:44] Video frame #2303: Render: 8254 µs, Process: 6 µs, Encoding: 1191 µs
[20:01:44] Video frame #2304: Render: 654 µs, Process: 5 µs, Encoding: 1199 µs
[20:01:44] Video frame #2305: Render: 991 µs, Process: 5 µs, Encoding: 1220 µs
[20:01:44] Video frame #2306: Render: 227 µs, Process: 5 µs, Encoding: 1145 µsIt's interesting to see that every 4th frame is slow.
[18:46:11] Video frame #12935: Render: 14392 µs, Process: 6 µs, Encoding: 861 µs
[18:46:11] Video frame #12936: Render: 75 µs, Process: 3 µs, Encoding: 768 µs
[18:46:11] Video frame #12937: Render: 69 µs, Process: 2 µs, Encoding: 1461 µs
[18:46:11] Video frame #12938: Render: 64 µs, Process: 4 µs, Encoding: 1841 µs
Average FPS: 205
Can you try Premiere CS6? I'm using it. CC 2019 seems to be slower.
Just to clarify:
Render: 15 µs <- Voukoder has no impact on this, it is entirely premiere
Process: 5 µs <- Voukoder has high impact on this
Encoding: 676 µs <- Voukoder has small impact on this. Mostly libav / FFmpeg
Voukoder is very performant with 8bit formats (esp. yuv420p). Formats with higher pixel depths require an expensive frame conversion and are slower.
Rendering is done on the CPU mostly. It also depends on your source pixel format and all effects and filters you have applied.
I have no filters and no effects in my test.
In voukoder 1 the settings were defaulted to proper values. Even if you did not change it they were already pretty optimized. In version 2 you start completely from zero. So you can not really compare both to eachother unless you are very careful and you are very sure about what values the nvenc gets called with.
But even then:
gpu=0 preset=slow qp=15 rc=constqp
[16:23:21] Video frame #13077: Render: 13 µs, Process: 3 µs, Encoding: 1429 µs
[16:23:21] Video frame #13078: Render: 12 µs, Process: 3 µs, Encoding: 1701 µs
[16:23:21] Video frame #13079: Render: 19 µs, Process: 4 µs, Encoding: 1532 µsgpu=0 preset=fast qp=15 rc=constqp
[16:24:15] Video frame #10041: Render: 17 µs, Process: 5 µs, Encoding: 594 µs
[16:24:15] Video frame #10042: Render: 10 µs, Process: 2 µs, Encoding: 492 µs
[16:24:16] Video frame #10043: Render: 15 µs, Process: 5 µs, Encoding: 676 µsIt always depends on your video sources / filters / effects / almost everything
On my system CPU and GPU are at 100% load, and it is encoding h264 and 1152p with 430fps. I can't see anything slow there. It is all about the settings.
I would like to really have some nice settings to create some presets, but i need to find someone who has really insight in encoder configuration to create the best presets available to make this easier for users.
BETA 5
Fixes:
Changes:
Added in 2.0-beta5.
I'll mark it as planned. It is a bit complicated to handle the pass logfile.
I implemented this for h264 and h265/hevc.
b=15000000 bufsize=15000000 cq=5 gpu=0 maxrate=15000000 rc=vbravailable in 2.0-beta5
Fixed in 2.0-beta5.
I tested these settings. Quantizer=1 is pretty tough. If you set it to a higher value (i.e. 19) it looks much better. This is no Voukoder issue.
It might have to to with libav logging a bit. When I disable the logging and have my own logging instead it looks like this:
My logging looks like this:
[2019-04-13T11:43:24] Frame #51212: Render: 6 µs, Process: 2 µs, Encoding: 1677 µs - Total: 1685 µs (593 fps)
[2019-04-13T11:43:24] Frame #51213: Render: 7 µs, Process: 2 µs, Encoding: 1592 µs - Total: 1601 µs (624 fps)
[2019-04-13T11:43:24] Frame #51214: Render: 4 µs, Process: 1 µs, Encoding: 1679 µs - Total: 1684 µs (593 fps)
[2019-04-13T11:43:24] Frame #51215: Render: 6 µs, Process: 1 µs, Encoding: 2169 µs - Total: 2176 µs (459 fps)
[2019-04-13T11:43:24] Frame #51216: Render: 6 µs, Process: 1 µs, Encoding: 1903 µs - Total: 1910 µs (523 fps)
[2019-04-13T11:43:24] Frame #51217: Render: 8 µs, Process: 2 µs, Encoding: 1788 µs - Total: 1798 µs (556 fps)
[2019-04-13T11:43:24] Frame #51218: Render: 178 µs, Process: 2 µs, Encoding: 1654 µs - Total: 1834 µs (545 fps)
[2019-04-13T11:43:24] Frame #51219: Render: 6 µs, Process: 2 µs, Encoding: 1642 µs - Total: 1650 µs (606 fps)
[2019-04-13T11:43:24] Frame #51220: Render: 17 µs, Process: 6 µs, Encoding: 2002 µs - Total: 2025 µs (493 fps)
[2019-04-13T11:43:24] Frame #51221: Render: 5 µs, Process: 2 µs, Encoding: 1859 µs - Total: 1866 µs (535 fps)
[2019-04-13T11:43:24] Frame #51222: Render: 8 µs, Process: 2 µs, Encoding: 1734 µs - Total: 1744 µs (573 fps)
[2019-04-13T11:43:24] Frame #51223: Render: 8 µs, Process: 2 µs, Encoding: 1885 µs - Total: 1895 µs (527 fps)The fps are actually misleading. It were "only" like 430 fps actually.
# GPU Session Process Codec H V Average Average
# Idx Id Id Type Res Res FPS Latency(us)
0 38 6840 H.264 2048 1152 421 2275
0 38 6840 H.264 2048 1152 430 2308
0 38 6840 H.264 2048 1152 425 2329
0 38 6840 H.264 2048 1152 425 2332
0 38 6840 H.264 2048 1152 427 2322
0 38 6840 H.264 2048 1152 435 2278I just compared the encoding speed of version 1 and 2. And it is pretty much identical.
Maybe you are comparing a release build and a debug build? Debug is always slower because performance optimizations are disabled there.
Can not reproduce it. Please tell me the exact steps or recorde a video of it again.