cubicibo
commented
6 months ago Hi, Interesting issue, thanks for filing it up. There are two problems:
#.1 SUP files problems
- DGDemux SUP file has all decoding timestamps (DTS) set to zero. The demuxer should NOT discard the DTS value. A stream without DTS will have compatibility issues on old decoders like the PS3. Moreover, DTS is needed to convert back to PES+MUI. I would suggest you to report this issue to DGDemux support forum.
- tsMuxer SUP uses a different default values for DTS than Scenarist, hence Scenarist complains.
To fix DGDemux or tsMuxer SUPs, you can use this script. You must have SUPer python package installed. It will create a new file "_fixed" in the same folder.
Usage: python3 script.py path_to_file.sup:
from SUPer.render2 import DSNode
from SUPer.pgraphics import PGObjectBuffer
from SUPer import SUPFile
from argparse import ArgumentParser
from pathlib import Path
ap = ArgumentParser()
ap.add_argument('supfile')
fp = Path(ap.parse_args().supfile)
assert fp.exists(), "Input SUP file does not exist."
sup = SUPFile(fp)
output = open(Path.joinpath(fp.parent, fp.stem + "_fixed" + fp.suffix), 'wb')
try:
for epoch in sup.gen_epochs():
buffer = PGObjectBuffer()
for ds in epoch:
DSNode.apply_pts_dts(ds, DSNode.set_pts_dts_sc(ds, buffer, epoch[0].wds))
output.write(bytes(ds))
except Exception as e:
print(f"Critical error while fixing stream: {e}")
output.close()Both SUP files will be identical once you execute this script. From there, you can use ScenariStream.
I don't think there is anything to fix in ScenariStream. The issue originates from the muxers/demuxers. A conversion utility should not fix the files on the fly. I can only suggest you to use this script to "fix" the files.
#.2 MUI Problem (??) Now, if you convert the "_fixed" file, you will see that MUI is nearly identical everywhere except for a few bytes every few lines. I have absolutely no idea why the KITe file is like this. Here's a test:
- Import _fixed PES+MUI in Scenarist
- Encode -> Build/Rebuild PES data (please try both operations)
- Please do the same for KITe PES+MUI file. Import then Build+Rebuild.
I expect that Scenarist will change the KITe data but not the tsMuxer data. To me, it seems like KITe output is incorrect, or the Blu-ray itself contains this oddity. tsMuxer_fixed.zip
Alllen
Hi cubicibo! I extracted the subtitle file (.SUP) from the Blu-ray Disc stream using tsmuxer and then converted it to PES+MUI format using ScenariStream, and there is an error occurred when I try to drag the resulting PES into Scenarist. I tried using DGDmuxer for demuxing and got the same result. But, the PES+MUI I generated with KITe demuxing can be successfully dragged into Scenarist, I checked them with hash software and found that the hash value of the PES file converted by ScenariStream is exactly the same as that of the PES file generated by KITe, while the MUI file is different. Is the problem with the new MUI file, is it that it doesn't conform to the Scenarist file spec? I've uploaded the test sample to the attach, please check it out.
tsMuxer.zip KITe demux.zip DGDemux.zip