Beiträge von Joe24

Zitat von Steve Rhoden (Hentys)

I am an expert....

Not in other people's affairs, you're not.

Zitat von Steve Rhoden (Hentys)

Trolling, constantly looking for an argument and a fight by jumping into other user's posts that does not concern you.....

Here we have the OP thanking the author for his work. A conversation which in no way involved you. You inserted yourself and your views on how the OP is doing everything wrong.

So, yeah... trolling. Which is what you've been doing to multiple people in multiple forums, such as this one...

If you don't understand why people are doing things a certain way, the intelligent approach would be to learn more about their specific use-case before opening your mouth. If they even want your help, which is unlikely.

If you've got a workflow that works for you, that's great! So does everybody else.

Zitat von Steve Rhoden (Hentys)

"what you should have initially done"

Suddenly you're an expert in everybody else's affairs?

Zitat von Steve Rhoden (Hentys)

What does my response to someone else have to do with you Joe24 ?

I was not talking to you!

I was addressing Jorge Luis on using old software, which of course will ultimately lead to errors and limitations when used in conjunction with newer technology and modern coding.

If he wants to use old software, "ultimately" that's none of your business. I also use Vegas 12 for some things, despite owning 15 and 20. Newer is not necessarily better, and 20 is actually a real PITA for some things. Neither of us owe you an explanation of our rationale for using "old" software. Nor do the other people whom you've attempted to 'convert' in the other forums. Mind your own business.

Zitat von Steve Rhoden (Hentys)

Why on earth are you still using those exceedingly old tools...?

Why would it matter to you what he does with his own property?

Zitat von Jorge Luis

Will it work on after effects cs6? And also premier cs6? How about vegas pro 12?

Somebody hasn't read the thread...

Zitat von Vouk

Joe24 Do you have that error message in the log file again?

No, the error message is not present in the 13.2beta3 logs.

Would a byte-compare of the files rendered by working/non-working versions of Voukoder be useful? The problem might be something at the very beginning of the file, because the clip posted above has zero video-motion throughout. Something breaks immediately at the start of playback, and stays broken.

I've attached 2 files and their logs below. Absolutely nothing is different between the 2 files except the Voukoder version. The 13.0.2 file plays normally, the 13.2beta3 file gives a still picture and plays audio only.

test files.zip

I also tried the 32-bit version of VLC, and a beta version v4.0. No change.

I'm sorry to say that the problem still exists, although that message is no longer present in the log.

