Is fixed in version 2.0.0-beta2.
Beiträge von Vouk
-
-
Well, could be done quite easily. But is it really neccessary? What's the use case?
-
This is known and has been fixed here: https://www.voukoder.org/forum/thread/271
-
Are these missing settings in dropdown boxes in the configure dialog?
Do other types of settings work? i.e. numeric values?
-
Currently this is on purpose. I am thinking about other possibilities.
-
Is fixed in version 2.0.0-beta2.
-
Thanks. PCM in mp4 is still considered experimental. Removed it.
Is fixed in version 2.0.0-beta2.
-
Is fixed in version 2.0.0-beta2.
-
-
-
-
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,i4x4It 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