Synchronizing multiple clients - feature request (2 Viewers)

[Lehmden]

AW: Synchronizing multiple clients - feature request

Hi.
The folder image has to be named like "folder.jpg" or something else that is listed in:
"Search movie folders for cover art named:"

"Moviename.jpg" or "movie_cover.jpg" did not work if you use the same values as on screenshots.
I'm organizing all movies the same way. A subfolder with movie name including the movie file itself, an .nfo with all db content a backdrop.jpg and folder.jpg as artwork. See new screenshot attached. This works perfect since ever.

 

[VdR]

Yes. That is the way I have it now that I realize that the .nfo files has to have the same name as the movie (rather than movie.nfo). Now it works fine.

I thought the folder.jpg import didn't work because the preview in the configuration did not change for some reason. That is why I experimented with other name for the coverart.

One question though. If I update f.i. a folder.jpg file in the movie directory, will the (slave) client automatically load this upload, or only when I re-import?


VdR

 

[Lehmden]

AW: Synchronizing multiple clients - feature request

Hi.
The Artwork will only be updated on reimport.
The previev of Covers is done by auto generated thumbs of available cover images. It's stored in an extra folder inside MPs Thumbs dir.. If you delete obsolete files or the whole folder before!!! importing someting, all covers has recent previews.

 

[p750mmx]

I work for some time now with a central database for all my MP clients. I only have to replace (or adjust) one xml file when MP is installed or updated. Thats a piece of cake.
Cant you use what's written here? Central Database - MediaPortal Wiki

 

[Lehmden]

AW: Synchronizing multiple clients - feature request

Hi.
Central Database can work without issues as long as you only use one client at a time and as long as you have the file path identical on all systems. If a Network share is mounted as e.G. Z: on one system and as Y: on another, central DB did not work. SQLite DB is not able to have multiple Write actions at once. If this happens (e.G. on two clients is a movie set to watched at same time) the DB crashes and is no longer usable. High risk with low advantage... not a really wise solution.

With upcoming MP2 all this is stored in a MySQL DB witch can have as much Users at once as you like. And the DB can store "per client data" like different file path, different watched flags,... But MP2 is not jet available. I think the first Alpha will be out in some month. Until then I think we better use SQLite carefully.

And with the .nfo method you always have a full "backup" of your DB as an extra...

 

[p750mmx]

Re: AW: Synchronizing multiple clients - feature request

Off-course all clients are setup the same (its just one file that holds the MediaPortal directory structure) and use only media storage outside the clients (only NAS storage is used for media), so no media sharing from a client is active. Even when using 2 clients on the same time there are no issues. The NAS devices we use can handle 2 or more data streams on the same time without any problem. We don't use the TV client, there is no recording of any data, only playing, so no writing is done while using MediaPortal.

Edit: I just fired up two clients (both are AMD E-350 systems) and startup the same full-HD stream stored on NAS. They are playing flawless as we speak. So maybe on a differend setup it can go wrong but that is not the case in our house (with five MP clients).

I think one central storage place, outside the clients, for all media, database, thumbs, backdrops, fan-art, etc. has a major advantage

 

[Lehmden]

AW: Synchronizing multiple clients - feature request

Hi.
If you watch a movie inside MP (MyVideos, TVSeries, MyFilms, DVD or Moving Pictures,... no matter) there are permanently data written to Database (played until,... watched,...) If two of this database actions are at the same time, the SQLite DB gets corrupt. This is a matter of SQLite and has nothing to do with MP at all. SQLite databases are "single user only" systems. That's why no central DB system is "officially" available in MP1. The dirty hack you use is at your own risk. Works for some user, but did not work for a lot of user also. If two (or more) MP clients grants write access to the same db file at the same time,.... crash, boom, bang. This could never happen if you use local databases.

You can use a thousand media streams at the same time if your network is capable of, this did not change anything about the SQLIte Database issue. And no matter too if the media is stored on a pc running a MP client or not..

 

[RoChess]

To be perfectly clear, concurrency (multiple users doing stuff at the same time) is perfectly possible with SQLite.

The reasons it doesn't work well is because it is done via file locking and that doesn't work well via Windows, especially when done via network. If however the software is written with a lot of safeguards in place (detecting if a concurrent action is taking place, etc), it is possible and lot of SQLite based projects actually make it work just fine.

But it requires rewrites in MediaPortal and most plugins, and with the work on MediaPortal 2 being done that is for the most part futile right now to even consider.

 

[p750mmx]

Re: AW: Synchronizing multiple clients - feature request

Hi Claus,
I don't mean to be stubborn or anything like that and I don't want to talk other users into something that will give them trouble. I only want to share that it works as I have written sins 1.2 Alpha. Maybe I've bin lucky until now or there never was a write action to the database at exactly the same time by 2 clients. However, there is auto=backup every night of the central storage, so I should be fine if it comes to a......, wait for it......, crash, boom, bang

With greets..

 

[VdR]

Re: AW: Synchronizing multiple clients - feature request

Hi.
The Artwork will only be updated on reimport. ...

That means this is not really working as a slave as I described. For new movies added it is ok, but for changes made in the master I still have to go to every client and re-import the data for the changes.

Is it really a big development to make a client check for updates of the movie.nfo, folder.jpg and background.jpg files every time MP starts and update the local database accordingly?

VdR