btw. Voukoder can only encoder (with or without GPU) what it gets from premiere/the nle. So if premiere renders frames slowly it and does not give enough raw frames to voukoder, it will more or less wait for premiere and thus GPU load will decrease or even stall. That might be related to your projects complexity (filters, effects, ...).
Good to know.
Please enable low level logging and attach the voukoder log file to your post.
The tricky thing was that premiere feeds in 25 frames (50 interlaced fields) and the deinterlacing method "bob" creates 50 full frames out of each field. So it doubles the export frame rate. Normally voukoder creates all frames by itself and marks each frame with an unique and incremental PTS (Presentation time stamp). The "bwdif" filter added the additional frames by itself, so Voukoder didn't know about the correct next PTS value. Additionally the interleaving functionality had to be changed to keep the audio and video at the same length and in sync.
Does it help if you use the setparams filter as a workaround?
This is more a feature request than a bug report. But it not that easy to implement.
The "adelay" filter works by modifying the PTS not by actually adding silence.
I can confirm the bug and need to work on it.
Alright, Chris. It took me around 7 hours today but it seems to be fixed now. And it is as easy as it can be. Just keep the default video settings (25i, tff), add the bwdif / yadif filter and start the export.
Available in the next release.
So it seems I'd have to add the dpb_size parameter to both nvenc encoders, right?
avwtp ... as refs and dpb_size are not the same anymore, right?
I will go through all bug reports on the weekend, but ...
Great analysis! So it seems I'd have to add the dpb_size parameter to both nvenc encoders, right?
Really great! I will add them to the x264 preset lists in voukoder!
CQ=23 is a pretty bad value and I'd expect a bad result with it (I'd recommend a value of 15). That would also explain the low bitrate. 70Mbps is waaaay to high for 2704x1520@30fps with CQ=23.
I strongly assume Voukoder is producing the correct result here.
Please be more specific about exactly is not working / not correct. I assume you are talking about the stereoscopic side data?
The NVIDIA driver reports:
[15:14:07] FFmpeg: Multiple reference frames are not supported by the device
The one working export in the logfile was using libx264 which doesn't have this limitation.
I have the impression we'll need to set premiere to 25fps interlaced and the voukoder has to export with 50fps progressive (because a deinterlace filter is active). Can you send me some interlaced footage to test this?
The issue is that at least one pixel format has to be mentioned here:
[14:00:04] Opening codec: libx264 with options:
Normally this has to be yuv420p by default.
Please try loading, saving and loading the settings again.
If it still fails delete all saved presets/templates and start with a clean new project.
I have added FFmpegs "g" parameter so you can change the "group of pictures" size. Available in the next version.
Deinterlacing
You have to set premiere to export interlaced material (and the correct field order) so Voukoder knows it gets interlaced fields from premiere and can convert them to progressive frames. If you set it to "progressive" Voukoder already gets progressive frames.
Framerate
I am not exactly sure about the 25i to 50p conversion. But the more I think about this, the more I get the impression this is not about a single filter (bwdif) but more about a whole filter chain. Do you know with what FFmpeg command line you'd get the expected result?
BWDIF
Fixed that. Thanks for pointing it out. Will be available in the next release.
LOG
This is fixed already and will be available in the next version
Do you have a sample video for this? before and after?
Actually premiere does the rendering and Voukoder simply encodes the rendered frames.
