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