Very file small file sizes are reported as being 0 KiB in bottom pane of DLE but show properly in the top pane.

[AlbertEinstein]

I'm not sure if this would be called a bug but I believe it is and it needs to be addressed. I burned some very small files to BD-R at less than 100 bytes a file. The bottom DLE pane shows this as  being 0 KiB in size while the top pane shows the same files as being 1 KiB in size. Now, we all know neither of these is 100% accurate. But when I just noticed this issue this morning it scared me. So, I went back to look at the file sizes on the actual finished product, the mastered BD-R and the files were burned properly. I thought something may have gone wrong.

And lastly, this issue was observed after loading "Most Recent Project" so, while the file sizes may have been reported accurately before the save/load cycle they aren't reported properly afterwards. Small bug, should be really easy fix.

But my recommendation is to round up versus rounding down even on files so small.

Thanks for reading!

Edited 12 hours ago by AlbertEinstein

[dbminter]

I would agree that 1 KB/KiB should be returned for files that are actually less than 1.  I can see how 0 could lead to some confusion.

 

The only problem I see is that/those components of ImgBurn might be enslaved to standards that Microsoft set.  Or however made the programming package that ImgBurn is written in.  Those components that return directory contents may be standardized by the programming language and beyond the control of LUK to do anything about.

[AlbertEinstein]

Possibly, but the way I look at it, if it displays properly 1) immediately after added and 2) no issues displaying 1kb versus 0kb in the top pane, then it's more than likely just a rare bug. Much like the mismatched icons issue I reported months ago. Things start out right, so, and then later on, you wake up your PC or load a saved project back into memory and then go "Huh?". So, I can't see it being a limitation of any existing API outside the programmers control.

But well let him inform us all. He knows best.

[LIGHTNING UK!]

It uses Bankers rounding for all of that stuff.

The top pane is a component and its code basically seems to return 1KB if it's anything less than 1.

Explorer must be rounding up as it calls a 1025 byte file 2KB.

[AlbertEinstein]

57 minutes ago, LIGHTNING UK! said:

It uses Bankers rounding for all of that stuff.

The top pane is a component and its code basically seems to return 1KB if it's anything less than 1.

Explorer must be rounding up as it calls a 1025 byte file 2KB.

Good God, I just checked the file again in Windows File Explorer on Windows 10 and it reported the 71 byte file in 3 different sizes. In the "Preview Pane" when the file is selected it reports the size exactly as 71 bytes. In the File Explorer "Size" column it reports as 1K. And when you right-click the file and select the "Properties" dialog box it reports the size correctly at 71 bytes but it reports "Size on disk" as 0 bytes. It's serving up a little bit of everything I guess.