Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: ffmpeg@gallery.co.uk
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Patches to add libomt OpenMediaTransport support to FFmpeg
Date: Wed, 13 Aug 2025 14:00:01 +0100
Message-ID: <611DDA9F-73BB-4EC8-94CA-FB94783589A9@gallery.co.uk> (raw)

Hi Folks

We are part of the group creating a new open source and free to use professional IP Video protocol called OMT (open media transport)
It's similar to NDI in many ways, but completely open source and royalty free.

The protocol will officially launch on August 18th.
You can read about it here:
https://openmediatransport.org/
and 
https://github.com/openmediatransport/
The github is not public yet, but will be after the launch

The video codec used in OMT is actually the same as the vmix codec which is already implemented in decoder-only form in FFMPEG.

We have already completed implementation of this protocol into FFMPEG 7 and I enclose patches to add this to the current FFmpeg origin/master.

To build this also requires the pre-built omt libraries which are available at   
https://github.com/openmediatransport/libomtnet/releases
also, available from:    
https://www.sienna-tv.com/omt/OMTlibs.zip

Please let me know if you have any questions

Best Regards
Mark Gilbert



_______________________________________________
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".

             reply	other threads:[~2025-08-13 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13 13:00 ffmpeg [this message]
2025-08-13 13:35 ` Derek Buitenhuis

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=611DDA9F-73BB-4EC8-94CA-FB94783589A9@gallery.co.uk \
    --to=ffmpeg@gallery.co.uk \
    --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