From: Howard Peacock <howard_peacock-at-hotmail.com@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] Fix incomplete implementation of framesync options for overlay filter Date: Fri, 5 Jan 2024 11:36:21 +0000 Message-ID: <LO4P123MB5350F4165F6319DA91D540AEE7662@LO4P123MB5350.GBRP123.PROD.OUTLOOK.COM> (raw) Hi - first time posting, so apologies in advance if this breaks an etiquette rule. Just a request / suggestion that the 'overlay' filter be updated to implement all the framesync options - including ts_sync_mode. Currently - although https://ffmpeg.org/ffmpeg-filters.html#overlay-1 states that 'This filter also supports the framesync options' - attempting to set ts_sync_mode results in an error - for example: $ ffmpeg -f v4l2 -i /dev/video0 -filter_complex "[0:v][0:]overlay=x=20:y=20:ts_sync_mode=nearest" -f flv - | ffplay - Error initializing complex filters. Option not found Running ffmpeg -h filter=overlay (and looking at latest source code) confirms that the ts_sync_mode framesync option is not currently implemented in the overlay filter. The reason for asking is that I'm in a programming context with multiple livestreams (with different start times) and multiple overlays where the second overlay needs to use the 'nearest' rather than 'default' sync behaviour to keep everything in sync, and it's not currently possible - I have to dial in delays manually. I was thinking of posting as a bug because of the mismatch between documentation and implementation but it's probably a feature request in fairness! Thanks! h _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next reply other threads:[~2024-01-05 11:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-05 11:36 Howard Peacock [this message] 2024-01-07 14:54 ` Stefano Sabatini
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=LO4P123MB5350F4165F6319DA91D540AEE7662@LO4P123MB5350.GBRP123.PROD.OUTLOOK.COM \ --to=howard_peacock-at-hotmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git