Has Plex Client Development stalled?
Posted: 10 Mar 2017, 13:23
When you added on the mrmc-plex client about a year ago I thought it was a stoke of genius. Drop MySQL servers for a much more user-friendly plex server back-end to share data between clients. For me the original-plex client was let down by insisting on transcoding when completely unnecessary (with no way to turn it off) which meant some media didn't play at all as I use a low powered server.
However nothing much seems to have happened recently on the plex client front. I understand you are a very small dev team, so I don't understand why minimal resources are diverted into v3:-
DVD support (does anyone still use DVD's? I stopped over a decade ago, 1080p and 4k have superseded their low res)
Adding transcoding support to mrmc plex client => may as well just use the original plex client, mrmc-plex differentiating feature was that as a thick client it didn't need transcoding.
shield platform = another hardware platform is great but do that many people really have these expensive machines and would it not be better to complete one feature i.e. Plex before embarking on new ones?
v17 database compatability = if running plex client instead of MySQL which seemed the new direction of travel why would you need this? Has MrMc fork now drifted so much as to not be able to very easily inherit such changes from Kodi trunk?
Now I understand everyone has different needs, requests and it is up to the dev's to decide the direction hence why they broke away from team kodi in the first place, but I noticed on other threads that you say you are unlikely to support the new Estuary default theme from Kodi (confluence is hideous) + other stuff, so if it is indeed a total break from Kodi and Plex client is not a priority when much is still missing from MrMc-Plex (see below) I get a bit lost on what the direction of travel is.
Photos
Collections
Filters
PlayLists (Both Plex ones and MrMC pointing at plex items ones)
AddOn Alternatives (not pirate stuff, but weather etc)
Continue watching, Ondeck, Resume etc
Plex Channels
Does MrMC cache thumbs other stuff from Plex. Can it operate directly (read-only) on Plex DB's for speed?
etc...
With the addition of the Plex client I thought I had seen the future, but the future seems to have stalled. A year has passed with minimal changes over the original basic functions. Latest Kodi is a doddle to install on FireTV using the Downloader app, + seems very stable with def estuary skin, if only it had your Plex Client. I wonder if the MrMc fork would have progressed faster if it had just conditionally not compiled the add-on and other unwanted kodi stuff and so kept more closely aligned to the main Kodi source trunk.
It's hard to write this sort of critical post without coming over as rude but rest assured that is 100% not my intention. I am just a bit lost on where MrMc is heading re priorities, differentiation from alternatives etc. I'm seeing Kodi (long avoided by me due to instability) moving ahead now at pace with its new skins, add-on auto installers etc.
However nothing much seems to have happened recently on the plex client front. I understand you are a very small dev team, so I don't understand why minimal resources are diverted into v3:-
DVD support (does anyone still use DVD's? I stopped over a decade ago, 1080p and 4k have superseded their low res)
Adding transcoding support to mrmc plex client => may as well just use the original plex client, mrmc-plex differentiating feature was that as a thick client it didn't need transcoding.
shield platform = another hardware platform is great but do that many people really have these expensive machines and would it not be better to complete one feature i.e. Plex before embarking on new ones?
v17 database compatability = if running plex client instead of MySQL which seemed the new direction of travel why would you need this? Has MrMc fork now drifted so much as to not be able to very easily inherit such changes from Kodi trunk?
Now I understand everyone has different needs, requests and it is up to the dev's to decide the direction hence why they broke away from team kodi in the first place, but I noticed on other threads that you say you are unlikely to support the new Estuary default theme from Kodi (confluence is hideous) + other stuff, so if it is indeed a total break from Kodi and Plex client is not a priority when much is still missing from MrMc-Plex (see below) I get a bit lost on what the direction of travel is.
Photos
Collections
Filters
PlayLists (Both Plex ones and MrMC pointing at plex items ones)
AddOn Alternatives (not pirate stuff, but weather etc)
Continue watching, Ondeck, Resume etc
Plex Channels
Does MrMC cache thumbs other stuff from Plex. Can it operate directly (read-only) on Plex DB's for speed?
etc...
With the addition of the Plex client I thought I had seen the future, but the future seems to have stalled. A year has passed with minimal changes over the original basic functions. Latest Kodi is a doddle to install on FireTV using the Downloader app, + seems very stable with def estuary skin, if only it had your Plex Client. I wonder if the MrMc fork would have progressed faster if it had just conditionally not compiled the add-on and other unwanted kodi stuff and so kept more closely aligned to the main Kodi source trunk.
It's hard to write this sort of critical post without coming over as rude but rest assured that is 100% not my intention. I am just a bit lost on where MrMc is heading re priorities, differentiation from alternatives etc. I'm seeing Kodi (long avoided by me due to instability) moving ahead now at pace with its new skins, add-on auto installers etc.