-
Notifications
You must be signed in to change notification settings - Fork 24
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
fourCcList definition should provide for a wildcard #15
Comments
Interesting idea. It might behove to expand the special style even further to help solve #10. Please see my comments there. |
i followed up in #10 as well, but for completeness here: i don't think we should add delimiters and ordering to
|
note though that "any audio codec" and "any video codec" would be solved with |
Fixed, please see https://veovera.org/docs/enhanced/enhanced-rtmp-v2. |
in traditional RTMP, clients that are capable of receiving any codec (like recorders or forwarders) can just set the
videoCodecs
andaudioCodecs
fields to0xffff
to enable all possible code points. however, the number of possible future fourCCs is way too large to list them all. to accommodate clients that can handle any codec, i propose defining a special value to include in thefourCcList
codec list (or its replacement(s)) to indicate "any/all codecs".i further propose this special value to be the one-character string "
*
" (ASTERISK
). being one character long it can never conflict with any real fourCC, and*
is already commonly used to mean "wildcard".The text was updated successfully, but these errors were encountered: