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 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.
Please select in the export "Video" group the proper frame rate. (Maybe this even fixes that problem).
[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.
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.
I can confirm this. Somehow the filter graph does an automated conversion from "full" to "limited" and I don't know why ... yet. Investigating ...
P.S.: This is not related to AV1 or DVR only... it's deep inside voukoder.
The Resolve Connector has the option "YUV (High bit depth)" too. That's also YUV 444 with 16 bit depth.
Currently I am getting 32bit float YUVA input from Adobe Premiere only. But I need to downconvert it to 16bit int to feed it into FFmpeg as it doesn't support float YUV pixel formats. (to my knowledge)
Voukoder does not support FFmpeg command line options, but it does support some FFmpeg filters.
I guess this could work if I add all the comma separated filters in the filter chain above.
ProRes is a group of codecs.
h264 is is a codec.
MOV is a container format.
MP4 is a container format similar to MOV.
A container format can contain audio and video streams encoded with a codec:
This plugin can encode ProRes video streams combined with ALAC, AAC (and more) audio streams in a MOV (or MKV) container, yes. In this case no h264 is involved at all. Note: The ProRes encoders are not certified by Apple (but should still work).
Make sure you are using the latest connector for your application(s). For using NVENC (SDK 12) encoders driver version 522.25 or later is required.
Thanks to my all supporters by either PayPal or Patreon. Also thanks alot to the translators.
Todd Scarbrough, Gronkh, Schauerland, Kleinrotti, Magnus Allgurén, Chris Woods
Voukoder 13 should work now with qsv.
You're welcome. Thanks for notifying me about these errors. This helps making this project more reliable.
So what error do you experience? What is the problem?
Please try 0.12.4.
Can you provide a sample clip again so I can investigate it? Thanks.
Nice! I shouldn't be working that late anymore. It's almost 11pm here.
Okay, please try connector 0.12.1.
And for the coders in this forum - This is the current code:
std::string VoukoderFormat::GetTimecode(double seconds)
{
std::stringstream timecode;
// HRS
const int hrs = std::floor(seconds / 3600.0);
seconds -= hrs * 3600;
timecode << std::setw(2) << std::setfill('0') << hrs << ':';
// MIN
const int mins = std::floor(seconds / 60.0);
seconds -= mins * 60;
timecode << std::setw(2) << std::setfill('0') << mins << ':';
// SEC
const int secs = std::floor(seconds);
seconds -= secs;
timecode << std::setw(2) << std::setfill('0') << secs << ':';
// FRM
const double n = m_info.video.timebase.num;
const double d = m_info.video.timebase.den;
timecode << std::setw(2) << std::setfill('0') << std::ceil((seconds * d) / n);
return timecode.str();
}
Alles anzeigen
I'm not sure about the last std::ceil (always round up) at the end ... or if it should be a std::round (round to nearest integer) ...