New File Browser UI is listing incorrect file sizes #69455

Closed
opened 2019-09-03 20:55:06 +02:00 by Jesse Yurkovich · 11 comments

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: Quadro 600/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 369.09

Blender Version
Broken: version: 2.81 (sub 5), branch: master, hash: 9e3cd98529
Worked: (optional)

Short description of error
It looks like the file sizes are incorrect -- is the mega byte calculation actually being done?

Take these 2 files for example (size listed in bytes):

07/30/2019  04:52 PM        70,220,480 perf-test.blend
03/18/2019  12:41 AM        31,345,332 Sample_Pack.blend

These should be ~66.9 MB and ~29.8 MB respectively but blender has other ideas:
wrong-size.png

Exact steps for others to reproduce the error

  • View a set of files in the new file browser and check their sizes with how big they actually are
**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: Quadro 600/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 369.09 **Blender Version** Broken: version: 2.81 (sub 5), branch: master, hash: 9e3cd98529 Worked: (optional) **Short description of error** It looks like the file sizes are incorrect -- is the mega byte calculation actually being done? Take these 2 files for example (size listed in bytes): ``` 07/30/2019 04:52 PM 70,220,480 perf-test.blend 03/18/2019 12:41 AM 31,345,332 Sample_Pack.blend ``` These _should_ be ~66.9 MB and ~29.8 MB respectively but blender has other ideas: ![wrong-size.png](https://archive.blender.org/developer/F7715533/wrong-size.png) **Exact steps for others to reproduce the error** - View a set of files in the new file browser and check their sizes with how big they actually are
Author
Member

Added subscriber: @deadpin

Added subscriber: @deadpin
Member

Added subscriber: @Harley

Added subscriber: @Harley
Member

The central issue is that the various platforms are not in agreement with how to show abbreviated file sizes. The terms many of us use, like "megabyte", has always been ambiguous in whether it is in base2 or base10. So on each platform the users have a different idea of what a "megabyte" is.

Not that is matters. What is important is that what we show matches what the user expects, so we should vary by platform.

First, I think we need a nice tooltip when you hover over the file size. It should show the sizes in base2, base10, and the number of bytes.

For what to show in the file list:

  • Windows: base2 number with "MB" abbreviation
  • Mac: base10 number with "MB" abbreviation
  • Linux: base2 number with "MiB" abbreviation
The central issue is that the various platforms are not in agreement with how to show abbreviated file sizes. The terms many of us use, like "megabyte", has always been ambiguous in whether it is in base2 or base10. So on each platform the users have a different idea of what a "megabyte" is. Not that is matters. What is important is that what we show matches what the user expects, so we should vary by platform. First, I think we need a nice tooltip when you hover over the file size. It should show the sizes in base2, base10, and the number of bytes. For what to show in the file list: - Windows: base2 number with "MB" abbreviation - Mac: base10 number with "MB" abbreviation - Linux: base2 number with "MiB" abbreviation
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

This actually works like designed, the units are now base 10, rather than base 2.

The issue is that the units KB, MB, etc are ambiguous in fact. They don't specify if numbers are calculated base 10, or base 2. To solve this ambiguity, the units KiB, MiB, etc were introduced for base 2, and the International System of Units (SI) defines MB to be base 10. We follow that definition.
MacOS and Gnome file manager show base 10 too, KDE's Dolphin seems to have it optional, but follows the SI definition.
Windows appears to be the only platform not following the SI definition, showing KB, MB, etc for base 2.

(From the chat I know this has already been figured out, just mentioning here for others seeing this.)

This actually works like designed, the units are now base 10, rather than base 2. The issue is that the units KB, MB, etc are ambiguous in fact. They don't specify if numbers are calculated base 10, or base 2. To solve this ambiguity, the units KiB, MiB, etc were introduced for base 2, and the International System of Units (SI) defines MB to be base 10. We follow that definition. MacOS and Gnome file manager show base 10 too, KDE's Dolphin seems to have it optional, but follows the SI definition. Windows appears to be the only platform not following the SI definition, showing *KB*, *MB*, etc for base 2. (From the chat I know this has already been figured out, just mentioning here for others seeing this.)

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
William Reynish self-assigned this 2019-09-03 22:08:06 +02:00

Archiving, since it is technically correct and works as designed.

Archiving, since it is technically correct and works as designed.

Added subscriber: @Regnas

Added subscriber: @Regnas

@Harley Since you are dealing with optional columns D5667 how about a new size column in base 2?

@Harley Since you are dealing with optional columns [D5667](https://archive.blender.org/developer/D5667) how about a new size column in base 2?
Member

@Regnas - how about a new size column in base 2?

That seems obvious but did not occur to me to be honest. Must need more coffee...

> @Regnas - how about a new size column in base 2? That seems obvious but did not occur to me to be honest. Must need more coffee...
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#69455
No description provided.