BD Rebuilder Beta - Bug Reports Only

[MrVideo]

What is experience with rebuilded Dolby vision UHD ?
FYI, just so you know, there is no such word as "rebuilded." The word I think you want is "rebuilt." Though "repackage" may be a better word for the process.

[FilipeAmadeuO]

Not for me. It's huge change in scene where it jumps from Solo answering a question to an explosion and a body flying through the air (right at the chapter point). But there is no stutter in my playback.

I'm testing it on a standalone Sony UBP-X800 UHD-BD Player.
Ok. On my Oppo the transition is not as smooth as it was on the “original”. The others m2ts transitions are perfect.

[jdobbs]

Ok. On my Oppo the transition is not as smooth as it was on the “original”. The others m2ts transitions are perfect.It's possible the bitrate spiked (from the high action explosion scene) and the player had a buffer issue... just wild guessing though.

[FilipeAmadeuO]

It's possible the bitrate spiked (from the high action explosion scene) and the player had a buffer issue... just wild guessing though.
It´s possible but does not happen in the original UHD :)
Only in the "rebuilt" version (no change in video, audio neither subtitles)

[Ch3vr0n]

FYI, just so you know, there is no such word as "rebuilded." The word I think you want is "rebuilt." Though "repackage" may be a better word for the process.

looks like the grammar police is active again. Not everone is fluent in english

[gonca]

Guess there is such a word as rebuilded
https://www.dictionary.com/browse/rebuilded

https://www.google.com/search?client=firefox-b-d&q=rebuilded

[Acerjen]

I am still having playback problems with Solo: A Star Wars Story.
Same as before. It will hit the chapter points right at the transition from one M2TS file to the next and will pause and stay paused. I can chapter rewind and then chapter forward to the scene it just paused at and it will resume smooth playback till the next transition to the next M2TS file occurs and it stops and pauses again. On solo, once you get to chapter 9, the rest of the film is contained in a one large M2TS file, so no more pausing. And it does play all the way to the end of the credits like it is supposed to. I ran it through the newest version of BD Rebuilder on a new PC I built with a fresh installation of everything. If you have any ideas, please share. Attached are my logs and related files. Thanks. Later.

Acerjen

[jdobbs]

It´s possible but does not happen in the original UHD :)
Only in the "rebuilt" version (no change in video, audio neither subtitles)The original is on a disc that has a higher transfer rate.

[jdobbs]

I am still having playback problems with Solo: A Star Wars Story.
Same as before. It will hit the chapter points right at the transition from one M2TS file to the next and will pause and stay paused. I can chapter rewind and then chapter forward to the scene it just paused at and it will resume smooth playback till the next transition to the next M2TS file occurs and it stops and pauses again. On solo, once you get to chapter 9, the rest of the film is contained in a one large M2TS file, so no more pausing. And it does play all the way to the end of the credits like it is supposed to. I ran it through the newest version of BD Rebuilder on a new PC I built with a fresh installation of everything. If you have any ideas, please share. Attached are my logs and related files. Thanks. Later.

AcerjenDon't know what to say. That same disc works fine for me. What player are you using?

[Acerjen]

Don't know what to say. That same disc works fine for me. What player are you using?

Thanks for replying. I am using an Xbox One X.


Edit: I am curious as to what player you have? It might be worth investing in one if more and more rebuilt discs have problems playing on the Xbox One X. Thanks.

[Acerjen]

I am also having a problem with Star Trek: Beyond. The disc loads up and plays the Paramount trailer. At the end of the trailer (which is 23 sec long), the player pauses like it doesn't know where to go next. I can stop the playback but can not fast forward or bring up the menu. The strange thing is this disc works fine after running it through BD Rebuilder version 60.25 but has the wrong runtime (as was fixed in the new version). When I used BD Rebuilder 60.26, the above happens. I re-did it once more with 60.25 and it works but again, has the wrong runtime. I am curious if you made any changes in the new version that might account for this? I am at a loss to explain it?
Thanks. Later.

[FilipeAmadeuO]

It's possible the bitrate spiked (from the high action explosion scene) and the player had a buffer issue... just wild guessing though.
Both UHD img are on the same hard drive :)
So same hard drive and same Oppo player :)
It´s something else...

Another issue I found. I rebuilded Star Wars The last Jedi UHD which has Dolby vision and it crash when I fast forward at speed > 1x
Can you please test ?
Thanks

