Print

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

[BaldMan]

All our music currently resides on a NAS and we have 3 copies of MC (mine, my wife's, and household) which access that music. Each PC has it's own library. Ideally I'd like us all to have "basically" the same library so things like tag editing, track linking, etc. only have to be done in that one library. Sort of seems like the Media Server might be the way to go. However, I would rather things like "Last Played", "Play Count", "Ratings", etc. -- things that are a bit more user-specific, be maintained on the local client.

We set up a lot of playlists using smartlists where the music is chosen based on how long it has been since it was last played. However, if I play it on my PC, I don't want the "master" library updated with that same "last played" date because that could prevent it from being included on a playlist on another machine.

Is there a way to do this?

Thanks,
--Mike

[NorthGeorgiaWX]

I have a lot of questions about the client/server relationship and so far no good answers.

[JimH]

If you set authentication in Media Network settings on the server, the clients will be able to sync changes to the server.

You will probably have to try it to be sure it meets your expectations.

[BryanC]

The easiest option is to use a master library with several library clients using Media Server: https://wiki.jriver.com/index.php/Media_Server

Another alternative is here: https://yabb.jriver.com/interact/index.php/topic,121116.0.html

[BaldMan]

The easiest option is to use a master library with several library clients using Media Server: https://wiki.jriver.com/index.php/Media_Server

Another alternative is here: https://yabb.jriver.com/interact/index.php/topic,121116.0.html

The first doesn't work because "The client will send play count and last played information back to the server." This is what I'm trying to avoid.

The second doesn't work because there is no need to sync the files, all clients are already accessing the files from the NAS. Unfortunately the track linking information is not stored in the file (it could be but no guarantee the library index is the same on each client). I would rather the link was the path to the file than its index.

[JimH]

The first doesn't work because "The client will send play count and last played information back to the server." This is what I'm trying to avoid.

Not unless you tell it to.

On this page,
https://wiki.jriver.com/index.php/Media_Server

search for "authentication" and then for "sync".

Also this page:
https://wiki.jriver.com/index.php/Library_Server_Sync

[dtc]

If I understand correctly, the idea is to maintain on the server a common value for tags that are in common across all clients (artist, album, etc.) but to also maintain individual tag values that are specific to a given client  (play count, ratings, etc.) Not sure that is possible, but it seems like a reasonable thing to be want to do.  It is not just a matter of not writing a value back to the server, but maintaining different values for some tags for different clients.

[Moe]

I'm with DTC, I don't think what is being requested is being understood completely by Jim.  I wonder if the user field could somehow be used to do what you want to do or it could be used for a new feature to achieve what you want.

The only solution I could give you would be for ratings.  You could create a new field for each individual in your family "BaldMan Ratings"  "BaldMan's Wife Ratings" etc. 

[BaldMan]

Not unless you tell it to.

On this page,
https://wiki.jriver.com/index.php/Media_Server

search for "authentication" and then for "sync".

Also this page:
https://wiki.jriver.com/index.php/Library_Server_Sync

Yes, but then all "master" changes need to be made on one machine. Tagging, especially genre should be able to be done on client machines and synched back.

[JimH]

You can sync back, depending on your settings.

[BaldMan]

You can sync back, depending on your settings.

What does that mean?

[BryanC]

What does that mean?

You can sync changes that clients make to the library (library field changes, etc) back to the server, which is then propagated to the rest of the clients.

[JimH]

It's explained in the wiki.

[dtc]

You can sync changes that clients make to the library (library field changes, etc) back to the server, which is then propagated to the rest of the clients.

But it is not selective. If authentication and syncing are set, all library field (tag) value changes made on a client are synced back to the library server, including fields like last played and ratings.


Does "propagated to the rest of the clients" mean sent to those client machines when they are connected as clients or does it propagate them out to the local databases on the client machines.  I believe the former, but have never tested it.

EDIT:  The tag value propagates to the client's temporary library when they are connected to the library server. They do not get propagated to the local permanent library on the client. This is as expected, but just wanted to confirm.

[BryanC]

But it is not selective. If authentication and syncing are set, all library field (tag) value changes made on a client are synced back to the library server, including fields like last played and ratings.


Does "propagated to the rest of the clients" mean sent to those client machines when they are connected as clients or does it propagate them out to the local databases on the client machines.  I believe the former, but have never tested it.

EDIT:  The tag value propagates to the client's temporary library when they are connected to the library server. They do not get propagated to the local permanent library on the client. This is as expected, but just wanted to confirm.

You can do this with the client-client model I posted using a third-party synchronization tool like syncthing. All you need to do is to select the library fields that you want to be written to the tags (or more likely, de-select the ones that you don't want to be sent back to the server) in the library field editor.

[dtc]

You can do this with the client-client model I posted using a third-party synchronization tool like syncthing. All you need to do is to select the library fields that you want to be written to the tags (or more likely, de-select the ones that you don't want to be sent back to the server) in the library field editor.

It would be nice to have this type of capability built into MC.