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

update #16

Merged
merged 54 commits into from Mar 13, 2019
Merged

update #16

merged 54 commits into from Mar 13, 2019

Conversation

tiliarou
Copy link
Owner

No description provided.

yellows8 and others added 30 commits February 24, 2019 22:17
…bPageShow to webShow. Various web improvements including version handling.
…nfigSetUserAgentAdditionalString. Improved web docs.
…w return Result. Moved webWifiCreate/webWifiShow immediately after _webShow in web.c.
…enum WebShimKind_Offline. Minor other web adjustments.
…ose. Updated WebBootDisplayKind. Removed 'Enabled' from WebArgType enums.
…essage and appletProcessMessage (with some improvements), which appletMainLoop now calls.
… webConfigSetPointer, and webConfigSetLeftStickMode. Fixed order of web funcs. Minor other web adjustments.
…tension, webConfigSetTouchEnabledOnContents, webConfigSetPageCache, webConfigSetWebAudio, webConfigSetFooterFixedKind, webConfigSetPageFade, webConfigSetBootLoadingIcon, and webConfigSetPageScrollIndicator. Minor other changes.
…BootAsMediaPlayerInverted. Added _webTLVRead/_webConfigGet*. Improved web docs.
yellows8 and others added 24 commits March 1, 2019 22:49
…ata, and webConfigSetMediaCreatorApplicationRatingAge. Improved web docs.
…s AppletHolder as a param. Added webConfigRequestExit. Renamed WebExitReason_Unknown2 to WebExitReason_Requested.
* Add wrappers for brightness-related functions
This second member indicates the Opus encoder's entropy coder's final
range. While nothing in the service actually does anything with the
final range as far as I can tell, this is specified within RFC 6716
(https://tools.ietf.org/html/rfc6716, see section "6. Conformance") as a
means of ensuring decoder conformance. States as follows:

"In addition, a compliant decoder implementation MUST have
 the same final range decoder state as that of the reference decoder."

So what is likely done when performing compliance testing is the data is
encoded, and then the final range of the encoder is sent via this
header, then during decoding, the final range would be checked against
to ensure that it's valid.
@tiliarou tiliarou merged commit a2a8bf9 into tiliarou:master Mar 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
6 participants