Refresh Smaller Groups than the Whole Library

Logged In: NO 

Why don't you use auto-refresh (set a refresh quick delay 
in the device configuration) ? this way your collection 
will be always up-to-date without having to deal with 
manual refreshing... Where is located your collection ? on 
an harddisk /external disk or on a file server ?

Logged In: YES 
user_id=1003260

My collection is on both. On the server computer, I use 
Jajuk, so the collection is local there, but I also use it 
on the client computers, so the collection is not local. 
(Although it is 100Mbps). Anyway, what is the difference 
between a fast refresh and a "Deep" refresh?? Many times I 
am changing the tags & even the filenames, so I figured I 
needed the deep refresh which takes a long time if I do it 
to the whole library. If a fast refresh will do, then I 
have no problem with setting up an auto-refresh. But if a 
deep refresh is needed, then the ability to just refresh a 
few folders or a single folder would be great.

Louie

Logged In: YES 
user_id=363565

A fast refresh will detect all new (or removed) files but is
not aware of tag changes on an existing file (id3 tags are
not read again). Deep scan force tags. Auto-refresh performs
fast refresh so if you want to be aware of tags changed
outside jajuk, you will have to perform a deep refresh
manually but jajuk should be smart enough to change tags by
itself so you will not have to do it...

If you change tags with jajuk, i advice you to use the
auto-refresh feature (with a delay of saying 30 min) so your
collection will be always up-to-date automatically (with a
delay of 30 mins). Do not use a delay too short if your
collection is really big because it could use a significant
bandwith.

Please have a try and tell us as we are interrested into
user feedback.

(trac cleaning, please close the ticket, if it has been fixed)