[Plugin] MPSync - MediaPortal multi-seat Synchronization (1 Viewer)

[doskabouter]

Hi, doskabouter,
Sound like you have setup you're sync wrong.
The Sync should sync both ways, but I know many experience that it only sync one way... So it all depence how you're setup is?!?!

Regarding you're second point, the Moving Picture sync... do you use Trakt?

I think I watched the movie through the videos plugin, that could be the cause.
And I don't use trakt

 

[barneh]

Hi, doskabouter,
Sound like you have setup you're sync wrong.
The Sync should sync both ways, but I know many experience that it only sync one way... So it all depence how you're setup is?!?!

Regarding you're second point, the Moving Picture sync... do you use Trakt?

I think I watched the movie through the videos plugin, that could be the cause.
And I don't use trakt

Okay... If you have chosen to sync the Video db in the configuration, it should sync that db to...

 

[doskabouter]

Okay... If you have chosen to sync the Video db in the configuration, it should sync that db to...

No, I don't have the video database synced.
I didn't realize the watched status is separately maintained by videos and moving pictures, so I think it's no problem after all

 

[doskabouter]

Here's another question: just found out about the resume function in moving pictures (one of the remaining issues for swapping out videos for moving pictures), it seems that this info is overwritten on the client db even though the "sync watched status" is unchecked. Is this solvable in the next version?

 

[doskabouter]

Anyone?

 

[m3rcury]

Anyone?

@doskabouter, will raise it as an issue in the tracker and look into it.

 

[ixdvc]

For some weeks MPSync does not work on my setup. In the logs I only see

[getDBInfo] waiting for background threads to finish...

Is this because of MePo 1.6 or do I have another problem?

 

[The_Stig]

The issue you are encountering can be due to timing issue. It could be that #2 is updating #1 quicker that #3 updating #1, hence overwriting the change. The plugin should cater for this as before doing any update, it will check the watch status first...

Is this valid for resume flag too? Meaning: should MPSync sync the resume flags too?

 

[m3rcury]

The issue you are encountering can be due to timing issue. It could be that #2 is updating #1 quicker that #3 updating #1, hence overwriting the change. The plugin should cater for this as before doing any update, it will check the watch status first...

Is this valid for resume flag too? Meaning: should MPSync sync the resume flags too?

@The_Stig, yes the plugin is designed to synch the resume position as well if the watch tick box is set.

 

[pmwolf]

Hi all
I just started getting the error tonight on my Master HTPC It is running MePo 1.6

3/11/2014 11:58:08 PM - [INFO] MPSync: DB synchronization complete.
3/11/2014 11:58:10 PM - [DEBUG] MPSync: [checkTriggers] waiting for background threads to finish...
3/11/2014 11:58:20 PM - [DEBUG] MPSync: [checkTriggers] waiting for background threads to finish...
3/11/2014 11:58:30 PM - [DEBUG] MPSync: [checkTriggers] waiting for background threads to finish...
3/11/2014 11:58:40 PM - [DEBUG] MPSync: [checkTriggers] waiting for background threads to finish...
3/11/2014 11:58:50 PM - [DEBUG] MPSync: [checkTriggers] waiting for background threads to finish...

Any Help would be great