-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
H265: FFmpeg support HEVC over RTMP, etc. #2562
Comments
This could be two questions:
|
This comment has been minimized.
This comment has been minimized.
FFmpeg's avformat does not support custom codec IDs like H.265 in flv. You can refer to this link for modification:
|
This comment has been minimized.
This comment has been minimized.
This comment was marked as outdated.
This comment was marked as outdated.
The problem is, even if it is resolved, can the server handle the load when using ffmpeg (CPU situation) to convert 10 streams simultaneously (h265->h264)?
|
It seems like your problem is about ffmpeg wanting to include flv support for h265. Refer to this link to compile ffmpeg4.1 by yourself: https://github.com/runner365/ffmpeg_rtmp_h265 The fearue/h265 branch of SRS supports h265 in flv. Are there any issues with h265 in the SRS streaming media server?
|
@runner365 The srs feature/h265 can successfully receive H.265 streams and also distribute FLV and RTMP H.265 streams without any issues. Currently, I want to configure the transcode feature to convert the incoming H.265 stream into an additional H.264 stream. When compiling the srs feature/h265 branch, I added the --ffmpeg-tool=on parameter. However, the compiled objs/ffmpeg/bin/ffmpeg does not support H.265. So, I manually compiled a version of FFmpeg from Kingsoft Cloud and plan to use this compiled FFmpeg for transcoding in transcode.
|
My internet monitoring scenario involves a large number of streams being pushed, but very few streams being pulled or hardly anyone watching them normally. @crazymxm What I have in mind is to use the originCluster mode, where transcoding at the Edge side will only be done on-demand when someone is watching the stream (i.e., transcoding will only be done when there are viewers). We just need to add machines on the server side, and we will use GPUs or dedicated NETINT transcoding cards for the transcoding process.
|
This comment was marked as outdated.
This comment was marked as outdated.
H265 transcoding consumes a lot of CPU resources. Adjusting ffmpeg parameters can reduce the latency of transcoded streaming playback.
|
Dup to #465
The text was updated successfully, but these errors were encountered: