Andrew,
The
2 modifications I made are in bdcreate.C to temporarily comment out the
choices of lpcm and truehd as neither 1 works for me (see error
messages in previous email).
those mesages come from players themselves?
No, from bdwrite -- see the last line in the terminal output below for the error message when I choose "truehd" and then "lpcm". I verified that 0004-Improve-truehd-decoder-encoder-from-ffmpeg.git.patch is in as well as all of the patches as stated earlier.
FFMPEG::open_decoder: some stream times estimated: /root/media/hockey.ts
Render::render_single: Session finished.
** rendered 679 frames in 15.393 secs, 44.111 fps
++ dirname /tmp/bd_20220417-102756/bd.sh
+ sdir=/tmp/bd_20220417-102756
++ cd /tmp/bd_20220417-102756
++ pwd
+ dir=/tmp/bd_20220417-102756
+ PATH=/root/.local/bin:/root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/tmp/cinelerra-5.1/bin
+ mkdir -p /tmp/bd_20220417-102756/udfs
++ tail -1
++ du -cb /tmp/bd_20220417-102756/bd.m2ts
++ sed -e 's/[ ].*//'
+ sz=40396800
+ blks=23821
+ rm -f /tmp/bd_20220417-102756/bd.udfs
+ '[' -f bd.meta ']'
+ mkudffs -b 2048 /tmp/bd_20220417-102756/bd.udfs 23821
filename=/tmp/bd_20220417-102756/bd.udfs
label=LinuxUDF
uuid=625c4025cebbb06e
blocksize=2048
blocks=23821
udfrev=2.01
start=0, blocks=16, type=ERASE
start=16, blocks=4, type=VRS
...
start=23648, blocks=16, type=RVDS
start=23664, blocks=156, type=ERASE
start=23820, blocks=1, type=ANCHOR
+ mount -t udf -o loop /tmp/bd_20220417-102756/bd.udfs /tmp/bd_20220417-102756/udfs
+ bdwrite /tmp/bd_20220417-102756/udfs /tmp/bd_20220417-102756/bd.m2ts
unknown bluray audio format 0 ch
FFMPEG::open_decoder: some stream times estimated: /root/media/hockey.ts
Render::render_single: Session finished.
** rendered 679 frames in 15.329 secs, 44.295 fps
++ dirname /tmp/bd_20220417-105416/bd.sh
+ sdir=/tmp/bd_20220417-105416
++ cd /tmp/bd_20220417-105416
++ pwd
+ dir=/tmp/bd_20220417-105416
+ PATH=/root/.local/bin:/root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/tmp/cinelerra-5.1/bin
+ mkdir -p /tmp/bd_20220417-105416/udfs
++ du -cb /tmp/bd_20220417-105416/bd.m2ts
++ tail -1
++ sed -e 's/[ ].*//'
+ sz=44015616
+ blks=25588
+ rm -f /tmp/bd_20220417-105416/bd.udfs
+ '[' -f bd.meta ']'
+ mkudffs -b 2048 /tmp/bd_20220417-105416/bd.udfs 25588
filename=/tmp/bd_20220417-105416/bd.udfs
label=LinuxUDF
uuid=625c464fcd7855e8
blocksize=2048
blocks=25588
udfrev=2.01
start=0, blocks=16, type=ERASE
start=16, blocks=4, type=VRS
start=20, blocks=76, type=ERASE
start=96, blocks=16, type=MVDS
...
start=25587, blocks=1, type=ANCHOR
+ mount -t udf -o loop /tmp/bd_20220417-105416/bd.udfs /tmp/bd_20220417-105416/udfs
+ bdwrite /tmp/bd_20220417-105416/udfs /tmp/bd_20220417-105416/bd.m2ts
unknown bluray stream type pcm_bluray
may
be I misread code, but I thought they were set at fixed 5 min
intervals.. I thought making them at say 10 mins or even 15 mins from
cmd line will be good idea.. apparently not (
No, it is a good idea, that is why I keep testing it because for a 2 hour movie which I might put on bluray, every 5 minutes is overkill for a chapter. But I will take your advice and move on for now. The biggest problem with the chapter patch is that on the bluray attached to the TV, when you move to the back to the previous chapter, it acts like it moves back but plays where you already were instead.
However, the choice of "tsmuxer" works, or at least does something and creates no problem but I do not see or hear any difference if checked off or on.
you need to have tsmuxer binary in $PATH to see it used
I wonder why the output is different when I check the tsmuxer box than when I don't? I do not have tsmuxer binary in the $PATH and when I do "whereis tsmuxer", I get nothing so I do not think it is installed. Also, when I play each of the blurary with and without tsmuxer checked, I don't really notice a difference but I have bad eyes (and ears).