Beiträge von fifonik

Here is VP22 demo project (no big files inside, ~300KB):

VoukoderPro - VP - Audio TrimEnd.zip

Shared with Dropbox

www.dropbox.com

Steps I used to create the project:

1. Open VP22 and create new project 640x480 (smaller frame -- faster render), framerate 59.940 (all my footage is in this framerate), audio frequency 48,000 kHz, ruler 'Time & Frames'. In menu -- Options 'Quantize o Frame' | 'Enable'
2. Drop the audio file (in archive) onto audio track and move it to very beginning
3. Move cursor to position 00:00:02.30 (2 sec and 30 frames, this is close to the end of the audio sample) and trim it on the right to make its length alligned with video framerate
4. Select the autio fragment, Ctrl+C, move cursor to position 00:00:02.30 and Ctrl+V three times -- so 4 autio fragments in total one after another without gaps with total duration ~10 seconds
5. Select these 4 fragments, RMB | Group | Create Group
6. Select the Group, CTRL+C, move cursor after the group (without gap) and press Ctrl+V multiple times so the total duration became ~3 minutes or more. I tried to create shorter project (2 minutes) and did not have the issue.
7. Drop Media Generator 'Text & Titles' at the beginning of video track above the audio track and move its right edge to align with audio end
8. This is the project that was saved and attached
9. Render with Voukoder Legacy and Voukoder Pro

10. Drop rendered files on tracks below and move to very beginning, then zoom in to the very end and notice the Voukoder Pro audio stream finishing earlier:

    

With 2S result is the same.

P.S. Sorry, did not reply as was busy with other stuff.

I've tried the 1.98912S and it gives the same results as 0.048

Re-testing everything.

Ignore my previous messages about black frames at the beginning and at the end. I failed during experiments.
However, there is still premature end of audio when I rendered all the project with adelay 1.98912S:

And I do not see any delay here at all.

I've just tried your suggestion:

Tested it with small fragment and unfortunately, it does not work as I expected.
With adelay 2131.2S the audio offset is way too big (the the bottom track).
With adelay 0.044 (without S) the audio looks in sync, however in this case video stream becoming longer. A few black frames were added at the very beginning of the video stream and a lot of frames were added at the very end of the stream.

Audio stream is also become longer with some silence in it.

Thanks for reply. I will give it a try (need to understand how to do whan you suggested) and report back.
You mentioned 1958.04. If I understand correctly, this is for 44.1kHz project. For 48kHz project I should use 0.0444 * 48000 = 2131.2. Is it correct?

Thanks.

I'm still evaluating VoukoderPro for Vegas 22 and noticed premature audio stream end in rendered file.
The same Vegas Pro project was rendered twice: with Voukoder Legacy (13.4.1 + connector 1.0.0) and Voukoder Pro (2.0.10).
Then I've put rendered files into the same project at tracks below and here what I see at the very end of these tracks:



MediaInfo tells similar story. Rendered with Voukoder Pro:

Rendered with Voukoder Legacy:

Any suggestions how this can be fixed?
Or, if this is a bug, what other details should I provide so it can be fixed?

Thanks.

P.S. You may also notice one frame offset in audio for both Voukoder renders. This is known issue that I'm living with when rendering from Vegas with Voukoder and it was discussed in the forum already.

P.P.S. You may notice bigger video stream size for legacy render on MediaInfo. That was final render so I added a bit of sharpness on the whole video track so higher bitrate with the same CRF value. No other changes were made in the project.

I've just played a little bit & encoded one file from Vegas Pro 22 and Voukoder Pro logs on drive C: are already 30MB+.
Most content are:

2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 24576
2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 25600
2025-03-26 19:24:47 (trace)    [FFmpeg:0] frame=   0 QP=22.82 NAL=3 Slice:I Poc:0   I:8160 P:0    SKIP:0    size=200798 bytes
2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 0
2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 26624
2025-03-26 19:24:47 (trace)    [FFmpeg:0] frame=   1 QP=22.40 NAL=2 Slice:P Poc:2   I:470  P:6493 SKIP:1197 size=95777 bytes
2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 1
2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 27648
2025-03-26 19:24:47 (trace)    [FFmpeg:0] frame=   2 QP=22.47 NAL=2 Slice:P Poc:4   I:121  P:6406 SKIP:1633 size=78706 bytes
2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 2
2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 28672
2025-03-26 19:24:47 (trace)    [FFmpeg:0] frame=   3 QP=22.86 NAL=2 Slice:P Poc:6   I:34   P:6096 SKIP:2030 size=58430 bytes
2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 3
2025-03-26 19:24:47 (debug)    [OutputNode.cpp:327] Muxing packet with pts 29696
2025-03-26 19:24:47 (trace)    [FFmpeg:0] frame=   4 QP=22.93 NAL=2 Slice:P Poc:8   I:27   P:6041 SKIP:2092 size=56022 bytes

