Beiträge von Vouk

So what does windbg.exe say about x264?

I check that, yes that is correct. I made a note in the release notes.

So i guess that issue has been solved, right?

Okay, normally I set:

info->max_width = 8192;
info->max_height = 4320;

But maybe that is a limitation from the encoder.

Fixed!

So what is not working in your case?

Rendering by Media Encoder? (prm file)

or

Rendering the Render queue? (aex file)

Released 2.3beta6

IMPORTANT: Please uninstall any old version of voukoder and its connectors first!

Fixes:

• Faststart setting did not get saved
• When using the color space filter the video track was missing
• Sometimes options from a previous configuration were not erased

Changes:

• Added 10bit export for hevc_qsv
• Added vp9_qsv in 8bit and 10bit for Ice Lake processors
• Removed lower bitrate limitation

Both updated components are available now. Please retest (and confirm that this is fixed now).

So, also strange one. According to the Premiere Developers Guide a key "CurrentVersion" should be present.

I have no clue why it can't start a software encoder. Maybe you can run it in a debugger (i.e. windgb.exe) so you get important additional logging information in the output console.

First, x264 is an encoder for the h264 codec. Just like there is an AMD h264 encoder, but not an AMD x264 encoder.

I would suggest you to test this with FFmpeg. Voukoder is always using the latest versions of all components from GIT master.

Existing for premiere but missing for VEGAS.

Requires additional UI elements.

On list for 2.4.

Should be possible.

I'll put it on the list for 2.4.

Can you post a voukoder log file? Then we can take a look at it.

What "bitrate=0" does is that it actually says "bitrate can be unlimited", which is what you want. This basically simulates a dynamic quantizer like CRF with x264.

So, yes i'll change it to allow bitrate=0.

Can't confirm.

If i run this ...

ffmpeg -i "z:\overvouk\2016-11-02-Dead by Daylight #001.mp4" -vcodec h264_nvenc -preset hp -profile:v main -rc:v vbr -qmin 0 -qmax 50 Out.mkv

... the quantizer value is frequently changing. Maybe the range between qmin and qmax in your case is just too small.

Gefunden und behoben. Benötigt allerdings für einen vollständigen Fix ein Update beider Komponenten.

• VEGAS Connector 0.4.5
  Erkennt nun den ausgewählten / gewechselten Preset und lädt diesen auch.
• Voukoder 2.3beta6
  Behebt einen Fehler das Optionen teilweise vom vorherigen ausgewähltem Preset übernommen werden.

can you start regedit.exe and make a screenshot of this key with all its entries first, please?

HKEY_LocalMachine\Software\Adobe\Premiere Pro\

Really strange. I have the impression that it is somehow related to your specific windows configuration.

Is it possible your user is a special restricted user? Maybe limited by various rules defined by a domain policy? Or in a citrix environment or similar?

I will add filters on demand. Please name the filters you need.

1. The connector should let you choose the installation directory. The default value will be taken from the registry:

C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore

2. Please make sure you have at least NVIDIA driver 418.81 installed

3. What happens if you use x264 with default options?

Das ist derzeit noch Baustelle die mir noch Kopfschmerzen bereitet. Ich fordere aktuell einen I420 Framebuffer an, bekomme aber keinerlei informationen über Farbraum und Pegel.

Der Workaround geht von Begrenzt/709 aus und das führt natürlich zu Problemen wenn es anderes ist.

Die Farbraum Filter konvertiert meines Wissens nach immer (spreizt/komprimiert). Sollte ich die Informationen von VEGAS korrekt bekommen müsstest du meinem Verständnis nach auch keinen Filter nutzen.

Der bekannte Frameserver macht es sich da einfacher. Er holt sich alles als RGB und rechnet es sich es dann in YUV ... um so wie er es gerade braucht. Diese Konvertierung will ich mir aber eigentlich sparen.