Talk:DivX, LLC
This is the talk page for discussing improvements to the DivX, LLC 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 C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||
|
Individuals with a conflict of interest, particularly those representing the subject of the article, are strongly advised not to directly edit the article. See Wikipedia:Conflict of interest. You may request corrections or suggest content here on the Talk page for independent editors to review, or contact us if the issue is urgent. |
Licensing
[edit]J. M. (Talk/contribs)has suggested in a revision summary that DivX, Inc. does not really license anything to manufacturers of consumer electronic devices. Instead it just certifes products. I would like to open this issue up for debate. I would note that Div, Inc. uses the term "license" frequently in its financial reports and press releases. For example, the company's most recent 10-Q includes the statement, "We license our technologies to manufacturers of integrated circuits designed for consumer hardware products, as well as consumer hardware device manufacturers who have licensed our technologies for incorporation in products such as DVD players, personal media players, portable media players, digital still cameras and mobile handsets." Additionally, the company's recent press release regarding the deal with Qualcomm includes the statement, "DivX, Inc. today announced a licensing agreement allowing QUALCOMM to include DivX(R) technology in a range of QUALCOMM video-enabled chipsets." So, I ask the question, does DivX, Inc. license any kind of intellectual property, e.g., patents on inventions or copyrights on software, to manufacturers of consumer electronic devices? Do these deals involve anything beyond certification of products? RandomWalker 15:28, 22 September 2007 (UTC)
- I did not say "DivX, Inc. does not license anything to manufacturers". I am not against the word "licensing" per se, the exact wording is what I was concerned about – it said DivX "licenses its codec for portable DivX players" which I found highly suspect, as I could not find any proof anywhere, including the DivX company website (plus most people don't understand what a codec is, they think that when a portable player can play DivX-encoded video, or even if the device is DivX-certified, it means there's the DivX codec inside). If DivX, Inc. licenses its software products (and it does, that's what the DivX software licensing is about), then the article can say DivX licenses its software products. If DivX licences its intellectual property, i.e. patents or copyrights, then the article can say so. But preferably in a way that's not vague and misleading (and the DivX, Inc. press releases are extremely vague, they hardly ever say anything particular). And with links to sources. —J. M. 23:11, 24 September 2007 (UTC)
- Actually, I am not an expert on the technology. My assumption was that if a DVD player, for example, can play a DivX-encoded video, then it must have the codec in it. Wouldn't the DVD player have to decompress the video before playing it, and therefore use the "dec" part of the "codec." Even with an integrated circuit, like in the Qualcomm deal, wouldn't the IC have a memory that could store the codec? My assumption also was that the software licensing component was just when DivX grants a license to a company like Roxio so that Roxio can include the ability to create DivX-encoded video in its Easy Media Creator software. Am I wrong?RandomWalker 02:46, 25 September 2007 (UTC)
- The DivX codec is an MPEG-4 ASP codec. Codec is a piece of software or hardware that encodes/decodes data to/from some format. This means that the DivX codec is a software product that encodes and decodes video in the MPEG-4 ASP format. The MPEG-4 specification is an ISO standard and it's publicly available (for a fee). The DivX codec does not use their own format, the DivX company did not invent it. They implement the MPEG-4 ASP specification (just like the authors of other MPEG-4 ASP codecs like Xvid or FFmpeg MPEG-4, that is, these codecs are mostly compatible, for example, you can play FFmpeg-encoded video with DivX and vice-versa). What various hardware manufacturers do is they read the MPEG-4 specification and then implement it in hardware. Which means that it can decode MPEG-4 video encoded with various MPEG-4 codecs, including DivX, Xvid etc. Now, the DivX company created their own "DivX profiles" for hardware devices, which is a set of restrictions within the broader MPEG-4 specification. This does not mean that video encoded with the DivX codec is not MPEG-4 video, it just uses a limited set of features (there can be bitrate restrictions etc.). The DivX-certified products are then guaranteed to play video that meets these conditions, and they may not necessarily play video that uses unsupported MPEG-4 ASP features (like Qpel) which would be more difficult/expensive to implement in hardware. So that's the DivX certification – it does not mean the products include the DivX decoder. Now, it may be possible, like you said, that some hardware products really include the DivX codec in some way (stored in the memory or whatever), and if it's true, by all means add it to the article. But please be careful to cite the source that says so. Statements like "DivX, Inc. licensed its technology to company XY" are not very clear...—J. M. 03:15, 25 September 2007 (UTC)
- Actually, I am not an expert on the technology. My assumption was that if a DVD player, for example, can play a DivX-encoded video, then it must have the codec in it. Wouldn't the DVD player have to decompress the video before playing it, and therefore use the "dec" part of the "codec." Even with an integrated circuit, like in the Qualcomm deal, wouldn't the IC have a memory that could store the codec? My assumption also was that the software licensing component was just when DivX grants a license to a company like Roxio so that Roxio can include the ability to create DivX-encoded video in its Easy Media Creator software. Am I wrong?RandomWalker 02:46, 25 September 2007 (UTC)
Fair use rationale for Image:Divx-black-blue.svg
[edit]Image:Divx-black-blue.svg is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot 06:38, 5 November 2007 (UTC)
- This concern has been taken care of. A specific rationale for fair use has been added on the page for the image. Certainly, a one-time use of a company's logo on Wikipedia page about the company qualifies as Fair Use. —Preceding unsigned comment added by RandomWalker (talk • contribs) 22:25, 10 November 2007 (UTC)
Image copyright problem with File:Divx logo.svg
[edit]The image File:Divx logo.svg is used in this article under a claim of fair use, but it does not have an adequate explanation for why it meets the requirements for such images when used here. In particular, for each page the image is used on, it must have an explanation linking to that page which explains why it needs to be used on that page. Please check
- That there is a non-free use rationale on the image's description page for the use in this article.
- That this article is linked to from the image description page.
This is an automated notice by FairuseBot. For assistance on the image use policy, see Wikipedia:Media copyright questions. --03:40, 15 February 2011 (UTC)
Inc. to LLC.?
[edit]On the official website the company is now referred as DivX, LLC
Is it possible that the type of the company has been changed from Inc. to LLC? --46.119.34.246 (talk) 17:10, 19 August 2012 (UTC)
- Yes. Thus, I suggest moving the page to DivX, LLC and making the infobox that of an active company. Michealin (talk) 05:22, 28 August 2013 (UTC)
Request edit on 19 August 2015
[edit]This edit request by an editor with a conflict of interest has now been answered. |
Hope this request is done correctly...
1. Replace current first sentence "DivX, Inc. (formerly DivXNetworks, Inc.), based in San Diego, California, now part of Sonic Solutions, a division of Rovi, was the corporation behind the MPEG-4 Part 2-based codec, DivX." with the updated "DivX, Inc (now DivX, LLC and also formerly known as DivXNetworks, Inc.), based in San Diego, California, is a subsidiary of NeuLion, Inc. DivX, LLC is best known as the corporation behind three popular codecs: the original MPEG-4 Part 2-based codec, the H.264/MPEG-4 AVC DivX Plus HD codec and the High Efficiency Video Coding DivX HEVC Ultra HD codec."
Why? This new sentence accurately refers to the correct company description (LLC vs. Inc.), addresses the acquisition by NeuLion, Inc. (http://www.marketwired.com/press-release/-2005759.htm) and addresses the multiple codecs mentioned in the DivX Wikipedia page (https://wiki.riteme.site/wiki/DivX)
2. Change second sentence from, "The company's codec has been downloaded over 240 million times since January 2003. DivX, Inc.'s offerings have expanded beyond the codec to include software for viewing and authoring DivX-encoded video." to, "The company's software has been downloaded over 1 billion times since January 2003. DivX, LLC's offerings have expanded beyond the codec to include software for viewing and authoring DivX-encoded video."
Why? This new sentence accurately represents the number of downloads of the DivX software as noted here: https://forums.divx.com/divx/topics/divx_celebrates_1_billion_downloads and in the NeuLion Wikipedia page: https://wiki.riteme.site/wiki/NeuLion#Services
3. Change the third and fourth sentence from, "DivX, Inc.'s offerings have expanded beyond the codec to include software for viewing and authoring DivX-encoded video. DivX, Inc. also licenses its technologies to manufacturers of consumer electronics devices and components used in these devices and certifies that these products are able to properly handle DivX-encoded video." to "DivX, LLC's offerings have expanded beyond the codec to include software for viewing and authoring DivX-encoded video. DivX, LLC also licenses its technologies to manufacturers of consumer electronics devices and components used in these devices, of which over billion DivX-enabled devices have shipped worldwide. DivX certifies that these licensed products are able to properly play DivX-encoded video."
Why? These new sentences accurately address the LLC status as well as mentions the 1 billion DivX devices shipped (as noted here: http://globenewswire.com/news-release/2013/09/12/572951/10048240/en/Rovi-Celebrates-1-Billion-DivX-Device-Milestone-at-IBC.html). Additionally, it more accurately represents how the process works (certification is done to license the technology and the word "play" DivX-encoded files is more accurate than "handle" DivX-encoded files.
4. In the History section, there are three acquisitions and/or divestitures to add:
In February 2011, Rovi Corporation acquired Sonic Solutions (including the DivX business).
In April 2014, Rovi Corporation sold the DivX and MainConcept business to Parallax Capital Partners and StepStone Group.
In February 2015, NeuLion, Inc. acquired DivX, LLC.
Citations are noted here:
Rovi acquisition: http://www.reuters.com/article/2011/02/14/idUS135654+14-Feb-2011+GNW20110214
Rovi divestiture: http://www.rttnews.com/2295136/rovi-sells-divx-mainconcept-businesses.aspx
NeuLion acquisition: http://www.marketwired.com/press-release/-2005759.htm
THANK YOU!
Jstyn (talk) 18:23, 20 August 2015 (UTC)
(The above requested edit was made by clicking on a link in an automatically added notice.)
Feedback on above?
[edit]Since I haven't received any guidance, approval, rejection, etc., I will go ahead and make the edits and cite each updated fact. Please let me know if there's a better approach to ensuring this page is accurate. Thank you! Jstyn (talk) 17:29, 26 August 2015 (UTC)
External links modified
[edit]Hello fellow Wikipedians,
I have just added archive links to one external link on DivX, Inc.. Please take a moment to review my edit. If necessary, add {{cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
- Added archive http://web.archive.org/web/20081205011806/http://www.divx.com/company/press/press_detail.php?pr_id=273 to http://www.divx.com/company/press/press_detail.php?pr_id=273
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}
).
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}}
(last update: 5 June 2024).
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—cyberbot IITalk to my owner:Online 19:20, 28 February 2016 (UTC)
External links modified
[edit]Hello fellow Wikipedians,
I have just modified 4 external links on DivX, Inc.. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive http://web.archive.org/web/20070216105854/http://www.divx.com:80/company/press/press_detail.php?pr_id=205 to http://www.divx.com/company/press/press_detail.php?pr_id=205
- Added archive http://web.archive.org/web/20101017022622/http://www.roxio.com:80/enu/company/press/releases/2010/sonic_completes_divx_acquisition.html to http://www.roxio.com/enu/company/press/releases/2010/sonic_completes_divx_acquisition.html
- Added archive http://web.archive.org/web/20090103151456/http://investors.divx.com:80/releasedetail.cfm?ReleaseID=348039 to http://investors.divx.com/releasedetail.cfm?ReleaseID=348039
- Added archive http://web.archive.org/web/20071213062704/http://www.stage6.com:80/# to http://www.stage6.com
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}
).
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}}
(last update: 5 June 2024).
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—cyberbot IITalk to my owner:Online 18:08, 26 May 2016 (UTC)
External links modified
[edit]Hello fellow Wikipedians,
I have just modified 2 external links on DivX, Inc.. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive https://web.archive.org/web/20150912041241/https://forums.divx.com/divx/topics/divx_celebrates_1_billion_downloads to https://forums.divx.com/divx/topics/divx_celebrates_1_billion_downloads
- Corrected formatting/usage for http://www.stage6.com/
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}}
(last update: 5 June 2024).
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot (Report bug) 13:58, 11 September 2017 (UTC)