Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Hanuma Teja Maddali <teja.maddali@headwallvr.com>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Request for help with decoding an mpeg2ts stream into a Unity app
Date: Mon, 3 Mar 2025 18:08:43 -0500
Message-ID: <CA+czF3+6VcCeo2ZKpF6j_NouHO70iyyeK7MypqWyfOpGOzwsrA@mail.gmail.com> (raw)

Hello,

We're looking for someone who can help with creating a Unity package for
decoding streaming video into Unity with minimal lag. From some googling,
we've found a good set of ffmpeg and ffplay arguments to stream an mpeg2-ts
udp stream with low latency on a windows desktop.
ffplay -hwaccel cuda -fflags nobuffer -flags low_delay -probesize 32
-analyzeduration 0 -strict experimental -framedrop -f mpegts -vf setpts=0
-i udp://@255.255.255.255:xxxx . However, we weren't able to find a way to
decode, and render this stream to a texture on a gameobject in our Unity
project.
We couldn't find many helpful community links for this purpose. The ones
that we did find were focussing on screen recording and encoding Unity
scenes into video or streaming a unity scene rather than decoding a stream
into a Unity scene. We've also already tried the vlc csharp package for
Unity but are unable to get the same low-latency performance as with
ffplay. Any help on this would be great!

Thanks!
_______________________________________________
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-03-03 23:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CA+czF3+6VcCeo2ZKpF6j_NouHO70iyyeK7MypqWyfOpGOzwsrA@mail.gmail.com \
    --to=teja.maddali@headwallvr.com \
    --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