Database: Refactor MP1 database for multi seat usage (2 Viewers)

[CyberSimian]

I was going to ask why you haven't moved MP to 64 bit yet. Does it contain components that still need to be 32 bit? Do you have users that are still on 32 bit machines,

My HTPC runs 64-bit Windows 7. But MP1 (and my file manager) are both 32-bit. Windows 64-bit seems to run 32-bit applications without problem.

By the way, I believe that the oldest Windows OS supported by MP is Windows Vista (MP no longer claims to work on Windows XP, although it may do so, with restrictions). I was re-arranging my boot partitions yesterday, and I noticed that I still have a 32-bit Vista partition (contains MP 1.12).

-- from CyberSimian in the UK

 

[doskabouter]

Yes, I think that is correct. The problem may arise with the teeny-tiny number of installers that are BAT files...

-- from CyberSimian in the UK

Bat files are not an issue too because whatever means you use (except running it from a command prompt) to start a batchfile will start cmd.exe /c<batchfile> and my guess would be that it picks the 64bit version on 64bit osses

Edit: I think were digressing a bit though...

 

[Anthony Vaughan]

I've made sure that the refactored version handles stacked files and I think I have a good understanding of the issues involved.

I now need to test my changes because I took the opportunity to slim down the code where possible. As you can imagine, with all of the multi-threading, there is a significant amount of repetitive processing that I have been trying to reduce where possible. I'm going to install this version on my production system tomorrow morning and will give it a few days in case of bugs before posting the changes in this thread.

 

[Anthony Vaughan]

By the way, I believe that the oldest Windows OS supported by MP is Windows Vista (MP no longer claims to work on Windows XP, although it may do so, with restrictions). I was re-arranging my boot partitions yesterday, and I noticed that I still have a 32-bit Vista partition (contains MP 1.12).

We'll have to drag you kicking and screaming to Windows 10 (you mention Windows 7). While I was great fan of Windows 7, Windows 10 has proven to be pretty reliable and, with Windows 11 on the horizon, I guess there will only be so long before everyone else will have to move forward.

As a developer I have had to be up-to-date to be current with latest techniques .

 

[doskabouter]

I've made sure that the refactored version handles stacked files and I think I have a good understanding of the issues involved.

I now need to test my changes because I took the opportunity to slim down the code where possible. As you can imagine, with all of the multi-threading, there is a significant amount of repetitive processing that I have been trying to reduce where possible. I'm going to install this version on my production system tomorrow morning and will give it a few days in case of bugs before posting the changes in this thread.

Can we have a preview of the code changes (hint: commits on your github)? Quite curious on how deep of an impact this has been

 

[Anthony Vaughan]

Sure. Once I'm certain this change is solid. I have pretty well completely re-written the back-end, keeping some SQLite.NET code for dynamic SQL and PRAGMAs. I am confidant about the changes, but there are some features of MP that I don't use, like stacking, and I think it is vital that those of you that usually test MP should make sure that I haven't missed anything important.

I have given stacking a real going over and I think it is doing everything it should,. But it would be great if someone could give it a green light.

AJS has mentioned using data view rather than share view and I don't think I have a handle on what that is all about. So that needs checking. I have also written upgrades for the music (trivial changes) and video (major) databases that have to tested to make sure that all of the features are passed over to the new database. For example, I have never used bookmarks, so it would be good to make sure that bookmarks still work as expected.

I think it may be ambitious to try to put this in the next release, but I trust you will be able to judge that better than I can. All I can say is that it is working really well for me.

Tony

P.S. We've also got the extensions to consider - though I've got Fanart Handler working as a starter.

 

[Anthony Vaughan]

Can we have a preview of the code changes (hint: commits on your github)? Quite curious on how deep of an impact this has been

Okay. So I thought it would be helpful to post the code I have changed into the first posting on this thread. The zip file is only 3MB. It contains the changed .csproj files as well as some packages files. I can post the full release on GitHub later when you are ready for it and I have given this a good testing .

 

[Anthony Vaughan]

I would like to now take a look at scanning, from the configuration application, for all of the databases, as I think it will be possible to speed things up a bit.
I will address any other issues raised as well, but I want to get the scanning sorted out sooner rather than later because it takes up so much time when adding new media to MP.

Does that meet general approval?

 

[Anthony Vaughan]

Looking at scanning movies, I have noticed that after scanning movies in and then going back into configuration and doing a scan with the following settings:

a) Refresh existing files only;
b) Fetch actors data.

the configuration application closes down.

I thought I had a bug in my code, but the main product does the same thing.

Is that intentional?

 

[ajs]

Is that intentional?

Never noticed this, used quite often, the last time was the day before yesterday on the test 1.29.