Manual rescan takes forever

[dbedgood]

Hi,

I have an issue with the scanning of local media on the Boxee Box. When you select to rescan it doesn't scan straight away, in fact it doesn't seem to refresh the new media until the next day. Someone else has created a ticket for this issue, so if you are experiencing the same problem then please vote for this so it moves up the list.

http://jira.boxee.tv/browse/BOXEE-7847

Thanks

[tonester99]

i agree with you. currently, it is painstakingly hard to get the BB to recognize new media added to my NAS as well. It should not be that hard everytime new media files are added.

[Kelmk]

Yes it is very slow and there is little feedback as to what it is actually doing.

[MikeyN]

There seriously needs to be a progress bar somewhere that informs the user what exactly it's doing and it's overall percentage.

[SecretAsianMan]

Or at least scope the scan to specific spots. That would be a massive optimization.

If I'm staring at Seinfeld Season 3 and hit rescan, I am probably asking Boxee to check for more episodes of Seinfeld Season 3. But no, it scans my entire NAS across all drives and all media types. Eventually I give up and go to the file browser.

[Ph8]

Ive personally never had an issue with geting new content scanned via the USB connected HDD. If I only add a few files, then I just go to them individually and manually identify them. Ive also forgotten to do this and usually by the next day it has been added for me. If you are watching a movie\stream however I believe the scanning will be skipped, so this may be an issue also for some.

[joflow]

It would be nice if there was some sort of API for updating the library..that way when new content is acquired, Boxee can be notified so that it can add the new file without doing a full directory scan. Doesn't XBMC have this?

[SecretAsianMan]

Better yet, vote for this one: http://jira.boxee.tv/browse/BOXEE-7298

I don't get it -- it's not rocket science. But they decided they won't fix it, insisting it slows the Boxee Box down. Despite the fact that subscribing to changes from the filesystem takes ZERO CPU cycles.