Re: [gentoo-dev] New global use flag: vpx or vp8

2010-08-03 Thread Luca Barbato
On 07/31/2010 05:09 PM, Paweł Hajdan, Jr. wrote:
 On 7/31/10 4:37 AM, Hanno Böck wrote:
 vpx for supporting googles vp8 codec used in webm.

No, vpx is for using libvpx.

 At the moment this is only mplayer and ffmpeg, but it's pretty obvious that 
 apps supporting vp8 will start popping up everywhere (currently working on 
 arista ebuild which will support it).

 Just verifying: does the vpx USE flag in ffmpeg control the support for
 encoding vp8, decoding it, or both? How should www-client/chromium
 depend on ffmpeg to make sure it will support vp8?

it does trigger the use of libvpx, curreng ffvp8 (decoder) is faster
than libvpx, libvpx is used for the encoding side for now.

 Though we might discuss if vpx is really a good name or it shouldn't be vp8.
 
 It might also be webm. Not sure what's more intuitive for people. Also,
 nteresting question would be whether to enable the flag by default an in
 which profiles (desktop?).

vpx - you use libvpx

vp8 - you want vp8

as for decoding ffmpeg is already a provider so application using it
won't need additional useflag IMHO

lu

-- 

Luca Barbato
Gentoo/linux
http://dev.gentoo.org/~lu_zero




[gentoo-dev] New global use flag: vpx or vp8

2010-07-31 Thread Hanno Böck
vpx for supporting googles vp8 codec used in webm.

At the moment this is only mplayer and ffmpeg, but it's pretty obvious that 
apps supporting vp8 will start popping up everywhere (currently working on 
arista ebuild which will support it).

Though we might discuss if vpx is really a good name or it shouldn't be vp8.

-- 
Hanno Böck  Blog:   http://www.hboeck.de/
GPG: 3DBD3B20   Jabber/Mail:ha...@hboeck.de


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-dev] New global use flag: vpx or vp8

2010-07-31 Thread Paweł Hajdan, Jr.
On 7/31/10 4:37 AM, Hanno Böck wrote:
 vpx for supporting googles vp8 codec used in webm.
 
 At the moment this is only mplayer and ffmpeg, but it's pretty obvious that 
 apps supporting vp8 will start popping up everywhere (currently working on 
 arista ebuild which will support it).

Just verifying: does the vpx USE flag in ffmpeg control the support for
encoding vp8, decoding it, or both? How should www-client/chromium
depend on ffmpeg to make sure it will support vp8?

 Though we might discuss if vpx is really a good name or it shouldn't be vp8.

It might also be webm. Not sure what's more intuitive for people. Also,
nteresting question would be whether to enable the flag by default an in
which profiles (desktop?).

Paweł



signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] New global use flag: vpx or vp8

2010-07-31 Thread Robert Bridge
On Sat, Jul 31, 2010 at 4:09 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
 On 7/31/10 4:37 AM, Hanno Böck wrote:
 Though we might discuss if vpx is really a good name or it shouldn't be vp8.

 It might also be webm. Not sure what's more intuitive for people. Also,
 nteresting question would be whether to enable the flag by default an in
 which profiles (desktop?).

Speaking as a user, I would ask what the standard file ending is? Most
users won't know what the codec is, they will just know is foo.webm or
foo.vpx/8.

Just a thought if debating the name.

RobbieAB.



Re: [gentoo-dev] New global use flag: vpx or vp8

2010-07-31 Thread Mike Frysinger
On Saturday, July 31, 2010 14:27:14 Jacob Godserv wrote:
 Honestly not sure what convention is for naming, but I found this
 recently, and thought I might throw it out there:
 
  ~ $ euse -i lame
 
 [+ C  ] lame - Prefer using LAME libraries for MP3 encoding support
 
 
 While, as a user, I prefer this to be mp3, I also understand there may
 be more than one library for such-and-so, so I'm willing to read up on
 USE flags to find out which is the best to use. Overall, I would prefer
 naming according to the names of the libraries they'll enable.

that example isnt relevant.  notice how the description includes the word 
prefer and isnt just enable mp3 support.

USE=mp3 is how you get mp3 support.  if there are multiple options (like 
ffmpeg or lame or mpg123 or something else), then USE=lame shows up to select 
one particular implementation over another.  but it would still be:
USE=mp3 lame
-mike


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-dev] New global use flag: vpx or vp8

2010-07-31 Thread Steve Dibb

On 07/31/2010 12:51 PM, Mike Frysinger wrote:

On Saturday, July 31, 2010 14:27:14 Jacob Godserv wrote:

Honestly not sure what convention is for naming, but I found this
recently, and thought I might throw it out there:

  ~ $ euse -i lame

[+ C  ] lame - Prefer using LAME libraries for MP3 encoding support


While, as a user, I prefer this to be mp3, I also understand there may
be more than one library for such-and-so, so I'm willing to read up on
USE flags to find out which is the best to use. Overall, I would prefer
naming according to the names of the libraries they'll enable.


that example isnt relevant.  notice how the description includes the word
prefer and isnt just enable mp3 support.


The description is misleading, and needs to be changed.  Just because 
something has an mp3 and a lame use flag, it does not mean that flipping 
on lame means that the application will prefer lame over mad or mpg123.


/nit

Steve



Re: [gentoo-dev] New global use flag: vpx or vp8

2010-07-31 Thread Mike Frysinger
On Saturday, July 31, 2010 16:02:51 Steve Dibb wrote:
 On 07/31/2010 12:51 PM, Mike Frysinger wrote:
  On Saturday, July 31, 2010 14:27:14 Jacob Godserv wrote:
  Honestly not sure what convention is for naming, but I found this
  
  recently, and thought I might throw it out there:
~ $ euse -i lame
  
  
  [+ C  ] lame - Prefer using LAME libraries for MP3 encoding support
  
  
  While, as a user, I prefer this to be mp3, I also understand there may
  be more than one library for such-and-so, so I'm willing to read up on
  USE flags to find out which is the best to use. Overall, I would prefer
  naming according to the names of the libraries they'll enable.
  
  that example isnt relevant.  notice how the description includes the word
  prefer and isnt just enable mp3 support.
 
 The description is misleading, and needs to be changed.  Just because
 something has an mp3 and a lame use flag, it does not mean that flipping
 on lame means that the application will prefer lame over mad or mpg123.

sounds like a bug in the package, or the package metadata.xml needs updating.  
the current lame desc sounds fine to me.
-mike


signature.asc
Description: This is a digitally signed message part.