Beiträge von Vouk

Unfortunately there is no way to ask Premiere to send the raw frames in a certain color space.

Most pixel formats are either:

• bt709
• non-bt709

Zitat von artofcharly

Vouk, everytime 165 FPs. Man! You're awesome =)

Yep, that is the advantage of using an intermediate (and lossless) codec.

And if you want to shoot video always use a camera that records in ProRes. Never use h264 or hevc. These codecs are good for exporting the final, finished media, but nothing else.

The logfile does not contain any encoder startup. Please reproduce the error and then send the logfile again.

Great news! The huge file size is because it is lossless compressed. you can't reduce the file size. But in my opinion it is perfect for intermediate video clips.

Make sure you are using the correct video levels (limited/full) and bt709 for hd video or bt601 for sd.

Happens sometimes. Esp. if source clips are recorded with variable frame rate (like shadowplay).

[10:49:28] Timebase:        423365927/-368203776 (-0.87 fps)

Check the framerate in premieres video tab before starting to encode. Seems it was not able to auto detect it. Please set a correct value and try again.

Where do I find the log file?

What steps are required to reproduce this?

What is the actual error message?

Please also provide a voukoder logfile.

Ich habe mir das mal angesehen:

Zitat

[18:41:51] - Video -------------------------------------

[18:41:51] Frame size: 1280x720

[18:41:51] Pixel aspect: 1:1

[18:41:51] Timebase: 1/25 (25.00 fps)

[18:41:51] Interlaced: No

Er bekommt eindeutig das Signal von Premiere das das Bild 1280x720 bei 25 fps ist.

Kannst du ggf. mal Screenshots von dem komlpetten Export-Fenster mit den Video Einstellungen machen?

You are right. This is a rare case (and a good example) where actually the video encoding is the bottleneck.

[17:12:11] Frame #233: vRender: 20 us, vProcess: 10567 us, vEncoding: 29849 us, aRender: 63 us, aEncoding: 793 us, Latency: 42414 us
[17:12:11] Frame #234: vRender: 20 us, vProcess: 10604 us, vEncoding: 29452 us, aRender: 63 us, aEncoding: 442 us, Latency: 41711 us
[17:12:11] Frame #235: vRender: 19 us, vProcess: 10465 us, vEncoding: 29521 us, aRender: 64 us, aEncoding: 462 us, Latency: 41812 us
[17:12:11] Frame #236: vRender: 20 us, vProcess: 10410 us, vEncoding: 29694 us, aRender: 61 us, aEncoding: 10 us, Latency: 41313 us
[17:12:11] Frame #237: vRender: 19 us, vProcess: 10273 us, vEncoding: 29524 us, aRender: 62 us, aEncoding: 446 us, Latency: 41454 us

As I can see you are encoding in 10 bit. That means:

You should get a huge performance boost if you render in 8 bit. Do you have to use 10 bit?

As far as I know the old version of Voukoder did not do a proper 10 bit encode. That's most likely why they were faster.

If Voukoder Performance Analysis is TL, DR here:

When looking at your Voukoder logfile we'll most likely see high "vRender" times. This is the time Premiere needs to render a single frame. As the whole export is a synchronous chain the final encoding fps can be any higher than a single part of the chain.

You might want to add your log, but I guess it'd most likely confirm this.

Even more DR:

Your GPU could be able to encode with like 1000 fps, but if premiere is only able to deliver 10 fps the usage would only be like 1%.

P.S.: I don't know why an older version might be faster. This should have been improved with the connector 1.5.0.

This is solved from version 7 on.

Zitat von artofcharly

And another question =) Which codec I should select? =)

YUV 420 is normally used for internet video. It is the default color subsampling format for h264 video.

Just expect huge files, but also a very pleasant scrubbing in the premiere timeline.

If you're only using 8 bit per channel (24 bit or 32 bit) then the cheaper one is okay.

To your other question: I can't answer this. Maybe the Adobe support / forum can help you with this. Voukoder gets into the process AFTER the NLE has rendered the frames.

The reason is most likely your frame width and / or height are not a multiple of 4. To be on the safe side always use a multiple of 8 for the width and a multiple of 4 for the height.

Well, this is not a voukoder bug or issue, but ... Ok. I don't see any correlation between the spikes and the projects timeline. The project itself is rather simple and uses not many effects and special transitions. I guess it is either premiere or the system itself.

I noticed you are using Bandicam for recording your screen to mp4 (NVENC). I did the same for game recording a loooong while ago (I love bandicam for screen recording). Did you ever try to record to AVI using the MagicYUV codec? It is designed to be mathematically lossless and extreme fast encoding and decoding. I loved working with that. Would be interesting to see if there is any difference. H264 was not designed to be an intermediate codec.

LanMinchang reports on twitter:

Zitat

There is a bug. When installing, the package will not replace existing file, such as voukoderplug.dll , voukoder.dll and voukoder.tlb.

Does that happen to anybody else?

If this is the case, please run the installer with this command line using the windows command prompt. (Replace that values in brackets with the actual filenames of course)

msiexec /i <path_to_msi> /L*V <path_to_log>

And share that logfile here.

fifonik Don't worry. I'm not going to change anything in this matter again as both fractions are happy now.

I don't think it's the audio filters. To me it seems your system is sometimes too busy / stalling.

[09:32:49] Frame #1277: vRender: 496 us, vProcess: 2 us, vEncoding: 7666 us, aRender: 162 us, aEncoding: 9 us, Latency: 8345 us
[09:32:49] Frame #1278: vRender: 17 us, vProcess: 4 us, vEncoding: 8207 us, aRender: 161 us, aEncoding: 734 us, Latency: 9135 us
[09:32:53] Frame #1279: vRender: 3814635 us, vProcess: 4 us, vEncoding: 683 us, aRender: 210 us, aEncoding: 1013 us, Latency: 3816571 us
[09:32:53] Frame #1280: vRender: 10 us, vProcess: 3 us, vEncoding: 584 us, aRender: 188 us, aEncoding: 11 us, Latency: 807 us
[09:32:53] Frame #1281: vRender: 1026 us, vProcess: 2 us, vEncoding: 5962 us, aRender: 148 us, aEncoding: 576 us, Latency: 7723 us
[09:32:53] Frame #1282: vRender: 11 us, vProcess: 3 us, vEncoding: 7750 us, aRender: 147 us, aEncoding: 849 us, Latency: 8769 us
[09:32:53] Frame #1283: vRender: 15 us, vProcess: 4 us, vEncoding: 7507 us, aRender: 190 us, aEncoding: 687 us, Latency: 8413 us

Premiere caused a delay of almost 4s to render one single frame.