[Acerjen]

Both UHD img are on the same hard drive :)
So same hard drive and same Oppo player :)
It´s something else...

Another issue I found. I rebuilded Star Wars The last Jedi UHD which has Dolby vision and it crash when I fast forward at speed > 1x
Can you please test ?
Thanks

When you play Star Wars The Last Jedi, are you having any trouble as it hits the chapter points? I ask because it is a multi-part (meaning multi M2TS files) disc and is giving me trouble. Also, which Oppo player do you have? Thanks.

Acerjen

[FilipeAmadeuO]

When you play Star Wars The Last Jedi, are you having any trouble as it hits the chapter points? I ask because it is a multi-part (meaning multi M2TS files) disc and is giving me trouble. Also, which Oppo player do you have? Thanks.

Acerjen
The last Jedi main movie only have 2 m2ts. You re problem is on chapter point or transition between m2ts ?
Oppo UDP-203 clone

[cartman0208]

@Acerjen

I'm testing it on a standalone Sony UBP-X800 UHD-BD Player.

[MrVideo]

looks like the grammar police is active again. Not everone is fluent in english
One doesn't learn unless told about the mistake.

[MrVideo]

Guess there is such a word as rebuilded
https://www.dictionary.com/browse/rebuilded
Notice how "rebuilded" is marked with "archaic," meaning that it is no longer used. Therefore, best not to use it. I was never taught about rebuilded, probably for that reason.

[Acerjen]

The last Jedi main movie only have 2 m2ts. You re problem is on chapter point or transition between m2ts ?
Oppo UDP-203 clone

Transition between M2TS files. I am using an Xbox One X, so maybe it is the problem. Thanks. Later.

Acerjen

[gonca]

Notice how "rebuilded" is marked with "archaic," meaning that it is no longer used. Therefore, best not to use it. I was never taught about rebuilded, probably for that reason.

Yeah I noticed, but such a word still exists, whether it is archaic or not.
You stated that the word doesn't exist, not that it was archaic and shouldn't be used

[Emulgator]

And now lets expand a bit.
Rebuild -> Rebuilder -> Rebuildest !
Or should we say Reboilt ?

[MrVideo]

Yeah I noticed, but such a word still exists, whether it is archaic or not.
You stated that the word doesn't exist, not that it was archaic and shouldn't be used
If you have spell check turned on, you will find that "rebuilded" gets flagged as a misspelled word. In other words, it doesn't exist. :D :D

[gonca]

And spell check is never wrong, just like you :eek:
In case you missed it that was sarcasm, case is the word exists, even if archaic, (must exist to be archaic) and you are wrong.
Live with it
Just like thou is archaic, but it exists.
Just read the bible to see it used all over the place

[videoh]

read the bible Off to the gulag for you.

[MrVideo]

Off to the gulag for you.
Well said. :sly:

[gonca]

Off to the gulag for you.
Are you lucky gulag isn't defined as an archaic word, or MrVideo would be all over it about it not existing
I guess ancient history doesn't exist either, it is kinda archaic:p

[jdobbs]

I got this error with John Wick Chapter 3, this is a Lionsgate disc.

...
- Bitstream exception Unknown exception. It does not have to be! Please...
...I may have a solution for this. While the error is caused within TSMUXER, I may have found a workaround. Look for it in the next release.

[AmigaFuture]

FYI, just so you know, there is no such word as "rebuilded." The word I think you want is "rebuilt." Though "repackage" may be a better word for the process.

:goodpost:

looks like the grammar police is active again. Not everone is fluent in english

These replies help those. :)

[choirboy]

Love this program :)

I'm having an issue with CRF Encoding being greyed out?

https://i.imgur.com/uQuuhMh.jpg

My INI is as follows:

[Options]
VERSION=0.60.0.26
ENCODER=0
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=8032
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=2
AVCHD=1
REMOVE_WORKFILES=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
MOVIEONLY_TYPE=0
ALTCRF=22
ALT_TARGET=1024
ALT_CRF_TARGET=22800
ALTMETHOD=3
ALTAUTOCROP=0
[Paths]
SOURCE_PATH=E:\BLU-RAY - DVD\FULLDISC\DOLLS\
WORKING_PATH=E:\BLU-RAY - DVD\OUTPUT\

I installed all the versions on the start page and in the right order.
I have the latest BDRebuilder installed.

Can anyone help? Not sure why it is like this?

[cartman0208]

Can anyone help? Not sure why it is like this?

In "Setup" set the DECODER to DirectshowSource ...
If it's set to X264's internal LAVF, then Onepass CRF is disabled

[jdobbs]

For those who are trying to do a UHD movie-only backup from a multipart source... a word of advice. Don't. I discovered an issue in which my TSMUXER correction process isn't handling the corrective remux properly when the source is multipart and backup mode is movie-only.

Please note: BD-RB works fine for full backups or ALTERNATE output. Only movie-only mode is affected and only when the source is UHD and multipart.

Hopefully I'll get a fix out for the next release. Unfortunately, though, it doesn't going to be an easy fix. So it may take some time.

This UHD thing has become a nightmare. It's getting to the point that the exceptions to the rule are starting to outnumber the rules -- especially for anything related to the TSMUXER process.

[FilipeAmadeuO]

Hi jdobbs
Why not try to help improving tsmuxer now that source code is available ?
It would decrease the number of Bdrebuilder workarounds because of tsmuxer bugs...

[choirboy]

In "Setup" set the DECODER to DirectshowSource ...
If it's set to X264's internal LAVF, then Onepass CRF is disabled

:thanks:

[jdobbs]

Hi jdobbs
Why not try to help improving tsmuxer now that source code is available ?
It would decrease the number of Bdrebuilder workarounds because of tsmuxer bugs...Yeah, I've thought about it and looked at it a little. But I'm not sure anyone has even had a successful compile that results in a working EXE with it yet. So it's not as easy as you might think. Again I only had a quick look at the code, but it seems comments are pretty few and far between as well, making it harder for someone (other than the original author) to follow.

The main factor holding me back on that front, though, is that it would take time and effort to start working on it -- time that I'd have to pull from BD Rebuilder -- and I'd like to have UHD working reliably before I consider doing that.

[FilipeAmadeuO]

Yeah, I've thought about it and looked at it a little. But I'm not sure anyone has even had a successful compile that results in a working EXE with it yet. So it's not as easy as you might think. Again I only had a quick look at the code, but it seems comments are pretty few and far between as well, making it harder for someone (other than the original author) to follow.

The main factor holding me back on that front, though, is that it would take time and effort to start working on it -- time that I'd have to pull from BD Rebuilder -- and I'd like to have UHD working reliably before I consider doing that.
Building in 32 seems to be already working (still some bugs on 64 bits)
In my personal opinion you would the perfect match to improve tsmuxer because you are aware of most of the bugs/limitations. Of course it would take a lot of time to understand author code.
But it would help you a lot not to be always with workarounds on bdrebuilder ...

[Mark_Venture]

apparently I'm having an issue with using SupTitle...

[10/06/19] BD Rebuilder v0.60.26
[14:04:44] Source: X-MEN_DARK_PHOENIX_00800
- Input BD size: 26.77 GB
- Approximate total content: [01:53:56.412]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, Intact Audio
- Quality: High Quality (Default)
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:04:48] PHASE ONE, Encoding
- [14:04:48] Processing: VID_02960 (1 of 1)
- [14:04:48] Extracting A/V streams [VID_02960]
- [14:12:59] Reencoding video [VID_02960]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 163,910 frames
- [14:12:59] Reencoding: VID_02960, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.60.26
- Windows Version: 6.2 [9200]
- Working Path Free Space: 2,685.78GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[14:13:00] - Failed video encode, aborted

[Options]
VERSION=0.60.0.26
ENCODER=0
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=1
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
DECODER=3
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=1
NEROAAC=0
SUPTITLE=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
PRIORITY_CLASS=0
TARGET_SIZE=23500
MOVIEONLY_TYPE=11
ALTCRF=19
ALT_TARGET=8096
ALTMETHOD=0
ALTAUTOCROP=0
QUICK_EXTRAS=1
AUDIO_DRC=0
PGSTOSRT=0
ALT_CRF_TARGET=1024
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=0

[Paths]
SupTitlePath=C:\Program Files (x86)\AviSynth\plugins\SupTitle.dll
SOURCE_PATH=F:\VIDEO\BACKUP\X-MEN_DARK PHOENIX\
WORKING_PATH=F:\BLURAY-WORKING\
DGIndexNV=D:\BD_Rebuilder\dgdecnv\DGIndexNV.exe
DGDecNV=D:\BD_Rebuilder\dgdecnv\DGDecodeNV.dll


