<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><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>