Probably because bluray compatibility setting!

And by the way, Stamper, if you're still willing to get a Zappiti player, I encourage you to stick with black bars included if you consider using PGS subtitles with your videos so that they are properly displayed. With cropped black bars, the PGS will look squished.

Well, the black bars should take a tiny fraction of the bitrate, so I'd retain them, for compatibility sake.

OK will do, thanks!

Refresh my memory, are we currently opening or closing our GOPs? I remeber there was a debate.

Struggling with an x264 encoded project of mine, where the audio don't want to sync - even when applying a certain delay, it's in sync here but not there - I discovered that the encode is different from the source, using a variable frame rate!

This using (a previous than later version) Simple x264/x265 Launcher; said that, I don't know if it's a bug limited to the version I used, but just to be safe, I propose to add the latter settings:


(of course fps values depends on the source)

Two settings that will avoid any problems.

Opinions?

(2019-08-08, 04:12 AM)spoRv Wrote:

IMPORTANT!

Struggling with an x264 encoded project of mine, where the audio don't want to sync - even when applying a certain delay, it's in sync here but not there - I discovered that the encode is different from the source, using a variable frame rate!

This using (a previous than later version) Simple x264/x265 Launcher; said that, I don't know if it's a bug limited to the version I used, but just to be safe, I propose to add the latter settings:

Code:

--force-cfr --fps 24000/1001

(of course fps values depends on the source)

Two settings that will avoid any problems.

Opinions?

Interesting. Did this solve your problem? I don't think I've had this problem with x264 yet.

On a side note, when dealing with VFR sources, I believe you can force ffvideosource to convert to a target framerate with fpsnum and fpsden parameters.

(2019-08-08, 05:16 AM)TomArrow Wrote: Interesting. Did this solve your problem? I don't think I've had this problem with x264 yet.

On a side note, when dealing with VFR sources, I believe you can force ffvideosource to convert to a target framerate with fpsnum and fpsden parameters.

I just downloaded the latest version, and added the two settings written before; encoding now!

(2019-08-08, 04:12 AM)spoRv Wrote: Opinions?

The only occasions on which I've seen people end up with VFR encodings unintentionally are when they using GUIs and something has gone wrong with the settings.  I've never had x264 deliver an unrequested VFR from a CLI encoding, and I've done many encodings over the years, all of which I've checked by running the output through eac3to, which is very good at flagging up VFR encodes (and can correct them if needed).

I don't know if this is the place to ask or not, so apologies if not. I'm trying to work out why a file ripped from a compliant Blu-ray is no longer compliant after trimming, and I assume it's because of the trimming, but I don't know for sure.

I started off with AVC video taken from a compliant BD-25, but wanted to remove frames without re-encoding. So, I split the file into 3, and joined parts 1 and 3, and it plays back without issues in various players on PC (this was done in MKVToolNix/mkvmerge). However, after muxing to BD folders in tsMuxeR and burning in ImgBurn, it's a slideshow on my Blu-ray player (again, fine on PC). Evidently, I've done something to make it no longer BD compliant.

I'm guessing it's either my tsMuxeR settings or the splitting and re-joining of the file, but I don't know which. For instance, I don't know whether I should have "continually insert SPS/PPS" on or off; same goes for "insert SEI and VUI data if absent" vs always rebuilding or never rebuilding.

Anybody got any ideas? I've got two coasters now, so I've got a BD-RE en route to test with so I don't keep making more, but it'd be good to understand what I've done and how to fix it, if I even can fix it. One solution could be to just not trim the frames out of the video track at all, but that isn't ideal because I'm using audio sources that don't match up with one of the logos at the start (hence just removing the logo altogether).