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.

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

Unclear on mine type paramters #76

Closed
fluffy opened this issue Oct 4, 2016 · 2 comments
Closed

Unclear on mine type paramters #76

fluffy opened this issue Oct 4, 2016 · 2 comments

Comments

@fluffy
Copy link
Contributor

fluffy commented Oct 4, 2016

It has the text

The container and codec format(s) for the recording, which may include any parameters that are defined for the format.

Not sure what types of parameters are included here. Can I provide H.264 fmtp like parameters?

@yellowdoge
Copy link
Member

Mimes are weird creatures, specially in what regards to the parameters (i.e. those entries after the type and subtype): they are subtype (==codec) specific, in other words you should go to the IANA Media Types appropriate entry and check the specifics. The Spec delegates the definition of any parameters to the appropriate MIME type template. For H264 for example I see there is a parameter 'use-level-src-parameter-sets' that might be what you are referring to. Does this make sense?

yellowdoge added a commit to yellowdoge/mediacapture-record that referenced this issue Oct 31, 2016
- Added more info on Mime Types as a note (touches w3c#78 and w3c#76),
 including referencing RFC6381, and adding the mentioned RFCs as
 references.
- Used 'fire an event named X' and reference what 'dispatch' means (w3c#69)
- Removed change log section, not needed and outdated.
- Added links here and there.
- Reflowed text.
@yellowdoge
Copy link
Member

More conversation in #78, @fluffy, let's have any further conversation there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants