Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[skarsol]

Is there a way to force changes to update the Server without having to quit entirely out of the Client?

Telling the Client to Delete and Remove From Disk a file results in (after quitting) the Server deleting the file from the library without removal from disk. Is this intended? (It surprised me).

[cncb]

I'm interested in the answer to this too.  The other problem is that tags are not written to the files themselves when changed via the Client (even after doing a sync).  This is particularly noticeable when editing keywords of images.

[Matt]

Is there a way to force changes to update the Server without having to quit entirely out of the Client?

File > Library > Library Sync...

[zxsix]

I'm interested in the answer to this too.  The other problem is that tags are not written to the files themselves when changed via the Client (even after doing a sync).  This is particularly noticeable when editing keywords of images.

Yes, it's definitely not writing to the files.  Now the file tags and the library are out of sync.
If I were to do an "update library from tags" later on, I'll actually lose data (mostly ratings in my case).

[Matt]

Yes, it's definitely not writing to the files.  Now the file tags and the library are out of sync.
If I were to do an "update library from tags" later on, I'll actually lose data (mostly ratings in my case).

Coming in build 47 and later:
Changed: When syncing changes from a client back to a Library Server, the server will update the tags for any changed files.

[skarsol]

Okay, so to fix the disconnect that's resulted from the current behavior, an Update Tags (from Library) should do it?

[zxsix]

Okay, so to fix the disconnect that's resulted from the current behavior, an Update Tags (from Library) should do it?

I would say so.  I'm rating a bunch from work right now.
I'll pull up my "recently played" playlist at home tonight and do an update tags from library on those and then check the file tags.  No reason that won't work.

Matt, thanks for the quick fix on this.  I've been using LS 6-8 hours a day lately.

[cncb]

Coming in build 47 and later:
Changed: When syncing changes from a client back to a Library Server, the server will update the tags for any changed files.

Thanks.  I hope something can be worked out for file deletion as well.

It would also be nice to have an option to do file manipulation (write, delete) directly from the Client if the file location can be resolved from the Client (mapped drive, network directory, etc.).

[Matt]

Thanks.  I hope something can be worked out for file deletion as well.

Deletion is on our list.

First, we want to add more sophisticated access control rights.  This is important before allowing a client to permanently delete files from disk.

[JimH]

Okay, so to fix the disconnect that's resulted from the current behavior, an Update Tags (from Library) should do it?

Try a few before you do very many.

[skarsol]

Heh, bit late on that. Seems to be going okay though. It doesn't appear to check if the tags have changed though (ie: it's going through all 21k tracks even though I know the vast majority haven't changed). Unfortunatly, I don't remember which ones were modified, so can't just select those. A moot point after the next release I guess.

[zxsix]

Yeah, it's gonna overwrite the tags in the files, whichever ones you selected.  That's what that utility does.
I'm gonna select my last 3000 listened.  That should cover the ones that would have been played over LS since version 15 came out.
Some day when I'm working out of town all week, I'll let it do the whole library.

[cncb]

Deletion is on our list.

First, we want to add more sophisticated access control rights.  This is important before allowing a client to permanently delete files from disk.

Is this coming soon?  File deletion from the Library Server client is the only thing preventing me from doing image/photo management via Library Server.