Beiträge von Vouk

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.

Es ist OpenSource und muss auch OpenSource sein da ich andere OpenSource Komponenten verwende. Ich könnte theoretisch Geld nehmen, aber wenn der Quellcode offen ist könnte sich jeder den auch wieder selber kompilieren von daher macht es dann auch wieder keinen Sinn.

Ich hoffe auf zukünftige geschäftliche Sponsoren, bzw. auf Unterstützung per Patreon / PayPal etc. Insbesonders von Personen / Firmen die mit dem Voukoder (u.A.) Geld verdienen.

Looks like your frame size is a pretty bad choice:

[15:00:06] Frame size:      3840x1607

A width or height should at least be able to be divided by 8. So i'd suggest you to use 1600 instead.

Does this also happen with version 2.3?

Yes, I like this idea.

Implemented AV1:

[21:27:01] Frame #439: vRender: 31 us, vProcess: 16 us, vEncoding: 63649 us, aRender: 61 us, aEncoding: 265 us, Latency: 64077 us
[21:27:01] Frame #440: vRender: 23 us, vProcess: 11 us, vEncoding: 27684 us, aRender: 54 us, aEncoding: 254 us, Latency: 28058 us
[21:27:05] Frame #441: vRender: 27 us, vProcess: 15 us, vEncoding: 3904113 us, aRender: 61 us, aEncoding: 509 us, Latency: 3904768 us
[21:27:06] Frame #442: vRender: 48 us, vProcess: 16 us, vEncoding: 565042 us, aRender: 64 us, aEncoding: 355 us, Latency: 565568 us
...
[21:27:06] Exported 445 frames in 170 seconds. (avg. 2.62 fps)

I guess I need a better CPU... my 8700K is too slow.

You don't want the smallest file size here. Smallest file size means highest compression. And as you want to put this clip as source media in a premiere project I guess you'd even like to have no compression (-artifacts) to get highest quality and fast timeline scrubbing.

Don't care about 17MB files.

Alpha channel makes only sense with intermediate codecs (like ProRes). You need these in the editing process. When you're exporting a finished project you don't need it anymore. h.264 does not support it.