ffmpeg does not take into account the -b <bitrate> value.

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

ffmpeg does not take into account the -b <bitrate> value.

juanjavier
It always encode with a waaaay too low bitrate....so the output gets horribly pixeled...no matter which value do I put

in -b <bitrate> option.

If no -b <bitrate> value is given, the output will surround the ~ 200 kbps value, which is the default.


This turns out to be unacceptably low.

If we do specify -for instance- -b 750 and keep monitoring the processing in the command line, we see values of
about 150 kbps and descending...

I have checked that the source streams has video bitrate high enough...they are 688x272 high quality divX streams in the

750-800-850 kbits/sec range.


The output does not even reach 250 kbits/sec.

Why does this happen? Googling did not help. Is there a way to *force* a high enough kbps rate in the video output?

Regards,

Juanjavier

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account the -b <bitrate> value.

Ví­ctor Paesa
Hi,

Juanjavier dijo:

> It always encode with a waaaay too low bitrate....so the output gets
> horribly pixeled...no matter which value do I put
>
> in -b <bitrate> option.
>
> If no -b <bitrate> value is given, the output will surround the ~ 200
> kbps value, which is the default.
>
>
> This turns out to be unacceptably low.
>
> If we do specify -for instance- -b 750 and keep monitoring the
> processing in the command line, we see values of  about 150 kbps and
> descending...
>
> I have checked that the source streams has video bitrate high
> enough...they are 688x272 high quality divX streams in the
>
> 750-800-850 kbits/sec range.
>
>
> The output does not even reach 250 kbits/sec.
>
> Why does this happen? Googling did not help. Is there a way to *force* a
> high enough kbps rate in the video output?

There are at least three options:
a) read the documentation on -b (run ffmpeg -h),
b) Google within the ffmpeg-user mail list,
c) upgrade to a recent ffmpeg, and read the output messages.

Regards,
Víctor


_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account the -b <bitrate> value.

juanjavier
Víctor Paesa wrote:

> Hi,
>
> Juanjavier dijo:
>  
>> It always encode with a waaaay too low bitrate....so the output gets
>> horribly pixeled...no matter which value do I put
>>
>> in -b <bitrate> option.
>>
>> If no -b <bitrate> value is given, the output will surround the ~ 200
>> kbps value, which is the default.
>>
>>
>> This turns out to be unacceptably low.
>>
>> If we do specify -for instance- -b 750 and keep monitoring the
>> processing in the command line, we see values of  about 150 kbps and
>> descending...
>>
>> I have checked that the source streams has video bitrate high
>> enough...they are 688x272 high quality divX streams in the
>>
>> 750-800-850 kbits/sec range.
>>
>>
>> The output does not even reach 250 kbits/sec.
>>
>> Why does this happen? Googling did not help. Is there a way to *force* a
>> high enough kbps rate in the video output?
>>    
>
> There are at least three options:
> a) read the documentation on -b (run ffmpeg -h),
>  
I did so before, thanks.

Video options:

-b                  set bitrate (in bits/s)

-vb                 set bitrate (in bits/s)

This does not help, sorry.


> b) Google within the ffmpeg-user mail list,
>  

How is that done? Supposed a `ffmpeg bitrate video' in google would be a
*much* wider scope search than `googling within the ffmpeg-user mail list'.

