by JSC632 » Thu May 15, 2014 1:31 am
I am having a very similar problem yet not exactly the same. I used BRU on Win 7 without any issues. On Win 8.1, I do not have any trouble launching BRU but when I try to navigate to a file location it can be slow or take forever depending on how I choose to get there.
If I manually expand the file tree to drill down to the subfolder I want, BRU can be a little stilted when it opens each folder. There are 3-5 second pauses on each folder. It is not smooth and fast, but I can get there and do what I need to do, just a little slower. However, the bugaboo is when I select from the menu Actions -> Jump to Path. Once I type in the path I want and hit Enter, it can take 20-40 minutes for BRU to get to that folder. It doesn't seem like BRU is doing anything at first, but after about 7-8 minutes it visibly shows the expansion of the file tree, folder by folder -- no stone left unturned. It appears BRU is opening every folder to index the drive. In fact, it's not just opening every folder in the file tree of my 1TB internal hard drive, it's also opening every folder on the file tree on my 3TB NAS. If this only occurred once, I could understand, but BRU does this every time it opens and I attempt to jump to a file path. Worse, if I leave BRU up and running, after about 20-30 minutes BRU forgets the indexing it performed previously and wants to re-index the whole thing all over again.
I do not have on the network an Xbox, Playstation, Sonos or any other kind of music file system. I do have music files on the NAS but my collection is small, perhaps 20GB. I only have about 1TB in files on the 3TB drive, mostly photos and videos, so if that thing were nearly full I'm sure BRU would likely take over an hour to do index everything. Having BRU index the drive where I am attempting to jump to a particular folder is okay, I guess, but why it needs to index an entirely different drive (the NAS) makes no sense.
This behavior is strange under Win 8.1 when it never did this under Win 7. Does anyone have a solution to this indexing/expanding-file-tree issue?