-
-
Notifications
You must be signed in to change notification settings - Fork 9k
RFC 45-5: Allow selection of the audio codec/encoder #8090
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
Conversation
4ed0766 to
ee0e3c5
Compare
07ee359 to
54284b0
Compare
fce386d to
573b2de
Compare
075d1ea to
f8f7163
Compare
f8f7163 to
4f972c4
Compare
007141a to
4999cbc
Compare
f7f26f2 to
8d73e25
Compare
168848c to
7875274
Compare
1aa2415 to
eb2fe43
Compare
If the server URL is not an RTMP(S) URL, the protocol field becomes required. The output field becomes required on non-RTMP(S) services to keep backward compatibility. Also skip service if the protocol is not available.
The fallback in now inside the output.
MPEG-TS standard is not ready for AV1
Also remove Opus-only "supported audio codecs" in the services JSON.
Also refactors AAC bitrate map too.
|
It's been merged 3 days ago so my remarks will be too late. Nevertheless it is unfortunate that there's been no discussion in this PR of the changes done to Simple Output Recording. They are per se outside the purview of RFC45 which deals with Protocols (and not Recording!) and should have been at the very least in a separate commit. |
Description
This PR is about the RFC 45.
Depends on:
Allow users to choose AAC or Opus to stream and record.
Stream side, codec are shown depending on the protocol used and the service compatibility.
If using different encoders in advanced, only common bitrates will be shown, this is made to avoid to over-complexify the UI.
Motivation and Context
Part of the implementation of the RFC 45.
How Has This Been Tested?
Only testing trying to stream SRT with opus and AAC, might need more testing.
Types of changes
Checklist: