Plex Pass Entitlements - Early releases or buggy releases? Are we beta testers?

Plex Pass ‘preview’ version vs non-pass version… I’m pretty sure both are beta post v0.9.16.6.

Plex have moved their resources to release new product lines (Sonos, pvr, shield) instead of bringing post 0.9.16.6 out of beta and stable.

Love plex, but not prepared to downgrade to a newer version based on the increased problems posted each time a new release is provided (pass or non-pass).

Hi @marshalleq,

We have noticed a scanner fail in our testing before, but it had also been fixed and verified before the application was released. Would you mind providing me with some additional information so we can replicate your environment? If possible, I would like the following information:

  1. PMS version
  2. OS version
  3. Device(s) seen with the issue
  4. Any logs (ideally verbose) captured

I agree that the wording can cause confusion, and I would like to thank you for this feedback. We will look at what pieces of documentation should be added and modified to help clear things up.

First I would say, ‘define released’. Released to Plex Pass or to public? As that would be very interesting.

Second, I don’t mind sharing this information with you in a separate thread - actually I believe there are one or two threads already existing - as there also are for others on the above topic. However other than validating for the purposes of this discussion, I don’t think it’s appropriate to hijack this thread, potentially avoiding some of the questions.

Right now today, I have metadata scanning weirdness still happening on a new database build (rebuilt out of desperation to try and find any working version), and failure of streaming music to Android at least. I think I have threads about both of those. Thanks.

Adding to the confusion is the long period where the latest Plexpass version of PMS was withtheld from the PlexPass auto-update channel due to the that newer version being “beta”. Well, if that was beta then what is it otherwise when it is sent right to the channel without being held back in that manner?

The naming is deceptive, and the treatment is inconsistent. Something needs to change. This complaint has been going on for years.

What irks me is the above statements around, ‘Point me at specific issues, we can’t see them’ yet they’re in plain sight in this forum. I consider this thread largely unanswered and it makes me grumpy that these issues are still not being accepted. There has been some response from Plex, but sorry Plex, it just isn’t good enough. It’s one thing to irritate a lifetime member whom isn’t funding any ongoing revenue, but there are of course plenty of people on here that may just give up their subscription altogether. Plex MUST resolve these issues, through communication as it appears presently there is a complete lack of understanding, acceptance, or visible action.

e.g. https://forums.plex.tv/discussion/comment/1249274#Comment_1249274

Hi @cpoon, further to your question, just because I logged in and read this, I think this example where a Plex Ninja has outlined some of the previous issues with the rollout’s affecting core features. The point being, this process clearly was not working and I assume is still not working.

Specifically, “There was an issue with 1.0.3 which took a bit to sort out fully” and “The bug fixes just happened to all come at once”.

Really, I’m not trying to be negative, however some response, 'We understand issue 1, 2 and 3" and we’ll post updates in this thread or something would be enough. I’m sure you’re aware of the many gripes in these threads to this end. The beta situation needs to be clarified, improved and communicated I think.

Thanks.

why update some thing if it not broken… just do not run the update processes until some thing is confirmed broken or you just have to have that new feature.

In my understanding the Plex Pass update channel has always been the “beta” channel so to speak. I use to only have my PMS set to public channel because I knew the Plex Pass channel could indeed introduce bugs to my system.

However they should have a stable channel and beta channel for Plex Pass subscribers like you said above. I think that would clear up a lot of confusion and really separate users who 1. Don’t want to be beta testers but do want early releases that are stable and 2. Allow users who enjoy testing out beta versions and new features the chance to do so knowing the risk it may be buggy.

Right now Plex Pass is just kind of lumping those two groups of users together and not really differentiating between the two.

Regards,

Even from day 1 of purchasing my lifetime pass (6+ years ago), I always understood Plex Pass software channel as an added perk if you want it.

Public/Stable - has all Plex Pass features
Plex Pass - has all the above but hasn’t been rolled into the stable branch yet, as being a Plex Pass user gets me some early access and gets Plex some beta testing IF I SO CHOOSE

Is this not how most people always understood this?

Hi @marshalleq,

We agree that the term, release, can be better defined. The right folks are informed about it to help with the definitions of the various types of releases.

Thank you for the helpful feedback.