Units used for file sizes

[E9A7F3bD]

Don't be confused because pixeldrain math calls it 1.53Gb. It is still the same file.

Thanks for sharing!

Interestingly, I think pixeldrain's mathematical calculations are correct.
But please note that it is "1.53GB" instead of "1.53Gb".
1 Byte = 8 bits
1 GB (Gigabyte) = 8 Gb (Gigabit)

Confusion often occurs in Windows OS, and the misuse and display of "GB (Gigabyte)" and "GiB (Gibibyte)" units.
1 GB = 10^9 Bytes = 1,000,000,000 Bytes
1 GiB = 2^30 Bytes = 1,073,741,824 Bytes

You can see the correct unit displayed in "mediainfo" results in your post: [Code] The best way to verify file consistency and integrity is still to calculate HASH (Message Digest) information, for example: [Code] The ed2k link itself also contains a kind of HASH information.
https://en.wikipedia.org/wiki/Ed2k_URI_scheme

[Night457]

E9A7F3bD - Thank you for spelling it out. I understand the base-2 calculations, but am annoyed by the use of both standards on different sites. (Use one formula and stick with it!) I was certain without checking it that their math was correct, because it is done automatically: there is not someone sitting at a desk with pencil and paper doing math for every file posted! I am afraid that I have never even attempted to distinguish GB - Gb - GiB because I know that I will never remember the correct difference, let alone type it. Changed meanings between upper-case and lower-case everywhere else also irritates me. ("Your user name is not case dependent but your password is.") People who ought to know better decided to have very similar abbreviations for two related but different calculations. That is so screamingly obviously a bad idea for anyone except a computer. Since "Giga comes from the Greek word for giant" there is no reason it must be used for "billion": we could use the term "billion" for 1,000,000,000 and "Giga" for 1,073,741,824 because DUH. Billion and Giga are both 2-syllable words! But we do not need to worry, because soon enough only computers will share movies with each other. Humans and their idiosyncratic use of languages as applied to math will not be necessary.

ghost - I would have been surprised if you somehow created a quality HighDef version but decided to keep it a secret, or shared it and later removed your post! Maybe relic saw some better version somewhere, but I did not think it was at FLM - nor at any place that we have access to!

Sully23 - I am guessing your Rich quote is for a different movie, since it references Hungary and not France or Germany. (?)

Thequietgirl - I think the letterboxd reviews simply mean that someone wants to review it. That normally means they watched it and could be any version or any language. They are just like anyone else online and there is no reason to believe they have special movie industry connections. If I understood either German or French and was not using subtitles I would certainly easily notice the dubbing -- but I have seen too many well-dubbed movies to be bothered by this one. *BAD* dubbing that I have watched is still a distraction, but that is not a problem here. Still, there are some other movies where the language spoken on set seems to be unavailable. When I watch them multiple times then I yearn for proper lip-sync...

Spoiler: There was one occasion where I watched a Hong Kong Chinese movie on DVD with audio options of Cantonese, Mandarin, or English. There were three lead actresses and I wanted to see it with the "correct" audio, but the actresses came from different regions. As I watched the lip sync carefully, it seemed to be the case that one actress was speaking Cantonese and was of necessity dubbed for the Mandarin track; another actress spoke Mandarin and was dubbed for the Cantonese track; and the third actress switched between Cantonese and Mandarin depending on who her partner in the scene was! I also learned that traditionally, Hong Kong movies were dubbed by professional voice actors no matter what language was spoken and that the actors on the screen were not even involved. It was only some of the time that they were available to do their own dubbing rather than being busy with their next project. That movie also had Japanese supporting actors speaking Japanese on set. I had to give up on being bothered by dubbing at that point.

[E9A7F3bD]

E9A7F3bD - Thank you for spelling it out. I understand the base-2 calculations, but am annoyed by the use of both standards on different sites. (Use one formula and stick with it!) I was certain without checking it that their math was correct, because it is done automatically: there is not someone sitting at a desk with pencil and paper doing math for every file posted! I am afraid that I have never even attempted to distinguish GB - Gb - GiB because I know that I will never remember the correct difference, let alone type it. Changed meanings between upper-case and lower-case everywhere else also irritates me. ("Your user name is not case dependent but your password is.") People who ought to know better decided to have very similar abbreviations for two related but different calculations. That is so screamingly obviously a bad idea for anyone except a computer. Since "Giga comes from the Greek word for giant" there is no reason it must be used for "billion": we could use the term "billion" for 1,000,000,000 and "Giga" for 1,073,741,824 because DUH. Billion and Giga are both 2-syllable words! But we do not need to worry, because soon enough only computers will share movies with each other. Humans and their idiosyncratic use of languages as applied to math will not be necessary.

I wouldn't say that these abbreviations or spellings are the best designs.

But since there are already some standards and consensuses like SI prefix and IEC 60027-2 there, let's just use and spread these unambiguous and well-documented things wherever possible, which I believe is true in any field.

Linux, macOS, mediainfo (even in Windows), and pixeldrain are all doing the right things, why can't we see these efforts?

Unless "you" could create a new standard and get enough consensus. Otherwise there is no harm in learning and using them correctly.

This is just like some of the rules and consensus of FLM. We are just learning and following them and maintaining things as good as possible.

Anyway, these are just my little tips and efforts to "promote" the right things. If you don't like them, plz forget everything, it's okay.

[Night457]