Lastcmd.txt.... "D:\BD_Rebuilder\tools\x264.exe" "F:\BLURAY-WORKING\WORKFILES\VID_02960.AVS" --preset medium --bluray-compat --b-pyramid none --weightp 1 --slow-firstpass --qpmin=0 --crf 19 --level 4.1 --qpfile "F:\BLURAY-WORKING\WORKFILES\VID_02960.CHP" --aud --nal-hrd vbr --pic-struct --vbv-bufsize 30000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 30000 --threads auto --slices 4 --thread-input --stats "F:\BLURAY-WORKING\WORKFILES\VID_02960.AVS.264.stats" --output "F:\BLURAY-WORKING\WORKFILES\VID_02960.AVS.264"


VID_02960.AVS
#Created by BD Rebuilder - v0.60.26
LoadPlugin("D:\BD_Rebuilder\dgdecnv\DGDecodeNV.dll")
DGSource("F:\BLURAY-WORKING\WORKFILES\VID_02960.DGI", fieldop=0)
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\SupTitle.dll")
SupTitle("F:\BLURAY-WORKING\WORKFILES\02960.track_9999.sup")
ConvertToYV12().AssumeFPS(24000,1001)

If I open a command prompt and re-run lastcmd.txt... I get...
avs [error]: System.IO.FileNotFoundException: Could not load file or assembly 'SupCore, Version=2.0.8.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

