Beiträge von Vouk
-
-
This is the first public beta release of Voukoder R2.
It is a beta release and it is absolutely not recommended to use it for production work. You will use it on your own risk!
Please test this release carefully and yes, try to break it! Try to produce bugs and crashes and report your findings to me. I was working almost 7 months on this new version and did the best I could to get it this far. But now it's on you to provide some testing feedback. Please use the new Voukoder R2 subforum: Voukoder R2
I did not implement all requested features yet. For me it is more important to get the base system running, and once we got it that far I will work on your requests and ideas.
Thanks.
P.S.: Your donations and your support are very welcome. PayPal, Patreon and wire transfer are possible and I would be also very happy about hardware donations. I especially need high performance (And I mean it!
) CPUs / systems. Just contact me in that case.
P.P.S: Thanks to Gronkh for beeing my first top tier patron on patreon!
P.P.P.S: Doing my final testing on my i7 8700K / RTX 2080 TI setup I got like 430fps encoding speed! (2048x1152@60 with h264 NVENC / aac) and CS6. I STILL can't believe that!!
-
Case 2: For some reason x264 does not take the subme=9 setting. There is also no clue in the log-file. Maybe it is related to the issue described in case 3.
Case 3 - Thats an actual issue:
Code[2019-03-19 22:28:32,266265][INFO] Unable to parse encoder configuration: crf=17,tune=film,x264-params=keyint=50:min-keyint=1:scenecut=0:bframes=0:partitions=p8x8,i8x8,i4x4
It can't parse the configuration right. The commas in the partitions value are mistaken as the comma for separating the man key/value pairs. This is part of ffmpeg / libav.
-
Maybe there is something in the logfile. Did you check %TMP%\voukoder.log? If not attach it to your post, please.
-
You can see it in the the voukoder.log file. But as i did roll back to ffmpeg 4.0 libfdk-aac-1.dll is required.
-
I already prototyped to implement the Aomedia AV1 encoder. It was basically working, but encoding a single frame was around 2 minutes. It makes no sense to implement it at this point. Once the encoders are better i will add it!
-
Changes:
- Reverted FFMpeg back to version 4.0 until audio issues are solved
- AAC / AC3 should work again properly now
If you have any insights why there are these audio issues with 4.1 please let me know.
-
Looked into it:
- Default profile in my case is "LC" (Low Complexity)
- Bit Rate is 48kbit/s on (auto) but does match to each setting i make
- Sampling Rate is 48KHz which looks also good
Maybe you can reset you parameter cache? I also don't know about your sequence/project settings.
Trying to find a fix for the noise with AAC now ...
Edit: When using FFMpeg 4.0 AAC audio is fine. When using 4.1 its distorted. The higher the framerate, the worse.
-
Yes, i will look into this.
-
I'd like to add it.
Not to myself: https://www.ffmpeg.org/doxygen/trunk/…rce.html#l03588
-
In version 1.2.0 the built-in AAC encoder of FFMpeg seems to be broken. I will look into this, yes.
But there is an alternative / workaround:
- Simply extract the libfdk-aac-2.dll file from the attached zip archive to your C:\windows\system32\ directory.
You will then have the Fraunhofer AAC encoder available in Voukoder. This will work - maybe even better.
For licensing reasons both needs to be separated.
-
Just a small update while I am still working on version 2. Follow me on twitter (@LordVouk) to stay up-to-date about progress on version 2.
Changes:
- Upgraded to latest FFMpeg 4.1
- nvenc_hevc: Supporting B-Frames (RTX GPUs only)
-
Thanks for analyzing this!
Note to myself:
av_dict_set(&formatContext->metadata->metadata, "major_brand", type, 0);
av_dict_set_int(&formatContext->metadata->metadata, "minor_version", minor_ver, 0);
-
If you are targeting a hardware decode (i.e. iPhone) you need to take care about the decoding capabilities and feature sets supported. This is normally defined in the so called "Levels".
Did you try encoding the 2-pass video with ffmpeg? Does this play on the iPhone?
-
It's been a bit quiet about Voukoder development as I am spending most of the time on Voukoder 2.0 in a private repository. Working with Microsoft Foundation Classes is a pain in the *** and is so very much time consuming.
Still, here is a small update:
Changes:
- Added additional framerates: 18, 119.88 and 120 fps
- Added HAP/Quicktime encoder
- Using the latest FFMpeg 4.0
Merry christmas and a happy new year.
Edit:
I added CS6 compatibility back to version 1.1.3. Everything else is still the same.
-
-
There is a new, free implementation "dav1d" done by the VLC team. This should be faster and stable. I'll give it a try soon.
-
Phew... never dealt with timecode tracks before.
I guess it is not possible to preserve it. But maybe it is possible to create a new timecode.
Need to look that up in the ffmpeg docs.
-
This is a hotfix release for CC 2019 users.
It fixes a resource loading issue that caused CC 2019 to crash on voukoder selection.
-
News:
If you like this project please support it on https://www.patreon.com/voukoder - even if you just plegde just $1. From $10 on you can get access to the nightly builds and test new functionalites before it is released to the public.
What is this money for? I have a regular 40h/week job. The more you fund me on patreon the more time I can shift from my day job to voukoder development.
TLDR: You fund voukoder development time!
I am also looking for a business partnership / sponsoring. Please contact me by email (vouk@mailbox.org) if you are interested.
Changes:
- AV1: Prepared for AV1 (but not included yet, because it is not really usable)
- FFV1: Added FFV1 (Level 3) encoder
- ProRes: Added vendor parameter to the UI so users can have a more "comaptible" ProRes export
- VP8/VP9: Added parameters -g, -auto-alt-ref, -lag-in-frames and -sharpness to both VP8 and VP9
- Made the encoder/muxer test before starting the export more safe (esp. when audio is disabled)
P.S: It might seem there is not much Voukoder development anymore, but I am working on the next major version which will bring the plugin to an entirely new level! So stay tuned.