Beiträge von Vouk

I tested these settings. Quantizer=1 is pretty tough. If you set it to a higher value (i.e. 19) it looks much better. This is no Voukoder issue.

It might have to to with libav logging a bit. When I disable the logging and have my own logging instead it looks like this:

My logging looks like this:

[2019-04-13T11:43:24] Frame #51212: Render: 6 µs, Process: 2 µs, Encoding: 1677 µs - Total: 1685 µs (593 fps)
[2019-04-13T11:43:24] Frame #51213: Render: 7 µs, Process: 2 µs, Encoding: 1592 µs - Total: 1601 µs (624 fps)
[2019-04-13T11:43:24] Frame #51214: Render: 4 µs, Process: 1 µs, Encoding: 1679 µs - Total: 1684 µs (593 fps)
[2019-04-13T11:43:24] Frame #51215: Render: 6 µs, Process: 1 µs, Encoding: 2169 µs - Total: 2176 µs (459 fps)
[2019-04-13T11:43:24] Frame #51216: Render: 6 µs, Process: 1 µs, Encoding: 1903 µs - Total: 1910 µs (523 fps)
[2019-04-13T11:43:24] Frame #51217: Render: 8 µs, Process: 2 µs, Encoding: 1788 µs - Total: 1798 µs (556 fps)
[2019-04-13T11:43:24] Frame #51218: Render: 178 µs, Process: 2 µs, Encoding: 1654 µs - Total: 1834 µs (545 fps)
[2019-04-13T11:43:24] Frame #51219: Render: 6 µs, Process: 2 µs, Encoding: 1642 µs - Total: 1650 µs (606 fps)
[2019-04-13T11:43:24] Frame #51220: Render: 17 µs, Process: 6 µs, Encoding: 2002 µs - Total: 2025 µs (493 fps)
[2019-04-13T11:43:24] Frame #51221: Render: 5 µs, Process: 2 µs, Encoding: 1859 µs - Total: 1866 µs (535 fps)
[2019-04-13T11:43:24] Frame #51222: Render: 8 µs, Process: 2 µs, Encoding: 1734 µs - Total: 1744 µs (573 fps)
[2019-04-13T11:43:24] Frame #51223: Render: 8 µs, Process: 2 µs, Encoding: 1885 µs - Total: 1895 µs (527 fps)

The fps are actually misleading. It were "only" like 430 fps actually.

# GPU Session    Process   Codec       H       V Average     Average
# Idx      Id         Id    Type     Res     Res     FPS Latency(us)
    0      38       6840   H.264    2048    1152     421        2275
    0      38       6840   H.264    2048    1152     430        2308
    0      38       6840   H.264    2048    1152     425        2329
    0      38       6840   H.264    2048    1152     425        2332
    0      38       6840   H.264    2048    1152     427        2322
    0      38       6840   H.264    2048    1152     435        2278

I just compared the encoding speed of version 1 and 2. And it is pretty much identical.

Maybe you are comparing a release build and a debug build? Debug is always slower because performance optimizations are disabled there.

Can not reproduce it. Please tell me the exact steps or recorde a video of it again.

Make sure you use the same settings in both cases. Don't compare the settings in the gui, but the settings in the logfile.

BETA 4

Fixes:

• (nvenc_hevc) Fixing main10 profile
• (vp8,vp9) Fixed storing and loading strategy options
• Showing help text for each encoder option again
• Fixed exporting is slow when using max. render quality and activated max. render precision
• Fixed default frame size in AME preset creation

Changes:

• Added multilanguage support
• Added some audio only formats

First of all: Thank you!

1. We have the similar problem with other languages too. Sometimes the english name is not translated because everyone is using the it already as it is i.e. "Bitrate". But sometimes the name is more descriptive which could be translated i.e. "Average bitrate". So i'd only translate the last one to "Durchschnittliche Bitrate". I trust in you to find the right balance here.

2. Well, i have the same with AMF. Just do as you think it's right. Maybe other chinese users can help you translating it and test the translations later on.

3. Would you like to be the official translation maintainer? You would also get a chinese subforum where you can discuss these things with other chinese?

tbd

Fixed in 2.0-beta4.

Logic to switch languages in 2.0-beta4.

Discussion about single languages here: Translations

Available in 2.0-beta4.

I suggest to also add WAV.

Default frame size is 1920x1080 now.

Fixed in 2.0-beta4.

Can someone else please test this? Thanks.

I removed the match_source entries, thanks.

But can you tell the exact steps on how to reproduce the first error?

Thank you for your support!

But if you experiences issues please make sure you give me enough information so I can reproduce it and see the issue myself. Only then i can really fix it.

Unfortunately Premiere does not provide this information. Thus I can not implement this feature.

What is the memory usage in the moment when this error appears?

[2019-04-06T09:42:42] InitializeEncoder failed: out of memory (10)

This has not necessarily to do with out-of-memory. In the past this often happened when the 2 allowed nvenc were already in use.

Close all programs that make use of nvenc.

You can check with the following commands how many nvenc session are used. You should only see dashes here:

cd "c:\Program Files\NVIDIA Corporation\NVSMI"

nvidia-smi.exe encodersessions

Not a voukoder bug, though.

Please copy the logfile in the general tab after reproducing the issue to the forum.