Difference between revisions of "Talk:Browser plugins"

From ArchWiki
Jump to: navigation, search
m (Page title change: argh, signed...)
(Adobe Flash Player: Hardware acceleration: re)
(38 intermediate revisions by 16 users not shown)
Line 1: Line 1:
This article's title is TOO SPECIFIC. It should be changed depending on article's scope. --[[User:Foxbunny|foxbunny]] 10:17, 17 November 2006 (PST)
+
== plugin location ==
  
I dont think that being "too specific" is the problem (see, for example, the [[Installing_VMware_Server_on_Arch64]] article that i authored. I think that's definitely worthy of a single article by itself). It's more of a case of the subject being too "trivial", or too "easy" to be worthy of an article by itself. And so in that sense you're right after all.
+
firefox (3.6.13) on arch 64 bit does look at /usr/lib/mozilla/plugins
--[[User:jf|jf]] 00:42, 24 November 2006 (UTC)
+
  
I think the title should be changed to include 'java', as people wouldn't know that java is included too. Apart from that, I think the article perfectly deserves a page for itself.
+
instead of
  
== acroread no longer in repo (demoted to AUR - redistribution rights issue) ==
+
~/mozilla/plugins/ or
 +
~/.mozilla/plugins/
  
I came to this page and tried to follow the instructions and they failed.
+
at least for libnpjp2.so I need to link to the correct /usr/lib/mozilla/plugins for it to work
  
The acroread component is not in the repo (it used to be !!) but a quick search of the AUR revealed why. It seems the acrobat reader licence denies redistribution rights (what a surprise) and so the acroread package cannot ever be promoted to a repository.
+
== Blue Tint Flash problem reloaded ==
  
I feel the instructions should be edited to reflect this but I don't personally have the necessary 'bottle' to just go in there and stomp over someone's hard work.
+
To solve the blue tint problem I had to right-click a flash element already running and set (in "preferences") off the hw acceleration, otherwise I had blue tint regardless the libvdpau workaround.
  
:: I do :) --[[User:Xiol|Xiol]] 06:24, 22 August 2008 (EDT)
+
Should this be added to the wiki?
  
== Page title change ==
+
== Adobe Flash Player: Hardware acceleration ==
  
I think this page's title should be changed to "Browser Plugins", as it contains (and can contain) general information on enabling plugins for your browser. --[[User:Xiol|Xiol]] 06:35, 22 August 2008 (EDT)
+
The Article states ''For hardware acceleration on Intel/AMD, you can use {{AUR|libvdpau-va-gl}} — VAAPI backend for VDPAU. For AMD you should also install {{AUR|xvba-video}}''.
 +
Can someone clarify that? It's totally unclear to me, which ATI/AMD drivers are meant. I assume, I need xvba-video when I use the catalyst/fglrx driver. What about libvdpau-va-gl? Do I need this when using the open-source radeon-driver? Do I need this if you use catalyst? Or do I need this anyway? [[User:Holzhaus|Holzhaus]] ([[User talk:Holzhaus|talk]]) 21:33, 25 October 2013 (UTC)
 +
 
 +
:See [[VA-API]], I wonder why it isn't linked from this page... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:48, 26 October 2013 (UTC)
 +
 
 +
::As I understand that page, {{AUR|libvdpau-va-gl}} and {{AUR|xvba-video}} are unnecessary, no matter what driver you use. I will then remove that part from the article and link the page you suggested. [[User:Holzhaus|Holzhaus]] ([[User talk:Holzhaus|talk]]) 08:58, 27 October 2013 (UTC)
 +
 
 +
:::Ah, see also [[Talk:VA-API#VDPAU vs VAAPI relationship]] for the {{AUR|libvdpau-va-gl}} and {{AUR|xvba-video}} detail, they are necessary to support VDPAU through VAAPI on Intel cards and AMD cards with proprietary drivers. However, you've correctly linked to [[VDPAU]], FlashPlayer does not use VAAPI. (Sorry for suggesting the [[VA-API]] link, I noticed [[VDPAU]] later...) -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 09:19, 27 October 2013 (UTC)

Revision as of 09:19, 27 October 2013

plugin location

firefox (3.6.13) on arch 64 bit does look at /usr/lib/mozilla/plugins

instead of

~/mozilla/plugins/ or ~/.mozilla/plugins/

at least for libnpjp2.so I need to link to the correct /usr/lib/mozilla/plugins for it to work

Blue Tint Flash problem reloaded

To solve the blue tint problem I had to right-click a flash element already running and set (in "preferences") off the hw acceleration, otherwise I had blue tint regardless the libvdpau workaround.

Should this be added to the wiki?

Adobe Flash Player: Hardware acceleration

The Article states For hardware acceleration on Intel/AMD, you can use libvdpau-va-glAUR — VAAPI backend for VDPAU. For AMD you should also install xvba-videoAUR. Can someone clarify that? It's totally unclear to me, which ATI/AMD drivers are meant. I assume, I need xvba-video when I use the catalyst/fglrx driver. What about libvdpau-va-gl? Do I need this when using the open-source radeon-driver? Do I need this if you use catalyst? Or do I need this anyway? Holzhaus (talk) 21:33, 25 October 2013 (UTC)

See VA-API, I wonder why it isn't linked from this page... -- Lahwaacz (talk) 06:48, 26 October 2013 (UTC)
As I understand that page, libvdpau-va-glAUR and xvba-videoAUR are unnecessary, no matter what driver you use. I will then remove that part from the article and link the page you suggested. Holzhaus (talk) 08:58, 27 October 2013 (UTC)
Ah, see also Talk:VA-API#VDPAU vs VAAPI relationship for the libvdpau-va-glAUR and xvba-videoAUR detail, they are necessary to support VDPAU through VAAPI on Intel cards and AMD cards with proprietary drivers. However, you've correctly linked to VDPAU, FlashPlayer does not use VAAPI. (Sorry for suggesting the VA-API link, I noticed VDPAU later...) -- Lahwaacz (talk) 09:19, 27 October 2013 (UTC)