вт, 10 июн. 2025 г., 19:31 Terje J. Hanssen <[email protected]>:
> > Den 10.06.2025 17:48, skrev Andrew Randrianasulu: > > > > вт, 10 июн. 2025 г., 18:43 Phyllis Smith <[email protected]>: > >> Although the patch >> 0001-Fixup-seg-name-to-segment-so-format-gui-button-work.patch works at >> our current version of ffmpeg 7.0 as does the audio render format >> "bluray_lpcm.seg" with the first line of "segment_format=mpegts", the >> corresponding video render format "mpeg2hd422p.seg" does not -- at least it >> fails for me. Its error message is: >> >> FFMPEG::encode_activate: write header failed /tmp/ccc.seg >>> err: Muxer not found >>> >> >> I will see what I may have done wrong. >> > > if it literally reads > > > segment mpeg2video > segment_format=mpegts > segment_time=00:10 <= your segment time > reset_timestamps=1 > cin_pix_fmt=yuv422p > > then "your segment time" was comment not meant to put in there in this > form, just reminder for human reader .... may be it choke on this? > > > Another question: > Maybe we should extend our segment counts to 3 digits, that is replace our > current %02d with %03d ? > Isn't this something you set as part of filename? Refere to these ffmpeg examples > https://ffmpeg.org/ffmpeg-formats.html#Examples-15 > > https://ffmpeg.org/ffmpeg-formats.html#Examples-15 >
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
