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 itemsldoes 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 <randrianasulu@gmail.com> wrote:
On Monday, April 25, 2022, Phyllis Smith <phylsmith2017@gmail.com> 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 <randrianasulu@gmail.com> wrote:Paul fixed bug preventing tsmuxer from recognizing our lpcm audio streamI 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..