Joiner...Always goes to 25fps, not the 29.9fps with a two file join...WHY

[jmc]

It does always put the first file segment first and stopped changing the aspect ratios... thank goodness.

DEFAULT Program Stream Profile...

BUT with 2 normal DVD.MPG files (25fps and 29.97fps)
It ALWAYS recodes BOTH to 25fps. WHY?

And why does it recode BOTH files. I would expect it to recode the 29fps file and FFCopy the 25fps file...?
(doing what it is doing)

It would be wonderful if it looked at the first file as the "no change" mpg profile and recoded ONLY the second file.
But it recodes BOTH. (single files FFCopy, two files...Both recoded)

Please make sense of this for me. Thanks.

 

[Dan203]

When we output from the joiner we use a single output "graph" to process all the files as if they were one long file. If all the files match each other then they'll be output without recoding. But if there is a mismatch then everything has to be recoded so that they match in the final output. The reason we have to recode everything, even the files that match the output settings, is because a graph is setup like a chain. If there is a decoder/encoder in that chain then every frame passes through them. Same with the frame rate converter. If it's in the chain then every frame passes through it. Although in that case it's smart enough to only change frames that actually need it, all others are just passed through as-is. So your file that's already 25fps isn't actually being processed by the frame rate converter, it's just being passed along to the next filter in the chain.

We have discussed making the output graph more dynamic like you want but that presents it's own set of challenges. For example if you stitch together two streams that aren't quite the same, even if the macro specs are the same, it can cause playback issues in a lot of players. So even though both files appear to have the same resolution, frame rate and codec there are minor differences in the encoding that can cause major issues during playback. Recoding everything fixes that problem completely because all frames are exactly the same.

 

[jmc]

Thank you! Good to know.

Does not bode well for the thread that started me testing the joiner.
He wanted to exactly match the short file to the long file so no recoding on the 4.5GB long file.

Probably down to the fine details you mention that we can not see.

 

[Dan203]

If you do it ahead of time and recode the one file to match the other then it'll work. No guarantees it'll play, but we don't check all the fine details, so if the macros match we allow both files to just pass through.

 

[Danr]

This makes me think that a nice feature, for a future version, would be to create a "force recode" output profile that matches a particular source file. I'll discuss with Dan203 as he's the keeper of everything related to profiles.

 

[jmc]

If you do it ahead of time and recode the one file to match the other then it'll work. No guarantees it'll play, but we don't check all the fine details, so if the macros match we allow both files to just pass through.

Yes, that's exactly what he got. He was able to finally stop the recoding but has lots of "play the file" problems.

""https://videoredo.net/msgBoard/inde...g-to-join-files-needs-help.37709/#post-134473""

So sure hope it is possible for you to create Danr's future version "match the file" Profile!

Thanks all.

 

[tobyW]

Sure hope it is possible for you to create Danr's future version "match the file" Profile!

Me too, I would use it a lot!