Setting project framerate to 29.97 fixed that!
My default testing file is 29.97 so that is what I have been testing all along. On Thu, Jun 25, 2026 at 4:15 PM Andrew Randrianasulu < randrianasulu@gmail.com> wrote:
пт, 26 июн. 2026 г., 00:47 Andrew Randrianasulu <randrianasulu@gmail.com>:
чт, 25 июн. 2026 г., 17:27 Phyllis Smith <phylsmith2017@gmail.com>:
Both Andrea and I tested the patch with Andrea's notes in BT #677. I also get bad results and am still looking for a workaround other than using a 2025 older AppImage prior to 8.0 - right now we are at FFmpeg 8.1 and I would like to at least check 8.0 to see how that works.
Strange. On termux without audio and with Terje's HDV short clip as input (1440*1080, interlaced)
I do not see "patch welcome" messages with my patch and dynamic ffmpeg libs 8.1.2
Can you test
1) without audio 2) with different input files?
I tested some FHD webm at 59.94 fps and it was failing with my patch too
Setting project framerate to 29.97 fixed that!
So, from beginning of bug 677 It seems main file was 59.97 fps. I wonder if we also hit some validation logic in mxf, as more strict broadcast container?
Unfortunately even with setting loglevel=debug in bin/ffmpeg/encode.opts I do not see additional output from muxer itself, so it a bit hard to figure out what gies on ...
and if possible with dynamic ffmpeg 8.1.2 ?
On Wed, Jun 24, 2026 at 10:48 PM Andrew Randrianasulu < randrianasulu@gmail.com> wrote:
Can you check if this patch fixes mxf profiles, while still leaving our language info etc in ts and other formats?
чт, 25 июн. 2026 г., 06:02 Andrew Randrianasulu < randrianasulu@gmail.com>:
чт, 25 июн. 2026 г., 05:17 Phyllis Smith <phylsmith2017@gmail.com>:
Andrew, I will also try to figure out what the cause is using gdb.
I tried to set breakpoint ("b" command in gdb ) to
avformat_write_header
but because Termux libavformat stripped from symbols for size reasons
single stepping ("s" command) just returned me to our function with already-set error code.
if I skip this error checking and go ahead libavformat segfaults kater on openjpeg/DNxHR at least (mxf openjpeg profile need change of encoder from libopenjpeg to jpeg2000 - libopenjpeg encoder was removed If I remember correctly some time ago from ffmpeg).
On Wed, Jun 24, 2026 at 6:08 PM Andrew Randrianasulu < randrianasulu@gmail.com> wrote:
> > > чт, 25 июн. 2026 г., 00:51 Phyllis Smith via Cin < > cin@lists.cinelerra-gg.org>: > >> See https://bug.cinelerra-gg.org/view.php?id=677 for problem >> and workaround to use an old 2025 AppImage. >> Root cause appears to me to be unimplemented patch - at least by >> February 2026 version of FFmpeg 8.1 - and hoping Andrew-R can check to see >> if by now there is a patch. Details in Mantis Bug Tracker of testing done. >> > > Yes, I am looking into it > > So far using termux's shared ffmpeg 8.1.2 libs I hit same error. > > Not really obvious what causes it - avformat_wrie_header returns > error, but there is no muxer-specific mxf write_header function in > libavformat/mxfenc.c ? > > >> On Wed, Jun 24, 2026 at 5:17 AM Andrea paz via Cin < >> cin@lists.cinelerra-gg.org> wrote: >> >>> On MantisBT, Quintao filed a bug report (BT 677) because he can't >>> render avc_intra_100 in MXF format. He can, however, use MXF with DNxHR. I, >>> on the other hand, can't use any MXF presets, but I can render >>> avc_intra_100 in MOV format. Are any of you able to render in MXF? >>> >>> _______________________________________________ >>> Cin mailing list -- cin@lists.cinelerra-gg.org >>> To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org >>> >> _______________________________________________ >> Cin mailing list -- cin@lists.cinelerra-gg.org >> To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org >> >