can you try to add strict -1 to mxf profiles and see how it goes?
Without the patch in and using strict -1, I am getting the same results.
IMPORTANT NOTE - I only have issues with my test file with the mxf_avcintra_100.mxf format, NOT any of the DNx ones.  Not sure which ones Andrea still have issue with; but again, I use 48000 samplerate and 29.97 fps.

Just another note, I do get an audio/video file created when rendering avcintra_100, BUT it will not load to the timeline and when I "ffplay" using a 2019 compiled ffplay, I get the following error messages.  The audio sounds decent, but the video gets corruption as noted in the following error messages:
 [root@keystone tmp]# ffplay avcstrict.mxf                                                                                        
[mxf @ 0x7f179c000bc0] broken or empty index                                                                                    
Input #0, mxf, from 'avcstrict.mxf':KB vq=    0KB sq=    0B f=0/0                                                                
  Metadata:                                                                                                                      
    operational_pattern_ul: 060e2b34.04010101.0d010201.01010900                                                                  
    uid             : adab4424-2f25-4dc7-92ff-000c00000000                                                                        
    generation_uid  : adab4424-2f25-4dc7-92ff-000c00000001                                                                        
    company_name    : FFmpeg                                                                                                      
    product_name    : OP1a Muxer                                                                                                  
    product_version : 62.12.100                                                                                                  
    application_platform: Lavf (linux)                                                                                            
    product_uid     : adab4424-2f25-4dc7-92ff-29bd000c0002                                                                        
    material_package_umid: 0x060A2B340101010501010D0013F2CD2B529471348EF2CD2B00529471348EF200                                    
    timecode        : 00:00:00:00                                                                                                
  Duration: N/A, start: 0.000000, bitrate: N/A                                                                                    
    Stream #0:0: Video: h264 (High 4:2:2), yuv422p10le(pc, smpte170m/unknown/unknown, progressive), 352x240 [SAR 1:1 DAR 22:15    ], 29.97 fps, 29.97 tbr, 29.97 tbn, 59.94 tbc                                                                                    
    Metadata:                                                                                                                    
      file_package_umid: 0x060A2B340101010501010D0013F2CD2B529471348EF2CD2B00529471348EF201                                      
    Stream #0:1: Audio: pcm_s24le, 48000 Hz, 2 channels, s32 (24 bit), 2304 kb/s                                                  
    Metadata:                                                                                                                    
      file_package_umid: 0x060A2B340101010501010D0013F2CD2B529471348EF2CD2B00529471348EF201                                      
[h264 @ 0x7f179c3e0c80] co located POCs unavailableq=    0B f=0/0  
[h264 @ 0x7f179c38b640] co located POCs unavailableq=    0B f=0/0  
[h264 @ 0x7f179c141540] co located POCs unavailableq=    0B f=0/0  
[h264 @ 0x7f179c3528c0] co located POCs unavailableq=    0B f=0/0  
[h264 @ 0x7f179c15e500] co located POCs unavailableq=    0B f=0/0  
[h264 @ 0x7f179c134380] reference picture missing during reorder0  
[h264 @ 0x7f179c134380] Missing reference picture, default is 66670
[h264 @ 0x7f179c3528c0] Missing reference picture, default is 66676
[h264 @ 0x7f179c3a7d80] mmco: unref short failure
[h264 @ 0x7f179c0de940] co located POCs unavailableq=    0B f=0/0  
[h264 @ 0x7f179c3fd340] co located POCs unavailableq=    0B f=0/0  
[h264 @ 0x7f179c0de940] reference picture missing during reorder0  
    Last message repeated 1 times
[h264 @ 0x7f179c0de940] Missing reference picture, default is 66904
    Last message repeated 1 times
[h264 @ 0x7f179c336540] reference picture missing during reorder0  
[h264 @ 0x7f179c336540] Missing reference picture, default is 66914
[h264 @ 0x7f179c36ef40] mmco: unref short failure sq=    0B f=0/0  
[h264 @ 0x7f179c164140] reference picture missing during reorder0  
[h264 @ 0x7f179c164140] Missing reference picture, default is 66946
[h264 @ 0x7f179c0de940] mmco: unref short failure sq=    0B f=0/0  

Sorry for multiple mails in short time.
No problem - keep them coming as you think of them!

On Thu, Jun 25, 2026 at 4:27 PM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:


пт, 26 июн. 2026 г., 01:14 Andrew Randrianasulu <randrianasulu@gmail.com>:


пт, 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 ...

I tried same file in ffmpeg 8.1.2 cli  and get error:

[mxf @ 0xb4000074e7f83c90] Unsupported frame rate 19001/317. Set -strict option to 'unofficial' or lower in order to allow it!                                                                       
 [out#0/mxf @ 0xb400007497f90190] Could not write header (incorrect codec parameters ?): Invalid argument                                                                                              
so even ffmpeg itself is confused now!


this worked (added "strict -1"):

ffmpeg -i /data/data/com.termux/files/home/storage/downloads/Swimming\ with\ Dusty\ -\ dusty\ the\ dolphin\ -\ Inisheer\ -\ Inis\ Oírr\ \ -\ Moxie\ -\ Dusty\ Dolphin\ \[unXz6Ur3yDo\].webm -c:v libx264 -strict -1 -profile:v high422 1.mxf

can you try to add strict -1 to mxf profiles and see how it goes?

Sorry for multiple mails in short time.






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