I may be wrong, however. How do you `google within the ffmpeg-user mail list'?

> c) upgrade to a recent ffmpeg, and read the output messages.
>
> Regards,
> Víctor

Just uninstalled whatever version should I have installed before (that from Debian Etch repository):
dpkg --purge ffmpeg

...then installed the most recent svn source checkout:
svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg

...built it succesfully with
sudo ./configure --enable libfaad --enable--libfaac --enable-libmp3lame --enable-libxvid --enable-libx264 --enable-liba52


...and finally installed the binaries with
sudo make install


As for the output information:

mycomputer@mydomain$ ffmpeg -i whatevervideo.avi -s 368x208 -b 512 -ab 64 -ar 24000 -f psp /tmp/M4V0001.MP4
FFmpeg version SVN-r11231, Copyright (c) 2000-2007 Fabrice Bellard, et al.
  configuration: --enable-libfaac --enable-libfaad --enable-libmp3lame --enable liba52 --enable-libxvid --enable-libx264 --enable-gpl
  libavutil version: 49.6.0
  libavcodec version: 51.49.0
  libavformat version: 52.2.0
  built on Dec 16 2007 17:36:27, gcc: 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)4
Input #0, avi, from 'whatevermovie.avi':
  Duration: 01:50:37.4, start: 0.000000 bitrate 885 kb/s
    Stream #0.0: Video: mpeg4, yuv420p, 576x232 [PAR 1:1 DAR 72:29], 25.00 tb (r)
    Stream #0.1: Audio: mp3, 48000 Hz, stereo, 128 kb/s
Output #0, psp, to '/tmp/M4V0001.MP4'
    Stream #0.0: Video: mpeg4, yuv420p, 368x208 [PAR 254:181 DAR 5842:2353], q=2-31, 0 kb/s, 25.00 tb(c)
    Stream #0.1: Audio: libfaac, 24000 Hz, stereo, 0 kb/s
Stream mapping:
    Stream #0.0 -> #0.0
    Stream #0.1 -> #0.1
Press [q] to stop encoding
frame=2108 fps=126 q=31.0 size=     880kB time=84.3 bitrate=   85.5kbits/s


Unfortunately, the output keeps looking horrible. The value bitrate in the last output line *never* rises beyond 115 kbits/s

Could you suggest any other thing?



_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account the -b <bitrate> value.

Eduardo M Kalinowski-2
Juanjavier wrote:

> Víctor Paesa wrote:
>  
>>
>> There are at least three options:
>> a) read the documentation on -b (run ffmpeg -h),
>>  
>>    
> I did so before, thanks.
>
> Video options:
>
> -b                  set bitrate (in bits/s)
>
> -vb                 set bitrate (in bits/s)
>
> This does not help, sorry.
>  

Hint: look at the units that -b takes.
> mycomputer@mydomain$ ffmpeg -i whatevervideo.avi -s 368x208 -b 512 -ab 64 -ar 24000 -f psp /tmp/M4V0001.MP4
>  

Hint: look at the units that you specify.


--
A friend is a present you give yourself.
                -- Robert Louis Stevenson

Eduardo M KALINOWSKI
[hidden email]
http://move.to/hpkb

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account the -b <bitrate> value.

Panagiotis Issaris
In reply to this post by juanjavier
Hi,


Juanjavier schreef:

> Víctor Paesa wrote:
>> Hi,
>>
>> Juanjavier dijo:
>>  
>>> It always encode with a waaaay too low bitrate....so the output gets
>>> horribly pixeled...no matter which value do I put
>>>
>>> in -b <bitrate> option.
>>>
>>> If no -b <bitrate> value is given, the output will surround the ~ 200
>>> kbps value, which is the default.
>>>
>>>
>>> This turns out to be unacceptably low.
>>>
>>> If we do specify -for instance- -b 750 and keep monitoring the
>>> processing in the command line, we see values of  about 150 kbps and
>>> descending...
>>>
>>> I have checked that the source streams has video bitrate high
>>> enough...they are 688x272 high quality divX streams in the
>>>
>>> 750-800-850 kbits/sec range.
>>>
>>>
>>> The output does not even reach 250 kbits/sec.
>>>
>>> Why does this happen? Googling did not help. Is there a way to *force* a
>>> high enough kbps rate in the video output?
>>>    
>> There are at least three options:
>> a) read the documentation on -b (run ffmpeg -h),
>>  
> I did so before, thanks.
>
> Video options:
>
> -b                  set bitrate (in bits/s)
>
> -vb                 set bitrate (in bits/s)
>
> This does not help, sorry.


Please, read it _carefully_ ... focus on the part between brackets :)

>
>
>> b) Google within the ffmpeg-user mail list,
>>  
>
> How is that done? Supposed a `ffmpeg bitrate video' in google would be a
> *much* wider scope search than `googling within the ffmpeg-user mail list'.
>
> I may be wrong, however. How do you `google within the ffmpeg-user mail list'?

I'd use gmane.


>> c) upgrade to a recent ffmpeg, and read the output messages.
>>
>> Regards,
>> Víctor
>

...

> Output #0, psp, to '/tmp/M4V0001.MP4'
>     Stream #0.0: Video: mpeg4, yuv420p, 368x208 [PAR 254:181 DAR 5842:2353], q=2-31, 0 kb/s, 25.00 tb(c)

Regarding bitrate, you should have noticed something as being a bit odd ...
:-)


> Unfortunately, the output keeps looking horrible. The value bitrate in the last output line *never* rises beyond 115 kbits/s
>
> Could you suggest any other thing?


With friendly regards,
Takis
--
vCard: http://issaris.org/pi.vcf
PGP key: http://issaris.org/pi.key
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account...[SOLVED]

juanjavier
Panagiotis Issaris wrote:

