Paul fixed bug preventing tsmuxer from recognizing our lpcm audio stream I backshoed fix into our ffmpeg 4.4.. I think having it all worked in monthly release quite important, even if names of patches kinda high... also attached raw pcm-bluenc file as I hacked it, and fix/patch as downloaded from gitweb.. https://github.com/justdan96/tsMuxer/issues/580 https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf...
Will try to test this tomorrow -- just FYI - the naming of the ffmpeg patches was used to ensure that they were added in order in case of routine overlap. So far it does not seem to matter, but that is why it was 1,2,...9,A,B, ... and would have been up to Z. With the addition of the underscore (_) the patching is getting done in the order of patch_1, patch_10, patch_2 ... It is fine though. Thanks! for all of your support and work lately. On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < [email protected]> wrote:
Paul fixed bug preventing tsmuxer from recognizing our lpcm audio stream
I backshoed fix into our ffmpeg 4.4..
I think having it all worked in monthly release quite important, even if names of patches kinda high...
also attached raw pcm-bluenc file as I hacked it, and fix/patch as downloaded from gitweb..
https://github.com/justdan96/tsMuxer/issues/580
https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a...
https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf...
Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it compiles but fails with error message "open failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file. On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < [email protected]> wrote:
Paul fixed bug preventing tsmuxer from recognizing our lpcm audio stream
I backshoed fix into our ffmpeg 4.4..
I think having it all worked in monthly release quite important, even if names of patches kinda high...
also attached raw pcm-bluenc file as I hacked it, and fix/patch as downloaded from gitweb..
https://github.com/justdan96/tsMuxer/issues/580
https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a...
https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf...
On Monday, April 25, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it compiles but fails with error message "open failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file.
strange. can you double-check patches applied correctly (by comparing pcm-bluenc.c I attached earlier and actual file in thirdparty/ffmpeg/libavcodec? )
On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < [email protected]> wrote:
Paul fixed bug preventing tsmuxer from recognizing our lpcm audio stream
I backshoed fix into our ffmpeg 4.4..
I think having it all worked in monthly release quite important, even if names of patches kinda high...
also attached raw pcm-bluenc file as I hacked it, and fix/patch as downloaded from gitweb..
https://github.com/justdan96/tsMuxer/issues/580
https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ 037fa0437d2aead40c1f786c6ad4d343afe0546d..058a1ff9b4cdbd2e1a93acc8bf0365 e7d01cc9f4:/libavcodec/pcm-blurayenc.c
https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ 93dfb6afddb278218da7f8c696bf35ede2ba05aa
Yes, it is very strange and I can not understand why it is happening. I checked that on 2 different computers but here it is: [root@keystone libavcodec]# diff pcm-bluenc.c /root/*Downloads/pcm-bluenc.c* [root@keystone libavcodec]# [root@keystone libavformat]# *diff mpegtsenc.c* /tmp/cinelerra-5.1/thirdparty/ffmpeg-4.4/libavformat/mpegtsenc.c 1959,1962d1958 < } else if (st->codecpar->codec_id == AV_CODEC_ID_PCM_BLURAY && ts->m2ts_mode) { < mpegts_write_pes(s, st, buf, size, pts, dts, < pkt->flags & AV_PKT_FLAG_KEY, stream_id); < return 0; On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < [email protected]> wrote:
On Monday, April 25, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it compiles but fails with error message "open failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file.
strange.
can you double-check patches applied correctly (by comparing pcm-bluenc.c I attached earlier and actual file in thirdparty/ffmpeg/libavcodec? )
On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < [email protected]> wrote:
Paul fixed bug preventing tsmuxer from recognizing our lpcm audio stream
I backshoed fix into our ffmpeg 4.4..
I think having it all worked in monthly release quite important, even if names of patches kinda high...
also attached raw pcm-bluenc file as I hacked it, and fix/patch as downloaded from gitweb..
https://github.com/justdan96/tsMuxer/issues/580
https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a...
https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf...
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Yes, it is very strange and I can not understand why it is happening. I checked that on 2 different computers but here it is:
[root@keystone libavcodec]# diff pcm-bluenc.c /root/ *Downloads/pcm-bluenc.c* [root@keystone libavcodec]#
[root@keystone libavformat]# *diff mpegtsenc.c* /tmp/cinelerra-5.1/thirdparty/ffmpeg-4.4/libavformat/mpegtsenc.c 1959,1962d1958 < } else if (st->codecpar->codec_id == AV_CODEC_ID_PCM_BLURAY && ts->m2ts_mode) { < mpegts_write_pes(s, st, buf, size, pts, dts, < pkt->flags & AV_PKT_FLAG_KEY, stream_id); < return 0;
'diff - u' a bit more widespread form of diff, for now.. but strange. you rebuild cin executable too? (because we link statically I typed "touch cinelerra/new.C" and this forced rebuild of this file and re-linking of executable...) does ffmpeg from thirdparty lists pcm_bluray as supported encoder?
On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < [email protected]> wrote:
On Monday, April 25, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it compiles but fails with error message "open failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file.
strange.
can you double-check patches applied correctly (by comparing pcm-bluenc.c I attached earlier and actual file in thirdparty/ffmpeg/libavcodec? )
On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < [email protected]> wrote:
Paul fixed bug preventing tsmuxer from recognizing our lpcm audio stream
I backshoed fix into our ffmpeg 4.4..
I think having it all worked in monthly release quite important, even if names of patches kinda high...
also attached raw pcm-bluenc file as I hacked it, and fix/patch as downloaded from gitweb..
https://github.com/justdan96/tsMuxer/issues/580
https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ 037fa0437d2aead40c1f786c6ad4d343afe0546d.. 058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm-blurayenc.c
https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ 93dfb6afddb278218da7f8c696bf35ede2ba05aa
I am out of ideas to try. [root@keystone libavcodec]# diff pcm-bluenc.c /root/*Downloads/pcm-bluenc.c*
[root@keystone libavcodec]#
[root@keystone libavformat]# *diff mpegtsenc.c* /tmp/cinelerra-5.1/thirdparty/ffmpeg-4.4/libavformat/mpegtsenc.c 1959,1962d1958 < } else if (st->codecpar->codec_id == AV_CODEC_ID_PCM_BLURAY && ts->m2ts_mode) { < mpegts_write_pes(s, st, buf, size, pts, dts, < pkt->flags & AV_PKT_FLAG_KEY, stream_id); < return 0;
'diff - u' a bit more widespread form of diff, for now..
Exact same results when do "diff -u".
but strange. you rebuild cin executable too? (because we link statically I typed "touch cinelerra/new.C" and this forced rebuild of this file and re-linking of executable...)
I do full rebuilds by running "make clean" which deletes all of the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes pretty fast on this laptop and it is not worth the aggravation to only rebuild changed itemsl
does ffmpeg from thirdparty lists pcm_bluray as supported encoder?
It must because what is checked into GIT, lets me choose the lpcm profile and on the bluray player, the info button clearly displays it as lpcm.
On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < [email protected]> wrote:
On Monday, April 25, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it compiles but fails with error message "open failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file.
strange.
can you double-check patches applied correctly (by comparing pcm-bluenc.c I attached earlier and actual file in thirdparty/ffmpeg/libavcodec? )
On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < [email protected]> wrote:
Paul fixed bug preventing tsmuxer from recognizing our lpcm audio stream
I backshoed fix into our ffmpeg 4.4..
I think having it all worked in monthly release quite important, even if names of patches kinda high...
also attached raw pcm-bluenc file as I hacked it, and fix/patch as downloaded from gitweb..
https://github.com/justdan96/tsMuxer/issues/580
https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a...
https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf...
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
I am out of ideas to try.
[root@keystone libavcodec]# diff pcm-bluenc.c /root/
*Downloads/pcm-bluenc.c* [root@keystone libavcodec]#
[root@keystone libavformat]# *diff mpegtsenc.c* /tmp/cinelerra-5.1/thirdparty/ffmpeg-4.4/libavformat/mpegtsenc.c 1959,1962d1958 < } else if (st->codecpar->codec_id == AV_CODEC_ID_PCM_BLURAY && ts->m2ts_mode) { < mpegts_write_pes(s, st, buf, size, pts, dts, < pkt->flags & AV_PKT_FLAG_KEY, stream_id); < return 0;
'diff - u' a bit more widespread form of diff, for now..
Exact same results when do "diff -u".
note, even if file named like c file it actually diff.. but both patches as send works for me as after full rebuild.. / if you (re)move those last two patches from tirdparty/src error (can't find codec..) disappears?
but strange. you rebuild cin executable too? (because we link statically I typed "touch cinelerra/new.C" and this forced rebuild of this file and re-linking of executable...)
I do full rebuilds by running "make clean" which deletes all of the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes pretty fast on this laptop and it is not worth the aggravation to only rebuild changed itemsl
does ffmpeg from thirdparty lists pcm_bluray as supported encoder?
It must because what is checked into GIT, lets me choose the lpcm profile and on the bluray player, the info button clearly displays it as lpcm.
try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray
On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < [email protected]> wrote:
On Monday, April 25, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it compiles but fails with error message "open failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file.
strange.
can you double-check patches applied correctly (by comparing pcm-bluenc.c I attached earlier and actual file in thirdparty/ffmpeg/libavcodec? )
On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < [email protected]> wrote:
Paul fixed bug preventing tsmuxer from recognizing our lpcm audio stream
I backshoed fix into our ffmpeg 4.4..
I think having it all worked in monthly release quite important, even if names of patches kinda high...
also attached raw pcm-bluenc file as I hacked it, and fix/patch as downloaded from gitweb..
https://github.com/justdan96/tsMuxer/issues/580
https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d 2aead40c1f786c6ad4d343afe0546d..058a1ff9b4cdbd2e1a93acc8bf03 65e7d01cc9f4:/libavcodec/pcm-blurayenc.c
https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb2 78218da7f8c696bf35ede2ba05aa
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
note, even if file named like c file it actually diff..
but both patches as send works for me as after full rebuild.. /
if you (re)move those last two patches from tirdparty/src error (can't find codec..) disappears?
Yes.
but strange. you rebuild cin executable too? (because we link statically I typed "touch cinelerra/new.C" and this forced rebuild of this file and re-linking of executable...)
I do full rebuilds by running "make clean" which deletes all of the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes pretty fast on this laptop and it is not worth the aggravation to only rebuild changed itemsl
does ffmpeg from thirdparty lists pcm_bluray as supported encoder?
It must because what is checked into GIT, lets me choose the lpcm profile and on the bluray player, the info button clearly displays it as lpcm.
try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray
[root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs |
grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < [email protected]> wrote:
On Monday, April 25, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it compiles but fails with error message "open failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file.
strange.
can you double-check patches applied correctly (by comparing pcm-bluenc.c I attached earlier and actual file in thirdparty/ffmpeg/libavcodec? )
On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < [email protected]> wrote:
> Paul fixed bug preventing tsmuxer from recognizing our lpcm audio > stream > > I backshoed fix into our ffmpeg 4.4.. > > I think having it all worked in monthly release quite important, > even if names of patches kinda high... > > also attached raw pcm-bluenc file as I hacked it, and fix/patch as > downloaded from gitweb.. > > https://github.com/justdan96/tsMuxer/issues/580 > > > https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... > > > https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
note, even if file named like c file it actually diff..
but both patches as send works for me as after full rebuild.. /
if you (re)move those last two patches from tirdparty/src error (can't find codec..) disappears?
Yes.
do you have some other libavcodec headers installed? what ldd bin/cin (assuming you run from src root for single user) says?
but strange. you rebuild cin executable too? (because we link statically I typed "touch cinelerra/new.C" and this forced rebuild of this file and re-linking of executable...)
I do full rebuilds by running "make clean" which deletes all of the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes pretty fast on this laptop and it is not worth the aggravation to only rebuild changed itemsl
does ffmpeg from thirdparty lists pcm_bluray as supported encoder?
It must because what is checked into GIT, lets me choose the lpcm profile and on the bluray player, the info button clearly displays it as lpcm.
try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray
[root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs |
grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < [email protected]> wrote:
On Monday, April 25, 2022, Phyllis Smith <[email protected]> wrote:
> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it > compiles but fails with error message "open failed > pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png > file. >
strange.
can you double-check patches applied correctly (by comparing pcm-bluenc.c I attached earlier and actual file in thirdparty/ffmpeg/libavcodec? )
> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < > [email protected]> wrote: > >> Paul fixed bug preventing tsmuxer from recognizing our lpcm audio >> stream >> >> I backshoed fix into our ffmpeg 4.4.. >> >> I think having it all worked in monthly release quite important, >> even if names of patches kinda high... >> >> also attached raw pcm-bluenc file as I hacked it, and fix/patch as >> downloaded from gitweb.. >> >> https://github.com/justdan96/tsMuxer/issues/580 >> >> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >> 058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm- >> blurayenc.c >> >> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >> >
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer. So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that. But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on". Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
note, even if file named like c file it actually diff..
but both patches as send works for me as after full rebuild.. /
if you (re)move those last two patches from tirdparty/src error (can't find codec..) disappears?
Yes.
do you have some other libavcodec headers installed?
what ldd bin/cin (assuming you run from src root for single user) says?
but strange. you rebuild cin executable too? (because we link statically I typed "touch cinelerra/new.C" and this forced rebuild of this file and re-linking of executable...)
I do full rebuilds by running "make clean" which deletes all of the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes pretty fast on this laptop and it is not worth the aggravation to only rebuild changed itemsl
does ffmpeg from thirdparty lists pcm_bluray as supported encoder?
It must because what is checked into GIT, lets me choose the lpcm profile and on the bluray player, the info button clearly displays it as lpcm.
try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray
[root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs |
grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < [email protected]> wrote:
> > > On Monday, April 25, 2022, Phyllis Smith <[email protected]> > wrote: > >> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it >> compiles but fails with error message "open failed >> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file. >> > > strange. > > can you double-check patches applied correctly (by comparing > pcm-bluenc.c I attached earlier and actual file in > thirdparty/ffmpeg/libavcodec? ) > > > >> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >> [email protected]> wrote: >> >>> Paul fixed bug preventing tsmuxer from recognizing our lpcm audio >>> stream >>> >>> I backshoed fix into our ffmpeg 4.4.. >>> >>> I think having it all worked in monthly release quite important, >>> even if names of patches kinda high... >>> >>> also attached raw pcm-bluenc file as I hacked it, and fix/patch as >>> downloaded from gitweb.. >>> >>> https://github.com/justdan96/tsMuxer/issues/580 >>> >>> >>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>> >>> >>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>> >>
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer.
So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that.
actually, up to 7.1 should be supported.. ( I'll look into both issues (sorry for making so slow progress on this)
But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on".
Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis
moment, while on termux I need to multitask between terminal and browser carefully, otherwise one or both will (soft) reset themselves, erasing lates work i had there.. so see you in hopefully 10-15 mins...
On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
note, even if file named like c file it actually diff..
but both patches as send works for me as after full rebuild.. /
if you (re)move those last two patches from tirdparty/src error (can't find codec..) disappears?
Yes.
do you have some other libavcodec headers installed?
what ldd bin/cin (assuming you run from src root for single user) says?
but strange. you rebuild cin executable too? (because we link statically I typed "touch cinelerra/new.C" and this forced rebuild of this file and re-linking of executable...)
I do full rebuilds by running "make clean" which deletes all of the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes pretty fast on this laptop and it is not worth the aggravation to only rebuild changed itemsl
does ffmpeg from thirdparty lists pcm_bluray as supported encoder?
It must because what is checked into GIT, lets me choose the lpcm profile and on the bluray player, the info button clearly displays it as lpcm.
try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray
[root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs |
grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < > [email protected]> wrote: > >> >> >> On Monday, April 25, 2022, Phyllis Smith <[email protected]> >> wrote: >> >>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it >>> compiles but fails with error message "open failed >>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png >>> file. >>> >> >> strange. >> >> can you double-check patches applied correctly (by comparing >> pcm-bluenc.c I attached earlier and actual file in >> thirdparty/ffmpeg/libavcodec? ) >> >> >> >>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>> [email protected]> wrote: >>> >>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm audio >>>> stream >>>> >>>> I backshoed fix into our ffmpeg 4.4.. >>>> >>>> I think having it all worked in monthly release quite important, >>>> even if names of patches kinda high... >>>> >>>> also attached raw pcm-bluenc file as I hacked it, and fix/patch >>>> as downloaded from gitweb.. >>>> >>>> https://github.com/justdan96/tsMuxer/issues/580 >>>> >>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>> 058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm- >>>> blurayenc.c >>>> >>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>> >>>
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer.
So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that. But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on".
Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis
try to add 'use_tsmuxer = 0; at this block? int CreateBD_Thread:: option_presets() { // reset only probed options use_deinterlace = 0; use_scale = Rescale::none; use_resize_tracks = 0; use_wide_audio = 0; use_labeled = 0; use_farmed = 0; in cinelerra/bdcreate.C?
On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
note, even if file named like c file it actually diff..
but both patches as send works for me as after full rebuild.. /
if you (re)move those last two patches from tirdparty/src error (can't find codec..) disappears?
Yes.
do you have some other libavcodec headers installed?
what ldd bin/cin (assuming you run from src root for single user) says?
but strange. you rebuild cin executable too? (because we link statically I typed "touch cinelerra/new.C" and this forced rebuild of this file and re-linking of executable...)
I do full rebuilds by running "make clean" which deletes all of the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes pretty fast on this laptop and it is not worth the aggravation to only rebuild changed itemsl
does ffmpeg from thirdparty lists pcm_bluray as supported encoder?
It must because what is checked into GIT, lets me choose the lpcm profile and on the bluray player, the info button clearly displays it as lpcm.
try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray
[root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs |
grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < > [email protected]> wrote: > >> >> >> On Monday, April 25, 2022, Phyllis Smith <[email protected]> >> wrote: >> >>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it >>> compiles but fails with error message "open failed >>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png >>> file. >>> >> >> strange. >> >> can you double-check patches applied correctly (by comparing >> pcm-bluenc.c I attached earlier and actual file in >> thirdparty/ffmpeg/libavcodec? ) >> >> >> >>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>> [email protected]> wrote: >>> >>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm audio >>>> stream >>>> >>>> I backshoed fix into our ffmpeg 4.4.. >>>> >>>> I think having it all worked in monthly release quite important, >>>> even if names of patches kinda high... >>>> >>>> also attached raw pcm-bluenc file as I hacked it, and fix/patch >>>> as downloaded from gitweb.. >>>> >>>> https://github.com/justdan96/tsMuxer/issues/580 >>>> >>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>> 058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm- >>>> blurayenc.c >>>> >>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>> >>>
Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full rebuild just to make sure). There must be a different spot It is possible that the 5:1 audio limitation is Fedora? On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer.
So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that. But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on".
Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis
try to add 'use_tsmuxer = 0;
at this block?
int CreateBD_Thread:: option_presets() { // reset only probed options use_deinterlace = 0; use_scale = Rescale::none; use_resize_tracks = 0; use_wide_audio = 0; use_labeled = 0; use_farmed = 0;
in cinelerra/bdcreate.C?
On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
note, even if file named like c file it actually diff..
but both patches as send works for me as after full rebuild.. /
if you (re)move those last two patches from tirdparty/src error (can't find codec..) disappears?
Yes.
do you have some other libavcodec headers installed?
what ldd bin/cin (assuming you run from src root for single user) says?
> but strange. you rebuild cin executable too? (because we link > statically I typed "touch cinelerra/new.C" and this forced rebuild of > this file and re-linking of executable...) > I do full rebuilds by running "make clean" which deletes all of the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes pretty fast on this laptop and it is not worth the aggravation to only rebuild changed itemsl
> > does ffmpeg from thirdparty lists pcm_bluray as supported encoder? > It must because what is checked into GIT, lets me choose the lpcm profile and on the bluray player, the info button clearly displays it as lpcm.
try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray
[root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs |
grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
> > > > >> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >> [email protected]> wrote: >> >>> >>> >>> On Monday, April 25, 2022, Phyllis Smith <[email protected]> >>> wrote: >>> >>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and it >>>> compiles but fails with error message "open failed >>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file. >>>> >>> >>> strange. >>> >>> can you double-check patches applied correctly (by comparing >>> pcm-bluenc.c I attached earlier and actual file in >>> thirdparty/ffmpeg/libavcodec? ) >>> >>> >>> >>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm >>>>> audio stream >>>>> >>>>> I backshoed fix into our ffmpeg 4.4.. >>>>> >>>>> I think having it all worked in monthly release quite important, >>>>> even if names of patches kinda high... >>>>> >>>>> also attached raw pcm-bluenc file as I hacked it, and fix/patch >>>>> as downloaded from gitweb.. >>>>> >>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>> >>>>> >>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>> >>>>> >>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>> >>>>
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full rebuild just to make sure). There must be a different spot It is possible that the 5:1 audio limitation is Fedora?
no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back .... try attached patches? one is for thirdparty/src another for cin herself..
On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer.
So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that. But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on".
Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis
try to add 'use_tsmuxer = 0;
at this block?
int CreateBD_Thread:: option_presets() { // reset only probed options use_deinterlace = 0; use_scale = Rescale::none; use_resize_tracks = 0; use_wide_audio = 0; use_labeled = 0; use_farmed = 0;
in cinelerra/bdcreate.C?
On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
note, even if file named like c file it actually diff..
but both patches as send works for me as after full rebuild.. /
if you (re)move those last two patches from tirdparty/src error (can't find codec..) disappears?
Yes.
do you have some other libavcodec headers installed?
what ldd bin/cin (assuming you run from src root for single user) says?
>> but strange. you rebuild cin executable too? (because we link >> statically I typed "touch cinelerra/new.C" and this forced rebuild of >> this file and re-linking of executable...) >> > I do full rebuilds by running "make clean" which deletes all of the > thirdparty libraries and then do a full rebuild with "./bld.sh". Goes > pretty fast on this laptop and it is not worth the aggravation to only > rebuild changed itemsl > >> >> does ffmpeg from thirdparty lists pcm_bluray as supported encoder? >> > It must because what is checked into GIT, lets me choose the lpcm > profile and on the bluray player, the info button clearly displays it as > lpcm. >
try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray
[root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs
| grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
> >> >> >> >> >>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>> [email protected]> wrote: >>> >>>> >>>> >>>> On Monday, April 25, 2022, Phyllis Smith <[email protected]> >>>> wrote: >>>> >>>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and >>>>> it compiles but fails with error message "open failed >>>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached >>>>> png file. >>>>> >>>> >>>> strange. >>>> >>>> can you double-check patches applied correctly (by comparing >>>> pcm-bluenc.c I attached earlier and actual file in >>>> thirdparty/ffmpeg/libavcodec? ) >>>> >>>> >>>> >>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>> [email protected]> wrote: >>>>> >>>>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm >>>>>> audio stream >>>>>> >>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>> >>>>>> I think having it all worked in monthly release quite >>>>>> important, even if names of patches kinda high... >>>>>> >>>>>> also attached raw pcm-bluenc file as I hacked it, and fix/patch >>>>>> as downloaded from gitweb.. >>>>>> >>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>> >>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >>>>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>>>> 058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm- >>>>>> blurayenc.c >>>>>> >>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>>>> >>>>>
Andrew, I am getting loopy and will have to quit for today. Patch 999a not getting applied correctly in the build but I will figure it out tomorrow morning. On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full rebuild just to make sure). There must be a different spot It is possible that the 5:1 audio limitation is Fedora?
no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back ....
try attached patches? one is for thirdparty/src another for cin herself..
On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer.
So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that. But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on".
Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis
try to add 'use_tsmuxer = 0;
at this block?
int CreateBD_Thread:: option_presets() { // reset only probed options use_deinterlace = 0; use_scale = Rescale::none; use_resize_tracks = 0; use_wide_audio = 0; use_labeled = 0; use_farmed = 0;
in cinelerra/bdcreate.C?
On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
> > note, even if file named like c file it actually diff.. > > but both patches as send works for me as after full rebuild.. > / > > if you (re)move those last two patches from tirdparty/src error > (can't find codec..) disappears? > Yes.
do you have some other libavcodec headers installed?
what ldd bin/cin (assuming you run from src root for single user) says?
> >>> but strange. you rebuild cin executable too? (because we link >>> statically I typed "touch cinelerra/new.C" and this forced rebuild of >>> this file and re-linking of executable...) >>> >> I do full rebuilds by running "make clean" which deletes all of the >> thirdparty libraries and then do a full rebuild with "./bld.sh". Goes >> pretty fast on this laptop and it is not worth the aggravation to only >> rebuild changed itemsl >> >>> >>> does ffmpeg from thirdparty lists pcm_bluray as supported encoder? >>> >> It must because what is checked into GIT, lets me choose the lpcm >> profile and on the bluray player, the info button clearly displays it as >> lpcm. >> > > try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray > > [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
> > >> >>> >>> >>> >>> >>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>> [email protected]> wrote: >>>>> >>>>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and >>>>>> it compiles but fails with error message "open failed >>>>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file. >>>>>> >>>>> >>>>> strange. >>>>> >>>>> can you double-check patches applied correctly (by comparing >>>>> pcm-bluenc.c I attached earlier and actual file in >>>>> thirdparty/ffmpeg/libavcodec? ) >>>>> >>>>> >>>>> >>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm >>>>>>> audio stream >>>>>>> >>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>> >>>>>>> I think having it all worked in monthly release quite >>>>>>> important, even if names of patches kinda high... >>>>>>> >>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>> fix/patch as downloaded from gitweb.. >>>>>>> >>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>> >>>>>>> >>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>> >>>>>>> >>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>> >>>>>>
Andrew, the patch.999a was getting applied before patch_99 so when I renamed it, the build took. Initial test shows that that fixed the 5:1 audio which is now working. I will have to create real bluray media and test that tomorrow to determine if tsmuxer and profile selection are getting correctly reset. Thank you. On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full rebuild just to make sure). There must be a different spot It is possible that the 5:1 audio limitation is Fedora?
no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back ....
try attached patches? one is for thirdparty/src another for cin herself..
On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer.
So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that. But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on".
Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis
try to add 'use_tsmuxer = 0;
at this block?
int CreateBD_Thread:: option_presets() { // reset only probed options use_deinterlace = 0; use_scale = Rescale::none; use_resize_tracks = 0; use_wide_audio = 0; use_labeled = 0; use_farmed = 0;
in cinelerra/bdcreate.C?
On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
> > note, even if file named like c file it actually diff.. > > but both patches as send works for me as after full rebuild.. > / > > if you (re)move those last two patches from tirdparty/src error > (can't find codec..) disappears? > Yes.
do you have some other libavcodec headers installed?
what ldd bin/cin (assuming you run from src root for single user) says?
> >>> but strange. you rebuild cin executable too? (because we link >>> statically I typed "touch cinelerra/new.C" and this forced rebuild of >>> this file and re-linking of executable...) >>> >> I do full rebuilds by running "make clean" which deletes all of the >> thirdparty libraries and then do a full rebuild with "./bld.sh". Goes >> pretty fast on this laptop and it is not worth the aggravation to only >> rebuild changed itemsl >> >>> >>> does ffmpeg from thirdparty lists pcm_bluray as supported encoder? >>> >> It must because what is checked into GIT, lets me choose the lpcm >> profile and on the bluray player, the info button clearly displays it as >> lpcm. >> > > try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray > > [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
> > >> >>> >>> >>> >>> >>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>> [email protected]> wrote: >>>>> >>>>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and >>>>>> it compiles but fails with error message "open failed >>>>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file. >>>>>> >>>>> >>>>> strange. >>>>> >>>>> can you double-check patches applied correctly (by comparing >>>>> pcm-bluenc.c I attached earlier and actual file in >>>>> thirdparty/ffmpeg/libavcodec? ) >>>>> >>>>> >>>>> >>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm >>>>>>> audio stream >>>>>>> >>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>> >>>>>>> I think having it all worked in monthly release quite >>>>>>> important, even if names of patches kinda high... >>>>>>> >>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>> fix/patch as downloaded from gitweb.. >>>>>>> >>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>> >>>>>>> >>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>> >>>>>>> >>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>> >>>>>>
Much better - now tsmuxer and profile value seem to be reset appropriately. But now tsmuxer error: tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.2% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-090605/bd.m2ts On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full rebuild just to make sure). There must be a different spot It is possible that the 5:1 audio limitation is Fedora?
no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back ....
try attached patches? one is for thirdparty/src another for cin herself..
On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer.
So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that. But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on".
Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis
try to add 'use_tsmuxer = 0;
at this block?
int CreateBD_Thread:: option_presets() { // reset only probed options use_deinterlace = 0; use_scale = Rescale::none; use_resize_tracks = 0; use_wide_audio = 0; use_labeled = 0; use_farmed = 0;
in cinelerra/bdcreate.C?
On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.
> > note, even if file named like c file it actually diff.. > > but both patches as send works for me as after full rebuild.. > / > > if you (re)move those last two patches from tirdparty/src error > (can't find codec..) disappears? > Yes.
do you have some other libavcodec headers installed?
what ldd bin/cin (assuming you run from src root for single user) says?
> >>> but strange. you rebuild cin executable too? (because we link >>> statically I typed "touch cinelerra/new.C" and this forced rebuild of >>> this file and re-linking of executable...) >>> >> I do full rebuilds by running "make clean" which deletes all of the >> thirdparty libraries and then do a full rebuild with "./bld.sh". Goes >> pretty fast on this laptop and it is not worth the aggravation to only >> rebuild changed itemsl >> >>> >>> does ffmpeg from thirdparty lists pcm_bluray as supported encoder? >>> >> It must because what is checked into GIT, lets me choose the lpcm >> profile and on the bluray player, the info button clearly displays it as >> lpcm. >> > > try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray > > [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media
> > >> >>> >>> >>> >>> >>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>> [email protected]> wrote: >>>>> >>>>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and >>>>>> it compiles but fails with error message "open failed >>>>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file. >>>>>> >>>>> >>>>> strange. >>>>> >>>>> can you double-check patches applied correctly (by comparing >>>>> pcm-bluenc.c I attached earlier and actual file in >>>>> thirdparty/ffmpeg/libavcodec? ) >>>>> >>>>> >>>>> >>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm >>>>>>> audio stream >>>>>>> >>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>> >>>>>>> I think having it all worked in monthly release quite >>>>>>> important, even if names of patches kinda high... >>>>>>> >>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>> fix/patch as downloaded from gitweb.. >>>>>>> >>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>> >>>>>>> >>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>> >>>>>>> >>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>> >>>>>>
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Much better - now tsmuxer and profile value seem to be reset appropriately. But now tsmuxer error:
tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.2% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-090605/bd.m2ts
can you provide example stream for tsmuxer's developers? https://github.com/justdan96/tsMuxer/issues I can enter issue for you, just need link to file in question...
On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full rebuild just to make sure). There must be a different spot It is possible that the 5:1 audio limitation is Fedora?
no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back ....
try attached patches? one is for thirdparty/src another for cin herself..
On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer.
So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that. But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on".
Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis
try to add 'use_tsmuxer = 0;
at this block?
int CreateBD_Thread:: option_presets() { // reset only probed options use_deinterlace = 0; use_scale = Rescale::none; use_resize_tracks = 0; use_wide_audio = 0; use_labeled = 0; use_farmed = 0;
in cinelerra/bdcreate.C?
On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> wrote:
> Andrew, if instead of choosing lpcm as the profile with the 2 > patches in, I choose the standard bluray, it works. > >> >> note, even if file named like c file it actually diff.. >> >> but both patches as send works for me as after full rebuild.. >> / >> >> if you (re)move those last two patches from tirdparty/src error >> (can't find codec..) disappears? >> > Yes. >
do you have some other libavcodec headers installed?
what ldd bin/cin (assuming you run from src root for single user) says?
>> >>>> but strange. you rebuild cin executable too? (because we link >>>> statically I typed "touch cinelerra/new.C" and this forced rebuild of >>>> this file and re-linking of executable...) >>>> >>> I do full rebuilds by running "make clean" which deletes all of >>> the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes >>> pretty fast on this laptop and it is not worth the aggravation to only >>> rebuild changed itemsl >>> >>>> >>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>> encoder? >>>> >>> It must because what is checked into GIT, lets me choose the lpcm >>> profile and on the bluray player, the info button clearly displays it as >>> lpcm. >>> >> >> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >> >> [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg > -codecs | grep bluray > DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for > Blu-ray media > > >> >> >>> >>>> >>>> >>>> >>>> >>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 and >>>>>>> it compiles but fails with error message "open failed >>>>>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached >>>>>>> png file. >>>>>>> >>>>>> >>>>>> strange. >>>>>> >>>>>> can you double-check patches applied correctly (by comparing >>>>>> pcm-bluenc.c I attached earlier and actual file in >>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>> >>>>>> >>>>>> >>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm >>>>>>>> audio stream >>>>>>>> >>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>> >>>>>>>> I think having it all worked in monthly release quite >>>>>>>> important, even if names of patches kinda high... >>>>>>>> >>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>> >>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>> >>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >>>>>>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>>>>>> 058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm- >>>>>>>> blurayenc.c >>>>>>>> >>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>>>>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>>>>>> >>>>>>>
The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably came from: https://test-videos.co.uk/bigbuckbunny/mkv Meanwhile I will try a different file -- I use bbb because it is bigger than most of my test cases and then is still only 10 minutes long. On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Much better - now tsmuxer and profile value seem to be reset appropriately. But now tsmuxer error:
tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.2% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-090605/bd.m2ts
can you provide example stream for tsmuxer's developers? https://github.com/justdan96/tsMuxer/issues
I can enter issue for you, just need link to file in question...
On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full rebuild just to make sure). There must be a different spot It is possible that the 5:1 audio limitation is Fedora?
no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back ....
try attached patches? one is for thirdparty/src another for cin herself..
On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, 10 million "mega" tests later, I finally figured it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to "Bluray" for profile and "no tsmuxer" for tsmuxer.
So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported* which is fine as long as I document that. But then I would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked and lpcm was not highlighted, I thought is should work and it did not because both LPCM and TSMUXER will still "on".
Since I am not sure if I can get it right, could you provide the lines of code to change so that the profile and tsmuxer are reset to default "not on" values every time BD Render is chosen from the File pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis
try to add 'use_tsmuxer = 0;
at this block?
int CreateBD_Thread:: option_presets() { // reset only probed options use_deinterlace = 0; use_scale = Rescale::none; use_resize_tracks = 0; use_wide_audio = 0; use_labeled = 0; use_farmed = 0;
in cinelerra/bdcreate.C?
On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < [email protected]> wrote:
> > > On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> > wrote: > >> Andrew, if instead of choosing lpcm as the profile with the 2 >> patches in, I choose the standard bluray, it works. >> >>> >>> note, even if file named like c file it actually diff.. >>> >>> but both patches as send works for me as after full rebuild.. >>> / >>> >>> if you (re)move those last two patches from tirdparty/src error >>> (can't find codec..) disappears? >>> >> Yes. >> > > > do you have some other libavcodec headers installed? > > what ldd bin/cin (assuming you run from src root for single user) > says? > > > >>> >>>>> but strange. you rebuild cin executable too? (because we link >>>>> statically I typed "touch cinelerra/new.C" and this forced rebuild of >>>>> this file and re-linking of executable...) >>>>> >>>> I do full rebuilds by running "make clean" which deletes all of >>>> the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes >>>> pretty fast on this laptop and it is not worth the aggravation to only >>>> rebuild changed itemsl >>>> >>>>> >>>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>>> encoder? >>>>> >>>> It must because what is checked into GIT, lets me choose the lpcm >>>> profile and on the bluray player, the info button clearly displays it as >>>> lpcm. >>>> >>> >>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>> >>> [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg >> -codecs | grep bluray >> DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for >> Blu-ray media >> >> >>> >>> >>>> >>>>> >>>>> >>>>> >>>>> >>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 >>>>>>>> and it compiles but fails with error message "open failed >>>>>>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file. >>>>>>>> >>>>>>> >>>>>>> strange. >>>>>>> >>>>>>> can you double-check patches applied correctly (by comparing >>>>>>> pcm-bluenc.c I attached earlier and actual file in >>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm >>>>>>>>> audio stream >>>>>>>>> >>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>> >>>>>>>>> I think having it all worked in monthly release quite >>>>>>>>> important, even if names of patches kinda high... >>>>>>>>> >>>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>>> >>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>> >>>>>>>>> >>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>>>> >>>>>>>>> >>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>>>> >>>>>>>>
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably came from: https://test-videos.co.uk/bigbuckbunny/mkv
Meanwhile I will try a different file -- I use bbb because it is bigger than most of my test cases and then is still only 10 minutes long.
I think most tsmuxer users use it from win/mac.... so, our linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit some less-known codepath.. so if you can upload resultant m2ts file somewhere I'll link it into issue, because this is what usually asked tehre - problematic ts file to look at.. .. If you can prepare appimage with all those patches applied may be someone will test it on Linux too, but I do not hold my breath for this...
On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Much better - now tsmuxer and profile value seem to be reset appropriately. But now tsmuxer error:
tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.2% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-090605/bd.m2ts
can you provide example stream for tsmuxer's developers? https://github.com/justdan96/tsMuxer/issues
I can enter issue for you, just need link to file in question...
On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full rebuild just to make sure). There must be a different spot It is possible that the 5:1 audio limitation is Fedora?
no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back ....
try attached patches? one is for thirdparty/src another for cin herself..
On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
> Andrew, 10 million "mega" tests later, I finally figured it out. > Neither the chosen "Profile" or "tsmuxer" setting is getting reset to > "Bluray" for profile and "no tsmuxer" for tsmuxer. > > So what was happening is I loaded a file with 5:1 audio, chose LPCM > and TSMUXER and the error message of: > * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' > is not supported* > which is fine as long as I document that. But then I would load Big > Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not checked > and lpcm was not highlighted, I thought is should work and it did not > because both LPCM and TSMUXER will still "on". > > Since I am not sure if I can get it right, could you provide the > lines of code to change so that the profile and tsmuxer are reset to > default "not on" values every time BD Render is chosen from the File > pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >
try to add 'use_tsmuxer = 0;
at this block?
int CreateBD_Thread:: option_presets() { // reset only probed options use_deinterlace = 0; use_scale = Rescale::none; use_resize_tracks = 0; use_wide_audio = 0; use_labeled = 0; use_farmed = 0;
in cinelerra/bdcreate.C?
> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < > [email protected]> wrote: > >> >> >> On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> >> wrote: >> >>> Andrew, if instead of choosing lpcm as the profile with the 2 >>> patches in, I choose the standard bluray, it works. >>> >>>> >>>> note, even if file named like c file it actually diff.. >>>> >>>> but both patches as send works for me as after full rebuild.. >>>> / >>>> >>>> if you (re)move those last two patches from tirdparty/src error >>>> (can't find codec..) disappears? >>>> >>> Yes. >>> >> >> >> do you have some other libavcodec headers installed? >> >> what ldd bin/cin (assuming you run from src root for single user) >> says? >> >> >> >>>> >>>>>> but strange. you rebuild cin executable too? (because we link >>>>>> statically I typed "touch cinelerra/new.C" and this forced rebuild of >>>>>> this file and re-linking of executable...) >>>>>> >>>>> I do full rebuilds by running "make clean" which deletes all of >>>>> the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes >>>>> pretty fast on this laptop and it is not worth the aggravation to only >>>>> rebuild changed itemsl >>>>> >>>>>> >>>>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>>>> encoder? >>>>>> >>>>> It must because what is checked into GIT, lets me choose the >>>>> lpcm profile and on the bluray player, the info button clearly displays it >>>>> as lpcm. >>>>> >>>> >>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>> >>>> [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg >>> -codecs | grep bluray >>> DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian >>> for Blu-ray media >>> >>> >>>> >>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 >>>>>>>>> and it compiles but fails with error message "open failed >>>>>>>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the >>>>>>>>> attached png file. >>>>>>>>> >>>>>>>> >>>>>>>> strange. >>>>>>>> >>>>>>>> can you double-check patches applied correctly (by comparing >>>>>>>> pcm-bluenc.c I attached earlier and actual file in >>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing our lpcm >>>>>>>>>> audio stream >>>>>>>>>> >>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>> >>>>>>>>>> I think having it all worked in monthly release quite >>>>>>>>>> important, even if names of patches kinda high... >>>>>>>>>> >>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>>>> >>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>> >>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >>>>>>>>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>>>>>>>> 058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm- >>>>>>>>>> blurayenc.c >>>>>>>>>> >>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>>>>>>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>>>>>>>> >>>>>>>>>
The 30 second and 1 minute 30 second files worked. So I think the last 2 patches are good. I am just going to see if I can put the 99 and 999a patch in 1 file and test that. If that goes well, I think I can check it into GIT. I will prepare an appimage and upload the files as you requested but it will not be done until later this evening. On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably came from: https://test-videos.co.uk/bigbuckbunny/mkv
Meanwhile I will try a different file -- I use bbb because it is bigger than most of my test cases and then is still only 10 minutes long.
I think most tsmuxer users use it from win/mac.... so, our linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit some less-known codepath.. so if you can upload resultant m2ts file somewhere I'll link it into issue, because this is what usually asked tehre - problematic ts file to look at.. ..
If you can prepare appimage with all those patches applied may be someone will test it on Linux too, but I do not hold my breath for this...
On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Much better - now tsmuxer and profile value seem to be reset appropriately. But now tsmuxer error:
tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.2% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-090605/bd.m2ts
can you provide example stream for tsmuxer's developers? https://github.com/justdan96/tsMuxer/issues
I can enter issue for you, just need link to file in question...
On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full rebuild just to make sure). There must be a different spot It is possible that the 5:1 audio limitation is Fedora?
no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back ....
try attached patches? one is for thirdparty/src another for cin herself..
On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < [email protected]> wrote:
> > > On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> > wrote: > >> Andrew, 10 million "mega" tests later, I finally figured it out. >> Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >> "Bluray" for profile and "no tsmuxer" for tsmuxer. >> >> So what was happening is I loaded a file with 5:1 audio, chose LPCM >> and TSMUXER and the error message of: >> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' >> is not supported* >> which is fine as long as I document that. But then I would load >> Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >> checked and lpcm was not highlighted, I thought is should work and it did >> not because both LPCM and TSMUXER will still "on". >> >> Since I am not sure if I can get it right, could you provide the >> lines of code to change so that the profile and tsmuxer are reset to >> default "not on" values every time BD Render is chosen from the File >> pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >> > > > > try to add 'use_tsmuxer = 0; > > at this block? > > int CreateBD_Thread:: > option_presets() > { > // reset only probed options > use_deinterlace = 0; > use_scale = Rescale::none; > use_resize_tracks = 0; > use_wide_audio = 0; > use_labeled = 0; > use_farmed = 0; > > in cinelerra/bdcreate.C? > > > >> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >> [email protected]> wrote: >> >>> >>> >>> On Tuesday, April 26, 2022, Phyllis Smith <[email protected]> >>> wrote: >>> >>>> Andrew, if instead of choosing lpcm as the profile with the 2 >>>> patches in, I choose the standard bluray, it works. >>>> >>>>> >>>>> note, even if file named like c file it actually diff.. >>>>> >>>>> but both patches as send works for me as after full rebuild.. >>>>> / >>>>> >>>>> if you (re)move those last two patches from tirdparty/src error >>>>> (can't find codec..) disappears? >>>>> >>>> Yes. >>>> >>> >>> >>> do you have some other libavcodec headers installed? >>> >>> what ldd bin/cin (assuming you run from src root for single user) >>> says? >>> >>> >>> >>>>> >>>>>>> but strange. you rebuild cin executable too? (because we link >>>>>>> statically I typed "touch cinelerra/new.C" and this forced rebuild of >>>>>>> this file and re-linking of executable...) >>>>>>> >>>>>> I do full rebuilds by running "make clean" which deletes all of >>>>>> the thirdparty libraries and then do a full rebuild with "./bld.sh". Goes >>>>>> pretty fast on this laptop and it is not worth the aggravation to only >>>>>> rebuild changed itemsl >>>>>> >>>>>>> >>>>>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>>>>> encoder? >>>>>>> >>>>>> It must because what is checked into GIT, lets me choose the >>>>>> lpcm profile and on the bluray player, the info button clearly displays it >>>>>> as lpcm. >>>>>> >>>>> >>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>> >>>>> [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg >>>> -codecs | grep bluray >>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian >>>> for Blu-ray media >>>> >>>> >>>>> >>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 >>>>>>>>>> and it compiles but fails with error message "open failed >>>>>>>>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png file. >>>>>>>>>> >>>>>>>>> >>>>>>>>> strange. >>>>>>>>> >>>>>>>>> can you double-check patches applied correctly (by comparing >>>>>>>>> pcm-bluenc.c I attached earlier and actual file in >>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing our >>>>>>>>>>> lpcm audio stream >>>>>>>>>>> >>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>> >>>>>>>>>>> I think having it all worked in monthly release quite >>>>>>>>>>> important, even if names of patches kinda high... >>>>>>>>>>> >>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>>>>> >>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>>>>>> >>>>>>>>>>
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The 30 second and 1 minute 30 second files worked. So I think the last 2 patches are good. I am just going to see if I can put the 99 and 999a patch in 1 file and test that. If that goes well, I think I can check it into GIT.
yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) while preparing patches. Hopefully wider testing will show if I get channel order right or there is some need for moving audio tracks into specific configuration... {not sure if this covered in manual}
I will prepare an appimage and upload the files as you requested but it will not be done until later this evening.
thanks a lot!
On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably came from: https://test-videos.co.uk/bigbuckbunny/mkv
Meanwhile I will try a different file -- I use bbb because it is bigger than most of my test cases and then is still only 10 minutes long.
I think most tsmuxer users use it from win/mac.... so, our linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit some less-known codepath.. so if you can upload resultant m2ts file somewhere I'll link it into issue, because this is what usually asked tehre - problematic ts file to look at.. ..
If you can prepare appimage with all those patches applied may be someone will test it on Linux too, but I do not hold my breath for this...
On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Much better - now tsmuxer and profile value seem to be reset appropriately. But now tsmuxer error:
tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.2% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-090605/bd.m2ts
can you provide example stream for tsmuxer's developers? https://github.com/justdan96/tsMuxer/issues
I can enter issue for you, just need link to file in question...
On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did full > rebuild just to make sure). There must be a different spot > It is possible that the 5:1 audio limitation is Fedora? >
no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back ....
try attached patches? one is for thirdparty/src another for cin herself..
> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < > [email protected]> wrote: > >> >> >> On Wednesday, April 27, 2022, Phyllis Smith < >> [email protected]> wrote: >> >>> Andrew, 10 million "mega" tests later, I finally figured it out. >>> Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >>> "Bluray" for profile and "no tsmuxer" for tsmuxer. >>> >>> So what was happening is I loaded a file with 5:1 audio, chose >>> LPCM and TSMUXER and the error message of: >>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' >>> is not supported* >>> which is fine as long as I document that. But then I would load >>> Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >>> checked and lpcm was not highlighted, I thought is should work and it did >>> not because both LPCM and TSMUXER will still "on". >>> >>> Since I am not sure if I can get it right, could you provide the >>> lines of code to change so that the profile and tsmuxer are reset to >>> default "not on" values every time BD Render is chosen from the File >>> pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >>> >> >> >> >> try to add 'use_tsmuxer = 0; >> >> at this block? >> >> int CreateBD_Thread:: >> option_presets() >> { >> // reset only probed options >> use_deinterlace = 0; >> use_scale = Rescale::none; >> use_resize_tracks = 0; >> use_wide_audio = 0; >> use_labeled = 0; >> use_farmed = 0; >> >> in cinelerra/bdcreate.C? >> >> >> >>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>> [email protected]> wrote: >>> >>>> >>>> >>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>> [email protected]> wrote: >>>> >>>>> Andrew, if instead of choosing lpcm as the profile with the 2 >>>>> patches in, I choose the standard bluray, it works. >>>>> >>>>>> >>>>>> note, even if file named like c file it actually diff.. >>>>>> >>>>>> but both patches as send works for me as after full rebuild.. >>>>>> / >>>>>> >>>>>> if you (re)move those last two patches from tirdparty/src error >>>>>> (can't find codec..) disappears? >>>>>> >>>>> Yes. >>>>> >>>> >>>> >>>> do you have some other libavcodec headers installed? >>>> >>>> what ldd bin/cin (assuming you run from src root for single user) >>>> says? >>>> >>>> >>>> >>>>>> >>>>>>>> but strange. you rebuild cin executable too? (because we link >>>>>>>> statically I typed "touch cinelerra/new.C" and this forced rebuild of >>>>>>>> this file and re-linking of executable...) >>>>>>>> >>>>>>> I do full rebuilds by running "make clean" which deletes all >>>>>>> of the thirdparty libraries and then do a full rebuild with "./bld.sh". >>>>>>> Goes pretty fast on this laptop and it is not worth the aggravation to only >>>>>>> rebuild changed itemsl >>>>>>> >>>>>>>> >>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>>>>>> encoder? >>>>>>>> >>>>>>> It must because what is checked into GIT, lets me choose the >>>>>>> lpcm profile and on the bluray player, the info button clearly displays it >>>>>>> as lpcm. >>>>>>> >>>>>> >>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>> >>>>>> [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg >>>>> -codecs | grep bluray >>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian >>>>> for Blu-ray media >>>>> >>>>> >>>>>> >>>>>> >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and ffmpeg-4.4.patch99 >>>>>>>>>>> and it compiles but fails with error message "open failed >>>>>>>>>>> pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the >>>>>>>>>>> attached png file. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> strange. >>>>>>>>>> >>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing our >>>>>>>>>>>> lpcm audio stream >>>>>>>>>>>> >>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>> >>>>>>>>>>>> I think having it all worked in monthly release quite >>>>>>>>>>>> important, even if names of patches kinda high... >>>>>>>>>>>> >>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>>>>>> >>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>> >>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >>>>>>>>>>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>>>>>>>>>> 058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm- >>>>>>>>>>>> blurayenc.c >>>>>>>>>>>> >>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>>>>>>>>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>>>>>>>>>> >>>>>>>>>>>
Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test file - are at: https://cinelerra-gg.org/download/testing/tsmuxer_problem_files.tar My guess of whether or not they will execute the AppImage (link below) is below 1% probability: https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The 30 second and 1 minute 30 second files worked. So I think the last 2 patches are good. I am just going to see if I can put the 99 and 999a patch in 1 file and test that. If that goes well, I think I can check it into GIT.
yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) while preparing patches. Hopefully wider testing will show if I get channel order right or there is some need for moving audio tracks into specific configuration... {not sure if this covered in manual}
I will prepare an appimage and upload the files as you requested but it will not be done until later this evening.
thanks a lot!
On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably came from: https://test-videos.co.uk/bigbuckbunny/mkv
Meanwhile I will try a different file -- I use bbb because it is bigger than most of my test cases and then is still only 10 minutes long.
I think most tsmuxer users use it from win/mac.... so, our linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit some less-known codepath.. so if you can upload resultant m2ts file somewhere I'll link it into issue, because this is what usually asked tehre - problematic ts file to look at.. ..
If you can prepare appimage with all those patches applied may be someone will test it on Linux too, but I do not hold my breath for this...
On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
Much better - now tsmuxer and profile value seem to be reset appropriately. But now tsmuxer error:
tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.2% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-090605/bd.m2ts
can you provide example stream for tsmuxer's developers? https://github.com/justdan96/tsMuxer/issues
I can enter issue for you, just need link to file in question...
On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < [email protected]> wrote:
> > > On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> > wrote: > >> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did >> full rebuild just to make sure). There must be a different spot >> It is possible that the 5:1 audio limitation is Fedora? >> > > no, just diff between av_ch_layout_5point1 and > av_ch_layout_5point1_back .... > > > try attached patches? one is for thirdparty/src another for cin > herself.. > > > >> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >> [email protected]> wrote: >> >>> >>> >>> On Wednesday, April 27, 2022, Phyllis Smith < >>> [email protected]> wrote: >>> >>>> Andrew, 10 million "mega" tests later, I finally figured it out. >>>> Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >>>> "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>> >>>> So what was happening is I loaded a file with 5:1 audio, chose >>>> LPCM and TSMUXER and the error message of: >>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout >>>> '5.1' is not supported* >>>> which is fine as long as I document that. But then I would load >>>> Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >>>> checked and lpcm was not highlighted, I thought is should work and it did >>>> not because both LPCM and TSMUXER will still "on". >>>> >>>> Since I am not sure if I can get it right, could you provide the >>>> lines of code to change so that the profile and tsmuxer are reset to >>>> default "not on" values every time BD Render is chosen from the File >>>> pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >>>> >>> >>> >>> >>> try to add 'use_tsmuxer = 0; >>> >>> at this block? >>> >>> int CreateBD_Thread:: >>> option_presets() >>> { >>> // reset only probed options >>> use_deinterlace = 0; >>> use_scale = Rescale::none; >>> use_resize_tracks = 0; >>> use_wide_audio = 0; >>> use_labeled = 0; >>> use_farmed = 0; >>> >>> in cinelerra/bdcreate.C? >>> >>> >>> >>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>> [email protected]> wrote: >>>>> >>>>>> Andrew, if instead of choosing lpcm as the profile with the 2 >>>>>> patches in, I choose the standard bluray, it works. >>>>>> >>>>>>> >>>>>>> note, even if file named like c file it actually diff.. >>>>>>> >>>>>>> but both patches as send works for me as after full rebuild.. >>>>>>> / >>>>>>> >>>>>>> if you (re)move those last two patches from tirdparty/src >>>>>>> error (can't find codec..) disappears? >>>>>>> >>>>>> Yes. >>>>>> >>>>> >>>>> >>>>> do you have some other libavcodec headers installed? >>>>> >>>>> what ldd bin/cin (assuming you run from src root for single >>>>> user) says? >>>>> >>>>> >>>>> >>>>>>> >>>>>>>>> but strange. you rebuild cin executable too? (because we >>>>>>>>> link statically I typed "touch cinelerra/new.C" and this forced rebuild >>>>>>>>> of this file and re-linking of executable...) >>>>>>>>> >>>>>>>> I do full rebuilds by running "make clean" which deletes all >>>>>>>> of the thirdparty libraries and then do a full rebuild with "./bld.sh". >>>>>>>> Goes pretty fast on this laptop and it is not worth the aggravation to only >>>>>>>> rebuild changed itemsl >>>>>>>> >>>>>>>>> >>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>>>>>>> encoder? >>>>>>>>> >>>>>>>> It must because what is checked into GIT, lets me choose the >>>>>>>> lpcm profile and on the bluray player, the info button clearly displays it >>>>>>>> as lpcm. >>>>>>>> >>>>>>> >>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>> >>>>>>> [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg >>>>>> -codecs | grep bluray >>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian >>>>>> for Blu-ray media >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png >>>>>>>>>>>> file. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> strange. >>>>>>>>>>> >>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing our >>>>>>>>>>>>> lpcm audio stream >>>>>>>>>>>>> >>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>> >>>>>>>>>>>>> I think having it all worked in monthly release quite >>>>>>>>>>>>> important, even if names of patches kinda high... >>>>>>>>>>>>> >>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>>>>>>> >>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>>>>>>>> >>>>>>>>>>>>
thanks! can you also specify exact tsmuxer commit/archive you used? for me it showed some git digits in version, but for your it was just saying '-dev' On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test file - are at: https://cinelerra-gg.org/download/testing/tsmuxer_problem_files.tar My guess of whether or not they will execute the AppImage (link below) is below 1% probability: https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage
On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The 30 second and 1 minute 30 second files worked. So I think the last 2 patches are good. I am just going to see if I can put the 99 and 999a patch in 1 file and test that. If that goes well, I think I can check it into GIT.
yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) while preparing patches. Hopefully wider testing will show if I get channel order right or there is some need for moving audio tracks into specific configuration... {not sure if this covered in manual}
I will prepare an appimage and upload the files as you requested but it will not be done until later this evening.
thanks a lot!
On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably came from: https://test-videos.co.uk/bigbuckbunny/mkv
Meanwhile I will try a different file -- I use bbb because it is bigger than most of my test cases and then is still only 10 minutes long.
I think most tsmuxer users use it from win/mac.... so, our linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit some less-known codepath.. so if you can upload resultant m2ts file somewhere I'll link it into issue, because this is what usually asked tehre - problematic ts file to look at.. ..
If you can prepare appimage with all those patches applied may be someone will test it on Linux too, but I do not hold my breath for this...
On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
> Much better - now tsmuxer and profile value seem to be reset > appropriately. > But now tsmuxer error: > > tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer > Decoding H264 stream (track 1): Profile: [email protected] Resolution: > 1920:1080i Frame rate: 29.97 > H.264 muxing fps is not set. Get fps from stream. Value: 29.97 > 0.0% complete > Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: > 48KHz Channels: 5.1 Bits per sample: 16bit > 18.2% complete > Finalize ISO disk > Reading buffer overflow. Possible container streams are not > syncronized. Please, verify stream fps. File name: > /tmp/bd_20220427-090605/bd.m2ts >
can you provide example stream for tsmuxer's developers? https://github.com/justdan96/tsMuxer/issues
I can enter issue for you, just need link to file in question...
> On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < > [email protected]> wrote: > >> >> >> On Wednesday, April 27, 2022, Phyllis Smith < >> [email protected]> wrote: >> >>> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did >>> full rebuild just to make sure). There must be a different spot >>> It is possible that the 5:1 audio limitation is Fedora? >>> >> >> no, just diff between av_ch_layout_5point1 and >> av_ch_layout_5point1_back .... >> >> >> try attached patches? one is for thirdparty/src another for cin >> herself.. >> >> >> >>> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >>> [email protected]> wrote: >>> >>>> >>>> >>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>> [email protected]> wrote: >>>> >>>>> Andrew, 10 million "mega" tests later, I finally figured it >>>>> out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >>>>> "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>>> >>>>> So what was happening is I loaded a file with 5:1 audio, chose >>>>> LPCM and TSMUXER and the error message of: >>>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout >>>>> '5.1' is not supported* >>>>> which is fine as long as I document that. But then I would load >>>>> Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >>>>> checked and lpcm was not highlighted, I thought is should work and it did >>>>> not because both LPCM and TSMUXER will still "on". >>>>> >>>>> Since I am not sure if I can get it right, could you provide the >>>>> lines of code to change so that the profile and tsmuxer are reset to >>>>> default "not on" values every time BD Render is chosen from the File >>>>> pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >>>>> >>>> >>>> >>>> >>>> try to add 'use_tsmuxer = 0; >>>> >>>> at this block? >>>> >>>> int CreateBD_Thread:: >>>> option_presets() >>>> { >>>> // reset only probed options >>>> use_deinterlace = 0; >>>> use_scale = Rescale::none; >>>> use_resize_tracks = 0; >>>> use_wide_audio = 0; >>>> use_labeled = 0; >>>> use_farmed = 0; >>>> >>>> in cinelerra/bdcreate.C? >>>> >>>> >>>> >>>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Andrew, if instead of choosing lpcm as the profile with the 2 >>>>>>> patches in, I choose the standard bluray, it works. >>>>>>> >>>>>>>> >>>>>>>> note, even if file named like c file it actually diff.. >>>>>>>> >>>>>>>> but both patches as send works for me as after full rebuild.. >>>>>>>> / >>>>>>>> >>>>>>>> if you (re)move those last two patches from tirdparty/src >>>>>>>> error (can't find codec..) disappears? >>>>>>>> >>>>>>> Yes. >>>>>>> >>>>>> >>>>>> >>>>>> do you have some other libavcodec headers installed? >>>>>> >>>>>> what ldd bin/cin (assuming you run from src root for single >>>>>> user) says? >>>>>> >>>>>> >>>>>> >>>>>>>> >>>>>>>>>> but strange. you rebuild cin executable too? (because we >>>>>>>>>> link statically I typed "touch cinelerra/new.C" and this forced rebuild >>>>>>>>>> of this file and re-linking of executable...) >>>>>>>>>> >>>>>>>>> I do full rebuilds by running "make clean" which deletes all >>>>>>>>> of the thirdparty libraries and then do a full rebuild with "./bld.sh". >>>>>>>>> Goes pretty fast on this laptop and it is not worth the aggravation to only >>>>>>>>> rebuild changed itemsl >>>>>>>>> >>>>>>>>>> >>>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>>>>>>>> encoder? >>>>>>>>>> >>>>>>>>> It must because what is checked into GIT, lets me choose the >>>>>>>>> lpcm profile and on the bluray player, the info button clearly displays it >>>>>>>>> as lpcm. >>>>>>>>> >>>>>>>> >>>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>> >>>>>>>> [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg >>>>>>> -codecs | grep bluray >>>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit >>>>>>> big-endian for Blu-ray media >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in >>>>>>>>>>>>> the attached png file. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> strange. >>>>>>>>>>>> >>>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing our >>>>>>>>>>>>>> lpcm audio stream >>>>>>>>>>>>>> >>>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I think having it all worked in monthly release quite >>>>>>>>>>>>>> important, even if names of patches kinda high... >>>>>>>>>>>>>> >>>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >>>>>>>>>>>>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>>>>>>>>>>>> 058a1ff9b4cdbd2e1a93acc8bf0365 >>>>>>>>>>>>>> e7d01cc9f4:/libavcodec/pcm-blurayenc.c >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>>>>>>>>>>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>>>>>>>>>>>> >>>>>>>>>>>>>
Do you mean this? *tsmuxer /tmp/bd_20220427-165207/bd.meta /tmp/bd_20220427-165207/bd.iso* tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.8% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-165207/bd.m2ts Also, it is possible that there is something not quite expected with the bluray media produced -- however, it plays on both the Samsung and LG players. Or it may be that the input is MKV instead of the more standard MP4 variety input file. I am looking the Big Buck mp4 but so far have not found it. On Wed, Apr 27, 2022 at 5:57 PM Andrew Randrianasulu < [email protected]> wrote:
thanks!
can you also specify exact tsmuxer commit/archive you used?
for me it showed some git digits in version, but for your it was just saying '-dev'
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test file - are at: https://cinelerra-gg.org/download/testing/tsmuxer_problem_files.tar My guess of whether or not they will execute the AppImage (link below) is below 1% probability: https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage
On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The 30 second and 1 minute 30 second files worked. So I think the last 2 patches are good. I am just going to see if I can put the 99 and 999a patch in 1 file and test that. If that goes well, I think I can check it into GIT.
yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) while preparing patches. Hopefully wider testing will show if I get channel order right or there is some need for moving audio tracks into specific configuration... {not sure if this covered in manual}
I will prepare an appimage and upload the files as you requested but it will not be done until later this evening.
thanks a lot!
On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably came from: https://test-videos.co.uk/bigbuckbunny/mkv
Meanwhile I will try a different file -- I use bbb because it is bigger than most of my test cases and then is still only 10 minutes long.
I think most tsmuxer users use it from win/mac.... so, our linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit some less-known codepath.. so if you can upload resultant m2ts file somewhere I'll link it into issue, because this is what usually asked tehre - problematic ts file to look at.. ..
If you can prepare appimage with all those patches applied may be someone will test it on Linux too, but I do not hold my breath for this...
On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < [email protected]> wrote:
> > > On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> > wrote: > >> Much better - now tsmuxer and profile value seem to be reset >> appropriately. >> But now tsmuxer error: >> >> tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer >> Decoding H264 stream (track 1): Profile: [email protected] Resolution: >> 1920:1080i Frame rate: 29.97 >> H.264 muxing fps is not set. Get fps from stream. Value: 29.97 >> 0.0% complete >> Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: >> 48KHz Channels: 5.1 Bits per sample: 16bit >> 18.2% complete >> Finalize ISO disk >> Reading buffer overflow. Possible container streams are not >> syncronized. Please, verify stream fps. File name: >> /tmp/bd_20220427-090605/bd.m2ts >> > > > can you provide example stream for tsmuxer's developers? > https://github.com/justdan96/tsMuxer/issues > > I can enter issue for you, just need link to file in question... > > >> On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < >> [email protected]> wrote: >> >>> >>> >>> On Wednesday, April 27, 2022, Phyllis Smith < >>> [email protected]> wrote: >>> >>>> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did >>>> full rebuild just to make sure). There must be a different spot >>>> It is possible that the 5:1 audio limitation is Fedora? >>>> >>> >>> no, just diff between av_ch_layout_5point1 and >>> av_ch_layout_5point1_back .... >>> >>> >>> try attached patches? one is for thirdparty/src another for cin >>> herself.. >>> >>> >>> >>>> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>> [email protected]> wrote: >>>>> >>>>>> Andrew, 10 million "mega" tests later, I finally figured it >>>>>> out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >>>>>> "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>>>> >>>>>> So what was happening is I loaded a file with 5:1 audio, chose >>>>>> LPCM and TSMUXER and the error message of: >>>>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout >>>>>> '5.1' is not supported* >>>>>> which is fine as long as I document that. But then I would >>>>>> load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >>>>>> checked and lpcm was not highlighted, I thought is should work and it did >>>>>> not because both LPCM and TSMUXER will still "on". >>>>>> >>>>>> Since I am not sure if I can get it right, could you provide >>>>>> the lines of code to change so that the profile and tsmuxer are reset to >>>>>> default "not on" values every time BD Render is chosen from the File >>>>>> pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >>>>>> >>>>> >>>>> >>>>> >>>>> try to add 'use_tsmuxer = 0; >>>>> >>>>> at this block? >>>>> >>>>> int CreateBD_Thread:: >>>>> option_presets() >>>>> { >>>>> // reset only probed options >>>>> use_deinterlace = 0; >>>>> use_scale = Rescale::none; >>>>> use_resize_tracks = 0; >>>>> use_wide_audio = 0; >>>>> use_labeled = 0; >>>>> use_farmed = 0; >>>>> >>>>> in cinelerra/bdcreate.C? >>>>> >>>>> >>>>> >>>>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Andrew, if instead of choosing lpcm as the profile with the 2 >>>>>>>> patches in, I choose the standard bluray, it works. >>>>>>>> >>>>>>>>> >>>>>>>>> note, even if file named like c file it actually diff.. >>>>>>>>> >>>>>>>>> but both patches as send works for me as after full >>>>>>>>> rebuild.. >>>>>>>>> / >>>>>>>>> >>>>>>>>> if you (re)move those last two patches from tirdparty/src >>>>>>>>> error (can't find codec..) disappears? >>>>>>>>> >>>>>>>> Yes. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> do you have some other libavcodec headers installed? >>>>>>> >>>>>>> what ldd bin/cin (assuming you run from src root for single >>>>>>> user) says? >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> >>>>>>>>>>> but strange. you rebuild cin executable too? (because we >>>>>>>>>>> link statically I typed "touch cinelerra/new.C" and this forced rebuild >>>>>>>>>>> of this file and re-linking of executable...) >>>>>>>>>>> >>>>>>>>>> I do full rebuilds by running "make clean" which deletes >>>>>>>>>> all of the thirdparty libraries and then do a full rebuild with >>>>>>>>>> "./bld.sh". Goes pretty fast on this laptop and it is not worth the >>>>>>>>>> aggravation to only rebuild changed itemsl >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>>>>>>>>> encoder? >>>>>>>>>>> >>>>>>>>>> It must because what is checked into GIT, lets me choose >>>>>>>>>> the lpcm profile and on the bluray player, the info button clearly displays >>>>>>>>>> it as lpcm. >>>>>>>>>> >>>>>>>>> >>>>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>> >>>>>>>>> [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg >>>>>>>> -codecs | grep bluray >>>>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit >>>>>>>> big-endian for Blu-ray media >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png >>>>>>>>>>>>>> file. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> strange. >>>>>>>>>>>>> >>>>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing our >>>>>>>>>>>>>>> lpcm audio stream >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I think having it all worked in monthly release quite >>>>>>>>>>>>>>> important, even if names of patches kinda high... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>>>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>
i mean version/date of archive you get tsmuxer from.. there is plenty of tags to choose from, and some appear quite recently https://github.com/justdan96/tsMuxer/releases On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Do you mean this?
*tsmuxer /tmp/bd_20220427-165207/bd.meta /tmp/bd_20220427-165207/bd.iso* tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.8% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-165207/bd.m2ts
Also, it is possible that there is something not quite expected with the bluray media produced -- however, it plays on both the Samsung and LG players. Or it may be that the input is MKV instead of the more standard MP4 variety input file. I am looking the Big Buck mp4 but so far have not found it.
On Wed, Apr 27, 2022 at 5:57 PM Andrew Randrianasulu < [email protected]> wrote:
thanks!
can you also specify exact tsmuxer commit/archive you used?
for me it showed some git digits in version, but for your it was just saying '-dev'
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test file - are at: https://cinelerra-gg.org/download/testing/tsmuxer_ problem_files.tar My guess of whether or not they will execute the AppImage (link below) is below 1% probability: https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage
On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The 30 second and 1 minute 30 second files worked. So I think the last 2 patches are good. I am just going to see if I can put the 99 and 999a patch in 1 file and test that. If that goes well, I think I can check it into GIT.
yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) while preparing patches. Hopefully wider testing will show if I get channel order right or there is some need for moving audio tracks into specific configuration... {not sure if this covered in manual}
I will prepare an appimage and upload the files as you requested but it will not be done until later this evening.
thanks a lot!
On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
> The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably > came from: > https://test-videos.co.uk/bigbuckbunny/mkv > > Meanwhile I will try a different file -- I use bbb because it is > bigger than most of my test cases and then is still only 10 minutes long. >
I think most tsmuxer users use it from win/mac.... so, our linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit some less-known codepath.. so if you can upload resultant m2ts file somewhere I'll link it into issue, because this is what usually asked tehre - problematic ts file to look at.. ..
If you can prepare appimage with all those patches applied may be someone will test it on Linux too, but I do not hold my breath for this...
> On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < > [email protected]> wrote: > >> >> >> On Wednesday, April 27, 2022, Phyllis Smith < >> [email protected]> wrote: >> >>> Much better - now tsmuxer and profile value seem to be reset >>> appropriately. >>> But now tsmuxer error: >>> >>> tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer >>> Decoding H264 stream (track 1): Profile: [email protected] Resolution: >>> 1920:1080i Frame rate: 29.97 >>> H.264 muxing fps is not set. Get fps from stream. Value: 29.97 >>> 0.0% complete >>> Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: >>> 48KHz Channels: 5.1 Bits per sample: 16bit >>> 18.2% complete >>> Finalize ISO disk >>> Reading buffer overflow. Possible container streams are not >>> syncronized. Please, verify stream fps. File name: >>> /tmp/bd_20220427-090605/bd.m2ts >>> >> >> >> can you provide example stream for tsmuxer's developers? >> https://github.com/justdan96/tsMuxer/issues >> >> I can enter issue for you, just need link to file in question... >> >> >>> On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < >>> [email protected]> wrote: >>> >>>> >>>> >>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>> [email protected]> wrote: >>>> >>>>> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did >>>>> full rebuild just to make sure). There must be a different spot >>>>> It is possible that the 5:1 audio limitation is Fedora? >>>>> >>>> >>>> no, just diff between av_ch_layout_5point1 and >>>> av_ch_layout_5point1_back .... >>>> >>>> >>>> try attached patches? one is for thirdparty/src another for cin >>>> herself.. >>>> >>>> >>>> >>>>> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Andrew, 10 million "mega" tests later, I finally figured it >>>>>>> out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >>>>>>> "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>>>>> >>>>>>> So what was happening is I loaded a file with 5:1 audio, chose >>>>>>> LPCM and TSMUXER and the error message of: >>>>>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout >>>>>>> '5.1' is not supported* >>>>>>> which is fine as long as I document that. But then I would >>>>>>> load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >>>>>>> checked and lpcm was not highlighted, I thought is should work and it did >>>>>>> not because both LPCM and TSMUXER will still "on". >>>>>>> >>>>>>> Since I am not sure if I can get it right, could you provide >>>>>>> the lines of code to change so that the profile and tsmuxer are reset to >>>>>>> default "not on" values every time BD Render is chosen from the File >>>>>>> pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> try to add 'use_tsmuxer = 0; >>>>>> >>>>>> at this block? >>>>>> >>>>>> int CreateBD_Thread:: >>>>>> option_presets() >>>>>> { >>>>>> // reset only probed options >>>>>> use_deinterlace = 0; >>>>>> use_scale = Rescale::none; >>>>>> use_resize_tracks = 0; >>>>>> use_wide_audio = 0; >>>>>> use_labeled = 0; >>>>>> use_farmed = 0; >>>>>> >>>>>> in cinelerra/bdcreate.C? >>>>>> >>>>>> >>>>>> >>>>>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Andrew, if instead of choosing lpcm as the profile with the >>>>>>>>> 2 patches in, I choose the standard bluray, it works. >>>>>>>>> >>>>>>>>>> >>>>>>>>>> note, even if file named like c file it actually diff.. >>>>>>>>>> >>>>>>>>>> but both patches as send works for me as after full >>>>>>>>>> rebuild.. >>>>>>>>>> / >>>>>>>>>> >>>>>>>>>> if you (re)move those last two patches from tirdparty/src >>>>>>>>>> error (can't find codec..) disappears? >>>>>>>>>> >>>>>>>>> Yes. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> do you have some other libavcodec headers installed? >>>>>>>> >>>>>>>> what ldd bin/cin (assuming you run from src root for single >>>>>>>> user) says? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>>> >>>>>>>>>>>> but strange. you rebuild cin executable too? (because we >>>>>>>>>>>> link statically I typed "touch cinelerra/new.C" and this forced rebuild >>>>>>>>>>>> of this file and re-linking of executable...) >>>>>>>>>>>> >>>>>>>>>>> I do full rebuilds by running "make clean" which deletes >>>>>>>>>>> all of the thirdparty libraries and then do a full rebuild with >>>>>>>>>>> "./bld.sh". Goes pretty fast on this laptop and it is not worth the >>>>>>>>>>> aggravation to only rebuild changed itemsl >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>>>>>>>>>> encoder? >>>>>>>>>>>> >>>>>>>>>>> It must because what is checked into GIT, lets me choose >>>>>>>>>>> the lpcm profile and on the bluray player, the info button clearly displays >>>>>>>>>>> it as lpcm. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>> >>>>>>>>>> [root@keystone cinelerra-5.1]# >>>>>>>>> thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit >>>>>>>>> big-endian for Blu-ray media >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen >>>>>>>>>>>>>>> in the attached png file. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> strange. >>>>>>>>>>>>>> >>>>>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing >>>>>>>>>>>>>>>> our lpcm audio stream >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I think having it all worked in monthly release quite >>>>>>>>>>>>>>>> important, even if names of patches kinda high... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>>>>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >>>>>>>>>>>>>>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>>>>>>>>>>>>>> 058a1ff9b4cdbd2e1a93acc8bf0365 >>>>>>>>>>>>>>>> e7d01cc9f4:/libavcodec/pcm-blurayenc.c >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>>>>>>>>>>>>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>
I did that on April 24. On Wed, Apr 27, 2022 at 6:34 PM Andrew Randrianasulu < [email protected]> wrote:
i mean version/date of archive you get tsmuxer from..
there is plenty of tags to choose from, and some appear quite recently
https://github.com/justdan96/tsMuxer/releases
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Do you mean this?
*tsmuxer /tmp/bd_20220427-165207/bd.meta /tmp/bd_20220427-165207/bd.iso* tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.8% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-165207/bd.m2ts
Also, it is possible that there is something not quite expected with the bluray media produced -- however, it plays on both the Samsung and LG players. Or it may be that the input is MKV instead of the more standard MP4 variety input file. I am looking the Big Buck mp4 but so far have not found it.
On Wed, Apr 27, 2022 at 5:57 PM Andrew Randrianasulu < [email protected]> wrote:
thanks!
can you also specify exact tsmuxer commit/archive you used?
for me it showed some git digits in version, but for your it was just saying '-dev'
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test file - are at:
https://cinelerra-gg.org/download/testing/tsmuxer_problem_files.tar My guess of whether or not they will execute the AppImage (link below) is below 1% probability: https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage
On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The 30 second and 1 minute 30 second files worked. So I think the last 2 patches are good. I am just going to see if I can put the 99 and 999a patch in 1 file and test that. If that goes well, I think I can check it into GIT.
yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) while preparing patches. Hopefully wider testing will show if I get channel order right or there is some need for moving audio tracks into specific configuration... {not sure if this covered in manual}
I will prepare an appimage and upload the files as you requested but it will not be done until later this evening.
thanks a lot!
On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < [email protected]> wrote:
> > > On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> > wrote: > >> The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably >> came from: >> https://test-videos.co.uk/bigbuckbunny/mkv >> >> Meanwhile I will try a different file -- I use bbb because it is >> bigger than most of my test cases and then is still only 10 minutes long. >> > > > I think most tsmuxer users use it from win/mac.... so, our > linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit > some less-known codepath.. so if you can upload resultant m2ts file > somewhere I'll link it into issue, because this is what usually asked tehre > - problematic ts file to look at.. .. > > If you can prepare appimage with all those patches applied may be > someone will test it on Linux too, but I do not hold my breath for this... > > > >> On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < >> [email protected]> wrote: >> >>> >>> >>> On Wednesday, April 27, 2022, Phyllis Smith < >>> [email protected]> wrote: >>> >>>> Much better - now tsmuxer and profile value seem to be reset >>>> appropriately. >>>> But now tsmuxer error: >>>> >>>> tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer >>>> Decoding H264 stream (track 1): Profile: [email protected] Resolution: >>>> 1920:1080i Frame rate: 29.97 >>>> H.264 muxing fps is not set. Get fps from stream. Value: 29.97 >>>> 0.0% complete >>>> Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: >>>> 48KHz Channels: 5.1 Bits per sample: 16bit >>>> 18.2% complete >>>> Finalize ISO disk >>>> Reading buffer overflow. Possible container streams are not >>>> syncronized. Please, verify stream fps. File name: >>>> /tmp/bd_20220427-090605/bd.m2ts >>>> >>> >>> >>> can you provide example stream for tsmuxer's developers? >>> https://github.com/justdan96/tsMuxer/issues >>> >>> I can enter issue for you, just need link to file in question... >>> >>> >>>> On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>> [email protected]> wrote: >>>>> >>>>>> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did >>>>>> full rebuild just to make sure). There must be a different spot >>>>>> It is possible that the 5:1 audio limitation is Fedora? >>>>>> >>>>> >>>>> no, just diff between av_ch_layout_5point1 and >>>>> av_ch_layout_5point1_back .... >>>>> >>>>> >>>>> try attached patches? one is for thirdparty/src another for cin >>>>> herself.. >>>>> >>>>> >>>>> >>>>>> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Andrew, 10 million "mega" tests later, I finally figured it >>>>>>>> out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >>>>>>>> "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>>>>>> >>>>>>>> So what was happening is I loaded a file with 5:1 audio, >>>>>>>> chose LPCM and TSMUXER and the error message of: >>>>>>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout >>>>>>>> '5.1' is not supported* >>>>>>>> which is fine as long as I document that. But then I would >>>>>>>> load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >>>>>>>> checked and lpcm was not highlighted, I thought is should work and it did >>>>>>>> not because both LPCM and TSMUXER will still "on". >>>>>>>> >>>>>>>> Since I am not sure if I can get it right, could you provide >>>>>>>> the lines of code to change so that the profile and tsmuxer are reset to >>>>>>>> default "not on" values every time BD Render is chosen from the File >>>>>>>> pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> try to add 'use_tsmuxer = 0; >>>>>>> >>>>>>> at this block? >>>>>>> >>>>>>> int CreateBD_Thread:: >>>>>>> option_presets() >>>>>>> { >>>>>>> // reset only probed options >>>>>>> use_deinterlace = 0; >>>>>>> use_scale = Rescale::none; >>>>>>> use_resize_tracks = 0; >>>>>>> use_wide_audio = 0; >>>>>>> use_labeled = 0; >>>>>>> use_farmed = 0; >>>>>>> >>>>>>> in cinelerra/bdcreate.C? >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Andrew, if instead of choosing lpcm as the profile with the >>>>>>>>>> 2 patches in, I choose the standard bluray, it works. >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> note, even if file named like c file it actually diff.. >>>>>>>>>>> >>>>>>>>>>> but both patches as send works for me as after full >>>>>>>>>>> rebuild.. >>>>>>>>>>> / >>>>>>>>>>> >>>>>>>>>>> if you (re)move those last two patches from tirdparty/src >>>>>>>>>>> error (can't find codec..) disappears? >>>>>>>>>>> >>>>>>>>>> Yes. >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> do you have some other libavcodec headers installed? >>>>>>>>> >>>>>>>>> what ldd bin/cin (assuming you run from src root for single >>>>>>>>> user) says? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>> but strange. you rebuild cin executable too? (because we >>>>>>>>>>>>> link statically I typed "touch cinelerra/new.C" and this forced rebuild >>>>>>>>>>>>> of this file and re-linking of executable...) >>>>>>>>>>>>> >>>>>>>>>>>> I do full rebuilds by running "make clean" which deletes >>>>>>>>>>>> all of the thirdparty libraries and then do a full rebuild with >>>>>>>>>>>> "./bld.sh". Goes pretty fast on this laptop and it is not worth the >>>>>>>>>>>> aggravation to only rebuild changed itemsl >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as >>>>>>>>>>>>> supported encoder? >>>>>>>>>>>>> >>>>>>>>>>>> It must because what is checked into GIT, lets me choose >>>>>>>>>>>> the lpcm profile and on the bluray player, the info button clearly displays >>>>>>>>>>>> it as lpcm. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>>> >>>>>>>>>>> [root@keystone cinelerra-5.1]# >>>>>>>>>> thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit >>>>>>>>>> big-endian for Blu-ray media >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png >>>>>>>>>>>>>>>> file. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> strange. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing >>>>>>>>>>>>>>>>> our lpcm audio stream >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I think having it all worked in monthly release >>>>>>>>>>>>>>>>> quite important, even if names of patches kinda high... >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, >>>>>>>>>>>>>>>>> and fix/patch as downloaded from gitweb.. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>
https://github.com/justdan96/tsMuxer/issues/589 On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
I did that on April 24.
On Wed, Apr 27, 2022 at 6:34 PM Andrew Randrianasulu < [email protected]> wrote:
i mean version/date of archive you get tsmuxer from..
there is plenty of tags to choose from, and some appear quite recently
https://github.com/justdan96/tsMuxer/releases
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Do you mean this?
*tsmuxer /tmp/bd_20220427-165207/bd.meta /tmp/bd_20220427-165207/bd.iso* tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.8% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-165207/bd.m2ts
Also, it is possible that there is something not quite expected with the bluray media produced -- however, it plays on both the Samsung and LG players. Or it may be that the input is MKV instead of the more standard MP4 variety input file. I am looking the Big Buck mp4 but so far have not found it.
On Wed, Apr 27, 2022 at 5:57 PM Andrew Randrianasulu < [email protected]> wrote:
thanks!
can you also specify exact tsmuxer commit/archive you used?
for me it showed some git digits in version, but for your it was just saying '-dev'
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test file - are at: https://cinelerra-gg.org/download/testing/tsmuxer_ problem_files.tar My guess of whether or not they will execute the AppImage (link below) is below 1% probability: https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage
On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
> The 30 second and 1 minute 30 second files worked. So I think the > last 2 patches are good. I am just going to see if I can put the 99 and > 999a patch in 1 file and test that. If that goes well, I think I can check > it into GIT. >
yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) while preparing patches. Hopefully wider testing will show if I get channel order right or there is some need for moving audio tracks into specific configuration... {not sure if this covered in manual}
> I will prepare an appimage and upload the files as you requested but > it will not be done until later this evening. >
thanks a lot!
> > On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < > [email protected]> wrote: > >> >> >> On Wednesday, April 27, 2022, Phyllis Smith < >> [email protected]> wrote: >> >>> The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably >>> came from: >>> https://test-videos.co.uk/bigbuckbunny/mkv >>> >>> Meanwhile I will try a different file -- I use bbb because it is >>> bigger than most of my test cases and then is still only 10 minutes long. >>> >> >> >> I think most tsmuxer users use it from win/mac.... so, our >> linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit >> some less-known codepath.. so if you can upload resultant m2ts file >> somewhere I'll link it into issue, because this is what usually asked tehre >> - problematic ts file to look at.. .. >> >> If you can prepare appimage with all those patches applied may be >> someone will test it on Linux too, but I do not hold my breath for this... >> >> >> >>> On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < >>> [email protected]> wrote: >>> >>>> >>>> >>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>> [email protected]> wrote: >>>> >>>>> Much better - now tsmuxer and profile value seem to be reset >>>>> appropriately. >>>>> But now tsmuxer error: >>>>> >>>>> tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer >>>>> Decoding H264 stream (track 1): Profile: [email protected] Resolution: >>>>> 1920:1080i Frame rate: 29.97 >>>>> H.264 muxing fps is not set. Get fps from stream. Value: 29.97 >>>>> 0.0% complete >>>>> Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: >>>>> 48KHz Channels: 5.1 Bits per sample: 16bit >>>>> 18.2% complete >>>>> Finalize ISO disk >>>>> Reading buffer overflow. Possible container streams are not >>>>> syncronized. Please, verify stream fps. File name: >>>>> /tmp/bd_20220427-090605/bd.m2ts >>>>> >>>> >>>> >>>> can you provide example stream for tsmuxer's developers? >>>> https://github.com/justdan96/tsMuxer/issues >>>> >>>> I can enter issue for you, just need link to file in question... >>>> >>>> >>>>> On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I >>>>>>> did full rebuild just to make sure). There must be a different spot >>>>>>> It is possible that the 5:1 audio limitation is Fedora? >>>>>>> >>>>>> >>>>>> no, just diff between av_ch_layout_5point1 and >>>>>> av_ch_layout_5point1_back .... >>>>>> >>>>>> >>>>>> try attached patches? one is for thirdparty/src another for cin >>>>>> herself.. >>>>>> >>>>>> >>>>>> >>>>>>> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Andrew, 10 million "mega" tests later, I finally figured it >>>>>>>>> out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >>>>>>>>> "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>>>>>>> >>>>>>>>> So what was happening is I loaded a file with 5:1 audio, >>>>>>>>> chose LPCM and TSMUXER and the error message of: >>>>>>>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout >>>>>>>>> '5.1' is not supported* >>>>>>>>> which is fine as long as I document that. But then I would >>>>>>>>> load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >>>>>>>>> checked and lpcm was not highlighted, I thought is should work and it did >>>>>>>>> not because both LPCM and TSMUXER will still "on". >>>>>>>>> >>>>>>>>> Since I am not sure if I can get it right, could you provide >>>>>>>>> the lines of code to change so that the profile and tsmuxer are reset to >>>>>>>>> default "not on" values every time BD Render is chosen from the File >>>>>>>>> pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> try to add 'use_tsmuxer = 0; >>>>>>>> >>>>>>>> at this block? >>>>>>>> >>>>>>>> int CreateBD_Thread:: >>>>>>>> option_presets() >>>>>>>> { >>>>>>>> // reset only probed options >>>>>>>> use_deinterlace = 0; >>>>>>>> use_scale = Rescale::none; >>>>>>>> use_resize_tracks = 0; >>>>>>>> use_wide_audio = 0; >>>>>>>> use_labeled = 0; >>>>>>>> use_farmed = 0; >>>>>>>> >>>>>>>> in cinelerra/bdcreate.C? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Andrew, if instead of choosing lpcm as the profile with >>>>>>>>>>> the 2 patches in, I choose the standard bluray, it works. >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> note, even if file named like c file it actually diff.. >>>>>>>>>>>> >>>>>>>>>>>> but both patches as send works for me as after full >>>>>>>>>>>> rebuild.. >>>>>>>>>>>> / >>>>>>>>>>>> >>>>>>>>>>>> if you (re)move those last two patches from tirdparty/src >>>>>>>>>>>> error (can't find codec..) disappears? >>>>>>>>>>>> >>>>>>>>>>> Yes. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> do you have some other libavcodec headers installed? >>>>>>>>>> >>>>>>>>>> what ldd bin/cin (assuming you run from src root for single >>>>>>>>>> user) says? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>>> but strange. you rebuild cin executable too? (because >>>>>>>>>>>>>> we link statically I typed "touch cinelerra/new.C" and this forced rebuild >>>>>>>>>>>>>> of this file and re-linking of executable...) >>>>>>>>>>>>>> >>>>>>>>>>>>> I do full rebuilds by running "make clean" which deletes >>>>>>>>>>>>> all of the thirdparty libraries and then do a full rebuild with >>>>>>>>>>>>> "./bld.sh". Goes pretty fast on this laptop and it is not worth the >>>>>>>>>>>>> aggravation to only rebuild changed itemsl >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as >>>>>>>>>>>>>> supported encoder? >>>>>>>>>>>>>> >>>>>>>>>>>>> It must because what is checked into GIT, lets me choose >>>>>>>>>>>>> the lpcm profile and on the bluray player, the info button clearly displays >>>>>>>>>>>>> it as lpcm. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>>>> >>>>>>>>>>>> [root@keystone cinelerra-5.1]# >>>>>>>>>>> thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit >>>>>>>>>>> big-endian for Blu-ray media >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen >>>>>>>>>>>>>>>>> in the attached png file. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> strange. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu >>>>>>>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing >>>>>>>>>>>>>>>>>> our lpcm audio stream >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I think having it all worked in monthly release >>>>>>>>>>>>>>>>>> quite important, even if names of patches kinda high... >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, >>>>>>>>>>>>>>>>>> and fix/patch as downloaded from gitweb.. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/ >>>>>>>>>>>>>>>>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>>>>>>>>>>>>>>>> 058a1ff9b4cdbd2e1a93acc8bf0365 >>>>>>>>>>>>>>>>>> e7d01cc9f4:/libavcodec/pcm-blurayenc.c >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>>>>>>>>>>>>>>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>
Checked into GIT, bdcreate.C patched file and new ffmpeg-4.4.patch_99 (with 999a included). On Wed, Apr 27, 2022 at 6:49 PM Andrew Randrianasulu < [email protected]> wrote:
Thank you. I checked the aboe BUT Big Buck Bunny has a frame rate of 60.000, so not sure why tsmuxer reports: sMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i *Frame rate: 29.97* H.264 muxing fps is not set. Get fps from stream. Value: 29.97
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
I did that on April 24.
On Wed, Apr 27, 2022 at 6:34 PM Andrew Randrianasulu < [email protected]> wrote:
i mean version/date of archive you get tsmuxer from..
there is plenty of tags to choose from, and some appear quite recently
https://github.com/justdan96/tsMuxer/releases
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Do you mean this?
*tsmuxer /tmp/bd_20220427-165207/bd.meta /tmp/bd_20220427-165207/bd.iso* tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.8% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-165207/bd.m2ts
Also, it is possible that there is something not quite expected with the bluray media produced -- however, it plays on both the Samsung and LG players. Or it may be that the input is MKV instead of the more standard MP4 variety input file. I am looking the Big Buck mp4 but so far have not found it.
On Wed, Apr 27, 2022 at 5:57 PM Andrew Randrianasulu < [email protected]> wrote:
thanks!
can you also specify exact tsmuxer commit/archive you used?
for me it showed some git digits in version, but for your it was just saying '-dev'
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test file - are at:
https://cinelerra-gg.org/download/testing/tsmuxer_problem_files.tar My guess of whether or not they will execute the AppImage (link below) is below 1% probability: https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage
On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < [email protected]> wrote:
> > > On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> > wrote: > >> The 30 second and 1 minute 30 second files worked. So I think the >> last 2 patches are good. I am just going to see if I can put the 99 and >> 999a patch in 1 file and test that. If that goes well, I think I can check >> it into GIT. >> > > yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) > while preparing patches. Hopefully wider testing will show if I get channel > order right or there is some need for moving audio tracks into specific > configuration... {not sure if this covered in manual} > > > >> I will prepare an appimage and upload the files as you requested >> but it will not be done until later this evening. >> > > > thanks a lot! > >> >> On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < >> [email protected]> wrote: >> >>> >>> >>> On Wednesday, April 27, 2022, Phyllis Smith < >>> [email protected]> wrote: >>> >>>> The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably >>>> came from: >>>> https://test-videos.co.uk/bigbuckbunny/mkv >>>> >>>> Meanwhile I will try a different file -- I use bbb because it is >>>> bigger than most of my test cases and then is still only 10 minutes long. >>>> >>> >>> >>> I think most tsmuxer users use it from win/mac.... so, our >>> linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit >>> some less-known codepath.. so if you can upload resultant m2ts file >>> somewhere I'll link it into issue, because this is what usually asked tehre >>> - problematic ts file to look at.. .. >>> >>> If you can prepare appimage with all those patches applied may be >>> someone will test it on Linux too, but I do not hold my breath for this... >>> >>> >>> >>>> On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>> [email protected]> wrote: >>>>> >>>>>> Much better - now tsmuxer and profile value seem to be reset >>>>>> appropriately. >>>>>> But now tsmuxer error: >>>>>> >>>>>> tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer >>>>>> Decoding H264 stream (track 1): Profile: [email protected] Resolution: >>>>>> 1920:1080i Frame rate: 29.97 >>>>>> H.264 muxing fps is not set. Get fps from stream. Value: 29.97 >>>>>> 0.0% complete >>>>>> Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: >>>>>> 48KHz Channels: 5.1 Bits per sample: 16bit >>>>>> 18.2% complete >>>>>> Finalize ISO disk >>>>>> Reading buffer overflow. Possible container streams are not >>>>>> syncronized. Please, verify stream fps. File name: >>>>>> /tmp/bd_20220427-090605/bd.m2ts >>>>>> >>>>> >>>>> >>>>> can you provide example stream for tsmuxer's developers? >>>>> https://github.com/justdan96/tsMuxer/issues >>>>> >>>>> I can enter issue for you, just need link to file in question... >>>>> >>>>> >>>>>> On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I >>>>>>>> did full rebuild just to make sure). There must be a different spot >>>>>>>> It is possible that the 5:1 audio limitation is Fedora? >>>>>>>> >>>>>>> >>>>>>> no, just diff between av_ch_layout_5point1 and >>>>>>> av_ch_layout_5point1_back .... >>>>>>> >>>>>>> >>>>>>> try attached patches? one is for thirdparty/src another for >>>>>>> cin herself.. >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Andrew, 10 million "mega" tests later, I finally figured it >>>>>>>>>> out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >>>>>>>>>> "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>>>>>>>> >>>>>>>>>> So what was happening is I loaded a file with 5:1 audio, >>>>>>>>>> chose LPCM and TSMUXER and the error message of: >>>>>>>>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel >>>>>>>>>> layout '5.1' is not supported* >>>>>>>>>> which is fine as long as I document that. But then I would >>>>>>>>>> load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >>>>>>>>>> checked and lpcm was not highlighted, I thought is should work and it did >>>>>>>>>> not because both LPCM and TSMUXER will still "on". >>>>>>>>>> >>>>>>>>>> Since I am not sure if I can get it right, could you >>>>>>>>>> provide the lines of code to change so that the profile and tsmuxer are >>>>>>>>>> reset to default "not on" values every time BD Render is chosen from the >>>>>>>>>> File pulldown? Then I can do a final test and check into GIT. Thanks, >>>>>>>>>> Phyllis >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> try to add 'use_tsmuxer = 0; >>>>>>>>> >>>>>>>>> at this block? >>>>>>>>> >>>>>>>>> int CreateBD_Thread:: >>>>>>>>> option_presets() >>>>>>>>> { >>>>>>>>> // reset only probed options >>>>>>>>> use_deinterlace = 0; >>>>>>>>> use_scale = Rescale::none; >>>>>>>>> use_resize_tracks = 0; >>>>>>>>> use_wide_audio = 0; >>>>>>>>> use_labeled = 0; >>>>>>>>> use_farmed = 0; >>>>>>>>> >>>>>>>>> in cinelerra/bdcreate.C? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> Andrew, if instead of choosing lpcm as the profile with >>>>>>>>>>>> the 2 patches in, I choose the standard bluray, it works. >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> note, even if file named like c file it actually diff.. >>>>>>>>>>>>> >>>>>>>>>>>>> but both patches as send works for me as after full >>>>>>>>>>>>> rebuild.. >>>>>>>>>>>>> / >>>>>>>>>>>>> >>>>>>>>>>>>> if you (re)move those last two patches from >>>>>>>>>>>>> tirdparty/src error (can't find codec..) disappears? >>>>>>>>>>>>> >>>>>>>>>>>> Yes. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> do you have some other libavcodec headers installed? >>>>>>>>>>> >>>>>>>>>>> what ldd bin/cin (assuming you run from src root for >>>>>>>>>>> single user) says? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>>> but strange. you rebuild cin executable too? (because >>>>>>>>>>>>>>> we link statically I typed "touch cinelerra/new.C" and this forced rebuild >>>>>>>>>>>>>>> of this file and re-linking of executable...) >>>>>>>>>>>>>>> >>>>>>>>>>>>>> I do full rebuilds by running "make clean" which >>>>>>>>>>>>>> deletes all of the thirdparty libraries and then do a full rebuild with >>>>>>>>>>>>>> "./bld.sh". Goes pretty fast on this laptop and it is not worth the >>>>>>>>>>>>>> aggravation to only rebuild changed itemsl >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as >>>>>>>>>>>>>>> supported encoder? >>>>>>>>>>>>>>> >>>>>>>>>>>>>> It must because what is checked into GIT, lets me >>>>>>>>>>>>>> choose the lpcm profile and on the bluray player, the info button clearly >>>>>>>>>>>>>> displays it as lpcm. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>>>>> >>>>>>>>>>>>> [root@keystone cinelerra-5.1]# >>>>>>>>>>>> thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit >>>>>>>>>>>> big-endian for Blu-ray media >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png >>>>>>>>>>>>>>>>>> file. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> strange. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew >>>>>>>>>>>>>>>>>> Randrianasulu <[email protected]> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing >>>>>>>>>>>>>>>>>>> our lpcm audio stream >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I think having it all worked in monthly release >>>>>>>>>>>>>>>>>>> quite important, even if names of patches kinda high... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, >>>>>>>>>>>>>>>>>>> and fix/patch as downloaded from gitweb.. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Checked into GIT, bdcreate.C patched file and new ffmpeg-4.4.patch_99 (with 999a included).
On Wed, Apr 27, 2022 at 6:49 PM Andrew Randrianasulu < [email protected]> wrote:
Thank you. I checked the aboe BUT Big Buck Bunny has a frame rate of 60.000, so not sure why tsmuxer reports:
sMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i *Frame rate: 29.97* H.264 muxing fps is not set. Get fps from stream. Value: 29.97
well, 60p fps for full hd not allowed on regular Blu-ray, may be only on UHD? But I tried 59.94 x 720p and this apparently worked at muxing stage (while I had weird error about auto-attaching scale/resize plugin, so my first enciding was all black! now doing second attempt.. x264 encodes, will finish in hour or so..)
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
I did that on April 24.
On Wed, Apr 27, 2022 at 6:34 PM Andrew Randrianasulu < [email protected]> wrote:
i mean version/date of archive you get tsmuxer from..
there is plenty of tags to choose from, and some appear quite recently
https://github.com/justdan96/tsMuxer/releases
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Do you mean this?
*tsmuxer /tmp/bd_20220427-165207/bd.meta /tmp/bd_20220427-165207/bd.iso* tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.8% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-165207/bd.m2ts
Also, it is possible that there is something not quite expected with the bluray media produced -- however, it plays on both the Samsung and LG players. Or it may be that the input is MKV instead of the more standard MP4 variety input file. I am looking the Big Buck mp4 but so far have not found it.
On Wed, Apr 27, 2022 at 5:57 PM Andrew Randrianasulu < [email protected]> wrote:
thanks!
can you also specify exact tsmuxer commit/archive you used?
for me it showed some git digits in version, but for your it was just saying '-dev'
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
> Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test > file - are at: > https://cinelerra-gg.org/download/testing/tsmuxer_ > problem_files.tar > My guess of whether or not they will execute the AppImage (link > below) is below 1% probability: > https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage > > On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < > [email protected]> wrote: > >> >> >> On Wednesday, April 27, 2022, Phyllis Smith < >> [email protected]> wrote: >> >>> The 30 second and 1 minute 30 second files worked. So I think the >>> last 2 patches are good. I am just going to see if I can put the 99 and >>> 999a patch in 1 file and test that. If that goes well, I think I can check >>> it into GIT. >>> >> >> yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) >> while preparing patches. Hopefully wider testing will show if I get channel >> order right or there is some need for moving audio tracks into specific >> configuration... {not sure if this covered in manual} >> >> >> >>> I will prepare an appimage and upload the files as you requested >>> but it will not be done until later this evening. >>> >> >> >> thanks a lot! >> >>> >>> On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < >>> [email protected]> wrote: >>> >>>> >>>> >>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>> [email protected]> wrote: >>>> >>>>> The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably >>>>> came from: >>>>> https://test-videos.co.uk/bigbuckbunny/mkv >>>>> >>>>> Meanwhile I will try a different file -- I use bbb because it is >>>>> bigger than most of my test cases and then is still only 10 minutes long. >>>>> >>>> >>>> >>>> I think most tsmuxer users use it from win/mac.... so, our >>>> linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit >>>> some less-known codepath.. so if you can upload resultant m2ts file >>>> somewhere I'll link it into issue, because this is what usually asked tehre >>>> - problematic ts file to look at.. .. >>>> >>>> If you can prepare appimage with all those patches applied may be >>>> someone will test it on Linux too, but I do not hold my breath for this... >>>> >>>> >>>> >>>>> On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Much better - now tsmuxer and profile value seem to be reset >>>>>>> appropriately. >>>>>>> But now tsmuxer error: >>>>>>> >>>>>>> tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer >>>>>>> Decoding H264 stream (track 1): Profile: [email protected] >>>>>>> Resolution: 1920:1080i Frame rate: 29.97 >>>>>>> H.264 muxing fps is not set. Get fps from stream. Value: 29.97 >>>>>>> 0.0% complete >>>>>>> Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample >>>>>>> Rate: 48KHz Channels: 5.1 Bits per sample: 16bit >>>>>>> 18.2% complete >>>>>>> Finalize ISO disk >>>>>>> Reading buffer overflow. Possible container streams are not >>>>>>> syncronized. Please, verify stream fps. File name: >>>>>>> /tmp/bd_20220427-090605/bd.m2ts >>>>>>> >>>>>> >>>>>> >>>>>> can you provide example stream for tsmuxer's developers? >>>>>> https://github.com/justdan96/tsMuxer/issues >>>>>> >>>>>> I can enter issue for you, just need link to file in >>>>>> question... >>>>>> >>>>>> >>>>>>> On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I >>>>>>>>> did full rebuild just to make sure). There must be a different spot >>>>>>>>> It is possible that the 5:1 audio limitation is Fedora? >>>>>>>>> >>>>>>>> >>>>>>>> no, just diff between av_ch_layout_5point1 and >>>>>>>> av_ch_layout_5point1_back .... >>>>>>>> >>>>>>>> >>>>>>>> try attached patches? one is for thirdparty/src another for >>>>>>>> cin herself.. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Andrew, 10 million "mega" tests later, I finally figured >>>>>>>>>>> it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset >>>>>>>>>>> to "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>>>>>>>>> >>>>>>>>>>> So what was happening is I loaded a file with 5:1 audio, >>>>>>>>>>> chose LPCM and TSMUXER and the error message of: >>>>>>>>>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel >>>>>>>>>>> layout '5.1' is not supported* >>>>>>>>>>> which is fine as long as I document that. But then I >>>>>>>>>>> would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was >>>>>>>>>>> not checked and lpcm was not highlighted, I thought is should work and it >>>>>>>>>>> did not because both LPCM and TSMUXER will still "on". >>>>>>>>>>> >>>>>>>>>>> Since I am not sure if I can get it right, could you >>>>>>>>>>> provide the lines of code to change so that the profile and tsmuxer are >>>>>>>>>>> reset to default "not on" values every time BD Render is chosen from the >>>>>>>>>>> File pulldown? Then I can do a final test and check into GIT. Thanks, >>>>>>>>>>> Phyllis >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> try to add 'use_tsmuxer = 0; >>>>>>>>>> >>>>>>>>>> at this block? >>>>>>>>>> >>>>>>>>>> int CreateBD_Thread:: >>>>>>>>>> option_presets() >>>>>>>>>> { >>>>>>>>>> // reset only probed options >>>>>>>>>> use_deinterlace = 0; >>>>>>>>>> use_scale = Rescale::none; >>>>>>>>>> use_resize_tracks = 0; >>>>>>>>>> use_wide_audio = 0; >>>>>>>>>> use_labeled = 0; >>>>>>>>>> use_farmed = 0; >>>>>>>>>> >>>>>>>>>> in cinelerra/bdcreate.C? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Andrew, if instead of choosing lpcm as the profile with >>>>>>>>>>>>> the 2 patches in, I choose the standard bluray, it works. >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> note, even if file named like c file it actually diff.. >>>>>>>>>>>>>> >>>>>>>>>>>>>> but both patches as send works for me as after full >>>>>>>>>>>>>> rebuild.. >>>>>>>>>>>>>> / >>>>>>>>>>>>>> >>>>>>>>>>>>>> if you (re)move those last two patches from >>>>>>>>>>>>>> tirdparty/src error (can't find codec..) disappears? >>>>>>>>>>>>>> >>>>>>>>>>>>> Yes. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> do you have some other libavcodec headers installed? >>>>>>>>>>>> >>>>>>>>>>>> what ldd bin/cin (assuming you run from src root for >>>>>>>>>>>> single user) says? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>>> but strange. you rebuild cin executable too? (because >>>>>>>>>>>>>>>> we link statically I typed "touch cinelerra/new.C" and this forced rebuild >>>>>>>>>>>>>>>> of this file and re-linking of executable...) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I do full rebuilds by running "make clean" which >>>>>>>>>>>>>>> deletes all of the thirdparty libraries and then do a full rebuild with >>>>>>>>>>>>>>> "./bld.sh". Goes pretty fast on this laptop and it is not worth the >>>>>>>>>>>>>>> aggravation to only rebuild changed itemsl >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as >>>>>>>>>>>>>>>> supported encoder? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> It must because what is checked into GIT, lets me >>>>>>>>>>>>>>> choose the lpcm profile and on the bluray player, the info button clearly >>>>>>>>>>>>>>> displays it as lpcm. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>>>>>> >>>>>>>>>>>>>> [root@keystone cinelerra-5.1]# >>>>>>>>>>>>> thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit >>>>>>>>>>>>> big-endian for Blu-ray media >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu >>>>>>>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as >>>>>>>>>>>>>>>>>>> seen in the attached png file. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> strange. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew >>>>>>>>>>>>>>>>>>> Randrianasulu <[email protected]> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from >>>>>>>>>>>>>>>>>>>> recognizing our lpcm audio stream >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I think having it all worked in monthly release >>>>>>>>>>>>>>>>>>>> quite important, even if names of patches kinda high... >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, >>>>>>>>>>>>>>>>>>>> and fix/patch as downloaded from gitweb.. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ >>>>>>>>>>>>>>>>>>>> ffmpeg.git/blobdiff/ >>>>>>>>>>>>>>>>>>>> 037fa0437d2aead40c1f786c6ad4d343afe0546d.. >>>>>>>>>>>>>>>>>>>> 058a1ff9b4cdbd2e1a93acc8bf0365 >>>>>>>>>>>>>>>>>>>> e7d01cc9f4:/libavcodec/pcm-blurayenc.c >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/ >>>>>>>>>>>>>>>>>>>> 93dfb6afddb278218da7f8c696bf35ede2ba05aa >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>
On Thursday, April 28, 2022, Andrew Randrianasulu <[email protected]> wrote:
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Checked into GIT, bdcreate.C patched file and new ffmpeg-4.4.patch_99 (with 999a included).
On Wed, Apr 27, 2022 at 6:49 PM Andrew Randrianasulu < [email protected]> wrote:
Thank you. I checked the aboe BUT Big Buck Bunny has a frame rate of 60.000, so not sure why tsmuxer reports:
sMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i *Frame rate: 29.97* H.264 muxing fps is not set. Get fps from stream. Value: 29.97
well, 60p fps for full hd not allowed on regular Blu-ray, may be only on UHD?
But I tried 59.94 x 720p and this apparently worked at muxing stage (while I had weird error about auto-attaching scale/resize plugin, so my first enciding was all black! now doing second attempt.. x264 encodes, will finish in hour or so..)
sadly no - error st 20%... may be lowering video max bitrate will fix (workaround) this...
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
I did that on April 24.
On Wed, Apr 27, 2022 at 6:34 PM Andrew Randrianasulu < [email protected]> wrote:
i mean version/date of archive you get tsmuxer from..
there is plenty of tags to choose from, and some appear quite recently
https://github.com/justdan96/tsMuxer/releases
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Do you mean this?
*tsmuxer /tmp/bd_20220427-165207/bd.meta /tmp/bd_20220427-165207/bd.iso* tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer Decoding H264 stream (track 1): Profile: [email protected] Resolution: 1920:1080i Frame rate: 29.97 H.264 muxing fps is not set. Get fps from stream. Value: 29.97 0.0% complete Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit 18.8% complete Finalize ISO disk Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-165207/bd.m2ts
Also, it is possible that there is something not quite expected with the bluray media produced -- however, it plays on both the Samsung and LG players. Or it may be that the input is MKV instead of the more standard MP4 variety input file. I am looking the Big Buck mp4 but so far have not found it.
On Wed, Apr 27, 2022 at 5:57 PM Andrew Randrianasulu < [email protected]> wrote:
> thanks! > > can you also specify exact tsmuxer commit/archive you used? > > for me it showed some git digits in version, but for your it was > just saying '-dev' > > On Thursday, April 28, 2022, Phyllis Smith <[email protected]> > wrote: > >> Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test >> file - are at: >> https://cinelerra-gg.org/download/testing/tsmuxer_problem_ >> files.tar >> My guess of whether or not they will execute the AppImage (link >> below) is below 1% probability: >> https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage >> >> On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < >> [email protected]> wrote: >> >>> >>> >>> On Wednesday, April 27, 2022, Phyllis Smith < >>> [email protected]> wrote: >>> >>>> The 30 second and 1 minute 30 second files worked. So I think >>>> the last 2 patches are good. I am just going to see if I can put the 99 >>>> and 999a patch in 1 file and test that. If that goes well, I think I can >>>> check it into GIT. >>>> >>> >>> yes, good idea - sorry I forgot about this detail (5.1 vs >>> 5.1_back) while preparing patches. Hopefully wider testing will show if I >>> get channel order right or there is some need for moving audio tracks into >>> specific configuration... {not sure if this covered in manual} >>> >>> >>> >>>> I will prepare an appimage and upload the files as you requested >>>> but it will not be done until later this evening. >>>> >>> >>> >>> thanks a lot! >>> >>>> >>>> On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>> [email protected]> wrote: >>>>> >>>>>> The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and >>>>>> probably came from: >>>>>> https://test-videos.co.uk/bigbuckbunny/mkv >>>>>> >>>>>> Meanwhile I will try a different file -- I use bbb because it >>>>>> is bigger than most of my test cases and then is still only 10 minutes long. >>>>>> >>>>> >>>>> >>>>> I think most tsmuxer users use it from win/mac.... so, our >>>>> linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit >>>>> some less-known codepath.. so if you can upload resultant m2ts file >>>>> somewhere I'll link it into issue, because this is what usually asked tehre >>>>> - problematic ts file to look at.. .. >>>>> >>>>> If you can prepare appimage with all those patches applied may >>>>> be someone will test it on Linux too, but I do not hold my breath for >>>>> this... >>>>> >>>>> >>>>> >>>>>> On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Much better - now tsmuxer and profile value seem to be reset >>>>>>>> appropriately. >>>>>>>> But now tsmuxer error: >>>>>>>> >>>>>>>> tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer >>>>>>>> Decoding H264 stream (track 1): Profile: [email protected] >>>>>>>> Resolution: 1920:1080i Frame rate: 29.97 >>>>>>>> H.264 muxing fps is not set. Get fps from stream. Value: 29.97 >>>>>>>> 0.0% complete >>>>>>>> Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample >>>>>>>> Rate: 48KHz Channels: 5.1 Bits per sample: 16bit >>>>>>>> 18.2% complete >>>>>>>> Finalize ISO disk >>>>>>>> Reading buffer overflow. Possible container streams are not >>>>>>>> syncronized. Please, verify stream fps. File name: >>>>>>>> /tmp/bd_20220427-090605/bd.m2ts >>>>>>>> >>>>>>> >>>>>>> >>>>>>> can you provide example stream for tsmuxer's developers? >>>>>>> https://github.com/justdan96/tsMuxer/issues >>>>>>> >>>>>>> I can enter issue for you, just need link to file in >>>>>>> question... >>>>>>> >>>>>>> >>>>>>>> On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I >>>>>>>>>> did full rebuild just to make sure). There must be a different spot >>>>>>>>>> It is possible that the 5:1 audio limitation is Fedora? >>>>>>>>>> >>>>>>>>> >>>>>>>>> no, just diff between av_ch_layout_5point1 and >>>>>>>>> av_ch_layout_5point1_back .... >>>>>>>>> >>>>>>>>> >>>>>>>>> try attached patches? one is for thirdparty/src another for >>>>>>>>> cin herself.. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> Andrew, 10 million "mega" tests later, I finally figured >>>>>>>>>>>> it out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset >>>>>>>>>>>> to "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>>>>>>>>>> >>>>>>>>>>>> So what was happening is I loaded a file with 5:1 audio, >>>>>>>>>>>> chose LPCM and TSMUXER and the error message of: >>>>>>>>>>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel >>>>>>>>>>>> layout '5.1' is not supported* >>>>>>>>>>>> which is fine as long as I document that. But then I >>>>>>>>>>>> would load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was >>>>>>>>>>>> not checked and lpcm was not highlighted, I thought is should work and it >>>>>>>>>>>> did not because both LPCM and TSMUXER will still "on". >>>>>>>>>>>> >>>>>>>>>>>> Since I am not sure if I can get it right, could you >>>>>>>>>>>> provide the lines of code to change so that the profile and tsmuxer are >>>>>>>>>>>> reset to default "not on" values every time BD Render is chosen from the >>>>>>>>>>>> File pulldown? Then I can do a final test and check into GIT. Thanks, >>>>>>>>>>>> Phyllis >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> try to add 'use_tsmuxer = 0; >>>>>>>>>>> >>>>>>>>>>> at this block? >>>>>>>>>>> >>>>>>>>>>> int CreateBD_Thread:: >>>>>>>>>>> option_presets() >>>>>>>>>>> { >>>>>>>>>>> // reset only probed options >>>>>>>>>>> use_deinterlace = 0; >>>>>>>>>>> use_scale = Rescale::none; >>>>>>>>>>> use_resize_tracks = 0; >>>>>>>>>>> use_wide_audio = 0; >>>>>>>>>>> use_labeled = 0; >>>>>>>>>>> use_farmed = 0; >>>>>>>>>>> >>>>>>>>>>> in cinelerra/bdcreate.C? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Andrew, if instead of choosing lpcm as the profile with >>>>>>>>>>>>>> the 2 patches in, I choose the standard bluray, it works. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> note, even if file named like c file it actually >>>>>>>>>>>>>>> diff.. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> but both patches as send works for me as after full >>>>>>>>>>>>>>> rebuild.. >>>>>>>>>>>>>>> / >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> if you (re)move those last two patches from >>>>>>>>>>>>>>> tirdparty/src error (can't find codec..) disappears? >>>>>>>>>>>>>>> >>>>>>>>>>>>>> Yes. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> do you have some other libavcodec headers installed? >>>>>>>>>>>>> >>>>>>>>>>>>> what ldd bin/cin (assuming you run from src root for >>>>>>>>>>>>> single user) says? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> but strange. you rebuild cin executable too? >>>>>>>>>>>>>>>>> (because we link statically I typed "touch cinelerra/new.C" and this >>>>>>>>>>>>>>>>> forced rebuild of this file and re-linking of executable...) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I do full rebuilds by running "make clean" which >>>>>>>>>>>>>>>> deletes all of the thirdparty libraries and then do a full rebuild with >>>>>>>>>>>>>>>> "./bld.sh". Goes pretty fast on this laptop and it is not worth the >>>>>>>>>>>>>>>> aggravation to only rebuild changed itemsl >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as >>>>>>>>>>>>>>>>> supported encoder? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> It must because what is checked into GIT, lets me >>>>>>>>>>>>>>>> choose the lpcm profile and on the bluray player, the info button clearly >>>>>>>>>>>>>>>> displays it as lpcm. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [root@keystone cinelerra-5.1]# >>>>>>>>>>>>>> thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>>>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit >>>>>>>>>>>>>> big-endian for Blu-ray media >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew >>>>>>>>>>>>>>>>>> Randrianasulu <[email protected]> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as >>>>>>>>>>>>>>>>>>>> seen in the attached png file. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> strange. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew >>>>>>>>>>>>>>>>>>>> Randrianasulu <[email protected]> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from >>>>>>>>>>>>>>>>>>>>> recognizing our lpcm audio stream >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I think having it all worked in monthly release >>>>>>>>>>>>>>>>>>>>> quite important, even if names of patches kinda high... >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked >>>>>>>>>>>>>>>>>>>>> it, and fix/patch as downloaded from gitweb.. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ >>>>>>>>>>>>>>>>>>>>> ffmpeg.git/blobdiff/037fa0437d >>>>>>>>>>>>>>>>>>>>> 2aead40c1f786c6ad4d343afe0546d >>>>>>>>>>>>>>>>>>>>> ..058a1ff9b4cdbd2e1a93acc8bf03 >>>>>>>>>>>>>>>>>>>>> 65e7d01cc9f4:/libavcodec/pcm-blurayenc.c >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ >>>>>>>>>>>>>>>>>>>>> ffmpeg.git/commit/93dfb6afddb2 >>>>>>>>>>>>>>>>>>>>> 78218da7f8c696bf35ede2ba05aa >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>
Here is the result of "tsmuxer --version": tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer I downloaded an compiled it from tsMuxer-master.zip from: https://github.com/justdan96/tsMuxer Then I think I followed the instructions in docs/Compiling.md to include installing ninja-build ``` # build the project ./scripts/rebuild_linux.sh On Wed, Apr 27, 2022 at 5:57 PM Andrew Randrianasulu < [email protected]> wrote:
thanks!
can you also specify exact tsmuxer commit/archive you used?
for me it showed some git digits in version, but for your it was just saying '-dev'
On Thursday, April 28, 2022, Phyllis Smith <[email protected]> wrote:
Files - bd.m2ts, bd.meta, bd.iso, and bbb-1920x1080-cfg06.mkv test file - are at: https://cinelerra-gg.org/download/testing/tsmuxer_problem_files.tar My guess of whether or not they will execute the AppImage (link below) is below 1% probability: https://cinelerra-gg.org/download/testing/cin-x86_64.AppImage
On Wed, Apr 27, 2022 at 1:04 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The 30 second and 1 minute 30 second files worked. So I think the last 2 patches are good. I am just going to see if I can put the 99 and 999a patch in 1 file and test that. If that goes well, I think I can check it into GIT.
yes, good idea - sorry I forgot about this detail (5.1 vs 5.1_back) while preparing patches. Hopefully wider testing will show if I get channel order right or there is some need for moving audio tracks into specific configuration... {not sure if this covered in manual}
I will prepare an appimage and upload the files as you requested but it will not be done until later this evening.
thanks a lot!
On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu < [email protected]> wrote:
On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> wrote:
The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably came from: https://test-videos.co.uk/bigbuckbunny/mkv
Meanwhile I will try a different file -- I use bbb because it is bigger than most of my test cases and then is still only 10 minutes long.
I think most tsmuxer users use it from win/mac.... so, our linux-only program driving Linux tsmuxer with hand-hacked ffmpeg might hit some less-known codepath.. so if you can upload resultant m2ts file somewhere I'll link it into issue, because this is what usually asked tehre - problematic ts file to look at.. ..
If you can prepare appimage with all those patches applied may be someone will test it on Linux too, but I do not hold my breath for this...
On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu < [email protected]> wrote:
> > > On Wednesday, April 27, 2022, Phyllis Smith <[email protected]> > wrote: > >> Much better - now tsmuxer and profile value seem to be reset >> appropriately. >> But now tsmuxer error: >> >> tsMuxeR version 2.6.16-dev. github.com/justdan96/tsMuxer >> Decoding H264 stream (track 1): Profile: [email protected] Resolution: >> 1920:1080i Frame rate: 29.97 >> H.264 muxing fps is not set. Get fps from stream. Value: 29.97 >> 0.0% complete >> Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: >> 48KHz Channels: 5.1 Bits per sample: 16bit >> 18.2% complete >> Finalize ISO disk >> Reading buffer overflow. Possible container streams are not >> syncronized. Please, verify stream fps. File name: >> /tmp/bd_20220427-090605/bd.m2ts >> > > > can you provide example stream for tsmuxer's developers? > https://github.com/justdan96/tsMuxer/issues > > I can enter issue for you, just need link to file in question... > > >> On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu < >> [email protected]> wrote: >> >>> >>> >>> On Wednesday, April 27, 2022, Phyllis Smith < >>> [email protected]> wrote: >>> >>>> Adding use_tsmuxer = 0 after use_farmed = 0 did not work (I did >>>> full rebuild just to make sure). There must be a different spot >>>> It is possible that the 5:1 audio limitation is Fedora? >>>> >>> >>> no, just diff between av_ch_layout_5point1 and >>> av_ch_layout_5point1_back .... >>> >>> >>> try attached patches? one is for thirdparty/src another for cin >>> herself.. >>> >>> >>> >>>> On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Wednesday, April 27, 2022, Phyllis Smith < >>>>> [email protected]> wrote: >>>>> >>>>>> Andrew, 10 million "mega" tests later, I finally figured it >>>>>> out. Neither the chosen "Profile" or "tsmuxer" setting is getting reset to >>>>>> "Bluray" for profile and "no tsmuxer" for tsmuxer. >>>>>> >>>>>> So what was happening is I loaded a file with 5:1 audio, chose >>>>>> LPCM and TSMUXER and the error message of: >>>>>> * [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout >>>>>> '5.1' is not supported* >>>>>> which is fine as long as I document that. But then I would >>>>>> load Big Buck Bunny (also 5:1 audio) and since I saw that tsmuxer was not >>>>>> checked and lpcm was not highlighted, I thought is should work and it did >>>>>> not because both LPCM and TSMUXER will still "on". >>>>>> >>>>>> Since I am not sure if I can get it right, could you provide >>>>>> the lines of code to change so that the profile and tsmuxer are reset to >>>>>> default "not on" values every time BD Render is chosen from the File >>>>>> pulldown? Then I can do a final test and check into GIT. Thanks, Phyllis >>>>>> >>>>> >>>>> >>>>> >>>>> try to add 'use_tsmuxer = 0; >>>>> >>>>> at this block? >>>>> >>>>> int CreateBD_Thread:: >>>>> option_presets() >>>>> { >>>>> // reset only probed options >>>>> use_deinterlace = 0; >>>>> use_scale = Rescale::none; >>>>> use_resize_tracks = 0; >>>>> use_wide_audio = 0; >>>>> use_labeled = 0; >>>>> use_farmed = 0; >>>>> >>>>> in cinelerra/bdcreate.C? >>>>> >>>>> >>>>> >>>>>> On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Tuesday, April 26, 2022, Phyllis Smith < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Andrew, if instead of choosing lpcm as the profile with the 2 >>>>>>>> patches in, I choose the standard bluray, it works. >>>>>>>> >>>>>>>>> >>>>>>>>> note, even if file named like c file it actually diff.. >>>>>>>>> >>>>>>>>> but both patches as send works for me as after full >>>>>>>>> rebuild.. >>>>>>>>> / >>>>>>>>> >>>>>>>>> if you (re)move those last two patches from tirdparty/src >>>>>>>>> error (can't find codec..) disappears? >>>>>>>>> >>>>>>>> Yes. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> do you have some other libavcodec headers installed? >>>>>>> >>>>>>> what ldd bin/cin (assuming you run from src root for single >>>>>>> user) says? >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> >>>>>>>>>>> but strange. you rebuild cin executable too? (because we >>>>>>>>>>> link statically I typed "touch cinelerra/new.C" and this forced rebuild >>>>>>>>>>> of this file and re-linking of executable...) >>>>>>>>>>> >>>>>>>>>> I do full rebuilds by running "make clean" which deletes >>>>>>>>>> all of the thirdparty libraries and then do a full rebuild with >>>>>>>>>> "./bld.sh". Goes pretty fast on this laptop and it is not worth the >>>>>>>>>> aggravation to only rebuild changed itemsl >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> does ffmpeg from thirdparty lists pcm_bluray as supported >>>>>>>>>>> encoder? >>>>>>>>>>> >>>>>>>>>> It must because what is checked into GIT, lets me choose >>>>>>>>>> the lpcm profile and on the bluray player, the info button clearly displays >>>>>>>>>> it as lpcm. >>>>>>>>>> >>>>>>>>> >>>>>>>>> try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray >>>>>>>>> >>>>>>>>> [root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg >>>>>>>> -codecs | grep bluray >>>>>>>> DEAI.S pcm_bluray PCM signed 16|20|24-bit >>>>>>>> big-endian for Blu-ray media >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Monday, April 25, 2022, Phyllis Smith < >>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Andrew, applied ffmpeg-4.4.patch_12 and >>>>>>>>>>>>>> ffmpeg-4.4.patch99 and it compiles but fails with error message "open >>>>>>>>>>>>>> failed pcm_bluray:/tmp/bd_date_tme/bd.m2ts" as seen in the attached png >>>>>>>>>>>>>> file. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> strange. >>>>>>>>>>>>> >>>>>>>>>>>>> can you double-check patches applied correctly (by >>>>>>>>>>>>> comparing pcm-bluenc.c I attached earlier and actual file in >>>>>>>>>>>>> thirdparty/ffmpeg/libavcodec? ) >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu < >>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Paul fixed bug preventing tsmuxer from recognizing our >>>>>>>>>>>>>>> lpcm audio stream >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I backshoed fix into our ffmpeg 4.4.. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I think having it all worked in monthly release quite >>>>>>>>>>>>>>> important, even if names of patches kinda high... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> also attached raw pcm-bluenc file as I hacked it, and >>>>>>>>>>>>>>> fix/patch as downloaded from gitweb.. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://github.com/justdan96/tsMuxer/issues/580 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6a... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>
participants (2)
-
Andrew Randrianasulu -
Phyllis Smith