-
Notifications
You must be signed in to change notification settings - Fork 602
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
Try h265 #615
Conversation
Preview environment mpromonet-webrtc-streamer-pr-615 is being deployed... |
谷歌已经支持HEVC的H265了,使用最新版本0.8.2 还是无法播放呢? |
所以 现在已经支持H265了? |
是否需要更新 webrtcstreamer.js |
Hi, The H265 support is not limited by webrtcstreamer.js, you can use another way to display webrtc stream it will be the same.
Best Regards, |
I used the same JavaScript code to set the RTSP URL, and updated the webrtc-streamer executable to the latest version (v0.8.3). I utilized the "-o" option in the command line to pass the stream to the web. When the stream is in h264 format, I can view the video in the browser; however, I am unable to do so when the stream is in h265 format. My JavaScript code involves importing "webrtcstreamer.js" for use. T_T (ps.) my chrome version is 118.0.5993.71 |
Hi @strong0716, I am sorry to do the same answer than before, but it is needed that the browser support h265, you can check this with Best Regards, |
I tested the command console.log(RTCRtpReceiver.getCapabilities('video').codecs) in my Chrome browser and indeed, I didn't see support for h265. Thank you! |
Hi @LucaArteco, If you are using -o option, the H265 frame should be forwarded through webrtc. Is it working with a H264 stream ? Best Regards, |
Hi @mpromonet yes everything's fine on H264, and I kept the -o option. Recap:
Did someone actually see the HEVC WebRTC stream working on any browser? I would like to replicate a working example to see if maybe the issues are in my RTSP out (VLC can play it but VLC eats everything usually) EDIT: Just adding some logs after comparing two sessions. One working H.264 and one not working (H.265) I made a little amendment in case of H.265 in order to force the priority for that code. It worked (for what I got) and now in case of h265 source I got the H265 (104 in my SDP) as first codec for both Local and Remote Description. webrtc-streamer log
Codec stats (from pc.getStats())
H.264
I've noticed that additional parameter, sdpFmtpLine, which is not appearing for H265 Thanks! |
Hi @LucaArteco, I am still waiting for a support on windows or linux to make tests... Best Regards, |
Hi @mpromonet thanks, we're now testing your commit. |
Hi Luca, |
Hi Michel I've tested your last commit but the problem is still I'm receiving bytes, but no frames were decoded on client side.
On client side, I see Bytes flowing but no decoding Many thanks, |
Hi Luca, In the log there is an error parsing SPS, but there is also an error forwarding PPS, I fixed this in 093e8b2. Best Regards, |
Hi luca, |
Safari 17.5 no longer uses H265 AnnexB packetization, they switched to RFC 7798 which means almost the same code as for H264 should also work for H265. |
Description
This pull request try to use recently support h265 parsing in webrtc SDK, with -o it forward h265 packet from RTSP to WebRTC.
It needs a web browser that support webrtc with h265 to validate and improve it.
Related Issue
#600
#611
Motivation and Context
Types of changes