Beiträge von Vouk

Zitat von kevinhuber

Here is an other try with 1920x800 frame size, and it doesn't work.

Zitat

[10:48:50] Frame size: 1920x801

Maybe you can try with exactly 1920x1080?

You can try to ZIP the logfile, but I guess I found the reason:

Zitat

[10:35:52] FFmpeg: VCEEncoderTrace: 2020-04-15 10:35:52.964 41B0 [VCEEncoderTrace] Info: SetProperty(-1) FrameSize:4096,1708

[10:35:52] FFmpeg: VCEEncoderTrace: 2020-04-15 10:35:52.964 41B0 [VCEEncoderTrace] Warning: SetProperty FrameSize failed in AMFPropertyStorageExImpl with return code:0x5

Seems the AMD VCE encoder can't handle that frame size.

For the english users: It seems the HD8000M series does not support GPU video encoding.

Can you try if the Advanced / Debugmode frame server work with Movie Studio HD / Platinum? It is using the same interface?

Seems to be a conflict with the selected level.

Can you please send a new logfile with low level debugging in the settings enabled.

But I guess this is some driver issue. Are both "h264" and "hevc" not available?

Works with CS6, CC2019 and CC2020.

Seems I can't install CC2018 anymore from CC. So I guess we'll treat it as a CC2018 bug.

• According to https://encodingwissen.de/codecs/x264/re…qpmax-quantizer qpmax has to be in the range of 1-69 (0 means disabled)
• The issue with "zones" and similar string input options is a known. The separators "," conflict with same named separators with FFmpegs / libavs av_dict_parse_string() function. I should actually remove these non-working options ...
• Removed rc-lookahead max. limit
• FFmpeg only allows surfaces values betwen 0 and 64 but it increases the value internally based on the given rc_lookahead.

Can you please post the voukoder logfile with low level debug enabled in the settings?

Unfortunately I don't have a Movie Studio Platinum license so I can't reproduce it myself.

Maybe the plugin interface is not 100% compatible with VEGAS. Can you show a screenshot of that "preset is not valid" message? Is there any more detail with it?

Please enable low level logging and copy the logfile again.

Maybe you can try upgrading to the latest voukoder version first?

Schick doch mal das Voukoder Logfile, dann sehe ich mir das an.

In the latest version the plugin identifies as "Voukoder" again.

I wrote an article about this effect: The mystery of delayed AAC audio tracks

I strongly suggest to use uncompressed (PCM) audio for intermediate files and only compressed/lossy codecs for the final result.

Voukoder does not multiplex at the end of encoding process.

It writes audio and video interleaved already.

If you have delays at the end make sure that "faststart" is not enabled.

I think so, yes.

Sorry for putting up some explanatory stuff here ...

The error message is back with connector 1.2.4. Seems Adobe has disabled that feature somehow.

Take a closer look

it is yuva444p16le