Reply to thread

Message

Hi ajs

I've got the single, multi-user, centrally configured database working for the Folder, Music, Picture and Video databases and I am using this system as my production system. I have also upgraded it to 1.29 in line with the latest version. I am working on streamlining the code to remove duplication of processing and the performance is really good

I downloaded the Fanart Handler extension and recompiled it with the new format. The GitHub didn't have the xmp2 file so I'm not sure what happens about promoting extensions. FanartHandler is different because it is included in the main file structure:

"C:\Program Files (x86)\Team MediaPortal\MediaPortal\plugins\process\FanartHandler.dll"

The other extensions don't seem to have the same close relationship with MP.

Can you give me a list of the extensions that use the client databases so I can go through them to align them with the new version?

I suppose what I really need to know is whether you are wanting to use what I have done. I have fixed a few issues including one or two of the cs scripts and the scan methodology and my version keeps the database current with disk changes; i.e. when a movie is deleted from disk using MP, the database is purged of all data associated with that movie. At the moment I install my version over the standard version by copying a list of files to the production system. The database is automatically changed to the new version but without trying to convert its data. I felt that this is such a major upgrade that users would be better off recreating their movie info data using the new version of configuration (which runs much faster than before). I've added some try/catches to a few scripts to make them more reliable. I can provide documentation of the new approach, in detail, if you want it (I need to finish it off but am happy to let you have it when it's ready).

Maybe you would want to have this as a third option. I recommend that you use this version because it means you will no longer need to sync databases - although you still could if you wanted to. It also offers several improvements in performance though I am still testing the procduct.

I'm happy to go along with whatever you decide.

Tony

<blockquote data-quote="Anthony Vaughan" data-source="post: 1286512" data-attributes="member: 153283">Hi ajsI've got the single, multi-user, centrally configured database working for the Folder, Music, Picture and Video databases and I am using this system as my production system. I have also upgraded it to 1.29 in line with the latest version. I am working on streamlining the code to remove duplication of processing and the performance is really goodI downloaded the Fanart Handler extension and recompiled it with the new format. The GitHub didn't have the xmp2 file so I'm not sure what happens about promoting extensions. FanartHandler is different because it is included in the main file structure:&quot;C:\Program Files (x86)\Team MediaPortal\MediaPortal\plugins\process\FanartHandler.dll&quot;The other extensions don't seem to have the same close relationship with MP.Can you give me a list of the extensions that use the client databases so I can go through them to align them with the new version?I suppose what I really need to know is whether you are wanting to use what I have done. I have fixed a few issues including one or two of the cs scripts and the scan methodology and my version keeps the database current with disk changes; i.e. when a movie is deleted from disk using MP, the database is purged of all data associated with that movie. At the moment I install my version over the standard version by copying a list of files to the production system. The database is automatically changed to the new version but without trying to convert its data. I felt that this is such a major upgrade that users would be better off recreating their movie info data using the new version of configuration (which runs much faster than before). I've added some try/catches to a few scripts to make them more reliable. I can provide documentation of the new approach, in detail, if you want it (I need to finish it off but am happy to let you have it when it's ready).Maybe you would want to have this as a third option. I recommend that you use this version because it means you will no longer need to sync databases - although you still could if you wanted to. It also offers several improvements in performance though I am still testing the procduct.I'm happy to go along with whatever you decide.Tony</blockquote>

[QUOTE="Anthony Vaughan, post: 1286512, member: 153283"] Hi ajs I've got the single, multi-user, centrally configured database working for the Folder, Music, Picture and Video databases and I am using this system as my production system. I have also upgraded it to 1.29 in line with the latest version. I am working on streamlining the code to remove duplication of processing and the performance is really good I downloaded the Fanart Handler extension and recompiled it with the new format. The GitHub didn't have the xmp2 file so I'm not sure what happens about promoting extensions. FanartHandler is different because it is included in the main file structure: "C:\Program Files (x86)\Team MediaPortal\MediaPortal\plugins\process\FanartHandler.dll" The other extensions don't seem to have the same close relationship with MP. Can you give me a list of the extensions that use the client databases so I can go through them to align them with the new version? I suppose what I really need to know is whether you are wanting to use what I have done. I have fixed a few issues including one or two of the cs scripts and the scan methodology and my version keeps the database current with disk changes; i.e. when a movie is deleted from disk using MP, the database is purged of all data associated with that movie. At the moment I install my version over the standard version by copying a list of files to the production system. The database is automatically changed to the new version but without trying to convert its data. I felt that this is such a major upgrade that users would be better off recreating their movie info data using the new version of configuration (which runs much faster than before). I've added some try/catches to a few scripts to make them more reliable. I can provide documentation of the new approach, in detail, if you want it (I need to finish it off but am happy to let you have it when it's ready). Maybe you would want to have this as a third option. I recommend that you use this version because it means you will no longer need to sync databases - although you still could if you wanted to. It also offers several improvements in performance though I am still testing the procduct. I'm happy to go along with whatever you decide. Tony [/QUOTE]