This is the
talk page for discussing improvements to the
VP8 article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||
|
This page needs references for the claims it makes. -- Tegbains ( talk) 07:42, 27 October 2008 (UTC)
"VP8 is an open source, a proprietary video codec..." - wait, what? How can it be open source and proprietary at the same time? That makes no sense. -- Wjbuys ( talk) 08:34, 24 May 2010 (UTC)
I can see VP8's source code. Therefore, it is open-source. The "owned by Google" part further on the sentence describes what you want to say. —Preceding unsigned comment added by DanimothWiki ( talk • contribs) 18:11, 25 May 2010 (UTC)
VP8 is a video compression format.
So concluding VP8 is a proprietary video compression format, it is an open video compression format and it has at least one open source implementation. 86.83.239.142 ( talk) 06:01, 26 May 2010 (UTC)
“ | Google hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise implementations of this specification where such license applies only to those patent claims, both currently owned by Google and acquired in the future, licensable by Google that are necessarily infringed by implementation of this specification. If You or your agent or exclusive licensee institute or order or agree to the institution of patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that any implementation of this specification constitutes direct or contributory patent infringement, or inducement of patent infringement, then any rights granted to You under the License for this specification shall terminate as of the date such litigation is filed. | ” |
— Google, Inc., VP8 Data Format and Decoding Specification |
For the above discussion here a citation that suggest the format should indeed be called proprietary. http://www.robglidden.com/2010/05/how-googles-open-sourcing-of-vp8-harms-the-open-web/ 86.83.239.142 ( talk) 12:55, 29 May 2010 (UTC)
The article states: This made VP8 the second product from On2 Technologies to be open-sourced to the free software community following the 2001 release of the older VP3 codec, which was later donated (under the BSD license) to the Xiph.Org Foundation as the Theora codec
This phrasing is very misleading as the control over the VP3 format was actually handed by On2 to an independant organization of OSS developers (xiph). The VP8 format is still owned by Google/On2 and is not handed over to an independant open source organization. 62.58.36.58 ( talk) 15:02, 28 May 2010 (UTC)
From http://webmproject.blogspot.com/search/label/vp8 and http://x264dev.multimedia.cx/?p=377 .
As with other codecs an initial Macroblock pass is initially run. Each block is then compared to blocks in the same frame (intra-prediction) and previous reference frames (inter-prediction) to produce a Motion_vector for it. A reference frame can be one of three types: The previous frame, the alternate reference frame (which itself is not shown and may consist of blocks from many different frames at the encoder's whim) and the golden frame (one frame worth of decompressed data from the arbitrarily distant past).
144.32.81.88 ( talk) 11:38, 27 August 2010 (UTC)
The article should be only about VP8 as a format. It should not include detailed information about libvpx, because that's one implementation of VP8, and other implementations will be coming (like xvp8, VP8 encoding in x264). libvpx should have its separate article. For example, Wikipedia has an article talking purely about H.264 as a format, and it also has separate articles on implementations like x264. —Preceding unsigned comment added by 2.90.131.86 ( talk) 07:51, 14 February 2011 (UTC)
Yes, that's what I'm saying, that the article should differentiate between implementation and specification, and that it should include information about both.
--
Gyrobo (
talk)
01:38, 18 February 2011 (UTC)
This article needs a "Future" paragraph discussing what is being worked on inside the scope of this format. If on2 is still working on a successor , if google is or if independent parties are. If yes , what are aspects of the format they expanding on. 83.101.79.165 ( talk) 04:29, 26 May 2012 (UTC)
What's with the "almost" irrevocable patent grant? Weasel words. If it isn't completely irrevocable, then the article should explain why. Jon ( talk) 12:38, 18 December 2012 (UTC)
Probably, macOS already supports WebM playback. I can confirmed WebM/VP8 video is able to be played on macOS 13.1 (22C65). But I'm not familiar with the multimedia framework so I'm not confident to update the description. Could someone who know about the framework update the description? Thanks!
Here's some references:
shuuji3 ( talk) 03:53, 9 January 2023 (UTC)
In the Related formats section of VP8's article it states that "Adobe also announced that the Flash Player will support VP8 playback in a future release."
In reality VP8 probably never made it to Adobe Flash Player and nothing in regards to VP8 support in Flash ever materialized, so it is assumed that Adobe quietly cancelled plans to implement VP8 for Flash Player's video codec. In addition, Flash Player in its standard global variant no longer works, so the statement in the Related formats about Adobe Flash Player supporting VP8 should be updated to indicate that it was never implemented. DeveloperPudú ( talk) 20:06, 6 July 2023 (UTC)
What's meant by "multiplexing" in the lead? Is it the I/O multiplexing definition given in the lead here: Multiplexing? 104.232.119.107 ( talk) 06:53, 28 April 2024 (UTC)
This is the
talk page for discussing improvements to the
VP8 article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||
|
This page needs references for the claims it makes. -- Tegbains ( talk) 07:42, 27 October 2008 (UTC)
"VP8 is an open source, a proprietary video codec..." - wait, what? How can it be open source and proprietary at the same time? That makes no sense. -- Wjbuys ( talk) 08:34, 24 May 2010 (UTC)
I can see VP8's source code. Therefore, it is open-source. The "owned by Google" part further on the sentence describes what you want to say. —Preceding unsigned comment added by DanimothWiki ( talk • contribs) 18:11, 25 May 2010 (UTC)
VP8 is a video compression format.
So concluding VP8 is a proprietary video compression format, it is an open video compression format and it has at least one open source implementation. 86.83.239.142 ( talk) 06:01, 26 May 2010 (UTC)
“ | Google hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise implementations of this specification where such license applies only to those patent claims, both currently owned by Google and acquired in the future, licensable by Google that are necessarily infringed by implementation of this specification. If You or your agent or exclusive licensee institute or order or agree to the institution of patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that any implementation of this specification constitutes direct or contributory patent infringement, or inducement of patent infringement, then any rights granted to You under the License for this specification shall terminate as of the date such litigation is filed. | ” |
— Google, Inc., VP8 Data Format and Decoding Specification |
For the above discussion here a citation that suggest the format should indeed be called proprietary. http://www.robglidden.com/2010/05/how-googles-open-sourcing-of-vp8-harms-the-open-web/ 86.83.239.142 ( talk) 12:55, 29 May 2010 (UTC)
The article states: This made VP8 the second product from On2 Technologies to be open-sourced to the free software community following the 2001 release of the older VP3 codec, which was later donated (under the BSD license) to the Xiph.Org Foundation as the Theora codec
This phrasing is very misleading as the control over the VP3 format was actually handed by On2 to an independant organization of OSS developers (xiph). The VP8 format is still owned by Google/On2 and is not handed over to an independant open source organization. 62.58.36.58 ( talk) 15:02, 28 May 2010 (UTC)
From http://webmproject.blogspot.com/search/label/vp8 and http://x264dev.multimedia.cx/?p=377 .
As with other codecs an initial Macroblock pass is initially run. Each block is then compared to blocks in the same frame (intra-prediction) and previous reference frames (inter-prediction) to produce a Motion_vector for it. A reference frame can be one of three types: The previous frame, the alternate reference frame (which itself is not shown and may consist of blocks from many different frames at the encoder's whim) and the golden frame (one frame worth of decompressed data from the arbitrarily distant past).
144.32.81.88 ( talk) 11:38, 27 August 2010 (UTC)
The article should be only about VP8 as a format. It should not include detailed information about libvpx, because that's one implementation of VP8, and other implementations will be coming (like xvp8, VP8 encoding in x264). libvpx should have its separate article. For example, Wikipedia has an article talking purely about H.264 as a format, and it also has separate articles on implementations like x264. —Preceding unsigned comment added by 2.90.131.86 ( talk) 07:51, 14 February 2011 (UTC)
Yes, that's what I'm saying, that the article should differentiate between implementation and specification, and that it should include information about both.
--
Gyrobo (
talk)
01:38, 18 February 2011 (UTC)
This article needs a "Future" paragraph discussing what is being worked on inside the scope of this format. If on2 is still working on a successor , if google is or if independent parties are. If yes , what are aspects of the format they expanding on. 83.101.79.165 ( talk) 04:29, 26 May 2012 (UTC)
What's with the "almost" irrevocable patent grant? Weasel words. If it isn't completely irrevocable, then the article should explain why. Jon ( talk) 12:38, 18 December 2012 (UTC)
Probably, macOS already supports WebM playback. I can confirmed WebM/VP8 video is able to be played on macOS 13.1 (22C65). But I'm not familiar with the multimedia framework so I'm not confident to update the description. Could someone who know about the framework update the description? Thanks!
Here's some references:
shuuji3 ( talk) 03:53, 9 January 2023 (UTC)
In the Related formats section of VP8's article it states that "Adobe also announced that the Flash Player will support VP8 playback in a future release."
In reality VP8 probably never made it to Adobe Flash Player and nothing in regards to VP8 support in Flash ever materialized, so it is assumed that Adobe quietly cancelled plans to implement VP8 for Flash Player's video codec. In addition, Flash Player in its standard global variant no longer works, so the statement in the Related formats about Adobe Flash Player supporting VP8 should be updated to indicate that it was never implemented. DeveloperPudú ( talk) 20:06, 6 July 2023 (UTC)
What's meant by "multiplexing" in the lead? Is it the I/O multiplexing definition given in the lead here: Multiplexing? 104.232.119.107 ( talk) 06:53, 28 April 2024 (UTC)