Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fourCcList description should explicitly state support for receiving those codecs #14

Closed
zenomt opened this issue May 26, 2023 · 1 comment
Closed

fourCcList description should explicitly state support for receiving those codecs #14

zenomt opened this issue May 26, 2023 · 1 comment

Comments

@zenomt
Copy link

zenomt commented May 26, 2023

the fourCcList currently says it contains strings each "representing a supported video codec". as discussed at #11 (comment) , the description should be clarified to say that this lists codecs that the client is able to receive and process.

the practical historical usage of the videoCodecs and audioCodecs bitmaps sent by the client in the connect command has been to indicate which codecs the client is able to receive. historically it's been irrelevant to the server what codecs a client can send, since the server could handle all traditional RTMP codecs.
@zenomt zenomt mentioned this issue May 26, 2023
Open
@veovera
Copy link
Owner

veovera commented May 16, 2024

Fixed please see <link>

@veovera veovera closed this as completed May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zenomt @veovera