it’s still in progress, promise. and yeah, i also wish it was done already…
8 Likes
@elan
It would be nice if you could also give an intermediate status for other inquiries. For me, the miserable problem with the 4K content is just as troublesome. I don’t understand why this can’t be limited per category with the non-transcoding of the video.
The forceAutoAdjustQuality flag is working great… when WAN users (and WAN users only) go through the web app. I do see in the logs that Plex automatically adjust the quality based on the available bandwidth and concurrent nbr of streams. This is exactly what I wanted to achieved for months!
But if using any fat client, I do not see any logs about automatic quality kicking in. In such case, the flag simply allow the client to go beyond the basic 2mbps - 720p setting, but leave it there.
Also, the Quality setting seems to be missing from Mac and Windows fat client, so the user cannot change the quality from these apps.
I’m just hoping for an upcoming beta version that will introduce such feature for every clients out there.
Side note:
For those who would like to test it without having to connect from WAN, don’t forget that you can specify your specific server IP address in the Settings > Network > LAN Network instead of any network/sub-mask so that any connections even from within your LAN is considered WAN and the forceAutoAdjustQuality flag will then be taken into account.
Any ETA yet? Getting less technical users to constantly update their settings is an absolute nightmare…
EDIT: Each user on average has 4 devices, NOT including mobile. 10-15 users * 4 devices = 40-60 devices not including mobile phones…
It’s great that Elan is a consumer too, but this should have been resolved ages ago.
Stop the Plex Arcade and other stuff until the Plex core can be fixed up.
I think it should default remote quality in client apps to max until the solution is here.
3 Likes
At least on non mobile devices.
5 Likes
So now the staff is salty about ppl being mad at their inability to fix KNOWN and long ongoing problems…and they’re deleting posts…? Maybe y’all should GTFO the forums and go fix PLEX…just a suggestion.
1 Like
Go ahead and delete this too lmao
I am not surprised at all.
Mods do not delete critical posts because they are critical.
Half of my posts are very critical.
2 Likes
That may usually be the case, but the comment that was deleted was criticizing the inability to implement a short term fix until the long term solution is ready for release.
It more or less looked like somebody took offense to very valid criticism. Sure, maybe he was a little blunt but at this point it’s hard to blame him lol.
1 Like
Judging from his last post I get the distinct feeling that it was because of the tone not because of the criticism.
3 Likes
Maybe a bit of a tangent - but has anyone used a competitor platform that solved this issue sufficiently?
I’m still looking for a plex fix, but am curious if others have firsthand experience with how folks like Emby and Jellyfin solve this issue.
It might give insight into the issues Plex is facing, or at least provide info on an option folks can use to vote with their feet/money.
1 Like
Jellyfin is looking really good, but client parity isn’t there yet. Some clients are very barebones and others are unofficial and maintained by other people.
Once all of the clients for the different platforms catch up, switching will be a no brainer.
Until then I’m personally running both side by side for the next time the plex api goes down…
3 Likes
Interesting. Thank you. I’m a watcher on the Jellyfin git repo to see their progress, but haven’t tried it yet. I think it’s almost there though.
I dug into the Emby forums a bit, but couldn’t really tell how they handle it. I did see lots of people complaining about issues with their auto quality settings. Apparently they default to max quality (I think?), but then have issues with downregulating. It defaults to too high, and then users have trouble turning it down. The exact opposite to Plex’s issue it seems. I’ll probably try Emby soon to see if their issues are not as bad as Plex’s - because I think the issues that come with “too high quality” are better than the reverse (what Plex does, start too low).
1 Like
I have not tried Emby for 2 years i think, but when i did everything worked in proper quality.
Jellyfish I tried recently, does not seem it ever will be a competitor due to lack of clients and dev speed, it’s going nowhere really slowly.
It has many issue BUT playing in proper quality works, it defaults to original quality, as it should and as a bonus feature: seeking works properly even if you seek multiple times in quick succession. Looking at you plex.
3 Likes
The only critical post on this entire thread are the ones looking for alternatives to Plex. Other than that its just a bunch of nothing.
Tried emby just now, besides being a giant slow clusterf… it also transcodes per default. Quality is set to “auto” which, for me at least, transcodes for no reason.
1 Like
I wouldn’t use Emby purely out of principle. (Licensing violations, lifetime perks only applying to major versions, etc). They’re arguably worse than Plex.
Not only that, I think Jellyfin has been reworking things under the hood to improve performance. For example, I believe they’ve ported it to .NET Core, which opens it up to being cross platform and comes with vast performance improvements across the board. Not only that, but Microsoft has been working on a cross platform UI framework as well.
Jellyfin is the future for open source media servers. Sure, it might be taking a while but so is Plex. In the long run we’re going to end up with better performance and less bloat being force fed to us. We really need client parity… Slowly but surely. 
3 Likes
@Orko Ha. Bummer. I have to think the transcode all the time thing is a config issue somewhere. But - it goes to show that switching may not be an easy home run here. Emby would have a whole other set of transcoder “quirks” to learn and adjust to. Maybe better to keep the devil we know vs one we don’t.
@Neureka Interesting. Call me crazy but I “want” to pay for software. Tech products need funding from somewhere to be sustainable. I think Jellyfin will be forked and/or morph to a paid model in 3-5 years. And Emby’s licensing model I like.
I think Plex hamstrung themselves with offering true lifetime tickets. Sure - customers love them, and they’re a short term boon for revenue. But as those users stay on plex longer - that revenue dries up. And so plex is forced to look at additional new revenue streams (cough arcade/streaming/ads cough). The long term, lifetime customer gets deprioritized - simply because they’re providing less revenue. Bugs drop in priority over diversifying revenue streams. Pure speculation though.
I wonder if the core plex user base had a lower percentage of lifetime ticket holders - we’d see core bug/feature gaps like this one resolved sooner?
I guess I’m trying to rationalize how a feature like this could get kicked down the road for so long lol. Who knows.
Competitor platform exploration are good ideas though when it seems like Plex just is really taking their time here.
1 Like