> Hi,
>
>
> Juanjavier schreef:
>  
>> Víctor Paesa wrote:
>>    
>>> Hi,
>>>
>>> Juanjavier dijo:
>>>  
>>>      
>>>> It always encode with a waaaay too low bitrate....so the output gets
>>>> horribly pixeled...no matter which value do I put
>>>>
>>>> in -b <bitrate> option.
>>>>
>>>> If no -b <bitrate> value is given, the output will surround the ~ 200
>>>> kbps value, which is the default.
>>>>
>>>>
>>>> This turns out to be unacceptably low.
>>>>
>>>> If we do specify -for instance- -b 750 and keep monitoring the
>>>> processing in the command line, we see values of  about 150 kbps and
>>>> descending...
>>>>
>>>> I have checked that the source streams has video bitrate high
>>>> enough...they are 688x272 high quality divX streams in the
>>>>
>>>> 750-800-850 kbits/sec range.
>>>>
>>>>
>>>> The output does not even reach 250 kbits/sec.
>>>>
>>>> Why does this happen? Googling did not help. Is there a way to *force* a
>>>> high enough kbps rate in the video output?
>>>>    
>>>>        
>>> There are at least three options:
>>> a) read the documentation on -b (run ffmpeg -h),
>>>  
>>>      
>> I did so before, thanks.
>>
>> Video options:
>>
>> -b                  set bitrate (in bits/s)
>>
>> -vb                 set bitrate (in bits/s)
>>
>> This does not help, sorry.
>>    
>
>
> Please, read it _carefully_ ... focus on the part between brackets :)
>
>  
>>    
>>> b) Google within the ffmpeg-user mail list,
>>>  
>>>      
>> How is that done? Supposed a `ffmpeg bitrate video' in google would be a
>> *much* wider scope search than `googling within the ffmpeg-user mail list'.
>>
>> I may be wrong, however. How do you `google within the ffmpeg-user mail list'?
>>    
>
> I'd use gmane.
>
>
>  
>>> c) upgrade to a recent ffmpeg, and read the output messages.
>>>
>>> Regards,
>>> Víctor
>>>      
>
> ...
>
>  
>> Output #0, psp, to '/tmp/M4V0001.MP4'
>>     Stream #0.0: Video: mpeg4, yuv420p, 368x208 [PAR 254:181 DAR 5842:2353], q=2-31, 0 kb/s, 25.00 tb(c)
>>    
>
> Regarding bitrate, you should have noticed something as being a bit odd ...
> :-)
>
>
>  
>> Unfortunately, the output keeps looking horrible. The value bitrate in the last output line *never* rises beyond 115 kbits/s
>>
>> Could you suggest any other thing?
>>    
>
>
> With friendly regards,
> Takis
> --
> vCard: http://issaris.org/pi.vcf
> PGP key: http://issaris.org/pi.key
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
>
>  
Uuups....thanks for the quick reply!!!! :-)  Your are right, friend !!! XDDD


Let me point something anyway...the documentation throws a bit of confussion, in my opinion...

-b bitrate'

Set the video bitrate in bit/s (default = 200 kb/s).

As for what I know, kb/s stands for kilobytes per second, and not kilobits per second.

kb/s is *not* the same as kbit/s.

So that it was.

Typing (for instance) -b 650000 outputted a wonderful video clip.

Thank you all for the quick help. Regards!





_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account the -b <bitrate> value.

Ví­ctor Paesa
In reply to this post by juanjavier
Hi,
Juanjavier dijo:

> Víctor Paesa wrote:
>> Hi,
>>
>> Juanjavier dijo:
>>
>>> It always encode with a waaaay too low bitrate....so the output gets
>>> horribly pixeled...no matter which value do I put
>>>
>>> in -b <bitrate> option.
>>>
>>> If no -b <bitrate> value is given, the output will surround the ~ 200
>>> kbps value, which is the default.
>>>
>>>
>>> This turns out to be unacceptably low.
>>>
>>> If we do specify -for instance- -b 750 and keep monitoring the
>>> processing in the command line, we see values of  about 150 kbps and
>>> descending...
>>>
>>> I have checked that the source streams has video bitrate high
>>> enough...they are 688x272 high quality divX streams in the
>>>
>>> 750-800-850 kbits/sec range.
>>>
>>>
>>> The output does not even reach 250 kbits/sec.
>>>
>>> Why does this happen? Googling did not help. Is there a way to
>>> *force* a high enough kbps rate in the video output?
>>>
>>
>> There are at least three options:
>> a) read the documentation on -b (run ffmpeg -h),
>>
> I did so before, thanks.
>
> Video options:
>
> -b                  set bitrate (in bits/s)
                                      ^^^^
The units are to be expressed in bits/s, not kilobits/s.

>
> -vb                 set bitrate (in bits/s)
>
> This does not help, sorry.
>> b) Google within the ffmpeg-user mail list,
>>
>
> How is that done? Supposed a `ffmpeg bitrate video' in google would be a
> *much* wider scope search than `googling within the ffmpeg-user mail
> list'.
>
> I may be wrong, however. How do you `google within the ffmpeg-user mail
> list'?

Sorry, I was not too informative. The trick is to use Gmane, the Google
mail archive. You can run searches per mail list archived there.

>
>> c) upgrade to a recent ffmpeg, and read the output messages.
>>
>> Regards,
>> Víctor
>
> Just uninstalled whatever version should I have installed before (that
> from Debian Etch repository): dpkg --purge ffmpeg
>
> ...then installed the most recent svn source checkout:
> svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg
>
> ...built it succesfully with
> sudo ./configure --enable libfaad --enable--libfaac --enable-libmp3lame
> --enable-libxvid --enable-libx264 --enable-liba52
>
>
> ...and finally installed the binaries with
> sudo make install
>
>
> As for the output information:
>
> mycomputer@mydomain$ ffmpeg -i whatevervideo.avi -s 368x208 -b 512 -ab
> 64 -ar 24000 -f psp /tmp/M4V0001.MP4 FFmpeg version SVN-r11231,
> Copyright (c) 2000-2007 Fabrice Bellard, et al.
>   configuration: --enable-libfaac --enable-libfaad --enable-libmp3lame
> --enable liba52 --enable-libxvid --enable-libx264 --enable-gpl
> libavutil version: 49.6.0
>   libavcodec version: 51.49.0
>   libavformat version: 52.2.0
>   built on Dec 16 2007 17:36:27, gcc: 4.1.2 20061115 (prerelease)
> (Debian 4.1.1-21)4
> Input #0, avi, from 'whatevermovie.avi':
>   Duration: 01:50:37.4, start: 0.000000 bitrate 885 kb/s
>     Stream #0.0: Video: mpeg4, yuv420p, 576x232 [PAR 1:1 DAR 72:29],
> 25.00 tb (r) Stream #0.1: Audio: mp3, 48000 Hz, stereo, 128 kb/s
> Output #0, psp, to '/tmp/M4V0001.MP4'
>     Stream #0.0: Video: mpeg4, yuv420p, 368x208 [PAR 254:181 DAR
> 5842:2353], q=2-31, 0 kb/s, 25.00 tb(c) Stream #0.1: Audio: libfaac,
> 24000 Hz, stereo, 0 kb/s
> Stream mapping:
>     Stream #0.0 -> #0.0
>     Stream #0.1 -> #0.1
> Press [q] to stop encoding
> frame=2108 fps=126 q=31.0 size=     880kB time=84.3 bitrate=
> 85.5kbits/s
>
>
> Unfortunately, the output keeps looking horrible. The value bitrate in
> the last output line *never* rises beyond 115 kbits/s
>
> Could you suggest any other thing?

Hmm, here I was expecting some verbose hint from ffmpeg. I don't
have access to the command line now, but it should be something like
"you entered a too low value for bitrate. Did you remember that units are
bits/s, instead of kbits/s?"
Anyway, you didn't complain about audio, but -ab also expects bits/s.

Regards,
Víctor




_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account the -b <bitrate> value.

The Wanderer-2
Víctor Paesa wrote:

> Hi, Juanjavier dijo:
>
>> Víctor Paesa wrote:

>>> b) Google within the ffmpeg-user mail list,
>>
>> How is that done? Supposed a `ffmpeg bitrate video' in google would
>> be a *much* wider scope search than `googling within the
>> ffmpeg-user mail list'.
>>
>> I may be wrong, however. How do you `google within the ffmpeg-user
>> mail list'?
>
> Sorry, I was not too informative. The trick is to use Gmane, the
> Google mail archive. You can run searches per mail list archived
> there.

As far as I can tell with a little checking (reading the Wikipedia entry
and looking at the Gmane front page and FAQ), Gmane has nothing to do
with Google; it's a completely independent project. (It also isn't
strictly a "mail archive", but a mail-to-Usenet gateway which also
provides archiving services.)

--
       The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Secrecy is the beginning of tyranny.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account...[SOLVED]

Phill Clarke
In reply to this post by juanjavier
On 16/12/2007, Juanjavier <[hidden email]> wrote:

>
>
> Let me point something anyway...the documentation throws a bit of
> confussion, in my opinion...
>
> -b bitrate'
>
> Set the video bitrate in bit/s (default = 200 kb/s).
>
> As for what I know, kb/s stands for kilobytes per second, and not kilobits
> per second.
>
> kb/s is *not* the same as kbit/s.
>
> So that it was.
>
Typing (for instance) -b 650000 outputted a wonderful video clip.
>
> Thank you all for the quick help. Regards!
>
>
You can also enter it like this:

-b 650k

This will output a file with a bitrate of 650 kilobits/second.

Your input of 650000 is actually only 634.8 kbps (650,000/1024)

kbits/s, kb/s and kbps are all the same thing:

http://en.wikipedia.org/wiki/Kbit/s

Bits, kilobits, megabits etc are all related to data transfer rate.

Bytes, kilobytes and megbytes are units of data storage.

Hope this helps.

Phill
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account the -b <bitrate> value.

Ví­ctor Paesa
In reply to this post by The Wanderer-2
Hi,
The Wanderer said:

> Víctor Paesa wrote:
>
>> Hi, Juanjavier dijo:
>>
>>> Víctor Paesa wrote:
>
>>>> b) Google within the ffmpeg-user mail list,
>>>
>>> How is that done? Supposed a `ffmpeg bitrate video' in google would
>>> be a *much* wider scope search than `googling within the
>>> ffmpeg-user mail list'.
>>>
>>> I may be wrong, however. How do you `google within the ffmpeg-user
>>> mail list'?
>>
>> Sorry, I was not too informative. The trick is to use Gmane, the
>> Google mail archive. You can run searches per mail list archived
>> there.
>
> As far as I can tell with a little checking (reading the Wikipedia entry
> and looking at the Gmane front page and FAQ), Gmane has nothing to do
> with Google; it's a completely independent project. (It also isn't
> strictly a "mail archive", but a mail-to-Usenet gateway which also
> provides archiving services.)

Ooops! Sorry for the false attribution.

Regards,
Víctor


_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account...[SOLVED]

Stefano Sabatini
In reply to this post by Phill Clarke
On date Sunday 2007-12-16 20:00:48 +0000, Phill Clarke encoded:
[...]
> kbits/s, kb/s and kbps are all the same thing:
>
> http://en.wikipedia.org/wiki/Kbit/s
>
> Bits, kilobits, megabits etc are all related to data transfer rate.
>
> Bytes, kilobytes and megbytes are units of data storage.

Also in this case, just to make life harder, the meaning of kilo and
mega is different from the usual meaning in Physics/Engineering, kilo
means 2^10 = 1024 and mega means 2^20 = 1048576, so it is a good idea
to use the Ki and Mi postfixes rather than K and M.

Regards.
--
ffmpeg-user random tip #4
ffmpeg -i FILE
prints information about the container format and the streams in a file.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: ffmpeg does not take into account...[SOLVED]

The Wanderer-2
Stefano Sabatini wrote:

> On date Sunday 2007-12-16 20:00:48 +0000, Phill Clarke encoded: [...]
>
>> kbits/s, kb/s and kbps are all the same thing:
>>
>> http://en.wikipedia.org/wiki/Kbit/s
>>
>> Bits, kilobits, megabits etc are all related to data transfer rate.
>>
>> Bytes, kilobytes and megbytes are units of data storage.

Twaddle. Bits and bytes are both units of data size; there may be
convention to use the former when talking about transfer and the latter
when talking about storage, but it's certainly not universal, and there
is no fundamental reason why you could not use either in either case.

(Warning: Rant follows.)

> Also in this case, just to make life harder, the meaning of kilo and
> mega is different from the usual meaning in Physics/Engineering, kilo
> means 2^10 = 1024 and mega means 2^20 = 1048576, so it is a good
> idea to use the Ki and Mi postfixes rather than K and M.

No, it's not a good idea to use those, because they are short for "kibi"
and "mebi" rather than "kilo" and "mega", and so using them constitutes
giving in on the issue of whether the invented replacement terms for the
power-of-two multipliers are remotely tolerable.

In context of binary-based data, "kilo" and "mega" and the like do in
fact refer to power-of-two multipliers; in most other contexts, they do
not. There is no need for other terms to indicate that difference, and
the attempt to foist the invented replacements on the world is very much
not appreciated by those of us who are aware of this.

(...which, for all I actually have evidence for at the moment, may be a
group consisting only of me...)

And no, we do *not* have the option of just not using the invented terms
if we do not like them, even if we go so far as to avoid (or alter
before using) all software which does use them; if anyone uses them for
data where they are not needed, that introduces ambiguity as to which
multiplier is meant in the context of data, and thus makes it unclear -
where it would not previously have been - which multiplier is meant
whenever the units are used *anywhere*.

--
       The Wanderer will probably shut up now

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Secrecy is the beginning of tyranny.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user