Talk:AV1

Lossless?

Does this codec support lossless RGB encoding/decoding? That seems like it would be useful information to have in this article. I came here looking for that information, but it was missing. -AlexFolland (talk) 11:29, 31 January 2017 (UTC)

I second that request. I've been reading up on all kinds of sources but could find no information regarding support for a lossless mode.2A02:8109:8700:11A0:8DD1:24F3:1D5D:BEB3 (talk) 14:41, 16 March 2017 (UTC)

If I read the specs correctly, it does: https://webmproject.github.io/av1-bitstream/ 83.87.131.205 (talk) 21:44, 4 July 2017 (UTC)

Yes, it does, see Changelog v1.3.0 too: https://github.com/mbebenita/aom/blob/master/CHANGELOG Slhck (talk) 12:23, 18 September 2017 (UTC)

Logo

Is the logo supposed to be an A+1+v for Av1? Anyway, please add an infobox here. –193.96.224.9 (talk) 12:47, 2 March 2017 (UTC)

lists

Shouldn't we describe important features and the process how features are added in prose instead of bloating the article with those questionable excessive lists? I find such lists to add little value and regard them mostly as a sign for low quality articles.--Flugaal (talk) 20:14, 25 December 2017 (UTC)

For current experiments, let's drop those lacking explanations – that's no sacrifice at all. Actually, it doesn't matter, since that list is supposed to be empty in a month's time. Meanwhile, the list of former experiments will gain at most 5 more (J.Krishnan, STSWE 2017) before it's final. That list, in list form, is golden: All sources we have about the features of the format so far are sparse or outdated, while this list, to the best of our knowledge, is complete! If/when an official or better list or overview of any sort is revealed, we should of course link to that instead.—84.208.177.88 (talk) 22:10, 26 December 2017 (UTC)

I see how you may profit from the knowledge that the list is complete. Maybe it's a useful aid for our work as authors here. But I still don't see how readers profit more from having this info in list form instead of having it in prose. (I don't see what kind of an argument "is golden" is supposed to be.) Therefore, I'll move forward with prosifying this stuff.--Flugaal (talk) 21:06, 14 January 2018 (UTC)

There is no point in putting WP:Too much detail into an encyclopedia article. Regurgitating what can already be found in documentation (rather than coverage in independent reliable sources) doesn't add encyclopedic value to the article. The lists should be removed. ~Anachronist (talk) 21:21, 14 January 2018 (UTC)

extended from VP10

VP10 is not a thing. It never made it past the vaporware state. AV1 is the successor to VP9, not VP10. There was an internal research project at Google whose results would have been named VP10 if AV1 and AOM had not happened and if it would have made reached publication. They decided against publishing a VP10. So, User:MennasDosbin, please leave VP10 out of the list in the "extended from" item of the infobox.--Flugaal (talk) 22:36, 15 January 2018 (UTC)

That wasn't me, that was MennasDosbin with this edit. Regardless, just because something wasn't published doesn't mean it didn't exist. Stickee (talk) 22:46, 15 January 2018 (UTC)

The official spec is abandoned

Documentation work has moved to github, apparently.

• What I initially noticed: The documentation is written for GitHub Pages. Googlesource's source code view does not render it very well (for one thing, the images are gone), whereas those able to guess the github pages url will find a glorious document.
• The nail in the coffin: The documentation repository on googlesource[1] hasn't seen updates in 2 months, whereas the github one[2] has, and is based on the last googlesource commit (90adec).

I'm changing the bitstream link back to github.—84.209.101.182 (talk) 20:18, 13 February 2018 (UTC)

Ambiguous wording/meaning in cited source: "binding specification," or software "bindings"? (AV1 Spec release, March 28th)

Hi all,

I am wondering what "binding" or "bindings" means in the context of this release. The source we cite isn't totally clear on the matter.

Relatedly, I just updated a sentence in the Wiki article: "The Alliance announced the release of the AV1 bitstream specification on 28 March 2018, along with a reference encoder, a reference decoder, test files ("reference streams"), and software bindings."

But the source seems a little vague with its usage of "binding" and "bindings":

"Designed at the outset for hardware optimization, the AV1 specification, reference code, and bindings are available for tool makers and developers to download here to begin designing AVI into products."

(This sentence seems to refer to software "language bindings".)

"Binding specifications to allow content creation and streaming tools for user-generated and commercial video"

(Does this sentence mean that the whole set of specs is "binding," in the sense that all implementers must now follow the specs? (Whereas before, the draft-status specs were "non-binding"?) Or does this refer to specifications that describe how to write/use bindings that ease use of the encoder and/or decoder libraries?)

In my own research on the subject, I have heard no reference to "bindings" anywhere else but this announcement. (No cite-worthy sources turned up, that I can remember.) I fear this might have been a typo or a brain fart or Freudian slip by the editor of the release announcement, and there may in fact be no bindings to speak of, only "binding specifications". But who can tell?

If anyone can help clear that up, I think it would help improve the factual accuracy of our treatment of this release event. — Preceding unsigned comment added by 68.81.226.126 (talk) 05:41, 29 March 2018 (UTC)

Found an informative (probably not citeable-quality?) source; Seems to clarify the meaning of "reference streams" as mentioned in spec release announcement (28 March)

http://www.argondesign.com/products/argon-streams-av1/

This company, Argon Design, is directly editing the spec document itself, which according to their site (see URL above) contains psuedo-code that they actually compile and use to generate "reference streams," which (near as I can tell) are just tiny, correctly-formatted video files matching the encoding spec. They have some mechanism to run these files through a given decoder programatically, and see if the output is "formally correct" per the encoding/decoding specs.

So basically, reading between the lines, Argon Designs will likely author the "reference streams" mentioned in the AV1 spec press release today (28 March). (They have already done similar for VP9 and HEVC, according to their site.)

(My reasoning here is something like original research, plus heavy reliance on primary sources, I know, so please don't put any of this into the article until we have proper source(s) to site. But I thought this was informative, and useful in interpreting the AOMedia announcement from today, so I wanted to mention it here in the mean-time.)