50, 100 and 128 GB discs have very often issues that data around the layer break is bad and the result is distorted video or hang-ups. This method developed by teaching-droid avoids this by burning dummy data at the layer break without compromising the video data.
Here is a first guide with a link to the program and how you use it. Enjoy!
https://mega.nz/folder/7IR2kZhD#S8_Ld_MXOZFbRZbewdYHOw
Muliti-layer discs / Breakthrough for burning
-
Coopervid
- Posts: 4706
- Joined: Tue Feb 19, 2019 10:32 pm
-
amhome
- Posts: 4
- Joined: Sat Nov 08, 2025 10:51 pm
Re: Muliti-layer discs / Breakthrough for burning
Thank you for sharing and thanks to the author for putting this together!
I didn't realize how much of a problem it is.
I didn't realize how much of a problem it is.
-
georgesgiralt
- Posts: 111
- Joined: Thu Jun 04, 2020 12:40 pm
Re: Muliti-layer discs / Breakthrough for burning
Hello,
I may be dumb but can't make this work.
At first I used git to copy the source tree on my Ubuntu 24.04.3 LTS computer.
As I'm used to compile "stuff" I did not had to install anything except QT6.
Then I used the script/rebuild_linux.sh to build the tsmuxer app. (I could not compile the GUI because of code errors.)
The app was compiled properly and I could give it a go.
I took one of my BD, MAX (a film about a war dog and the brother of it's handler) and using MakeMkv saved it to disk including The decrypted files.
I then removed the MakeMkv folder in order to have only a "proper" BD structure.
I then used the command line to produce the iso file for burning :
It worked ... and produced both an ISO file and a text file containing :
As the source size is 27G, I bet the above is correct ?
But the produced ISO file does not play in VLC. In order to be sure, I burned a BD 50 using one of my Pioneer drives (I know, I know...but) And then tried it into my Sony BD player. It says "Data BD" and refuse to play the movie.
Same also using VLC or other players on my computer.
So, what did I do wrong ?
I would be delighted to hear from others more lucky than I am !
Have a nice and bright day !
I may be dumb but can't make this work.
At first I used git to copy the source tree on my Ubuntu 24.04.3 LTS computer.
Code: Select all
git clone https://github.com/teaching-droid/tsMuxer.git Then I used the script/rebuild_linux.sh to build the tsmuxer app. (I could not compile the GUI because of code errors.)
The app was compiled properly and I could give it a go.
I took one of my BD, MAX (a film about a war dog and the brother of it's handler) and using MakeMkv saved it to disk including The decrypted files.
I then removed the MakeMkv folder in order to have only a "proper" BD structure.
I then used the command line to produce the iso file for burning :
Code: Select all
./build/tsMuxer/tsmuxer --bdmv-to-iso --layer-break-guard=64 --layer-break-lbn=12,219,392 /media/georges/256G/Max /media/georges/256G/MAX-break.iso Code: Select all
tsMuxeR layer break map (sectors of 2048 bytes)
image: /media/georges/256G/MAX-break.iso
break 12: zeros 1280 .. 32780 (-2.5 MB before + 64.0 MB after)
location not matched to a file
But the produced ISO file does not play in VLC. In order to be sure, I burned a BD 50 using one of my Pioneer drives (I know, I know...but) And then tried it into my Sony BD player. It says "Data BD" and refuse to play the movie.
Same also using VLC or other players on my computer.
So, what did I do wrong ?
I would be delighted to hear from others more lucky than I am !
Have a nice and bright day !
-
Coopervid
- Posts: 4706
- Joined: Tue Feb 19, 2019 10:32 pm
Re: Muliti-layer discs / Breakthrough for burning
The author is an vacation but he thinks that you copied from the help file with separators.georgesgiralt wrote: Thu Sep 10, 2026 1:50 pm Hello,
I may be dumb but can't make this work.
At first I used git to copy the source tree on my Ubuntu 24.04.3 LTS computer.As I'm used to compile "stuff" I did not had to install anything except QT6.Code: Select all
git clone https://github.com/teaching-droid/tsMuxer.git
Then I used the script/rebuild_linux.sh to build the tsmuxer app. (I could not compile the GUI because of code errors.)
The app was compiled properly and I could give it a go.
I took one of my BD, MAX (a film about a war dog and the brother of it's handler) and using MakeMkv saved it to disk including The decrypted files.
I then removed the MakeMkv folder in order to have only a "proper" BD structure.
I then used the command line to produce the iso file for burning :It worked ... and produced both an ISO file and a text file containing :Code: Select all
./build/tsMuxer/tsmuxer --bdmv-to-iso --layer-break-guard=64 --layer-break-lbn=12,219,392 /media/georges/256G/Max /media/georges/256G/MAX-break.isoAs the source size is 27G, I bet the above is correct ?Code: Select all
tsMuxeR layer break map (sectors of 2048 bytes) image: /media/georges/256G/MAX-break.iso break 12: zeros 1280 .. 32780 (-2.5 MB before + 64.0 MB after) location not matched to a file
But the produced ISO file does not play in VLC. In order to be sure, I burned a BD 50 using one of my Pioneer drives (I know, I know...but) And then tried it into my Sony BD player. It says "Data BD" and refuse to play the movie.
Same also using VLC or other players on my computer.
So, what did I do wrong ?
I would be delighted to hear from others more lucky than I am !
Have a nice and bright day !
Help says as standard "12,219,392".
break 12 confirms it.
It should be --layer-break-lbn=12219392. Without the commas! Try again.
-
georgesgiralt
- Posts: 111
- Joined: Thu Jun 04, 2020 12:40 pm
Re: Muliti-layer discs / Breakthrough for burning
Well, you were right !
Without the commas, the generated image is waaaay better and plays fine in Vlc.
I also added
which is overkill here as the original BD is 29 GB in size !
Thank you for your help
As I said, I am dumb.... Didn't figure the commas were the culprit.....
Without the commas, the generated image is waaaay better and plays fine in Vlc.
I also added
Code: Select all
--disc-capacity 24438784which is overkill here as the original BD is 29 GB in size !
Thank you for your help
As I said, I am dumb.... Didn't figure the commas were the culprit.....