AlbertEinstein Posted 3 hours ago Posted 3 hours ago (edited) 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 3 hours ago by AlbertEinstein
dbminter Posted 1 hour ago Posted 1 hour ago 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.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now