JJZolx;470093 Wrote:
> There may also a little bit for removing stale tracks (files referenced
> in the database but no longer found on disk), although traditionally the
> scanner has been very poor at removing stale data, so I'm not sure this
> is even done.
I added some albums and removed other
You can't tell what's new without looking up in the database every track
that you find on disk. If a track is already in the db, but hasn't
changed, then it's skipped. If it's not in the database, then it's read
and added.
The only added overhead of looking for 'changed' files is the
comparison
It has to scan all files in the music library path to see if there are new
files, which also processes changed files.
If you want to add new music to the library, one potentially faster option may
be to use Browse Music Folder and drill down to the folder that holds the new
music and play it th
Simply if I only add one new CD it's doing a lot of "other" stuff that
does not seems related to that new CD ? Could be a complete
missunderstanding by me .
When adding new stuff by browsing it, it takes less than a second to
add a new album with the new and changed scan it takes minutes.
For ex
Mnyb;470051 Wrote:
> I only been to this forum since 2006 so I have to ask.
>
> Why is new and changed scan piggybacked on each other ?
>
> I want a new scan and one changed scan ? ( I know that there is work in
> the 8.0 release with sqlite to get new stuff automatically ).
>
> I often use th
I only been to this forum since 2006 so I have to ask.
Why is new and changed scan piggybacked on each other ?
I want a new scan and one changed scan ? ( I know that there is work in
the 8.0 release with sqlite to get new stuff automatically ).
I often use the bmf workaround.
I seems like 98%
