Beiträge von Vouk

You will find some information here: https://ffmpeg.org/ffmpeg-filters.html#unsharp-1

Added hqdn3d, nlmeans and removegrain filters.

Normally Premiere allocates as much Ram as possible to to parallelize as much as possible (there is a setting for that. So that is not necessarily a bad thing. Well, it shouldn't crash of course.

I still recommend using CRF. High bitrate doesn't relate to a high visual qualitym a low quantizer value does.

In your case the first pass was fine.

I guess you are the first one how tried to encode a >3hrs video with Voukouder. Does the error also occur on a 1pass encode? I'd also recommend to use CRF instead of ABR/VBR if you don't target a specific filesize.

I tested both. But MediaInfo did not report any interesting values being set.

Would it help if this fields can be set in the "Side Data" tab?

https://ffmpeg.org/doxygen/trunk/…htMetadata.html

Not sure how this is being used internally (and if it is used at all).

Maybe I'll do this in the future. It requires basically to write a parser and a whole editor understanding the whole parameter symantics. Nothing to expect soon.

So which of these denoisers would you like to have?

https://ffmpeg.org/ffmpeg-filters.html#toc-atadenoise

https://ffmpeg.org/ffmpeg-filters.html#toc-dctdnoiz

https://ffmpeg.org/ffmpeg-filters.html#vaguedenoiser

https://ffmpeg.org/ffmpeg-filters.html#owdenoise

https://ffmpeg.org/ffmpeg-filters.html#toc-dctdnoiz

https://ffmpeg.org/ffmpeg-filters.html#toc-bm3d

https://ffmpeg.org/ffmpeg-filters.html#toc-hqdn3d-1

https://ffmpeg.org/ffmpeg-filters.html#toc-nlmeans-1

https://ffmpeg.org/ffmpeg-filters.html#toc-removegrain

https://ffmpeg.org/ffmpeg-filters.html#toc-fftdnoiz

I was finally able to also include hevc_svt and vp9_svt. Still need to test both.

Unfortunately not (that i know of).

Well, I put a 30 fps file on a 60 fps project / sequence / timeline. That's not under voukoders control, it will be handled by premiere / the NLE. The NLE will send a 60fps frames stream to voukoder. These frames can be anything. Applying a decimate filter at this staged doesn't make any sense, right? Setting cycle to 3 would just output a 40fps file.. but... why?

Ok, crop and pad added.

Not sure about decimate as it adjusts the output framerate.

With a file of 25 fps "decimate=cycle=3" would generate a 16.66666 fps file. Wouldn't it make more sense to let the NLE handle all framerate stuff?

Seems Voukoder has some issues when the sequence is based on variable framerate (VFR).

Thanks for this very detailed error report.

[15:36:17] Timebase:        815626929/612929536 (0.75 fps)

I guess this is because of the strange framerate of 27.01 fps in your project. Can you try disabling "Match Source" for the framerate in premieres video tab and select a proper one?

I can't find an "addborders" filter in the latest FFmpeg. Are you sure about the name?

So they way I get the pixel data from premiere is okay?

morphinapg Could you write down the settings (encoder, options, muxer, filter, etc) and a short description text so I could add this as preset? Or maybe even more than one.

Unfortunately AE (unlike ME) does not support multipass encoding.

Planned

• Presets (Recommended presets for various use cases / scenarios)
  (Done)
• UI Changes (Redesign the User Interface)
  (Done)
• AV1 encoder (Implementing SVT-VP9/AV1 in Voukoder)
  (Not implemented)
• One log per export (Option to write the log file/settings info next to the output file)
  (Done)
• Add more filters
  (Done, added: crop, pad, hqdn3d, nlmeans, removegrain)

Version 1.0.1 of the premiere connector has a better auto detection of the install path.

There is an issue with the adobe installer unfortunately.

Short version: Update to Connector 1.0.1.

Connector

Normally there should be a registry key like this:

HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Premiere Pro\CurrentVersion

But if you have multiple versions of premiere installed (i.e. 2019 and 2020) and you uninstall one version it seems this key gets deleted in the adobe deinstallation process. This means the connector installer can't autodetect the target directory and it looks like this:

You have to change this path to the adobe shared plugin directory (In my case):

Otherwise the plugin can't be found.

I will try to find a workaround for this next week.

Voukoder Core

The voukoder.dll should be installed to an independent directory (i.e. the default one). It gets registered as a COM server then. In the registry it should look like this :

Normally there is no need to copy it over to the adobe plugin directory.