Linux, macOS, mediainfo (even in Windows), and pixeldrain are all doing the right things

It does not matter to me which standard or unit is used, I simply want consistency!

For the file in question:
The FLM ed2k link has it as 1.42Gb
my eMule client has it as 1.42 GB
mediainfo has it as 1.42 GiB
pixeldrain has it as 1.53 GB
Windows File Explorer has it as 1,494,164 KB

I looked carefully back and forth to be sure I was capitalizing what they had capitalized but still I am not confident I did it all right because I am not looking at each at the moment. Are all of those usages correct? Is just one incorrect? I will assume Windows at least is most likely correct.

I am not saying that I REFUSE to learn the difference between GB, GiB, and Gb. I am saying that I am INCAPABLE. I will learn it for 5 minutes and then forget. If I later encounter it used incorrectly, I would not be able to say for sure which one is wrong. I would have to look it up all over again every single time. I have better things to do than that. All I want is quick comparison of file sizes without having to do mathematical conversions and verifying the units. When I was young I learned how to mentally convert between Celsius and Fahrenheit and I can still do that. I am no longer young, so spending time on new math tricks does not appeal to me. (And I also think that Kelvin with its Absolute Zero and no negative temperatures makes the most sense. I really do not care whether water boils at 100 C, 212 F, or 373.15 K. I just turn up the heat on the stovetop and wait until it bubbles.)

[E9A7F3bD]

It does not matter to me which standard or unit is used, I simply want consistency!

Consistency can only be achieved if people adopt the same broad consensus standard!
This is the whole meaning of standards and units.

I will assume Windows at least is most likely correct.

Windows is the main source of all these error usages!

The FLM ed2k link has it as 1.42Gb
my eMule client has it as 1.42 GB
mediainfo has it as 1.42 GiB
pixeldrain has it as 1.53 GB
Windows File Explorer has it as 1,494,164 KB

Correct:
1,530,023,653 bytes
1,530,024 kB
1,530 MB
1.53 GB
1,494,164 KiB
1,459 MiB
1.42 GiB

Therefore, except mediainfo and pixeldrain, there all errors and confusions.

[Night457]

OOPS! You edited your post while I was responding, so now some of my response does not make sense. I will look at your newly edited post to absorb the information.
***
So we agree then. Right? I simply copy whatever value I see in front of me; I do not calculate the number of bits in a file and then convert them to a chosen standard. Yet I will probably get the letter capitalization wrong because I sometimes miss the shift key and do not notice. I do not have any control at all over what numbers I am given in the first place, and I am not going to email a bot to inform it that its company owner is doing it wrong. The bot does not care.

(Seriously: I wanted to know who was using it wrong. I would guess the ancient and no longer updated eMule client...) People can agree to use a standard but that does mean they will be successful at it when there is another standard that is so close to it. At least Celsius and Fahrenheit are far apart for most of their scale. If I say it is 100 degrees outside, no one will seriously think I mean Celsius!

I do appreciate you patiently explaining the facts. I simply despair of my ability to retain them. Please don't be too disappointed with me!

Everyone else: I apologize for derailing this thread! I just wanted to say it was the same file no matter what the numbers said!

Windows is the main source of all these error usages!

I guess I should not be surprised. Yet what is the likelihood of anyone convincing Microsoft ever that they are wrong? It will not happen. They will ignore it or deny it, and introduce new errors in each new version of Windows.

Therefore, except mediainfo and pixeldrain, there all errors and confusions.

I am glad that they at least are using the units and calculations correctly. However, they are using different units rather than agreeing to use the same units for file sizes. So I am back where I started: I have to do the math calculations in order to compare file sizes. I have no control over their software. I could refuse to use a file uploading site unless it uses the same units as mediainfo, but that would be cutting off my nose to spite my face. I will not stop using Windows or eMule, either.

[E9A7F3bD]

The FLM ed2k link has it as 1.42Gb

And thank you for making and noting this, and in response, I have made suggestions for revisions in the board development section:

viewtopic.php?t=16677

This will at least add to the consistency.

I don't expect Windows and eMule to change.

Regarding eMule, its ed2k HASH finally has two different computing implementations due to the imperfect rigor of historical documents.

[pillowbaker]

It's only been a couple posts, with on-topic posts in between.

[edit: post occurred before I posted mine, so I am here referring to Night]
You have a point, it is sometimes confusing to see a supposedly slightly different size on pixeldrain than what you have already downloaded, so you grab the file to check it out, only to find it was the same all along. We could learn this, but calculating on the fly get in the way, it feels. I think we all understand the basics of it at least.

For the on-topic, I of course noticed your upscale previews, E9A7F3bD. Are you learning to upscale movies like this with topaz? This movie does look like it could benefit from a higher quality source. Sad, this looks like one of the classics that may never get the treatment.

[E9A7F3bD]

Everyone else: I apologize for derailing this thread! I just wanted to say it was the same file no matter what the numbers said!
...
I have to do the math calculations in order to compare file sizes.

I know there are some chaos that cannot be resolved, I am just explaining why the chaos is created and how we can reduce the creation of them.

I've mentioned in my initial post that the best way to check file consistency is not "file size", but the file HASH values, using them is simple, and I highly recommend this.

Sorry for all noises from this thread.

[Night457]

I should have known I was going to cause chaos by talking about file sizes!

I moved multiple posts from a movie thread to try to keep it more streamlined.