My settings are this (although as I mentioned, I've tried several other known working presets, both h.264 and h.265):

Software: Vegas 20.0 build 411, Vegas 15.0 build 416, Voukoder 13.1 through 13.2beta3, Windows 10 version 22H2 build 19045.3086.

Audio: AC3 96kbps, no boxes checked in Voukoder settings, 48 kHz 16-bit Vegas project output.

Video: 1080p29.97, 8-bit (full range), Nvidia NVENC on RTX 3060 Ti, drivers v536.23 DCH patched with keylase.

Voukoder parameters: b=2500000 bluray-compat=1 bufsize=2500000 coder=cabac cq=0 g=48 gpu=0 level=4 maxrate=5000000 multipass=disabled preset=p7 profile=high rc=vbr rc-lookahead=20 tune=hq

Player: VLC 3.0.18 64-bit

My (older server) processors do not have Intel QSV, although I doubt that's the problem.

On a hunch, I rendered the same 10-second video project as above, using every available Voukoder audio format. The only thing that I changed was the audio format; video settings are identical to the clip posted above. All tests done with Vegas Pro 20.0 / Voukoder 13.2beta1.

Results varied widely, and none worked properly except Uncompressed PCM. All PCM bit depths work, 16/24/32-bit.

Rendering using AAC, AC3, MP3, EAC-3 (DD+), and Vorbis yields files where the video does not move on the screen, although the audio plays.

ALAC format gives a video that plays, but no audio except the last 1 second.

Dolby TrueHD crashes Vegas after 39 rendered frames. See screenshot.

DTS yields a 1m50s file (remember the project is only 10s) that will never stop playing in VLC. Video plays, but picture stops moving at 10s. No audio except brief blips at ~6.5s and ~9.5s.

FLAC yields a 1m50s file. Video plays but picture stops moving at 10s. Brief (~0.5s) audio at beginning of track, then no audio until last 10s of file (i.e., audio plays from about 1m40s to 1m50s).

MP2 audio format gives a video that plays, but no audio except the last 2 seconds.

WAVPACK format gives a video that plays, but no audio except the last 1 second.

Log files: Voukoder logs 20230710.zip

Update: All of the above formats tested and working properly in Voukoder 13.0.2 except Dolby TrueHD which still crashes Vegas, and DTS which produces a 10s (not 1m50s as above) infinitely-playing track where the video stops after 10s and with no audio except brief blips from time to time.

Something obviously changed somewhere. Hardware, Vegas, and drivers have not changed, so the problem lies elsewhere.

Is there a setting in the new FFmpeg version that uses a different syntax or has a different default? Or perhaps there's a new feature which has a default setting that breaks everything?

The video clip (above) uses a custom preset that is Blu-ray compatible, but I have not tested BD-compatibility of renders using Voukoder 13.1+. I'm away from home at the moment, and unable to do so. Where I'm going with this is: Is there a way to test what h.264 profile/level is actually being used in the encoded file?

The fact that this affects both h.264 and h.265 is interesting. Whatever is broken is evidently shared by both formats.

I noticed in the unplayable file logs that there are numerous messages like this:

FFmpeg: Delay between the first packet and last packet in the muxing queue is 10016000 > 10000000: forcing output

These messages do not appear in the logs of the playable files. Did FFmpeg change bit resolution of any arguments?

Both VLC 3.0.18 64-bit and Windows 10 Media Player. Both programs will play video encoded by Voukoder 13.0.2, and both programs refuse to play video from Voukoder 13.1 and 13.2beta1.

bicycling short - Voukoder 13.2beta1.zip

Zitat von Vouk

Does this version fix the issue?

https://github.com/Vouk/voukoder/…r-13.2beta1.msi

No.

bicycling temp - voukoder 13.2beta1.log.txt

Confirmed the issue. All renders that I tried, using my known good presets, produced unplayable video files. My presets all use NVENC in h.264 and h.265 formats, various settings, various resolutions and framerates. Sound plays okay, but there is only a still image throughout. Sometimes you get a file which will produce a new still image every time you seek, but picture never moves.

The problem seems limited to Voukoder 13.1, and affects both my Vegas Pro versions 15.0 and 20.0. I didn't try Vegas Pro 12.0, but presumably the same. Rolling back to Voukoder 13.0.2 fixed the problem. See logs below. If you want me to upload video files, I might be able to. Not sure what the site's download limit is . . .

bicycling temp - non-functional Vegas 15.0 - connector 1.5.0 - Voukoder 13.1.log.txt

bicycling temp - non-functional Vegas 20.0 - connector 1.6.0 - Voukoder 13.1.log.txt

bicycling temp - working Vegas 15.0 - connector 1.5.0 - Voukoder 13.0.log.txt

bicycling temp - working Vegas 20.0 - connector 1.6.0 - Voukoder 13.0.log.txt

Looking forward to the Vegas version...

Zitat von vayore

I have to change it in the project settings right?

In Vegas' project settings, yes.

Zitat von Bowtie

Confused little bit here. So I can't use 13 if my driver is lower version than that? Or just SDK 12 won't be used? I'm still running Windows 7

Why don't you go experiment on your own? You seem good at solo activities.

What are your output resolution and framerate?

Log file?

Does rendering the same project without using Voukoder produce a playable file?

To remove the session limit on Nvidia GeForce cards, search for the driver patch by keylase on GitHub. NB: You will have to re-apply the patch every time you update drivers or change graphics cards.