-
-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Does this module support H.265? #61
Comments
No. |
Maybe you could consider adding SRT support like Wowza had. This would open
the possibility of using H.265 (ffmpeg can be used as a live encoder as it
already supports SRT output).
20.08.2018 04:36 "winshining" <notifications@github.com> napisał(a):
No.
If Adobe doesn't update FLV tag to support H.265 officially, ffmpeg won't
support it, you can see ticket6389 <http://trac.ffmpeg.org/ticket/6389>.
Moreover, players won't support H.265 over RTMP neither. Someone has
attempted to add private tags for FLV. However, it will cost so much to
adapt publishers, servers and players to support the private tags, because
it is not GENERAL.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB049ovgAjahM1QaliF0Ua5DwzjVS7Suks5uSiCVgaJpZM4WDEfP>
.
|
@matiaspl What does |
SRT stands for Secure Reliable Transport - https://www.srtalliance.org/.
It's a quite advanced opensource protocol that allows data streams
(usually "broadcast tv" style MPEG-TS) to be sent over IP networks with
encryption, packet retransmission and forward error correction. There's a
public repository at https://github.com/Haivision/srt
|
@winshining Thanks for your patient reply. So I have to re-encode my media file into H.264 :( |
Hi, @winshining, you've done such a great job! I've searched a long time to see if there are some modules meet my needs that pull streams through http-flv.
But I found it didn't support H.265, right? Do you have a plan to add the feature?
The text was updated successfully, but these errors were encountered: