Thank you Manni, it most definitely helps. I appreciate you taking the time to share your perspective.
The good news is that nothing on your list sounds unreasonable. With some time and effort, I think all are doable.
I do have some thoughts to share on a few of your items.
Manni wrote: ↑Tue May 28, 2019 7:08 am
There are bugs in MyMovies with file support, especially with ISO and .mkv. Even when using single files, it's recommended to use folder, otherwise the metadata files aren't generated. Maybe that's part of the issue you experienced.
Even if CMC files are in the same location as MyMovies, a big turn off is the sheer number of files.
With MyMovies, you have 4-5 files, most of them in the BDMV folder, and that's it. CMC seems to be generating many files as there are episodes related files as far as I can see. Maybe it's just me, but it starts to look messy, especially when I don't need them with MyMovies/MCE.
Yes, that is the bug I was thinking of, with online file vs. online folder.
To be fair, when properly configured, MyMovies will generate a lot more than 4-5 files. It will actually create every one of those episode files, but only if you map the file location on the episode in MMCM, and will generate the Series and Season files if you click the export metadata button while selecting a TV Series or Season in CCMC.
This is something we discovered last year, and I had devised manual methods to force MMCM to export most of these files, which contain all the episode metadata that is otherwise not exported.
Not counting artwork, CME creates the exact same number of files that MMCM creates, but the difference is that CME does it easily, while in MMCM you had to jump through hoops to make it happen. CME will also export all the artwork, most of which isn't exported by MMCM at all, so if you factor in artwork, yes CME produces more files, but these all provide for a richer browsing experience.
And no, I'm not missing your point that you don't want any files, so in that respect MMCM is better because it creates less of what you don't want, which is fine for WMC since it doesn't use the files anyway. And I agree that it looks messy (though I thought I did a real nice job on filenaming/organization). But for users who want to see full TV Series info in CMC, these files are a goldmine of data, a luxury.
And many would ask why you are busy looking up the Audi's sooty exhaust pipe when the leather-clad interior is so nice and inviting...
And yes, I anticipate your response that "Teslas don't have exhaust pipes..."
Manni wrote: ↑Tue May 28, 2019 7:08 am
2) TV/Series Episode mapping relying on a background sync with the MM database and generating myriads of unnecessary files. I was expecting the API to access the MyMovies database as and when needed. I understand that the performance issue is not within your control, but having syncs in the background and having to keep all my NASes on isn't an option. It's already a pain to keep MyMovies database clean and up to date with CM, if I have to double this with another utility, it becomes worse. I also don't like having background processes than run scans at times I can't control, because it increases the chances of getting dropped frames and other performances issues, even on a powerful PC. A fast sync when I launch CMC is acceptable if it doesn't take too long, but ideally I'd want a fast, on-demand API access to the existing MM database, or failing this to a centralized CMC database.
Wow, you bundled a lot into that one
let me try to cover it all. The files are only unnecessary with WMC. All other external browsers that can leverage your My Movies collection require files, JRiver too. The extra Series and Episode metadata files allow CMC to provide a superior TV Series browsing solution, far better than any other GUI frontend. Yes, I understand the expectation that if CMC used the API, it would be 'just like WMC' and there wouldn't be files at all, but the aforementioned API performance issues derail that possibility. You can thank Microsoft and Binnerup for the way things are going...
Regarding doubling the maintenance effort, I think this is misguided. You still maintain your collection with CCMC. Once you set up CME, it should run automatically in the background, and you shouldn't have to do anything with it. There's no maintenance there, and all those settings are so you can tweak it to your preferences - set them once then forget it. Regarding having background processes that run at times that you can't control... I provide control right in the settings so you can set when this runs. If you would like additional ways to control the schedule - just ask.
Besides, the main scans you are talking about are scans that are against the My Movies API/DB, not your directories. For example, lets say you wake up all your servers, run a full export, then put your archive servers back to sleep, and set CME to run in a Changes Only since the last run. CME will ping the My Movies API on the frequency that you define (i.e. every minute, once a day, etc...) to see if there were any changes to your collection. If there were none, it goes back to sleep until the next set interval. If there was a change, it will export only that change, and requires only the server holding that title to be awake. And once I add in the ability to restrict the API export to only selected shares (should be today), then you can prevent it from trying to write to shares/servers that you like to sleep.
Regarding dropped frames from background syncs at times you can't control, I think you are theorizing a bit too much, and you need more hands on experience with the solution before having these types of concerns. When you start CMC, you don't even have to do a sync. If you do a sync, you can choose either a "SmartSync" or a "Full Sync". On my machine, a Full Sync takes only about 70 seconds for my 1300+ titles. The SmartSync (changes only) takes about 10 seconds. That's it. Even if you have CME running on your My Movies PC, scanning for changes every 1 minute (the fastest possible), that creates zero network traffic unless a change is detected.
Obviously your sleeping servers is a scenario that isn't currently handled correct by CMC, but I will fix that.
A centralized CMC database would actually result in a worse browsing experience, as you would be adding network latency into the equation. CMC is very fast, especially when run from a fast SSD and with Artwork Caching enabled. I've worked extremely hard to make CMC extremely fast, even the Sync. It seems like you are looking for flaws based upon a spec-sheet, and trying to re-engineer CMC based upon your personal ideals, without having fully experienced CMC in day to day operation for an extended period of time.
Sorry if it seems like I am coming off defensive or dismissive - I don't intend to be either of those, but I feel that some of your statements and concerns don't ring true to anyone that's used CMC for more than a few days. I really don't know how you've reached some of your conclusions, but I do challenge you to spend more time with CMC, and see if some of the perceived pain-points don't dissolve into the background.
Manni wrote: ↑Tue May 28, 2019 7:08 am
3) Showing TV Series separately from Movies. AFAIK CMC only makes a difference between Movies and Music in the browser.
I personally don't like how the WMC solution makes you completely change modes just to see TV series. How archaic. Perhaps you have missed the Media Type Filter on the top IconBar, the TV Series only view you are looking for is only a click away. You can also control in the Settings the default Media Type Filter applied upon CMC startup, so if you want to only show Movies or only show TV Series when you start CMC, that is possible.
- Media Type Filter.jpg (135.01 KiB) Viewed 37581 times
Manni wrote: ↑Tue May 28, 2019 7:08 am
1) A title is shown as "watched" even if it has only been played for a few seconds.
This can happen if the Runtime for the title is missing or incorrect. By default, CMC requires you to have watched (technically, been away from CMC in the external player, presumably watching...) 85% of the Movie or Episode's runtime. But if that runtime is wrong in MMCM (i.e. 0), then yes CMC will mark the title as watched after only a few seconds.
If you find an instance of CMC marking a title watched after only a few seconds, and the title's runtime is correct (i.e. 19+ minutes for an episode or 80-180 minutes for a movie), then please let me know, that would be a bug.
Manni wrote: ↑Tue May 28, 2019 7:08 am
2) The browser menu doesn't cycle (if you want to go from far left to far right, you have to press "right" many times, vs a single left)
Which one is the browser menu? Is that the top IconBar with the Settings gear icon on the left and the Exit X on the right? If so, personally I like that it doesn't wrap. For example, I can just hold down the Right button and get to Exit without much trouble. But I suppose I could make this an option if that's what you want.
Manni wrote: ↑Tue May 28, 2019 7:08 am
3) Minor exception errors (for example when pressing "ESC" from the main menu, which is the usual substitute for "EXIT").
Okay, you lost me a bit on this one. By "exception errors", do you mean inconveniences? Or are you actually getting an "Exception!" error message? What is the main menu, is it the top IconBar? Are you suggesting that you want the ability to press "Back" while on the IconBar and have it jump to the Exit icon? Or is there a different behavior you would like.
Please be specific - almost anything's possible in code, but I require my users to tell me what they want so I can get it right for them. My mind goes a thousand miles an hour, and can turn your simple statement into twenty different possibilities - it's a weakness of mine that I don't always understand what people are communicating, so I need your help.
Manni wrote: ↑Tue May 28, 2019 7:08 am
4) Lack of mouse support.
Yes, I hear you, and this is coming. When I first wrote MM Browser, I only intended for it to be used with a remote control, as that is how I would use it. My users have made clear my shortsightedness, and I'm working on fixing it. v2.2 addresses most of this, though I've yet to implement touch support for the covers themselves. That will be coming in a future version, but I didn't want to further hold up v2.2 which already has a ton of improvements including touch support for about 90% of the GUI, as adding touch to the covers themselves is going to be a big programming challenge.
Again, thank you for sharing your thoughts. I appreciate the constructive criticism and guidance, and hope you don't take any offense at any of my responses - I'm a matter of fact type of guy and that sometimes (often?) comes off as brash. I try to do better these days, but I often fail with my social skills.
Paul