View Full Version : BD Rebuilder Beta - Bug Reports Only
videoh
27th September 2019, 18:57
Just play the end of the transcoded movie and see if anything is missing. It there were anything missing in the transcodes, I'm sure jdobbs would have noticed it and there would be a lot of reports about it.
My Sony Player stops the film at the end of the reauthored mpls-file. Players do generally stop playing at the end of the movie. So your point is a bit opaque. Is there anything missing at the end?
jdobbs
27th September 2019, 19:06
Here the mpls-file from the main film. The first is the reauthored BD-Rebuilder and the second is the original file.You only posted one.
If there's a bug I will fix it. But first I need to be sure there is a bug.
Michi
27th September 2019, 19:14
The sreenshot of tsmuxer shows both mpls-files.
videoh
27th September 2019, 19:15
Is content missing or not?
jdobbs
27th September 2019, 19:23
The sreenshot of tsmuxer shows both mpls-files.Ok. I see. Then if TSMUXER is reporting properly (which isn't clear) there is a 10 minute delta between the original and the recode.
So when it plays, does it actually stop 10 minutes short of the end?
Michi
27th September 2019, 19:26
The reauthored mpls-file is over 9 minutes shorter than the original. My Player plays only the shorter time-length of the reauthored mpls-file. The m2ts-file has the correct time-length
Michi
27th September 2019, 19:30
Ok. I see. Then if TSMUXER is reporting properly (which isn't clear) there is a 10 minute delta between the original and the recode.
So when it plays, does it actually stop 10 minutes short of the end?
Yes, the player stops 10 minutes short of the end and this is the time length, that show tsmuxer in the screenshot.
videoh
27th September 2019, 19:58
I ask again, is content missing? It should be a simple answer.
Michi
27th September 2019, 19:59
Yes, the film is shorter.
videoh
27th September 2019, 20:13
OK, thank you.
FilipeAmadeuO
27th September 2019, 20:52
That's the part that throws me. The original MPLS is used in a full backup. The only MPLS changes would be if the encode involved resolution change or if it was reencoded to a different format (like VC-1 to AVC). The chapter information, etc, is never changed. I'll go back through the code to make sure... but I'm pretty confident that's the case.
Also, no one else is reporting this issue. I think if the end of the movie was missing people would notice/report it???
A movie-only backup would be different. BD-RB generates the MPLS from scratch in that case.
Are you doing any external editing or modifications?
It´s strange that you do not make any MPLS change on full backup.
I tried to do a FULL BACKUP of a UHD disc without any change (kept all audio, subtitles and no vídeo encode) and MPLS and CLPI are very diferent.
The problem i face it´s that is a image shutter/problem when on the same MPLS it changes between M2TS.
See the exemple attached.
jdobbs
27th September 2019, 22:48
It´s strange that you do not make any MPLS change on full backup.
I tried to do a FULL BACKUP of a UHD disc without any change (kept all audio, subtitles and no vídeo encode) and MPLS and CLPI are very diferent.
The problem i face it´s that is a image shutter/problem when on the same MPLS it changes between M2TS.
See the exemple attached.There are other changes that can be made... like when you only keep certain audio tracks, subs, etc. But they are all made to a copy of the original MPLS. So it will never likely be identical, but also doesn't change radically. I don't change anything that doesn't have to be changed. Most of that code hasn't changed in years.
The CLPI file, on the other hand is completely revamped -- it has things like tables of pointers to access units throughout the M2TS -- so when there is a reencode it has to be made to match the reencoded output. The HD/SD baseline CLPI it is created by TSMUXER, but for UHD there have to be many updates to make it compatible with the UHD spec so BD-RB creates it from scratch.
I'll look at your attachment when I get a chance.
If there's something wrong I'll fix it... I'm running some jobs to see if I can repeat what was reported. Unfortunately, though, each job takes many hours to complete... so it may be a while.
videoh
28th September 2019, 00:39
Can you please approve all the attachments for us? Thank you.
Acerjen
28th September 2019, 05:11
The CLPI file, on the other hand is completely revamped -- it has things like tables of pointers to access units throughout the M2TS -- so when there is a reencode it has to be made to match the reencoded output. The HD/SD baseline CLPI it is created by TSMUXER, but for UHD there have to be many updates to make it compatible with the UHD spec so BD-RB creates it from scratch.
I am having the same (or similar) issue with my UHD Full Backups. Based on your desciption of the CLPI file, it may be the problem, not the MPLS file as Michi has claimed. Here is an example:
When I play the full backup of Star Trek Beyond 4K on my hardware player (an Xbox One X) it plays the entire film all the way to the end of the runtime, which is 1:59:03, but when I play the M2TS file on my computer (in Windows 10), it shows the film to be 2:02:22. So, it's not that the actual video file is short (or re-encoded improperly), but the pointer file(s) that the hardware players use to navigate the disc is wrong and off by just a bit. Again, based on your description of the CLPI file that has to be regenerated from scratch, it may be the issue.
Thanks for your time. Later.
Acerjen
Acerjen
28th September 2019, 05:34
Most films seem to have one large M2TS file to play the contains everything, but I am running into some films that are spanned across more than one M2TS files. These tend to be films that have more than one version of the film on the discs. (I believe is is called seamless branching???) or have alternate intro credits using different languages (like Star Wars films). I am running into playback problems with these films right when the film goes from one M2TS file into the next. My player simply pauses and stays paused. I can chapter rewind back to the beginning and chapter forward to the spot it paused at and it plays fine. I am wondering if there is an issue with the pointer files (maybe the CLPI file) that navigate the player across the different M2TS files?
I can provide you with a specific example, but need to be reminded of which files you would need me to post?
FilipeAmadeuO
28th September 2019, 09:35
Most films seem to have one large M2TS file to play the contains everything, but I am running into some films that are spanned across more than one M2TS files. These tend to be films that have more than one version of the film on the discs. (I believe is is called seamless branching???) or have alternate intro credits using different languages (like Star Wars films). I am running into playback problems with these films right when the film goes from one M2TS file into the next. My player simply pauses and stays paused. I can chapter rewind back to the beginning and chapter forward to the spot it paused at and it plays fine. I am wondering if there is an issue with the pointer files (maybe the CLPI file) that navigate the player across the different M2TS files?
I can provide you with a specific example, but need to be reminded of which files you would need me to post?
Exact the same problem that I am facing. On my OPPO player it shutters a bit but moves to next m2ts.
jdobbs
28th September 2019, 12:20
Can you please approve all the attachments for us? Thank you.I can't because part of the information in the attachment would violate rules.
jdobbs
28th September 2019, 12:29
I am having the same (or similar) issue with my UHD Full Backups. Based on your desciption of the CLPI file, it may be the problem, not the MPLS file as Michi has claimed. Here is an example:
When I play the full backup of Star Trek Beyond 4K on my hardware player (an Xbox One X) it plays the entire film all the way to the end of the runtime, which is 1:59:03, but when I play the M2TS file on my computer (in Windows 10), it shows the film to be 2:02:22. So, it's not that the actual video file is short (or re-encoded improperly), but the pointer file(s) that the hardware players use to navigate the disc is wrong and off by just a bit. Again, based on your description of the CLPI file that has to be regenerated from scratch, it may be the issue.
Thanks for your time. Later.
AcerjenThanks for the info, I'll check it out.
The first job to test it is still running (it takes about 16 hours to do a typical UHD encode on my computer).
jdobbs
28th September 2019, 15:59
Thanks for the info, I'll check it out.
The first job to test it is still running (it takes about 16 hours to do a typical UHD encode on my computer).Well... the first job completed (after 16 hours)... and the times and playback matched perfectly with the original.
I need one of you guys to provide me with your log and settings (the contents of BDREBUILDER.INI). I can't keep wasting 16 hours at a time chasing rabbits down holes.
jdobbs
28th September 2019, 16:25
@FilipeAmadeuO
You said you have many titles that experienced the issue. Can you give me a list of them in the hope that I have one of them to work with?
FilipeAmadeuO
28th September 2019, 16:47
@FilipeAmadeuO
You said you have many titles that experienced the issue. Can you give me a list of them in the hope that I have one of them to work with?
---------------------
[09/28/19] BD Rebuilder v0.60.25
[16:05:19] Source: STAR_WARS_STORY_-_SOLO_(UHD)
- Input BD size: 52,77 GB
- Approximate total content: [02:16:43.320]
- Target BD size: 91,80 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[16:05:19] PHASE ONE, Encoding
- [16:05:19] Processing: VID_00058 (1 of 5)
- [16:05:19] Extracting A/V streams [VID_00058]
- [16:08:00] Reencoding video [VID_00058]
- [16:08:00] Keeping original video (no reencode)
- [16:08:00] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
- Track 4354 (fra): Keeping original audio
- Track 4355 (spa): Keeping original audio
- Track 4356 (tha): Keeping original audio
- [16:08:00] Multiplexing M2TS
- [16:11:55] Processing: VID_00062 (2 of 5)
- [16:11:55] Extracting A/V streams [VID_00062]
- Extracting video streams [VID_00062]
- Extracting audio/subtitle streams [VID_00062]
- [17:08:26] Reencoding video [VID_00062]
- [17:08:26] Keeping original video (no reencode)
- [17:08:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
- Track 4354 (fra): Keeping original audio
- Track 4355 (spa): Keeping original audio
- Track 4356 (tha): Keeping original audio
- [17:08:26] Multiplexing M2TS
- [17:44:23] Processing: VID_00063 (3 of 5)
- [17:44:23] Extracting A/V streams [VID_00063]
- [17:44:35] Reencoding video [VID_00063]
- [17:44:35] Keeping original video (no reencode)
- [17:44:35] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
- Track 4354 (fra): Keeping original audio
- Track 4355 (spa): Keeping original audio
- Track 4356 (tha): Keeping original audio
- [17:44:35] Multiplexing M2TS
- [17:44:45] Processing: VID_00064 (4 of 5)
- [17:44:45] Extracting A/V streams [VID_00064]
- [17:44:57] Reencoding video [VID_00064]
- [17:44:57] Keeping original video (no reencode)
- [17:44:57] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
- Track 4354 (fra): Keeping original audio
- Track 4355 (spa): Keeping original audio
- Track 4356 (tha): Keeping original audio
- [17:44:57] Multiplexing M2TS
- [17:45:12] Processing: VID_00065 (5 of 5)
- [17:45:12] Extracting A/V streams [VID_00065]
- [17:45:22] Reencoding video [VID_00065]
- [17:45:22] Keeping original video (no reencode)
- [17:45:22] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
- Track 4354 (fra): Keeping original audio
- Track 4355 (spa): Keeping original audio
- Track 4356 (tha): Keeping original audio
- [17:45:22] Multiplexing M2TS
[17:45:34]PHASE ONE complete
[17:45:34]PHASE TWO - Rebuild Started
- [17:45:34] Rebuilding BD file Structure
[17:45:51] - Encode and Rebuild complete
[17:45:51] JOB: STAR_WARS_STORY_-_SOLO_(UHD) finished.
Acerjen
29th September 2019, 05:07
One title I am having that issue with is Everest. Here is the BDREBUILDER.INI
[Options]
VERSION=0.60.0.25
ENCODER=0
MODE=0
ENCODE_QUALITY=5
ONEPASS_ENCODING=2
AUTO_QUALITY=0
TARGET_SIZE=23500
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
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=0
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
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
MOVIEONLY_TYPE=3
ALTCRF=23
ALT_TARGET=1024
ALTMETHOD=1
ALTAUTOCROP=0
ALT_CRF_TARGET=1024
PGSTOSRT=0
SUPPRESS_FF_WARNING=1
MENU_BACKGROUND=C:\BD_Rebuilder\Misc\colorado-mountains2.jpg
MENU_AUDIO=C:\BD_Rebuilder\tools\blankclip\blank.ac3
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0
[Paths]
WORKING_PATH=F:\00 - 4K ENCODING\
DGIndexNV=C:\Program Files (x86)\dgdecnv2051\DGIndexNV.exe
DGDecNV=C:\Program Files (x86)\dgdecnv2051\DGDecodeNV.dll
SOURCE_PATH=F:\MOVIES (UHD)\EVEREST (UHD)\
I will report back after I rerun it through BD Rebuilder as I have deleted the log files you need. Thanks. Later.
Acerjen
jdobbs
29th September 2019, 12:40
I made over twenty UHD full backups and all backups have this bug.Name them.
I have encoded numerous discs... and none have that issue. Just to test your report I have done two more (wasting more than 30 hours of my video computer's time encoding) -- and both came out with the times being exactly what they should have been.
jdobbs
29th September 2019, 12:40
@FilipeAmadeuO
You said you have many titles that experienced the issue. Can you give me a list of them in the hope that I have one of them to work with?My mistake. That should have been addressed to Michi.
jdobbs
29th September 2019, 12:44
@Acerjen
Thanks for the INI file.
The disc I ran last night was the one reported to have "shutter" problems. I'll test it some time today and see if I can repeat that issue.
FilipeAmadeuO
29th September 2019, 13:21
Yes, the player stops 10 minutes short of the end and this is the time length, that show tsmuxer in the screenshot.
I can confirm this issue.
Tested disc "Pirates of the Caribenean - Dead Man tell no tales" UHD. Did not removed anything from the disc and just rebuilded (no vídeo encode, no áudio/subtitles removal)
The rebuilded file is smaller and check the Windows time info.
Original: 02:09:06
Rebuilded: 01:43:34
BD Info reports the same time on original and rebuilded but the m2ts it´s smaller.
jdobbs
29th September 2019, 13:23
Yep. There is definitely an issue with transition between M2TS files on SOLO. It's possible this may be related to what Michi reported, but I'm not sure. I'll see what I can find.
jdobbs
29th September 2019, 13:24
I can confirm this issue.
Tested disc "Pirates of the Caribenean - Dead Man tell no tales" UHD. Did not removed anything from the disc and just rebuilded (no vídeo encode, no áudio/subtitles removal)
The rebuilded file is smaller and check the Windows time info.
Original: 02:09:06
Rebuilded: 01:43:34
BD Info reports the same time on original and rebuilded but the m2ts it´s smaller.Unfortunately I don't have that disc.
Can you play back the end of the two files and see if they match? I want to see if the time discrepancy is in the M2TS itself, or the what is reported in the CLPI. I suspect it may be in the CLPI based on what I saw in SOLO. But if part of the file isn't being encoded -- that may be a bigger issue outside of BD-RB (and a lot harder to fix).
FilipeAmadeuO
29th September 2019, 14:03
Unfortunately I don't have that disc.
Can you play back the end of the two files and see if they match? I want to see if the time discrepancy is in the M2TS itself, or the what is reported in the CLPI. I suspect it may be in the CLPI based on what I saw in SOLO. But if part of the file isn't being encoded -- that may be a bigger issue outside of BD-RB (and a lot harder to fix).
Removed
Michi
29th September 2019, 14:12
My BD Rebuilder.ini:
[Options]
VERSION=0.60.0.25
MODE=0
ENCODER_MENU=1
ENCODE_QUALITY=5
ONEPASS_ENCODING=2
AUTO_QUALITY=0
AUDIO_TO_KEEP=deu;gem;ger;
SUBS_TO_KEEP=deu;gem;ger;gmh;goh;gsw;
SD_CONVERT=0
OPEN_GOP=1
RESIZE_1080=0
DEINTERLACE=0
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=1
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
DGDECNV=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=66000
TARGET_SIZE=47366
AUTO_BURN=2
MOVIEONLY_TYPE=40
ALTCRF=18
ARCHIVE_265=1
ARCHIVE_AUDIO=100
ARCHIVE_CRF=16
ARCHIVE_ENABLE=1
ARCHIVE_LIMIT=1
ALT_TARGET=7800
ALTMETHOD=0
ALTAUTOCROP=0
QUICK_EXTRAS=0
OUTPUT_3D=0
RESIZE_1440=0
RESIZE_720=0
NEROAAC=0
SUPTITLE=0
IGNORE_3D=0
OUTPUT_SBS=0
ENCODER_MENU=1
HC_PROFILE=BEST
IMPORT_HEVC_INTACT=1
MIN_M2TS_SIZE=20
NEW_CRF_PREDICTION=1
MULTIPROCESS=0
THREADS=auto
BD5_SIZE=4520
BD9_SIZE=8200
BD25_SIZE=23200
QUALITY_ULTRA=1
FRIMSOURCE=0
ENCODER=0
DGDECIM=1
FRIM_SW_DECODE=1
FRIM_SW_ENCODE=1
PRIORITY_CLASS=1
MENU_BACKGROUND=C:\BD_Rebuilder\misc\menuback.jpg
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
DECODER=2
AUDIO_DRC=0
MENU_AUTO_DVDAUDIO=1
IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0
ALT_CRF_TARGET=4000
PGSTOSRT=0
[Paths]
SOURCE_PATH=E:\4K BLU RAY\CLIFFHANGER.1993.2160P
WORKING_PATH=Q:\4K\
Name them.
I have encoded numerous discs... and none have that issue. Just to test your report I have done two more (wasting more than 30 hours of my video computer's time encoding) -- and both came out with the times being exactly what they should have been.
The following discs have that issue and the end is shorter (I would like to update the list):
Creed - Rockys Legacy 2015
Creed II 2018
Allied 2016
Cliffhanger Studio Canal Version 1993
The little Mermaid 1989
Wildes Venedig
Ballon 2018
Apollo 13 1995
Asterix 2018
Ghostbuster 1984
I deleted the most backups.
Today I'm testing more and send logs to Jdobbs.
Michi
29th September 2019, 15:46
Wildes Venedig Log:
[09.29.19] BD Rebuilder v0.60.25
[14:57:43] Source: WILDES_VENEDIG
- Input BD size: 25,80 GB
- Approximate total content: [00:53:08.921]
- Target BD size: 22,66 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[14:57:43] PHASE ONE, Encoding
- [14:57:43] Processing: VID_00005 (1 of 1)
- [14:57:43] Extracting A/V streams [VID_00005]
- [15:01:25] Reencoding video [VID_00005]
- Source Video: HEVC, 3840x2160
- Rate/Length: 25,000fps, 78.047 frames
- Bitrate: 35.000 Kbs
- [15:01:25] Reencoding: VID_00005, Pass 1 of 1
- [16:38:08] Video Encode complete
- [16:38:08] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- Track 4353 (deu): Keeping original audio
- [16:38:09] Multiplexing M2TS
[16:44:47]PHASE ONE complete
[16:44:47]PHASE TWO - Rebuild Started
- [16:44:47] Rebuilding BD file Structure
[16:44:51] - Encode and Rebuild complete
[16:44:51] Writing BD structure to ISO file
- ImgBurn completed successfully
- WILDES_VENEDIG folder removed.
- WORKFILES folder removed.
[16:45:12] JOB: WILDES_VENEDIG finished.
Mark_Venture
29th September 2019, 17:56
My BD Rebuilder.ini:
[Paths]
SOURCE_PATH=E:\4K BLU RAY\CLIFFHANGER.1993.2160P.UHD.BLURAY.HDR.HEVC.DTS-HD.MA.5.1-HDBEE\
WORKING_PATH=Q:\4K\
.Are you working on discs you owned and ripped yourself or something you downloaded?
I ask because the source path looks like something that was downloaded.
Michi
29th September 2019, 18:18
Are you working on discs you owned and ripped yourself or something you downloaded?
I ask because the source path looks like something that was downloaded.
I edit the path.
prologic
29th September 2019, 18:32
I can confirm this issue.
Tested disc "Pirates of the Caribenean - Dead Man tell no tales" UHD. Did not removed anything from the disc and just rebuilded (no vídeo encode, no áudio/subtitles removal)
The rebuilded file is smaller and check the Windows time info.
Original: 02:09:06
Rebuilded: 01:43:34
BD Info reports the same time on original and rebuilded but the m2ts it´s smaller.
I did this film, exept I took some audio and subtitle streams out ..
Just checked the movie , and the length of the film is
02:09:06 ... I did Toy story 4 , it has many m2ts files, around 126 ..
took the unwanted streams out , and worked a treat ..have my size set at stupid size 900500 , because I only take out streams , these days .
FilipeAmadeuO
29th September 2019, 18:57
I did this film, exept I took some audio and subtitle streams out ..
Just checked the movie , and the length of the film is
02:09:06 ... I did Toy story 4 , it has many m2ts files, around 126 ..
took the unwanted streams out , and worked a treat ..have my size set at stupid size 900500 , because I only take out streams , these days .
I think it was my mistaque. The problem was generated because of low free disc size space. Rebuilded again and working perfect.
gamete
29th September 2019, 19:02
Is it possibile make a backup of 4K bluray into BD25 or BD50 ?
The 4k bluray have same structure of bluray ?
Thanks
prologic
29th September 2019, 19:22
Is it possibile make a backup of 4K bluray into BD25 or BD50 ?
The 4k bluray have same structure of bluray ?
Thanks
Yes it is possible, thats what this thread is all about, but still in test yet.
I personally do all my cartoon type stuff on bd25 .
Michi
29th September 2019, 19:25
Ghostbuster 1984:
[16:46:48] Source: GHOSTBUSTERS.1984
- Input BD size: 57,65 GB
- Approximate total content: [02:09:54.241]
- Target BD size: 22,66 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[16:46:48] PHASE ONE, Encoding
- [16:46:48] Processing: VID_00001 (1 of 2)
- [16:46:48] Extracting A/V streams [VID_00001]
- [16:51:44] Reencoding video [VID_00001]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 151.248 frames
- Bitrate: 26.056 Kbs
- [16:51:44] Reencoding: VID_00001, Pass 1 of 1
- [20:09:52] Video Encode complete
- [20:09:52] Processing audio tracks
- Track 4355 (deu): Keeping original audio
- [20:09:53] Multiplexing M2TS
- [20:17:55] Processing: VID_00100 (2 of 2)
- [20:17:55] Extracting A/V streams [VID_00100]
- [20:17:59] Reencoding video [VID_00100]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 346 frames
- Bitrate: 7.723 Kbs
- [20:17:59] Reencoding: VID_00100, Pass 1 of 1
- [20:18:19] Video Encode complete
- [20:18:19] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [20:18:19] Multiplexing M2TS
[20:18:23]PHASE ONE complete
[20:18:23]PHASE TWO - Rebuild Started
- [20:18:23] Rebuilding BD file Structure
[20:18:35] - Encode and Rebuild complete
[20:18:35] Writing BD structure to ISO file
- ImgBurn completed successfully
- GHOSTBUSTERS.1984 folder removed.
- WORKFILES folder removed.
[20:19:08] JOB: GHOSTBUSTERS.1984 finished.
Ch3vr0n
29th September 2019, 19:53
@Michi
Just because you edit the path from
E:\4K BLU RAY\CLIFFHANGER.1993.2160P.UHD.BLURAY.HDR.HEVC.DTS-HD.MA.5.1-HDBEE to E:\4K BLU RAY\CLIFFHANGER.1993.2160P doesn't make it an original disc magically. No retail disc uses that entire string as a disc name. Ever.
That is a pirated release, which means most likely GHOSTBUSTERS.1984 is aswell. Which is against the forum rules (specifically nr 6). We can't assist you any further, and i doubt jdobbs will too at this point. Get the original discs, then come back. Anything else, is off limits.
gamete
30th September 2019, 10:30
Yes it is possible, thats what this thread is all about, but still in test yet.
I personally do all my cartoon type stuff on bd25 .
Bd25 ?,how % of compression ?
jdobbs
30th September 2019, 18:52
@FilipeAmadeuO and Acerjen
I found the issue you were describing. After a remux is done by TSMUXER, the MPLS's sequence table was updated with the new start/end presentation timestamps (PTS). It just so happens, though, that TSMUXER loses frames when it muxes UHD. I'd written code in BD-RB that corrects that issue by remuxing the video. The corrected length information was updated in a new CLPI (generated by BD-RB) but that information was never transferred to the MPLS. So individual M2TS playback times on UHD sources (specified in the MPLS) were off by the number of frames that were lost in the original TSMUXER process.
I've fixed it for the next release, which will probably be posted sometime later today after I do some testing.
videoh
30th September 2019, 18:56
Bravo, jdobbs! Looking forward to it.
lithiumus
30th September 2019, 20:46
@FilipeAmadeuO and Acerjen
I found the issue you were describing. After a remux is done by TSMUXER, the MPLS's sequence table was updated with the new start/end presentation timestamps (PTS). It just so happens, though, that TSMUXER loses frames when it muxes UHD. I'd written code in BD-RB that corrects that issue by remuxing the video. The corrected length information was updated in a new CLPI (generated by BD-RB) but that information was never transferred to the MPLS. So individual M2TS playback times on UHD sources (specified in the MPLS) were off by the number of frames that were lost in the original TSMUXER process.
I've fixed it for the next release, which will probably be posted sometime later today after I do some testing.
Can't say it enough... this is amazing work you do.
Just curious, any further thoughts on not remuxing streams that are not being touched? Could also ensure that streams don't see any regression due to issues with TSMuxer that you may not always foresee and compensate for!
MrVideo
30th September 2019, 21:23
@jdobbs
I thought you were going to fix tsmuxer, since you now had the source. I must have misread that.
jdobbs
30th September 2019, 21:33
@jdobbs
I thought you were going to fix tsmuxer, since you now had the source. I must have misread that.That's a task for another day.
jdobbs
30th September 2019, 21:38
I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.60.26). Changes for this release:- Corrected an issue in which stopping an
encode of a source that is being inverse
telecined -- and then restarting without
exiting could (on rare occasions) cause an
incorrect framecount that truncates the
the video output.
- Added a new hidden option FORCE_MONO_RATE
which allows the user to force the bitrate
used for monophonic audio.
- 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.
- Other minor corrections and cosmetic fixes.
FilipeAmadeuO
1st October 2019, 00:46
@FilipeAmadeuO and Acerjen
I found the issue you were describing. After a remux is done by TSMUXER, the MPLS's sequence table was updated with the new start/end presentation timestamps (PTS). It just so happens, though, that TSMUXER loses frames when it muxes UHD. I'd written code in BD-RB that corrects that issue by remuxing the video. The corrected length information was updated in a new CLPI (generated by BD-RB) but that information was never transferred to the MPLS. So individual M2TS playback times on UHD sources (specified in the MPLS) were off by the number of frames that were lost in the original TSMUXER process.
I've fixed it for the next release, which will probably be posted sometime later today after I do some testing.
Tested and seems correct now. Many thanks
Jdobbs
Can you please check the transition between chapter 7 and 8 on SOLO - STAR WARS STORY (UHD) of the rebuilded version ?
Seems there is still a stuttering...
FilipeAmadeuO
1st October 2019, 00:48
That's a task for another day.
Maybe this could help a lot on bdrebuilder dirty fixes :)
FilipeAmadeuO
1st October 2019, 22:44
What is experience with rebuilt Dolby vision UHD ?
jdobbs
1st October 2019, 23:04
Tested and seems correct now. Many thanks
Jdobbs
Can you please check the transition between chapter 7 and 8 on SOLO - STAR WARS STORY (UHD) of the rebuilded version ?
Seems there is still a stuttering...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.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.