@Aaron44126 said:
I rolled back even further, to version 0.9.16.6.1993 (the latest pre-1.0 version that I have on file). I didn’t try a lot of different versions, I just picked this one “out of a hat” so to speak. This one works with the latest Windows Update patch and it works with my Sony Blu-ray player’s DLNA.So I’ll stick here for a while. sigh
Thanks for this! I’m back up and running now. It seems like all the later versions won’t launch after the latest Windows update.
@Russ4h said:
It seems like all the later versions won’t launch after the latest Windows update.
This should not be the case. i know it does not help with the DLNA issue but just correcting the statement
A change was made in 1.4.1 that avoids the crash on launch caused by faulty windows dll CompPkgSup.dll that was in (limited release) cumulative patch KB3216755 and is now suspected to be in new (general release) cumulative patch KB4013429 (March 14, 2017—KB4013429 (OS Build 14393.953) - Microsoft Support). So update to PMS 1.4.4 public or 1.5.0 Plex Pass avoids the crash at launch.
And if you do have a copy of the old version of Plex Media Server to go back to for DLNA to work, it is worth trying out 1.5.0 in case DLNA streaming is better.
@sa2000: Most of us can’t test 1.5.0 since it is only available to Plex Pass members. According to the release notes there is no mention of any DLNA fixes and only a transcoding audio fix which I doubt is the problem. It would be great if it was! I sincerely hope that you guys can get this sorted out because I’d like to start using Plex again. I’ll even buy a Plex Pass if future releases prove to be stable.
It is nice to see a comment from @BigWheel but saddening that there is no indication of commitment to resolve the problem, only to investigate it. My intuition is that Plex is trying to phase out DLNA and diverting resources to other projects like the “Plex Cloud”. Until the DLNA issues are sorted, I’ve begun using Universal Media Server. While it is more of a pain, the DLNA support is vastly superior.
Thanks @Aaron44126 for the info!
I assume there are many people here who thought about getting the PLEX pass (me included).
However, my main usage is the DLNA streaming. If that does not work soon AGAIN (remember, nobody asks for new features, only the very basic functionality as it was until 1.1.4), obvioulsy PLEX is not for me and all the others sharing Sony hardware equipment.
It looks like the Windows Update patch that is crashing 1.1.4 is affecting more than just Plex. It also affects Directory Opus (which I use so I hit that one already), PowerDVD, DVB Viewer, Power Media Server, and others. There is a Microsoft forum thread and an article on the Directory Opus blog.
Hopefully Microsoft fixes this with the next big patch, and then we can at least hop back up to 1.1.4 again.
[Edit]
Today’s Windows patch, KB4015438, is supposed to fix the MPEG-2 crash issue introduced in the last patch.
[Edit 2]
Confirmed, 1.1.4 is working again after applying the latest Windows patch.
Given the fix to this is currently “Roll back to an older version where DLNA isn’t broken” is there any chance of links to older versions? I’ve had a hunt on the web and every link that used to work now just gets that link is not found and redirects you to the latest version.
Here is a link to 1.1.4 hosted on my Google Drive account:
https://drive.google.com/file/d/0B1KInK__g_VoWXh6blRueEYyVHc/view?usp=sharing
When downloading software from a non-trusted source, you should confirm that it is genuine. To confirm this file, right-click on it after downloading and select “Properties” from the menu. Go to the “Digital Signatures” tab. Select a signature and click “Details”. It should say “This digital signature is OK” at the top.
@Aaron44126 said:
Here is a link to 1.1.4 hosted on my Google Drive account:
https://drive.google.com/file/d/0B1KInK__g_VoWXh6blRueEYyVHc/view?usp=sharing
I can confirm that this file have exactly the same size and properties that the one wich i have in my computer (Legit downloaded from Plex -while available-).
Size: 93,3 MB (97.891.320 bytes)
Size on HDD: 93,3 MB (97.894.400 bytes)
Versión: 1.1.4.2757
Thanks for posting that up, I should’ve been more specific I’m chasing the linux (Ubuntu 64bit .deb) version, but I’m sure someone else will definitely want a copy of the Windows version.
It looks as if not much is moving on the DLNA issue.
I now switched over to emby.
Provides all the functionality I need, looks nice and supports DLNA on all my TVs.
Good bye Plex…
@hgewald I’d have to agree, Emby is a great plex replacement. Not only is it open source but they provide better support! plex, you suck!
While I understand priorities because I do work on a multi-arch project with limited staff and the complexities are really difficult I would appreciate knowing if the DLNA service is going to be fixed or if it is the intent of the programmers/publisher to cripple by abandonment of older hardware the ability to properly use it or even deprecate the service. It is of course your decision if you are and I understand the need for progression with new offerings, but to abandon such a worthwhile element for a lot of users just seems counter productive to me.
For myself ever time I get ready to pull the trigger and purchase a life time license something like this happens and I am forced to wait until it is fixed or if not then decide if I can live without it. Sadly the DLNA service is not one I am willing to eliminate on a paid for ( closed source ) product.
I am currently forced to use Version 1.0.3.2461 due to this issue and while it does work ( for now ) in stand alone use I have the feeling that it will become useless one of these days when an update to one of the applications like Samsung decides it will not work on such an old server like I have seen in the past.
Hi Guys,
That is known that “1.1.4” is the last well-working verion of Plex DLNA Server for devices like Sony Bravia 2012.
However recent versions of Plex still work fine with some media files downloaded from e.g. youtube.
In my case Plex works on QNAP TS-453 Pro, which is Intel 64 bit platform.
Starting from QNAPs firmware version “4.3” it is impossible to run Plex “1.1.4” which is 32 bit; 64bit app is required.
Is it possible for Plex Development team to generate 64bit build which is based on v1.1.4?
From my side I would be happy to assist somehow with investigation/resolving of this issue (provide logs, …); just let me know.
a small addition to the post above:
SInce some media files work fine on my Sony Bravia 2012, I suspect something is wrong with transcoding…
Everything was working for me up until the very latest update. Now “Playback not available” on 1.5.5.3634
DLNA works fine on everything in the house except my Sony Bravia 2010. Was there an undocumented change in the latest that removed the config for the device?
Sounds like all the transcoder modification in the previous updates have broken other things.
Hi…
Version 1.5.6.3790 it’s working for me
Sony KDL-32EX721
@fernandoaza said:
Hi…Version 1.5.6.3790 it’s working for me
Sony KDL-32EX721
Thanks for the feedback
Could others please check and confirm if ok now ? Either 1.5.6 / 1.5.7 or plex pass 1.7.3 release
Doesn’t work for me, on either 1.5.7 nor 1.7.3.
However, here’s the very interesting part, which may provide some insight on what’s going on. Long story short: after downgrading back to 1.1.4, which used to work, now results in the same problem affecting 1.1.4. Through trial & error I’ve narrowed down the culprit.
Quick side bar: the problem in 1.5.7 and 1.7.3 is similar to what was described before: the client shows trying to start playing the media, it sits and spins for a minute, then gives up and says ‘The server is not accessible. Access may not be permitted by the server’. Initially there is clear processor activity with the transcoder/PMS, but that goes away after 3-5 seconds. So the remaining time nothing is happening on the server.
Back on the fun topic of downgrade being affected by this issue. I went through the motions of restarting everything, entire OS, router/etc, to eliminate any residual problems. Nothing helped, until I decided to restore the entire plexmedia application directory from last night’s backup. The problem was gone!
So, upon closer inspection I’ve found that the culprit was this directory: Library/Application Support/Plex Media Server/Codecs/
Specifically, under 1.1.4 version there were three subdirs:
6209f91-1114-linux-ubuntu-x86_64
79d11e7-1182-linux-ubuntu-x86_64
c9ea179-1157-linux-ubuntu-x86_64
and each had the following libs:
libaac_decoder.so
libaac_encoder.so
libac3_decoder.so
libac3_encoder.so
libamrnb_decoder.so
libdca_decoder.so
libeac3_decoder.so
libh264_decoder.so
libhevc_decoder.so
liblibx264_encoder.so
libmpeg2video_decoder.so
libmpeg4_decoder.so
libmsmpeg4v1_decoder.so
libmsmpeg4v2_decoder.so
libmsmpeg4v3_decoder.so
librv40_decoder.so
libvc1_decoder.so
libvp9_decoder.so
libwmv1_decoder.so
libwmv2_decoder.so
Now when plex 1.7.3 starts, and NOT during the rpm upgrade part, PMS removes all of those directories, and creates a new one: 271ddd5-1239-linux-ubuntu-x86_64, with similar files there. EXCEPT libeac3_decoder.so is missing there!
When you revert back to 1.1.4 version, absence of those directories and that library affects playback, and the issue persists. PMS creates 6209f91-1114-linux-ubuntu-x86_64 directory, but it’s empty. Restoring its content from backup solves the problem.
Now here’s even more interesting. If I remove all those subdirs under Codecs, reinstall 1.1.4 package and restart PMS, 6209f91-1114-linux-ubuntu-x86_64 directory remains empty, and 1.1.4 continues to be broken. So where did its content come from, perhaps one of the earlier packages?
Back to the culprit at hand: I believe that lack of libeac3_decoder.so in the new PMS 1.5.X/1.7.X may be the actual cause behind this whole mess.
@sa2000 : I’d appreciate if this information was forwarded to the devs, hopefully it will help nail down the issue.
Cheers!
@ananke said:
Doesn’t work for me, on either 1.5.7 nor 1.7.3.However, here’s the very interesting part, which may provide some insight on what’s going on. Long story short: after downgrading back to 1.1.4, which used to work, now results in the same problem affecting 1.1.4. Through trial & error I’ve narrowed down the culprit.
Quick side bar: the problem in 1.5.7 and 1.7.3 is similar to what was described before: the client shows trying to start playing the media, it sits and spins for a minute, then gives up and says ‘The server is not accessible. Access may not be permitted by the server’. Initially there is clear processor activity with the transcoder/PMS, but that goes away after 3-5 seconds. So the remaining time nothing is happening on the server.
Back on the fun topic of downgrade being affected by this issue. I went through the motions of restarting everything, entire OS, router/etc, to eliminate any residual problems. Nothing helped, until I decided to restore the entire plexmedia application directory from last night’s backup. The problem was gone!
So, upon closer inspection I’ve found that the culprit was this directory: Library/Application Support/Plex Media Server/Codecs/
Specifically, under 1.1.4 version there were three subdirs:
6209f91-1114-linux-ubuntu-x86_64
79d11e7-1182-linux-ubuntu-x86_64
c9ea179-1157-linux-ubuntu-x86_64and each had the following libs:
libaac_decoder.so
libaac_encoder.so
libac3_decoder.so
libac3_encoder.so
libamrnb_decoder.so
libdca_decoder.so
libeac3_decoder.so
libh264_decoder.so
libhevc_decoder.so
liblibx264_encoder.so
libmpeg2video_decoder.so
libmpeg4_decoder.so
libmsmpeg4v1_decoder.so
libmsmpeg4v2_decoder.so
libmsmpeg4v3_decoder.so
librv40_decoder.so
libvc1_decoder.so
libvp9_decoder.so
libwmv1_decoder.so
libwmv2_decoder.soNow when plex 1.7.3 starts, and NOT during the rpm upgrade part, PMS removes all of those directories, and creates a new one: 271ddd5-1239-linux-ubuntu-x86_64, with similar files there. EXCEPT libeac3_decoder.so is missing there!
When you revert back to 1.1.4 version, absence of those directories and that library affects playback, and the issue persists. PMS creates 6209f91-1114-linux-ubuntu-x86_64 directory, but it’s empty. Restoring its content from backup solves the problem.
Now here’s even more interesting. If I remove all those subdirs under Codecs, reinstall 1.1.4 package and restart PMS, 6209f91-1114-linux-ubuntu-x86_64 directory remains empty, and 1.1.4 continues to be broken. So where did its content come from, perhaps one of the earlier packages?
Back to the culprit at hand: I believe that lack of libeac3_decoder.so in the new PMS 1.5.X/1.7.X may be the actual cause behind this whole mess.
@sa2000 : I’d appreciate if this information was forwarded to the devs, hopefully it will help nail down the issue.
Cheers!
Thanks for the tests. So you believe the media you have that does not play on DLNA on the Sony, requires the libeac3_decoder.so codec file. I will pass this info on. What was the media info for the file tested?
With regards to 1.1.4 not working after a fresh re-install - that is correct. Only existing installs may continue to work or as you found - a restore from a backup. Support for versions before 1.5.x was removed after release of this Service Support Statement http://forums.plex.tv/discussion/268072/plex-media-server-1-5-1-and-plex-media-player-1-2-4-or-newer-are-mandatory-updates
So they made mandatory upgrade to a version with known bugs for a significant portion of the user base. Wow this project is off the rails, customer support left behind for chasing new customers. Short term strategy.
