Print

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

[alexgit]

When auto import is used restarting library server is kind of counterintuitive.
Scenario:
1. MC is down
2. Add files to auto import folder
3. Start MC - library server starts automatically
4. Look in the local library - new files are added
5. Connect to MC remotely - files are missing unless library server is restarted.

Best
Alex

[Robert Taylor]

I think the library server has always been this way (I'm not saying this is a good thing!!).

ie. When a remote client connects to the library server it downloads the library "as at now", and any subsequent changes to the library on the server are unknown to the client(s). Also, any changes made at the client end are lost to the server (ie. they are never propagated to the server). The exception here is play stats.

This is one thing certain of us have been craving for a long time, that is the ability to have a dynamic fully two-way conversation between library client-server. ie. the ability to tag on the client, and have changes applied to server database.

I was hoping this might appear in MC12...I live in eternal optimistic hope...

8-)

[alexgit]

ie. When a remote client connects to the library server it downloads the library "as at now"

Actually I am connecting remote client after I already can see change on local machine. That's why I think it's counterintuitive

Best
Alex

[Robert Taylor]

Yes I see what you mean.

That is odd, it's like the library server duplicates the library for serving, and then doesn't notice subsequent changes...

[lalittle]

Are you saying that when you make changes to the library on the server, reloading the library on the client will not see these changes until you restart Media Server on the server?

Thanks,

Larry