@Kwiboo two weeks later, when can we expect fix?
@“Bartlomiej Baraniec” the release is slightly delayed as there have been some issues when using a secure connection to PMS
@Kwiboo that’s terrible, terrible news but thanks for update. Can’t wait for fix.
@“Bartlomiej Baraniec” said:
@Kwiboo two weeks later, when can we expect fix?
I’m not @kwiboo, but it’s still being worked on. This bug is squashed in the next release, but there are other bugs needing squishing as well. Patience.
I’m very patient. That bug just makes OpenPHT much harder to use.
Unfortunately it makes Rasplex useless for anyone using it to stream remotely, unless they can watch whatever it is in one sitting whilst transcoding. Otherwise you’ll need to be happy to have all your bandwidth sucked up.
I was considering buying a lifetime pass when I saw the discount recently, but when I saw Alexa was given priority over core fixes like this I passed, again.
@ClubLife keep in mind that OpenPHT is a community project. Plex ditched PHT for PMP.
@ClubLife said:
I was considering buying a lifetime pass when I saw the discount recently, but when I saw Alexa was given priority over core fixes like this I passed, again.
As @“Bartlomiej Baraniec” said above, OpenPHT is a community project – PlexPass money entirely goes to Plex, Inc. and not the OpenPHT team. We’re not prioritizing Alexa over core fixes, and we have nothing to do with PlexPass.
Guys an update on this matter please. Is three a fix already? Do you want to bake it into next release?
In so many cases OpenPHT is not usable in remote locations. Ignore the progress but even subtitles won’t work if the was interruption in stream.
We should have a fixed release in a couple days provided no new critical bugs raise their head during internal testing.
However, it seems Plex may have fixed the issue in the new Plex Pass PMS 1.4.4.3495. I haven’t tested it, but looks like it was causing issues with Chrome and some TV clients as well. Either way, we plan to leave in the new fixes to OpenPHT so it doesn’t happen again.
@benjaminwolf I’m on 1.5.0.3501 and unfortunately the problem still exists.
this is fixed in the 1.8.0 just released.
@daniel.cull said:
this is fixed in the 1.8.0 just released.
I love you.
@“daniel.cull” oh, you can’t imagine how happy I am to hear that. BRB
