Question for peeps using HW acceleration AND this PMS as a Service.
Lots of users are having issues with the PMS transcoder crashing on Windows. NOT necessarily using this program, but with the latest build, it seems it’s a big issue and no real explanation from PLEX.
So my question is - is it possible this service wrapper is making those issues worse? Using this service wrapper already disables the HW decoding functionality (https://forums.plex.tv/discussion/291564/pms-error-ffmpeg-failed-to-create-direct3d-device#latest) So that’s a big downfall. However, I’m more concerned that I’m also having random crashes. Although nothing is logged in the server wrapper logs I can’t help but think this service wrapper is contributing to those issues.
Also of note, I know this application has not been updated in a long time. I wonder how it’s possible this can still work efficiently with PMS given the very frequent updates that are pushed out. All the other tools I use with PMS (PlexPY, OMBI, etc) need to be constantly updated when new PMS builds are released.
So, to sum up:
1 - Is this application still reliable when using HW transcoding?
2 - Is this application still being developed?
There’s very little that needs changing so I don’t need to update very often. All I change these days is when Plex add extra processes. I add them to my list of processes to kill on shut down. So to answer your question, sure it’s being actively developed. As much as any software that does one simple task is ever actively developed.
When running as a service the windows shell is not available. Lots of things that happen when a user logs in are not available, like mapped drives. Also depending on the user the service is run as, you may have permissions issues. I don’t use hw transcoding so I can’t speak to any specifics.
@cjmurph said:
There’s very little that needs changing so I don’t need to update very often. All I change these days is when Plex add extra processes. I add them to my list of processes to kill on shut down. So to answer your question, sure it’s being actively developed. As much as any software that does one simple task is ever actively developed.
When running as a service the windows shell is not available. Lots of things that happen when a user logs in are not available, like mapped drives. Also depending on the user the service is run as, you may have permissions issues. I don’t use hw transcoding so I can’t speak to any specifics.
Appreciate the response @Cjmurph. Totally understandable. If it’s not broke, don’t fix it!
Do you have any plans to develop/test this under HW acceleration conditions?
Not at this stage. I don’t have the hardware to test it.
From what you have said, it seems like there are lots of issues with it when Plex is run normally anyway. I think it would be best to wait for some more stability before jumping into that fire.
@seanvree81 said:
Do you have any plans to develop/test this under HW acceleration conditions?
Running latest PMS + HW transcoding (based on Intel Quick Sync) with cjmurph’s service wrapper → no known issues
Different hardware same conclusion. HW transcoding works aok as service
Windows 10 x64
Latest Radeon (optional x.11) drivers
AMD A10 APU (GPU secondary in UEFI)
AMD XFX RX 460 Slim (primary)
@cjmurph Currently the automatic port forwarding doesn’t work unless the UPnP Host service is running under Windows. If it isn’t the port forwarding will not occur automatically and manual will be required.
So it may be worth having your service wrapper check if the Remote Access has been activated and isn’t on manual port forwarding. If it isn’t then have it alter it’s service windows registry entry to include “upnphost” as a dependency for the service. With the reverse being true (where appropriate) so that it doesn’t auto forward if remote access isn’t required or is on manual. Then issue an automatic service restart (or prompt the user to restart the service) in order to trigger the UPNP Host to be started. Which will then enable the service software for Windows to have the remote access configured automatically so people can log in to their Plex Media Servers.
Alternatively make upnphost a dependency by default in order for the Remote Access (automatic port forwarding) to function.
I’ve just published a new version. check out the first post for details.
To summarize:
Add menu option for Auxiliary Applications issue #17
Add mapped drives issue #27
Add upnphost as dependency service. @MrGrymReaper
some settings layout changes and better window handling (single instance of windows allowed)
The mapped drives option is experimental at this stage. I’d appreciate some feedback from anyone willing to do some testing. It seems to work OK for me.
The auxiliary applications now allow a url to be defined. If this is populated, a new menu item will be created on teh tray icon context menu to navigate to this url.
@Macivervfr said:
Sorry to say this but on my setup the latest version cannot start the service. I´ve tried numerus times. But when i install 1.1.2 it runs at ones.
Ok, thanks for the feedback.
Do you mean to say the service won’t start, or the service can’t start Plex?
Would you mind looking in your system event logs for me?
After entering the credentials during the install process. When the progess bar Shows Starting Service. An Error accures for me too. The only solution is to go back to 1.1.2
Got the Plex running on a Win server 2012 R2. Plex is the only program to run on this machine.
I´ve got manual port forwarding. No DNLA.
Tried to do the install again and this pops up during installation:
Yes, i´ve got the admin rights.
Pressed retry once, same window pops up i then press cancel and installed 1.1.2 and 1.1.2 just runs. No hickups.
@Macivervfr said:
Got the Plex running on a Win server 2012 R2. Plex is the only program to run on this machine.
I´ve got manual port forwarding. No DNLA.
Tried to do the install again and this pops up during installation:
Yes, i´ve got the admin rights.
Pressed retry once, same window pops up i then press cancel and installed 1.1.2 and 1.1.2 just runs. No hickups.
Where do i find the upnphost?
Click Start, type services.msc. open the services snap in and scroll through the list until you see upnp host service.
That’s the error I received when I had that service disabled.
