Beiträge von avwtp

This will probably take a while to narrow this down and it may be similar to another bug posted regarding "GPU fail". Just want to put this in as a placeholder for future updates.

But what I'm seeing is that if I have Effects plugins that use the GPU on the first clip of the work area (that is being encoded), Voukoder sometimes blows.

[16:52:15] ---------------------------------------------

[16:52:15] Opening codec: h264_nvenc with options: 2pass=0|aq-strength=8|b=65000000|bf=2|bluray-compat=1|bufsize=60000000|g=30|gpu=0|init_qpB=51|init_qpI=51|init_qpP=51|level=5.1|maxrate=75000000|nonref_p=1|preset=hq|profile=high|rc=vbr|rc-lookahead=300|spatial-aq=1|strict-gop=0|surfaces=64|temporal-aq=1

[16:52:15] Failed opening codec: h264_nvenc

[16:52:15] Unable to open video encoder: h264_nvenc

[16:52:15] Closing encoders ...

[16:52:15] Opening encoder failed! Aborting ...

[16:52:15] 00000000169A6BA0

Yep, that's one take away, thanks

also document that "B frames as References" = Middle is the only option with older cards.

* Finally, a more graceful exit (actually non-exit) with a dialog message when the nvenc encode fails at startup would help.

-- I'm adding a feature request for this.

I used another NVenc tool that allowed me to dump capabilities of my card:

#0: GeForce GTX 950 (768 cores, 1329 MHz)[PCIe3x16][442.74]

List of available features.

Codec: H.264/AVC

Max Bframes 4

B Ref Mode yes

RC Modes 63

Field Encoding yes

MonoChrome no

FMO no

Quater-Pel MV yes

B Direct Mode yes

CABAC yes

Adaptive Transform yes

Max Temporal Layers 0

Hierarchial P Frames no

Hierarchial B Frames no

Max Level 51

Min Level 1

4:4:4 yes

Min Width 33

Max Width 4096

Min Height 17

Max Height 4096

Multiple Refs no

So, it looks like my 950 has Ref Mode but NOT Multiple Refs. And this works in only one way:

* leave Number of Reference frames undefined (should be able set it to 1 but even ffmpeg errors on that).

* Set Use B frames as references = Middle

Output now shows:

FFmpeg: : Video: h264 (h264_nvenc) (High), 1 reference frame,

So the plot thickens. Running ffmpeg from the commandline on an OLD 2018 version of ffmpeg, it works fine (-refs=4). Using a new 4.2.2 build it now gets the error:

[h264_nvenc @ 0000000002d49800] Multiple reference frames are not supported by the device

[h264_nvenc @ 0000000002d49800] Provided device doesn't support required NVENC features

Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters

such as bit_rate, rate, width or height

Conversion failed!

So I found (thank you google) a bug report with ffmpeg https://trac.ffmpeg.org/ticket/8254 that explains what's going on:

------

The -refs option used to be used to control the dpb size of nvenc.

With the latest generation of cards and SDKs, nvidia added support for actually using multiple reference frames.

That series of patches brings nvenc in line with libx264 in what the -refs option does.

As of e929b2f248a9c49761475e07d1a089e05912d1c6, the old function of -refs has its own option, -dpb_size.

Since -refs actually controlling the dpb size very likely was not what users of the option expected or intended, it was decided to go for this slightly breaking change.

And it seems like it worked in making you aware of the -refs option not doing what you expected it do to.

------

When I ran my command line with -dpb_size 4, it works (accepts dpb_size).

>>> So now the next question is: What chipsets DO support the -refs option?

BTW, I have been buried in other projects and haven't been able to track Voukoder development since probably May 2019. For the most part I've been using 1.2x and an even older nvenc_export version. This new set up is a work of art! Everything in my work flow is now on 4.x and it's working cleanly. The Ref frame issue is the only outstanding issue I have. (other than FFMpeg not supporting slices=4 for NVENC but that's a separate battle outside of what you have control over).

Sigh. Here is a 2.2 log where it works. It's just that 2.2 logging is a bit more difficult to extract. This happens to be a 4K encode but good result for 1080p. My guess is that 2.3+ is doing something wrong on what parameter it is pushing out (not refs=4) so it's erroring.