at SupTitle.{ctor}(SupTitle* , PClip* child, String filename, Boolean forcedOnly, Boolean swapCbCr, Boolean relocate, String relocOffset, IScriptEnvironment* env)
at SupTitle.Create(AVSValue* , AVSValue* args, Void* user_data, IScriptEnvironment* env)
(F:\BLURAY-WORKING\WORKFILES\VID_02960.AVS, line 5)
x264 [error]: could not open input file `F:\BLURAY-WORKING\WORKFILES\VID_02960.AVS'

Everything was working. I'm not sure when it stopped. I haven't touched my AviSynth folder. SupTitle.dll is still located in that path.

While I'm using BD Rebuilder v0.60.26, the issue also happened with v0.60.23. I'm not sure when it stopped working.

If I uncheck Use SupTitle in the setup menu, the re-build to MKV works fine.

[jdobbs]

I have updated the first post of this thread with a link to the most recent version (v0.60.27) of BD-RB. Changes for this release:- Created a workaround for a TSMUXER issue
that could result in "Bitstream exception
Unknown exception." on UHD sources.
- Implemented a strategy that speeds muxing
of UHD sources considerably by using a
short filler in TSMUXER rather than the
complete UHD source before BD-RB makes
M2TS corrections.
- Corrected an error in which multipart UHD
sources with Dolbyvision could fail during
rebuild (calling out a missing file).
- Corrected an error in which multipart UHD
sources would fail to mux properly when
MOVIE-ONLY output is selected.
- Other minor corrections and cosmetic fixes.Originally posted in the wrong thread. Thanks, Ch3vron, for pointing that out! mistake.

[FilipeAmadeuO]

Hi jdobbs
Using v0.60.27 (and previous versions) i have a problem with fast-forward at speed > 1x and fast-rewind at any speed on STAR WARS - THE LAST JEDI (Dolby vision title)
The fast-rewind simply does not work at any speed and fast-forward at speed > 1x moves the play to the next title.
Original version works ok on my Oppo UDP-203 player.
Also SOLO - STAR WARS STORY rebuilded version works ok on both fast-forward and back-forward (not dolby vision title).
Can you please check if it´s a dolby vision titles problem on fast-forward/fast-rewind ?

[jdobbs]

Hi jdobbs
Using v0.60.27 (and previous versions) i have a problem with fast-forward at speed > 1x and fast-rewind at any speed on STAR WARS - THE LAST JEDI (Dolby vision title)
The fast-rewind simply does not work at any speed and fast-forward at speed > 1x moves the play to the next title.
Original version works ok on my Oppo UDP-203 player.
Also SOLO - STAR WARS STORY rebuilded version works ok on both fast-forward and back-forward (not dolby vision title).
Can you please check if it´s a dolby vision titles problem on fast-forward/fast-rewind ?I'll try it and let you know what I find... but I'm pretty sure I've tested it with dolby vision titles and it worked.

[jdobbs]

Hi jdobbs
Using v0.60.27 (and previous versions) i have a problem with fast-forward at speed > 1x and fast-rewind at any speed on STAR WARS - THE LAST JEDI (Dolby vision title)
The fast-rewind simply does not work at any speed and fast-forward at speed > 1x moves the play to the next title.
Original version works ok on my Oppo UDP-203 player.
Also SOLO - STAR WARS STORY rebuilded version works ok on both fast-forward and back-forward (not dolby vision title).
Can you please check if it´s a dolby vision titles problem on fast-forward/fast-rewind ?Ok. I just tried it on a couple discs with dolby vision that I'd rebuilt and it works fine for me.

But...

Since my player doesn't support dolby vision, that may not mean there is no problem. A guess would be that my player simply ignores the dolby tracks and so it doesn't affect it.

The CLPI file has a table called the Characteristic Point Information (CPI). Within it are contained pointers to the video packets that are the beginning of accessible points used for fast forward/rewind and chapter skips. My guess is that there may be something I'm missing related to those points within the separate dolby stream.

I'll look at my CPI table and that of an original disc and see if I can catch anything that might stand out.

This UHD support has become a major pain in my ass.

[FilipeAmadeuO]

Ok. Excelent.
My oppo player in fact it supports dolby vision. I must say that i only tested one dolby vision disc (The last jedi) and it crashs on fast forward.

PS - I sugest you to buy a M9702 v3
It´s a oppo clone box and it plays every format you can image including isso/bmdv folder style of BD/UHD. Also is compatible with HDR+ and dolby vision :)

[Ch3vr0n]

He doesn't HAVE to buy anything. A 5 second google shows me that's around a $400 machine? Donations are scarce often barely covering costs to buy test disc for a specific problem. Now you're telling me jdobbs HAS to buy such a device? Why not buy it for him and ship it?

[SeeMoreDigital]

He doesn't HAVE to buy anything. A 5 second google shows me that's around a $400 machine?Oh wow... That's an over-priced device by at least $300 ;)

[FilipeAmadeuO]

He doesn't HAVE to buy anything. A 5 second google shows me that's around a $400 machine? Donations are scarce often barely covering costs to buy test disc for a specific problem. Now you're telling me jdobbs HAS to buy such a device? Why not buy it for him and ship it?
That was a sugestion. No need to be as agressive :)
The advantage of the player is that it´s the most compatible device avaiable so would help on testing.
I am sending a donation to help :)

[jdobbs]

Ok. Excelent.
My oppo player in fact it supports dolby vision. I must say that i only tested one dolby vision disc (The last jedi) and it crashs on fast forward.

PS - you have to buy a M9702 v3
It´s a oppo clone box and it plays every format you can image including isso/bmdv folder style of BD/UHD. Also is compatible with HDR+ and dolby vision :)I sent you a PM with a link to an experimental build of BD-RB. I'd like to see if it helps with your FF/REW issue. No guarantees, as I couldn't test it myself, I was just wondering if the changes might make the difference.

[FilipeAmadeuO]

I sent you a PM with a link to an experimental build of BD-RB. I'd like to see if it helps with your FF/REW issue. No guarantees, as I couldn't test it myself, I was just wondering if the changes might make the difference.
Tested and it´s much better.
Now the FF works perfect.
The REW works perfect at speeds > 2x. The REW at 1x and 2x i can see bitrate changing on oppo player but image is freezed.
You are on the right track :)

Can you just please test other issue on LAST JEDI.
At 00:02:05 in a scene transition i have another "non smooth transition".
The transition is when it moves from 00007.m2ts -> 00018.m2ts on the 00800.mpls.
So something is still not perfect on m2ts transitions...

[jdobbs]

Tested and it´s much better.
Now the FF works perfect.
The REW works perfect at speeds > 2x. The REW at 1x and 2x i can see bitrate changing on oppo player but image is freezed.
You are on the right track :)

Can you just please test other issue on LAST JEDI.
At 00:02:05 in a scene transition i have another "non smooth transition".
The transition is when it moves from 00007.m2ts -> 00018.m2ts on the 00800.mpls.
So something is still not perfect on m2ts transitions...I will probably never be able to do anything about that transition issue -- as I suspect it is your player rather than the mux/disc (since my player handles it without issue). I'll keep looking and see if anything looks odd. It might be related to maximum bitrate on BD-25/50 with UHD (based upon our prior discussion). Just guessing, though. You might try setting UHD_MAXRATE to a value lower than 45000 in your setup file just to see. Don't set it any lower than 15000 or higher than 60000 -- as those will cause it to default back to 45000.

Don't know what you mean by "other issue"... but I don't have LAST JEDI, so I'm not sure whether I could test it anyway.

[FilipeAmadeuO]

I will probably never be able to do anything about that transition issue -- as I suspect it is your player rather than the mux/disc (since my player handles it without issue). I'll keep looking and see if anything looks odd. It might be related to maximum bitrate on BD-25/50 with UHD (based upon our prior discussion). Just guessing, though. You might try setting UHD_MAXRATE to a value lower than 45000 in your setup file just to see. Don't set it any lower than 15000 or higher than 60000 -- as those will cause it to default back to 45000.

It can’t be anything related to max bitrate because I do not reencode the video. My only goal is to replace one of UHD subtitle by the Portuguese subtitle of the BD version.

There was a big improvement on previous version v.0.60.26 change:
- Corrected an error in which MPLS sequence end times could be incorrectly updated on UHD sources due to TSMUXER losing HEVC frames. This could cause stutter between M2TS files on multipart sources or early playback termination on singlepart sources.

So I believe it’s something still not fixed related to the same issue (clpi or mpls file or TSMUXER losing frames).
Is there any way I can do to check lost frames in the end or beginning of m2ts ?

[meadrocks]

I did Princess Mononoke, movie only, Alternative output, h265 encoder. mediainfo states the duration is 4 hours 21 minutes, yet the movie is only 2 hours 13 minutes. When I play it in vlc it states the movie is 4:21, yet when it finishes playing it at 2:13 stops playing, so there's not an additional 2 hours of silence.
This also happened on Sucker Punch Dir Cut, movie is 2 hours 7 minutes, yet mediainfo & vlc state the duration is 4 hours 9 minutes.

[AmigaFuture]

Can you just please test other issue on LAST JEDI.
At 00:02:05 in a scene transition i have another "non smooth transition".
The transition is when it moves from 00007.m2ts -> 00018.m2ts on the 00800.mpls.
So something is still not not right on m2ts transitions...

I will probably never be able to do anything about that transition issue -- as I suspect it is your player rather than the mux/disc (since my player handles it without issue).

I came across this problem with multiple M2TS files with my older LG Blu-ray player (with Hard Drive). I really noticed it when I bought my copy of 50 Shades of Grey..ripped and processed it...and there were transition errors that you're typing about. Once I found another good LG player, and Ch3vr0n helped me realize that Cinavia isn't used as much anymore...I decided to get a new one. That movie, plus others..all the transition errors are gone. For a bit, I was thinking JD really goofed in BD-RB. Nope.. So, I'm with JD..I betcha it's your player, too. Now I have a note on that player.."Don't play non-original movies before 2015 or so with this." with a description of why. The newer player supports SRTs much better and other features the other didn't have (Don't care about the "apps".)

What I'm hoping is coming some time soon is the ability to play a Blu-ray root from USB..or ISO mount from USB.. Then not use BD-RE so much.. Would be useful for Cameras and more. Dreaming visionary is fun. :D

[FilipeAmadeuO]

I came across this problem with multiple M2TS files with my older LG Blu-ray player (with Hard Drive). I really noticed it when I bought my copy of 50 Shades of Grey..ripped and processed it...and there were transition errors that you're typing about. Once I found another good LG player, and Ch3vr0n helped me realize that Cinavia isn't used as much anymore...I decided to get a new one. That movie, plus others..all the transition errors are gone. For a bit, I was thinking JD really goofed in BD-RB. Nope.. So, I'm with JD..I betcha it's your player, too. Now I have a note on that player.."Don't play non-original movies before 2015 or so with this." with a description of why. The newer player supports SRTs much better and other features the other didn't have (Don't care about the "apps".)

What I'm hoping is coming some time soon is the ability to play a Blu-ray root from USB..or ISO mount from USB.. Then not use BD-RE so much.. Would be useful for Cameras and more. Dreaming visionary is fun. :D

I understand that players can make some difference but only the rebuilded version have small shutter problem. If I play original there is no shutter.
I believe that it’s something not 100% perfect.
Regarding player the OPPO is considered the best player around so I am not talking about low quality player :)