Frame Mismatch with wrong assumption about staxrip HOT 9 CLOSED

so far one time issue

from staxrip.

_new_staxrip.log

from staxrip.

This has nothing to do with Dolby Vision or so. 🤔

The source has 36930 frames, the target has 36930 frames, the encoder encodes 36930 frames, so I'm curious where the 73860 frames come from. 😕

I will try to investigate it, but haven't had such an issue before, so we will see...

The result should be absolutely valid, the only issue you should have is that StaxRip aborted with this error message. So if you want you can disable it in Project » Options » Misc so this warning will appear in the log file, but won't abort the processing anymore.

DoVi metadata has been cropped by DoVi_Scripts.bat from here

Is there a reason why you do that, when StaxRip makes everything for you already?

from staxrip.

DoVi metadata has been cropped by DoVi_Scripts.bat from here

Is there a reason why you do that, when StaxRip makes everything for you already?

i get used to do that....

from staxrip.

i get used to do that....

No problem with that in general, but be aware that you might potentially create broken results in case of specific conditions like on your sample above.

from staxrip.

this is first time when i had this issue... My workflow for dovi encode worked even before you where added dovi extract ability...

from staxrip.

That's what I mean.
But I had enough discussions about the right handling, for example #1280 and #1304, and created a guide with all the necessary information. If you don't care, it's okay for me.

Nevertheless I try to reproduce this issue, but was not able so far. 😕

from staxrip.

so pospond this.. if it will happen again i will try do everything by staxrip

from staxrip.

I still can't reproduce it, but I have added a bit of code to make the check a bit more robust.

I will close this issue for now, feel free to reopen it when you encounter this issue again - again with a log file, please.

from staxrip.