I have the following directory structure on a network drive:
X:\a <- almost empty (1 dummy file to make sure the empty directory is not problem)
X:\a\b <- <2,1 GB (slightly larger than 2 GB) in 6 files
X:\a\c <- 0,98 GB in 9 files
Whenever I select any of the directories "b" and "c" for burning I get the proper view of the files but if I select directory "a" (or the drive root X) after clicking on "Start", the console writes:
Scanning Folders
Empty/too big: b
Empty/too big: c
I tested one of the larger partitions on my local disc and the same error pops up on some directories, one of them with 1,54 GB data in 272 files.
I don't see anything I could have missed so I guess this is a bug?
Thanks for the work on this software so far,
Philipp
Logged In: NO
Is Splitting Depth set above zero?
Logged In: YES
user_id=554139
I do feel dumb now.
In fact, Splitting Depth was set to zero and that caused my
problem. Re-reading the help about folder splitting again
(and again) gave me the clue.
Setting it to zero effectively forbids splitting up root
folders.
Maybe it would be a good idea to give a hint when the "too
big" part of the "empty/too big" message is printed.