-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Transcoding Bitrate Not in control #27
Comments
We have been discussing the solution of the problem a while ago. This is an alternative to low latency and quality issues. Maybe we have to replace the encoder with OpenH264 to x264. If we solve the problem, I will reply again. Thank you for your contribution. |
Thanks @JehoenHan for looking into the issue. I appreciate your contribution to the opensource community. Is there any workaround where we can ingest RTMP and take webrtc out without transcoding? Also i too agree and think that the Encoding should be replaced with HW accelerated NVENC or QSV. Regards, Jackson |
RTMP supports H.264 and AAC. However, to support WebRTC in most browsers, VP8 and OPUS are required. So we do not yet support bypass (or codec copy). We are going to support more ingest protocols (such as MPEGTS / UDP) and we plan to support bypass function at that time. |
I just wanted to leave a comment that I am really looking forward to having support for direct streaming without transcoding. UDP would be just fine as the input protocol. |
We decided to develop the Bypass Profile (#28) feature in v1.0 |
Hardware accelerated transcoding is planned for #23 . |
Hello @jacksonvm. |
hi @sfreet
|
Hello @janyo1201 |
@sfreet |
Hi Han, I was able to solve it temporarily by setting RC_BITRATE_MODE in the file src/projects/transcode/codec/transcode_codec_enc_avc.cpp. Will soon test the libx264 built and update. Regards, Jackson |
Hello @jacksonvm |
@jacksonvm @Ape - are you still interrested in the video bypass feature? I actually implemented that for my needs, so if that is useful I can share a feature branch with you. |
@rubu , Thats great, yes Im very much interested in the video bypass feature as re scaling and transcoding was eating up my CPU. Also I have tested out the x264 thread and it works flawless on the bitrate control side. Regards, Jackson |
@jacksonvm - so I have a branch (https://github.com/rubu/OvenMediaEngine/tree/feature/dynamic-fragmentation-header) where I made the video bypass derived from master (seems to work in our uses cases, just set true in the video encode you need to bypass. I will try and integrate these changes in upstream dev, so that it is released as a part of the official release, but if you wan't to try it out, you can simply clone that branch. |
This has been patched in version 0.10.0. |
Hi Team,
I'm ingesting an RTMP feed with 1280x720p and Video Bitrate 1M, but in the OME server.xml also I have mentioned the H264 video bitrate as 500K ,RES 620x360 and Opus audio 96k. The output from OME are webrtc and HLS. I notice that the bandwidth of the output is always between 1.5M to 2.5M. But the resolution is getting changed which means Transcoding is working. I assume there is an issue with Bitrate Control.
Regards,
Jackson
The text was updated successfully, but these errors were encountered: