[Ffmpeg-devel] [PATCH] Remove "bufsize" OptionDef option
Mon Sep 18 00:29:14 CEST 2006
The Wanderer <inverseparadox at comcast.net> writes:
> Gary Corcoran wrote:
>> The Wanderer wrote:
>>> M?ns Rullg?rd wrote:
>>>> It means 1024 when dealing with bytes. When dealing with bits
>>>> (as in bitrates), it's usually 1000.
>>> I'm aware of this attempt to draw a line (or I am now, at any
>>> rate), but I think I still stand by my statement; I see no
>>> particular reason to change the meaning of the prefix just because
>>> we've changed the magnitude of the unit.
>> It's not the magnitude of the unit - it's the context. As far as I'm
>> concerned, when dealing with memory sizes, be they in RAM or on
>> disk, K means 1024. But dealing with bitrates, K means 1000. I
>> think that's the way most of us on this list think of these.
> Yes, I'm aware of that. I was saying that that is *not* the case for me
> - in referring to bitrates just the same as when referring to other
> types of binary data, I believe that I think of K as being 1024.
You are of course entitled to think whatever way you want, but most
people mean 1000 bits when they talk of 1 kilobit.
> However, I could probably stand having the meaning split in that way, as
> long as we don't try to change the underlying terms - which, of course,
> is precisely what those responsible for "kibi" etc. are trying to do.
It's an evil scheme invented by hard drive makers so they can boost
the numbers while still calling it gigabytes.
mru at inprovide.com
More information about the ffmpeg-devel