OK

Slipstream for DGDemux/DGDemuxGUI build 74:

* Fixed regression in detection of the video PIDs for build 73->74. hubblec4

Fixed. Please re-download 74.

Thanks I should I have noticed that. Squirrel tunnel vision. Will fix straightaway.

Sorry not yet implemented.

You are welcome. Released as build 74. Marking resolved.

DGDemux/DGDemuxGUI 74:

* Fix 3D plane numbering when there are hidden PGS streams. von Suppé

https://rationalqm.us/dgdemux/binaries

Thank you for the update.

Thank you for your testing. Hidden PGS don't have to be hidden in other playlists. As an example here, the Japanese PGS isn't hidden in both playlist 00099 and 00101. Where it does show a plane value: 1. Since these playlists refer to the same m2ts/SSIF, maybe it's a handy idea to retrieve values fr...

According to my understanding, to try to assign a plane number to a hidden stream requires parsing the MVC SEI and doing some heuristics, which I currently do not do. So I will report the plane for hidden streams as 255, consistent with tsMuxer. Please test this and let me know if there are any issu...

OK, the problem is that the list of plane numbers in the STN_table_SS excludes hidden PGS tracks, whereas I have been including them. Should be an easy fix. Now, regarding the hidden streams, tsMuxer shows no plane for them, while BD3D2MK3D shows them with plane 1. I plan to follow tsMuxer in this r...

Emulgator wrote: ↑

Mon May 27, 2024 11:44 am

1961-1962.

Correct, see 13:17 in the video.

I cobbled up a 00049.clpi but I'm going to need the full disk. Please provide a link to purchase it or offer to provide it under fair use. If you agree to the latter, can send FTP details, etc. in PM.

Thank you. Please provide 00049.clpi from the CLIPINF folder.

Yet the 3D trilogy I aforementioned does show different in DGDemux GUI. Where both BD3D2MK3D and tsMuxer show 3d-plane 2 for the english PGS, DGDemux shows plane 3. Is it possible both tsMuxer and BD3D2MK3D are wrong here? I you'd like I can upload some key elements out of the ISOs. Anything is pos...

Maybe the warning text could be changed to be more clear about what is happening.

Marking resolved. We can re-open it if needed.

It seems that you are perhaps misinformed that tsMuxer has ironed out its issues. It appears to me (with Prometheus_3D) to still be assuming the planes are in PID order. My plane numbers are parsed from the MPLS according to spec and they agree with BD3D2MK3D, which rolz has meticulously researched ...

Ah, that is music to my ears. Thank you for the update.

That is not good. I'll test it with the 3D disks I have on hand. What is the TSMuxerGUI version?

Thank you, Frankaboy for helping out. I've nothing to add to that.

Looks like a hit and run. Marking resolved.

I've got ranges implemented. Just gonna check some corner cases and error checking and then I'll make a test release.

The DGBob() filter with a thresh parameter is ancient. It is from 2003! I strongly suggest that you move to a later bobbing filter. I have DGBob() and PVBob() integrated into DGSource() for example. Nevertheless, talking about old DGBob()... Back then basic filters were just starting to appear gener...