2pass=0 aq-strength=8 b=62000000 bf=2 bluray-compat=1 bufsize=60000000 g=30 gpu=0 init_qpB=51 init_qpI=51 init_qpP=51 level=5.1 maxrate=70000000 no-scenecut=0 nonref_p=1 preset=hq profile=high rc=vbr rc-lookahead=128 refs=4 spatial-aq=1 strict-gop=0 surfaces=16 temporal-aq=1

Also the fact that 2.3+ crashes out vs. displaying some more user friendly error message would be great to fix. Note the user friendly error message when I set refs=8. Did that code get taken out?

I just hit this problem and what's odd about it for me is that setting Ref frames "worked" fine prior to 2.3. I confirmed that setting ref frames in 2.2 between 1- 4 DID work and change the encoded stream accordingly. Now in 2.3+, it aborts the encoder process and drops back to the PPro window (not pretty). Note also that in 2.2, if I set Ref Frames = 8, I get a nice dialog message after encode starts that this value is not supported.

BTW, analyzing the 2.3+ generated streams has a ref steams = 2.

Ditto. I really like to have the embedded encoding info. I too use it for debugging.

It is an overclock issue. Caught me off guard.

BIGGIE is that the if PPro or the plugin crashes, you can't get to the log file. Really want that old txt file backin $TEMP.

Hold up it may just be my computer overclocking. Done hours of x264 at this setting, not seen it at this Ghz before.

x264 2 pass encoding, consistent crash but since there isn't a log file, can't give you any more info. Really can't tell you how much I can suggest the plugin go back to keeping a log file in $TEMP.

I'm going to go back and try it with 1.2.1

Wow forgot about that. Even my Win 10 still the classic look and I have nearly every single "pretty display" feature disabled. I just want speed.

Thank you for taking the time on this. I tell ya, my eyes hurt going to all those rounded edges, shading and coloring. Couldn't wait to switch back after confirming it really was the theme.

OH my, how do make it not classic I had to enable Theme server (had it disabled). I have tried to maintain the same look since Windows NT 3.51 ... and that's going back quite a few years.

>> Secondly How in the World did you think about switching to Classic to find it? I would have never thought a Desktop can mess things up like this.

Anyway, confirmed it now works for me too.

2.0.6 preview for me still fails Win 7, CC 2015 and CS6. CS6 is a bit slower to crash but will happen on 2nd instance of the right things are poked. Same behavior (no change) from 2.0.5. Attached is a screen grab after 2nd entry into Configure and accessing Video panel (I think same as 2.0.5 but may tell you something). Reason I attach is that you'll notice that the dialog when mouse over sort of half refreshes. If I try to scroll or fiddle with the dialog, it crashes. Hope this may give you some idea. The initial/usual view is total blank.

Thanks for trying. When I have time I'm going to try it on 4 other installs, 2 are Win 10, the other two are Win 7. Yes I have a lot of computers/laptops here at the house.

Happy to give you a challenge. As long the separator syntax is documents in the paramenter "tool-tip" popup, it will work.

>> I confirm the problem. On Windows 8.1 in Premiere 2018, the export window can only be launched once after updating the Voukoder plugin When you restart the export window just does not appear

This is a different problem, I think, but I am seeing this inability to launch File->Export->Media (grey'd out) on a Sequence that I had done an export on previously.

That really seems like a problem as events/errors leading up to a hard crash can't be looked at.

moved aside Presets directory and created new one so nothing from 1.x would affect the plugin. No change in failure.

Could there be a file/directory protection issue? What new location are you saving the log file to? Any other new/different folders is 2.x writing to than 1.x?

Windows 7, 2015, GTX 950. Fails with x264 and NVENC. Seems way too basic a failure. 1.x plugin works fine, have it commented out (changed file type from prm -> prmx) when testing 2.x.

With 2.x not showing 1.x presets, I assume I don't have to hide them from the preset folder. I don't know what other cleanup I need to do.

Is there a 1.x -> 2.x upgrade FAQ?