<div dir="ltr"><div class="gmail_default" style="font-size:small">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.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I will prepare an appimage and upload the files as you requested but it will not be done until later this evening.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 27, 2022 at 12:16 PM Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com">randrianasulu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br>On Wednesday, April 27, 2022, Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com" target="_blank">phylsmith2017@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">The file is Big Buck Bunny bbb-1920x1080-cfg06.mkv and probably came from:</div><div class="gmail_default" style="font-size:small"> <a href="https://test-videos.co.uk/bigbuckbunny/mkv" target="_blank">https://test-videos.co.uk/bigbuckbunny/mkv</a></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">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.<br></div></div></blockquote><div><br></div><div><br></div><div>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.. .. </div><div><br></div><div>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... </div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 27, 2022 at 11:19 AM Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com" target="_blank">randrianasulu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br>On Wednesday, April 27, 2022, Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com" target="_blank">phylsmith2017@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">Much better - now tsmuxer and profile value seem to be reset appropriately.</div><div class="gmail_default" style="font-size:small">But now tsmuxer error:</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">tsMuxeR version 2.6.16-dev. <a href="http://github.com/justdan96/tsMuxer" target="_blank">github.com/justdan96/tsMuxer</a><br>Decoding H264 stream (track 1): Profile: High@4.1 Resolution: 1920:1080i Frame rate: 29.97<br>H.264 muxing fps is not set. Get fps from stream. Value: 29.97<br>0.0% complete<br>Decoding LPCM stream (track 2): Bitrate: 4608Kbps Sample Rate: 48KHz Channels: 5.1 Bits per sample: 16bit<br>18.2% complete<br>Finalize ISO disk<br>Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: /tmp/bd_20220427-090605/bd.m2ts<br></div></div></blockquote><div><br></div><div><br></div><div>can you provide example stream for tsmuxer's developers? </div><div><a href="https://github.com/justdan96/tsMuxer/issues" target="_blank">https://github.com/justdan96/tsMuxer/issues</a></div><div><br></div><div>I can enter issue for you, just need link to file in question... </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 26, 2022 at 7:13 PM Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com" target="_blank">randrianasulu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br>On Wednesday, April 27, 2022, Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com" target="_blank">phylsmith2017@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">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</div><div class="gmail_default" style="font-size:small">It is possible that the 5:1 audio limitation is Fedora?<br></div></div></blockquote><div><br></div><div>no, just diff between av_ch_layout_5point1 and av_ch_layout_5point1_back .... </div><div><br></div><div><br></div><div>try attached patches? one is for thirdparty/src another for cin herself.. </div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 26, 2022 at 6:26 PM Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com" target="_blank">randrianasulu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br>On Wednesday, April 27, 2022, Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com" target="_blank">phylsmith2017@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">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. <br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">So what was happening is I loaded a file with 5:1 audio, chose LPCM and TSMUXER and the error message of: <br></div><div class="gmail_default" style="font-size:small"> <i> [pcm_bluray @ 0x7f002b5ff9c0] Specified channel layout '5.1' is not supported</i></div><div class="gmail_default" style="font-size:small">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".</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">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<br></div></div></blockquote><div><br></div><div><br></div><div><br></div><div>try to add 'use_tsmuxer = 0;</div><div><br></div><div>at this block? </div><div><br></div><div>int CreateBD_Thread::</div><div>option_presets()</div><div>{</div><div>// reset only probed options</div><div> use_deinterlace = 0;</div><div> use_scale = Rescale::none;</div><div> use_resize_tracks = 0;</div><div> use_wide_audio = 0;</div><div> use_labeled = 0;</div><div> use_farmed = 0;</div><div><br></div><div>in cinelerra/bdcreate.C? </div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 26, 2022 at 7:22 AM Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com" target="_blank">randrianasulu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br>On Tuesday, April 26, 2022, Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com" target="_blank">phylsmith2017@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-size:small" class="gmail_default">Andrew, if instead of choosing lpcm as the profile with the 2 patches in, I choose the standard bluray, it works.</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br></div><div>note, even if file named like c file it actually diff.. </div><div><br></div><div>but both patches as send works for me as after full rebuild.. </div><div>/</div><div><br></div><div>if you (re)move those last two patches from tirdparty/src error (can't find codec..) disappears? </div></blockquote><div><span class="gmail_default" style="font-size:small">Yes.</span> </div></div></div></blockquote><div><br></div><div><br></div><div>do you have some other libavcodec headers installed? </div><div><br></div><div>what ldd bin/cin (assuming you run from src root for single user) says? </div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br></div><div>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...) </div></blockquote><div><span class="gmail_default" style="font-size:small">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</span> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br></div><div>does ffmpeg from thirdparty lists pcm_bluray as supported encoder? </div></blockquote><div><span class="gmail_default" style="font-size:small">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.<br></span></div><div></div></div></div></blockquote><div><br></div><div>try thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray</div><div><br></div></blockquote><div><span class="gmail_default" style="font-size:small"></span>[root@keystone cinelerra-5.1]# thirdparty/ffmpeg-4.4/ffmpeg -codecs | grep bluray<br><div dir="ltr"><div class="gmail_default" style="font-size:small"> DEAI.S pcm_bluray PCM signed 16|20|24-bit big-endian for Blu-ray media</div></div><span class="gmail_default" style="font-size:small"></span> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br></div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 25, 2022 at 2:00 PM Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com" target="_blank">randrianasulu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><br>On Monday, April 25, 2022, Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com" target="_blank">phylsmith2017@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-size:small">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.<br></div></div></blockquote><div><br></div><div>strange. </div><div><br></div><div>can you double-check patches applied correctly (by comparing pcm-bluenc.c I attached earlier and actual file in thirdparty/ffmpeg/libavcodec? )</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Apr 24, 2022 at 9:18 AM Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com" target="_blank">randrianasulu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Paul fixed bug preventing tsmuxer from recognizing our lpcm audio stream<div><br></div><div>I backshoed fix into our ffmpeg 4.4.. </div><div><br></div><div>I think having it all worked in monthly release quite important, even if names of patches kinda high... </div><div><br></div><div>also attached raw pcm-bluenc file as I hacked it, and fix/patch as downloaded from gitweb.. </div><div><br></div><div><a href="https://github.com/justdan96/tsMuxer/issues/580" target="_blank">https://github.com/justdan96/tsMuxer/issues/580</a></div><div><br></div><div><a href="https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6ad4d343afe0546d..058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm-blurayenc.c" target="_blank">https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/037fa0437d2aead40c1f786c6ad4d343afe0546d..058a1ff9b4cdbd2e1a93acc8bf0365e7d01cc9f4:/libavcodec/pcm-blurayenc.c</a></div><div><br></div><div><a href="https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf35ede2ba05aa" target="_blank">https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/93dfb6afddb278218da7f8c696bf35ede2ba05aa</a></div>
</blockquote></div>
</blockquote>
</blockquote></div>
</blockquote>
</blockquote></div></div>
</blockquote>
</blockquote></div></div>
</blockquote>
</blockquote></div>
</blockquote>
</blockquote></div>
</blockquote>
</blockquote></div>
</blockquote>
</blockquote></div>
</blockquote>
</blockquote></div>