Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Luigi1943]

I'm confused: a track whose real size (as displayed by Windows Explorer Properties) is 745472 bytes (size on disk 753664 because of cluster byte loss) is displayed by MJ8 as 789.327KB (about 6% more than real). The same happens for all the tracks. Can anyone explain this difference? I could understand a difference in the other way round, since a Kb is 1024 bytes.

I also have a request: since I use the italian Windows version (decimal point is comma) I perceive 789.327Kb as  a very large 789327Kb... the same with MB and GB: MJ8 tells me that my track library is some 20 thousand Gigabytes... could the sizes be displayed with one or two decimals instead of three, so to avoid the false perception? In the above example the size would be displayed as a non ambiguous 789.3Kb or 789.33Kb.
I (and the other European users) would appreciate very much.
Thanks for the attention and for a reply
Luigi

[KingSparta]

I would like It Display Beads, Like On An Abacus

[cjdshaw]

Or MJ could use Windows' locale to decide whether to use a decimal point or a comma.

[KingSparta]

>> I could understand a difference in the other way round, since a Kb is 1024 bytes.
I think i read somewhere that KB is now going to be counted as 1000bytes thru out the computer industry.

I don't have a clue why the size would be 6% more, since i checked a few of my files and the size MJ tells me it is it is the same in Windows XP (US Version).

[Mr,X]

Here's an article about why there's confusion over this...

Giga vs Gigi