From: Jacob Lifshay via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Jacob Lifshay <programmerjake@gmail.com>
Subject: Re: [FFmpeg-devel] Patches to add libomt OpenMediaTransport support to FFmpeg
Date: Tue, 19 Aug 2025 02:43:04 -0700
Message-ID: <F5C52DB2-1064-487F-87CD-3547225F2318@gmail.com> (raw)
In-Reply-To: <A44D4DF5-9A73-481F-8578-C4184AD66EFB@gallery.co.uk>
On August 19, 2025 1:45:01 AM PDT, ffmpeg--- via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
> We have have already completed implementation of this protocol into FFMPEG 7 and I enclose patches to add this to the current FFmpeg origin/master.
>
>
> If the .eml patches dont make it through the email, here are links to them:
> https://www.sienna-tv.com/omt/0001-Added-libomt-support-for-OpenMediaTransport.eml
> https://www.sienna-tv.com/omt/0002-Patched-libomt-into-FFmpeg.eml
It seems to me that it might be better to add libomt as a ffmpeg protocol rather than as devices, devices seem to be intended only for things plugged into your computer or local in some sense (e.g. screen capture). libomt seems to be for network stuff.
Also, you may want to consider opening a PR on the experimental forgejo instance: https://code.ffmpeg.org/FFmpeg/FFmpeg
Jacob
_______________________________________________
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 prev parent reply other threads:[~2025-08-19 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 8:45 ffmpeg--- via ffmpeg-devel
2025-08-19 9:43 ` Jacob Lifshay via ffmpeg-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-13 13:00 ffmpeg
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=F5C52DB2-1064-487F-87CD-3547225F2318@gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=programmerjake@gmail.com \
/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