Confirming that after upgrading ffmpeg from version 7.1 release to version 7.1.1 release the option `"profile": "high"` is not causing issues any longer.

Thanks.

Thanks, will try to update to the most recent release version (7.1.1)

Not the most recent one. 7.1 gyan's full shared build

I tried the lowercased and the outcome is exactly the same.

Checked log and fixed the issue. Thanks.

P.S The issue was caused by option "profile: high" that I added. Not sure why it does not like the option:

2025-03-26 19:23:19 (info)    [EncoderNode.cpp:345] Opening video encoder plugin 'libx264' with params '{"rc":0,"crf":18,"g":12,"bf":0,"preset":"Slow","profile":"High"}'
2025-03-26 19:23:19 (trace)    [FFmpeg:0] Undefined constant or missing '(' in 'High'
2025-03-26 19:23:19 (trace)    [FFmpeg:0] Unable to parse option value "High"
2025-03-26 19:23:19 (trace)    [FFmpeg:0] Error setting option profile to value High.
2025-03-26 19:23:19 (error)    [EncoderNode.cpp:354] Opening the encoder plugin failed with error code: -22

I'm having the same issue with Vegas Pro 22.

Performance test works (I assume this means that FFMpeg that in %PATH% works fine).
However, when rendering I'm getting this error:

My Voukoder Pro settings:

How I can investigate what is cousing the issue?
Any logs available?

Thanks.

I'm using free voukoder with Vegas Pro. Thanks alot for the program.
Just found that free version is not supported any longer so thinking about buying the Pro license.

However, I have a few questions (have not found answers in FAQ, but they may be already answered in forum. Sorry if I repeat).

1. Is it possible to transfer a license from one PC to another (I'm upgrading my PC periodically). Is it complicated process?

2. Do you have plans to support old major PRO version when you release a new one? Like releasing new connectors for new versions of NLE. Asking as new major version may contain issues or be completely uncompatible with NLE that works fine with older version.

3. License mentioned as perpetual for major version number. How often are you planning to increase major version number? I mean if you will increase major version number every month/year and stop supporting older PRO versions, so technically it would be similar to subscription

4. Can I install and use Voukoder Pro aside with free Voukoder in the same NLE? I'm a bit afraid to install Pro trial as it might ruin my existing encoding profiles.

Thanks.

Zitat von rsmith02

Vegas shows the file as it is, so the preview is correct

Well, it depend on what do you mean correct.

Technically speaking you are right and it is correct as 235 is shown in preview not as pure white.

However, after rendering to mp4 235 will be shown as pure white. "Hello video levels".

So people sees in preview not what they will get after render and so many complains. I'm not complaining, I perfectly understand what is going on and why and I completely happy with it.

This is why I called it "wrong".

My only concern was a new voukoder's default option that will try to fix this.

I asked that if such option implemented in voukoder -- it should be off by default so voukoder behaves the same way as other VP's encoders.

P.S. Sure, I know about the new pixel format.

Vegas shows wrong preview. This is "known feature". There is a plugin exists that can be used to "fix" that. If preview is on separate monitor, everything can be configured to be displayed correctly.

So if you decide to add anything related to the "issue" in Voukoder, could you please do not make it "default"?

Thanks.

I'm not noticing any delays in VP17 with Voukoder, so not sure what OP is talking about.

It is possible that something changed in VP18 that I do not have and it was fixed.

In VP, when I select any profile and click Apply I see the option opencl=1 (with "Show advanced option" checkbox ticked).

Just curious, how can I remove/disable it?

Thanks.

P.S. In profiles created with earlier versions of connector do not have the option.

Any chance the -itsofffset option will be implemented one day?

I'm aware about another thread related to the issue and that you've already made it much better in version 0.7.1.

However, I'm forced to disable so4compoundplug in VP15-17 as it has issues with my 5.1 sources so I still have 1 frame audio shift

Thanks.

5.1 audio works in my tests now. MediaInfo 20.03 reported 6 channels as for source.