rfgamaral Beginner
- Member since June 11, 2024
- Last Activity:
January 7, 2025 at 8:07 PM
- Posts
- 25
- Reactions Received
- 3
- Points
- 148
- Profile Hits
- 75
rfgamaral replied to the thread About VoukoderPro in DaVinci Resolve.
To be clear, I wasn't necessarily making comparisons, that was not my goal. I was just giving an example, and I used Handbrake.
The same thing happens if I encode from DaVinci with any other encoder other than Voukoder. I can crank up the bitrate in all methods to make sure that all encodes produce the highest quality file possible. The Voukoder version is the only one that has a slight blur applied to the edges compared to all other encodes. This doesn't feel right to me.
rfgamaral replied to the thread About VoukoderPro in DaVinci Resolve.
[…]
That makes no difference. I'm using the same exact encoder and settings in Voukoder (uses DaVinci timeline directly) and Handbrake (uses a DNxHR HQX 12-bit master exported by DaVinci), and the Handbrake version is slightly sharper (and more accurate with that I see on DaVinci). I've tripled-checked and all settings and parameters are the same, and I've disabled all Handbrake filters.
Maybe the difference is in the FFmpeg version being used by Voukoder and Handbrake?
rfgamaral reacted with to Vouk’s post in the thread About VoukoderPro in DaVinci Resolve.
rfgamaral replied to the thread About VoukoderPro in DaVinci Resolve.
[…]
@Vouk Colour wise, everything is perfect now, thanks. But now I'm noticing that the image is slightly less sharpened (compared to a DNxHR HQX 12-bit export from DaVinci); the difference is subtle, but it is there.
I could work around but increasing the sharpness in the editor, but I think the output should be the same, regardless of method of delivery. Especially since if I export a DNxHR HQX master and transcode it with Handbrake, I keep the original sharpness level.
rfgamaral reacted with to Vouk’s post in the thread About VoukoderPro in DaVinci Resolve.
rfgamaral replied to the thread About VoukoderPro in DaVinci Resolve.
I've just selected my DaVinci render preset, which includes the attached scene. I then added 5 jobs to the render queue, all for the same timeline, just with different file names.
File 1 & 2 looked like this:
File 3, 4 & 5 like this:
rfgamaral replied to the thread About VoukoderPro in DaVinci Resolve.
[…]
Not all the time, but I observed a few instances where it did.
[…]
Tried both "Video" and "Full", neither solved the issue, the colours are still a bit off.
rfgamaral reacted with to Vouk’s post in the thread About VoukoderPro in DaVinci Resolve.
rfgamaral posted the thread About VoukoderPro in DaVinci Resolve.
I've been testing the latest VoukoderPro with DaVinci Resolve (with both libsvtav1 and libx265), and almost everything seems to be working great.
1. To start, I have a simple question. Regardless of the codec I use, I'm always going for yuv420p10le for 10-bit. In DaVinci, you can pick one of multiple options for the "Type" in the render settings, and as you know, most of them say "8-bit", but there's one with "16-bit". I'm assuming I should use the "16-bit" one, however, I've tested them all,…
rfgamaral replied to the thread - Fixed
"codec is not opened yet" ?.
I can confirm that v2.0.3 works. I've been doing some tests with both x265 and AV1, everything seems to be working all the time. However, I'm having small issues and a few questions that I'll post in a different topic. Thank you, @Vouk .
rfgamaral reacted with to Vouk’s post in the thread - Fixed
"codec is not opened yet" ?.
rfgamaral replied to the thread - Fixed
"codec is not opened yet" ?.
@Vouk I got the same error within DaVinci but now looking at the logs I got:
(Code, 2 lines)
Since I haven't been able to actually test this new version during the trail, any chance you can extend my trial licence?
rfgamaral reacted with to Vouk’s post in the thread - Fixed
"codec is not opened yet" ?.
rfgamaral replied to the thread - Fixed
"codec is not opened yet" ?.
@Vouk DaVinci doesn't seem to crash any more, but I still get the "Codec is not opened yet" message every time (same error on the log files).
I've prepared a small project with a small test file, maybe that will help figure out things. All I did was create a project, load the project settings preset I normally use, and add a small test file to a timeline, nothing else. This file comes from the same camera/settings I use most of the time, and it's from the same session of recordings for the…
rfgamaral reacted with to Vouk’s post in the thread - Fixed
"codec is not opened yet" ?.
rfgamaral replied to the thread - Fixed
"codec is not opened yet" ?.
Here you go, @Vouk .
Although I have a feeling, the issue is not on the scene. Based on the logs, it looks like it's not able to connect to FFmpeg/x265, and/or there's something wrong with my source data. But I'm just taking guesses.
rfgamaral replied to the thread - Fixed
"codec is not opened yet" ?.
It's in the log file but it was "yuv420p10le".
rfgamaral replied to the thread - Fixed
"codec is not opened yet" ?.
@Vouk I'm having the same issue VoukoderPro v2.0.2 (just installed).
Here are my settings:
I get the same "Codec is not opened yet" message on the first render attempt, and on the second, DaVinci just crashes/closes. I've attached a log, but the problem is likely here:
2025-01-02 12:27:31 (trace) [FFmpeg:0] Cannot open libx265 encoder.
2025-01-02 12:27:31 (error) [EncoderNode.cpp:342] Opening the encoder plugin failed with error code: -1094995529
Not exactly sure what I've done…
rfgamaral replied to the thread Voukoder Pro 2.0.
I've installed FFmpeg.GPL.Installer.msi from GitHub, reboot my PC just in case, but opening DaVinci 19 I get this:
[Blocked Image: https://i.ibb.co/Wv8QhSk/Screenshot-2024-12-22-111211.png]
I've checked and C:\Program Files\FFmpeg is in the system PATH.
What am I doing wrong?