I updated from FFmpeg 5 to FFmpeg 6 in these version. I didn't change anything else.
I might try to make a new build with a recent version of FFmpeg and we can check the results.
Beiträge von Vouk
-
-
According to the devs the difficulty is NotchLC is not compatible to FFmpegs GPL. That's why nobody is including it.
-
Please update your NVIDIA drivers.
-
Yes, I can confirm that. Need to investigate when I have time.
-
You've probably heard about the mysterious Voukoder successor app I've been working on for years. This application was completely rewritten, and I even made sure I can compile it for both MacOS and Linux as well.
However, the app called VoukoderPro is currently in beta at best. It works basically, but I haven't added all the functionality (encoders, post processing, ...) yet.
But I want to give you a chance to test it and I'm curious about your feedback.
- Is the handling intuitive?
- What is your impression?
- What is still missing?
- What can be improved?
- What bugs have you noticed?
- ...
Currently VoukoderPro supports DaVinci Resolve Studio as well as Adobe Premiere Pro and Media Encoder. Other applications will follow. All components are included in the installer, no more external connectors are needed. You can also install it parallel to the current Voukoder.
Thanks.
P.S.: A good start is to open the designer and do "Scene > New > Simple".
P.P.S.: Please create one new topic for each issue you find in the beta version.
Download here: Downloads & Instructions
Version history
0.7.0.0
- Added first VEGAS Pro plugin version (VEGAS Pro 20.0 only)
0.6.0.0
- Fixed opening the Designer from within an NLE
- Fixed minor bugs
- Updated exp. date to end of september 2023
0.5.0.1
- Added AfterEffects Plugin
- Fixed save-bug
- Minor improvements
0.4.0.4
- Digitally signed all binaries compiled by me
- Digitally signed the MSI package
- Added a "Latest News" dialog window
0.4.0.2
- Migrated to Qt6
- Fixed issues with audio only scenes
0.4.0.1
- Fixed handling filter graphs with multiple output nodes
0.4.0.0
- Initial beta release
-
Please share your voukoder log file with us? (after repeating the issue)
-
Please check the Voukoder log file. => Where do I find the log file?
-
Yes, that looks a bit suspicious.
Code[18:36:03] Timebase: 63937/2360865 (36.92 fps)I'm pretty sure some encoders or formats/muxer could have problems with it
-
Well, I have added this to VoukoderPro recently, maybe that is helpful:
Which then changes this view
to this view:
-
alex2310 First, thanks for your suggestions.
you can see the encoder parameters in the advanced options, but you can't edit (or copy-paste them) manually
Each parameter you can configure in Voukoder does have a name (as you can see in the box below). But this name is not necessarily exactly like on the command line level. In your example the keyframe interval is sometimes "keyint" and sometimes "g". It's not easy to interpret and parse all parameters reliably.
perhaps it's best to leave the commandline uneditable, but make the all the options searchable.
That could be a possibilty. Would that help?
use separately compiled libraries like SvtAv1EncApp.exe, x265.exe
That's not possible. These binaries are compiled in as libraries and used on the C API level. Voukoder is not just a GUI frontend for the exe files (like other tools).
-
Code
[10:43:23] - Audio ------------------------------------- [10:43:23] Timebase: 1/192000 [10:43:23] Channels: 2 [10:43:23] Encoder: aac [10:43:23] Options: _sampleFormat=fltp b=320000 profile=aac_low [10:43:23] Side data: <none> [10:43:23] Filters: filter.adelay#delays=8525S:all=1You have set a sample rate of 192 kHz in your audio settings in VEGAS Pro. But ...
CodeEncoder aac [AAC (Advanced Audio Coding)]: Supported sample rates: 96000 88200 64000 48000 44100 32000 24000 22050 16000 12000 11025 8000 7350... AAC only supports up to 96 kHz.
Usually this is set to 48 kHz - which should work perfectly.
-
The other options are set to its default value (which is the same as if they were not applied). So it shouldn't make a difference.
-
It is enabled by default. See Where do I find the log file?
-
Unfortunately this is currently not possible.
-
I have just tested it with a freshly installed VEGAS Pro 20.0 (Build 403). Everything works as expected.
You might want to try holding CTRL and Shift during VEGAS startup to clear the cache. This worked for me a couple of times in the past.
-
I see a couple of issues here.
Code[18:02:53] Timebase: 1209076067/1928261632 (1.59 fps)Please select in the export "Video" group the proper frame rate. (Maybe this even fixes that problem).
Code[18:03:02] Frame #12: vRender: 31 us, vProcess: 27 us, vEncoding: 1563 us, aRender: 462179 us, aEncoding: 103786 us, Latency: 603058 us [18:03:03] Frame #13: vRender: 14 us, vProcess: 4 us, vEncoding: 2494 us, aRender: 425731 us, aEncoding: 127034 us, Latency: 591155 us [18:03:03] Unable to write packet to disk. [18:03:03] 000000007B0730B0 [18:03:03] 000000007B0730B0 [18:03:03] Exported 14 frames in 9 seconds. (avg. 1.41 fps) [18:03:03] Encoding loop finished (Code: 20)It was not able to write the exported file to disk. Maybe this is somehow related to the first issue. If not, make sure the current user has write access, and there is enough disk space left.
-
Please attach a Voukoder log file.
Where do I find the log file?
Main log file
The main log file contains all log data for one single day:- Voukoder initialization
- All exported files
(Quelltext, 1 Zeile)
The files are named by the ISO date (yyyy-mm-dd).log:
Export specific log file
If you have "Create log next to the export file" enabled you can also find it - well ... - next to the exported file. This log file contains only the export relevant information.
Low level debugging
Sometimes its…
-
Around 5am local time, but that's okay.
-
Your installation path is wrong. It is supposed to be: C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\IOPlugins
-
Are you using the free Version of DVR or the non free version (DVR studio)?
Only DVR studio is supporting external plugins.
