I’ve successfully created pgs subs that contain the original reel change markers for 4k83. This allows you to see the original reel change markers for projects that have had them removed (v1.2 and up).
That’s a really cool, creative use of subtitles. I just wanted to say that before I went on to the technical stuff.
I’ve only created a 2160p version for now but I notice when muxed into a 1080p file they scale down to the proper size and location.
CatBus is there any advantage to having native 1080p and 2160p pgs subs? The 2160p work in both.
The only difference is player compatibility. Most (all?) subtitles for commercial UHD video are 1080p, and I don’t know if there are any players (and I’m talking hardware players here) that simply don’t understand what a 2160p subtitle is – the detailed specs for UHD subtitles aren’t publicly available, AFAICT. Certainly some 2K-only players (regular Blu-ray hardware players) would balk at 2160p subs.
Also when I timecoded it I assumed the first frame would be at 0. The markers were one frame early. Is it the standard for the first frame to be 1 during playback?
Thanks for the tools which allowed me to do this.
I swear the timing of PGS subtitles was codified by my archnemesis. There are actually a lot of issues with this whole topic, but the short answer is you just do what works 😉
Just a side note but when rendering them it gave a warning that the duration for each was less than 500.5ms. I overcame this by adding a blank marker to the end of each set, otherwise the last marker displayed for around 500ms.
If you’re using BDSup2Sub, there’s a command line option (–minimum-time) to reduce the minimum display time.
https://github.com/mjuhasz/BDSup2Sub/wiki/Command-line-Interface