Beiträge von Vouk

Here are the mp4 atoms of both files:

So there are really differences with handling the audio (ac-3) stream.

https://twitter.com/LordVouk/status/1679043325980995586

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

Does anybody have this issue with Adobe Premiere? I didn't experience it there.

Alright. I stepped through the interleaving muxing process manually: It looks okay.

I increased that muxing buffer from 10,000,000 to 9,223,372,036,854,775,807. I hope that's big enough (it's actually the maximum value).

A one hour test export with premiere QSV h264/aac doesn't show the error message anymore. The file plays in both MPC_HC and VLC. It doesn't play with Windows Media Player, but ... Windows Media Player doesn't play files created with Premieres built-in h264 encoder either. So... forget that crappy Windows Player.

If the error is still present: Please tell me exactly how to reproduce it! And with which player incl. version number it is not playable with.

Is this version any better?

Seems it's die Video/Audio interleaved muxing logic. I need to debug this step by step.

Seems its exactly the same issue Joe has. I use MPC-HC too. Seems it can handle and correct broken files on the fly better than other players.

I guess it's a VEGAS only issue?

Thanks for testing this. Does anybody know if this is only happening with VEGAS Pro or with other NLEs too?

Thanks. I'll investigate this.

The strange thing is: There are no difference in the voukoder-code between those versions. I Just updated the FFmpeg libs.

What player do you try to play the files with? esp. some hardware players are only capable to play encoded files up to a certain "level" (i.e. "4.2").

It's playing perfectly here.

What player do you use?

Can you render me a short non-playable clip and send it to me? I just need a couple of frames.

Does this version fix the issue?

https://github.com/Vouk/voukoder/releases/download/13.2beta1/voukoder-13.2beta1.msi

The topic speaks for itself I guess.

Working von VEGAS Pro support right now!

Thanks. I'll investigate this on the weekend.

Regarding the 3. point: Can you open the scene and click on the Test run button and copy the log in here?

P.S.: It's a good practice to test your scene first before you are actually using it in your NLE.

Can you enable low level debugging in the settings and share the logfile again?

Did anyone of you test it already? What are your impressions?

The solution is the same as with message #3 above.