Jump to content

Talk:VDPAU

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Pronunciation?

[edit]

When in conversation does anyone know how to pronounce this?

Well VDPAU is an abbreviation for "Video Decode and Presentation API for Unix" so I guess that it should really be pronunciated as each letter by itself, so "V.D.P.A.U." but most people that I personally know pronunce it is "V.D.-PAU" or "V.D.-PAO" 164.4.17.32 (talk) 17:25, 17 November 2009 (UTC)[reply]
I say "Vee Dee Pow" :D -andy —Preceding unsigned comment added by 173.166.78.9 (talk) 15:57, 5 October 2010 (UTC)[reply]

Relation to PureVideo

[edit]

The table and the list of feature sets should be moved into PureVideo. VDPAU is not vendor-specific, PureVideo is. CE--62.178.80.242 (talk) 08:52, 28 September 2009 (UTC)[reply]

Done. CE 62.178.80.242 (talk) 16:14, 22 February 2010 (UTC)[reply]


You should at the very least still link to the table from the VDPAU page, or update the table to include Non-NVIDIA GPUs, for now I have replaced the table. —Preceding unsigned comment added by 24.19.106.152 (talk) 04:23, 27 February 2010 (UTC)[reply]

I did link to the table (you removed it), and information about all non-NVIDIA VDPAU GPUs was (and still is) in the article, but not in the table I removed. I think your edit was not very constructive, so I reverted it. Please feel free to discuss this further here. CE --80.108.89.202 (talk) 18:04, 28 February 2010 (UTC)[reply]

FFmpeg

[edit]

FFmpeg does not support VDPAU. It does support MPlayer's VDPAU implementation through libavcodec (libavcodec would support any application's VDPAU implemtation, but all other Liux media players decided not to use libavcodec's VDPAU code). --Regression Tester (talk) 11:35, 7 April 2010 (UTC)[reply]

VDPAU support through Gallium in Mesa

[edit]

A VDPAU state tracker has been added to the Gallium library in Mesa for almost 2 years now, bringing a basic (as of now) level of support to the Gallium-based drivers. — Preceding unsigned comment added by 84.223.83.110 (talk) 17:00, 13 April 2012 (UTC)[reply]

Clarify and rewrite

[edit]

Please see Talk:Video Acceleration API#Clarify and rewrite User:ScotXWt@lk 09:24, 28 June 2014 (UTC)[reply]

[edit]

Hello fellow Wikipedians,

I have just modified 2 external links on VDPAU. 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:

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:19, 26 May 2016 (UTC)[reply]

VP8, VP9 and NVDEC

[edit]

According to the official VDPAU website, VDPAU does not support VP8 or VP9. You can also browse the source code, and see that there's no mention of VP8/VP9. The email linked to by User:Bassmadrigal talks about some unofficial patch that was never accepted upstream.

Phoronix says: . The GStreamer people also talk about "VPDAU is dead".

While I can't find an official source saying that VPDAU is dead, it is very clear that it doesn't support VP8 or VP9.

--Lonaowna (talk) 16:34, 13 November 2017 (UTC)[reply]

It just doesn't seem right to have that information listed there without anything to back it up... especially in the article's lead. Maybe it could just be stated what formats VDPAU does support (which is already covered in the Functional range of the interface) and that VDPAU is being replaced by NVDEC. I don't think that we should be adding every future format to this article, because that could add quite a few items in 5, 10, or 20 years. Saying something isn't supported without references seems to fringe on WP:OR, even though many people would come to the same conclusion. What are your thoughts on that? --Bassmadrigal (talk) 18:56, 13 November 2017 (UTC)[reply]
I agree that it might be inappropriate in the intro without any references. Although I wouldn't call the Phoronix references OR (one literally says "NVIDIA's VDPAU-successor, NVDEC"), they still aren't ideal as they don't go in on any detail on that point. I'm OK with leaving the sentence out until we find a better reference. (BTW sorry for my late response; didn't see yours) Lonaowna (talk) 18:27, 15 November 2017 (UTC)[reply]
I wasn't considering the Phoronix article to be OR for the NVDEC (which is why I used it as a reference for the sentence mentioning NVDEC is superseding VDPAU), just that it doesn't mention anything about VP8/VP9 not being supported with VDPAU. That conclusion can be surmised by looking at the documents for VDPAU and NVDEC and see that nothing mentions VP8/VP9 for VDPAU. But I don't think it needs to be stated what is *not* supported (especially without references), since the article does state what *is* supported. --Bassmadrigal (talk) 22:56, 15 November 2017 (UTC)[reply]
Ah yes, I agree. It is not useful to list what's not supported. I really hope that Nvidia is going to clear things up by doing a proper announcement. Thanks for your improvements! Lonaowna (talk) 19:44, 16 November 2017 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:VDPAU&oldid=1210843163"