@RedSocks157 said:
I don’t get why this hasn’t been implemented. This feature has been requested for ages, just look how far back this thread goes and there were others before it. And they haven’t even addressed the issue. I don’t need lyrics for my music, I don’t need half the crap they keep shoehorning into this software. GPU encoding on the other hand would be easy to implement (the libraries already exist for god’s sake, why not just include them?) and it would make a HUGE difference for a ton of users. It wouldn’t take a freaking Xeon or i7 processor to stream multiple HD movies at once, or to transcode a bluray rip for an off-network client. Suddenly, APUs and i3s would be able to handle WAY more stuff, and a system with a video card would be even better.
The improvement in lower-end hardware being used for servers would be huge, and it would make Plex more appealing to people who can’t afford to have a server rack in their basement. And if I’m not spending $300 on the processor for my server, maybe I can afford to pay $150 for PlexPass features. Just throwing that out there.
Overall, it’s honestly nuts that hardware encoding isn’t supported. If Emby manages to get it working before Plex does, I’m going to use Emby instead.
I relate to this, except that i do own perpetual plexpass… and i use NONE of its features (cause i tried and droped them all…). The only benefit is that now that my wife has an iphone, i did not have to pay for plex there (i payed for the plex app in the amazon store for android before buying plexpass).
Then go use Emby, nobody is retaining you.
If you don’t get why this is not implemented, read the post from rcombs just above.
GPU encoding is not easy to implement contrary to your belief.
I especially love the fact that non-plexpass user is bitching about this, and use the word maybe afford the plex pass if this gets implemented.
Other than the “easy to implement”, I agree with you. Plex pushes an astonishing number of fringe “features” while major issues go unaddressed and bugs fester in core functions. I’m glad that rcombs addressed this thread and helped to clarify some of the issues. That said, I’d really hate to see QS delayed because of something as simple as requiring customers to download an extra package. My Plex server is Linux based, and it sounds like I won’t be seeing QS support for quite some time. Very frustrating.
Oh, so because I don’t have $150 to pony up I don’t get to share my opinions? Plex started as FREE software, and people would do well to remember that. It’s always been community based. I have just as much reason and right to share my thoughts as anyone who has already paid.
Yes, FFMPEG has libraries that provide hardware encoding. All the Plex team would have to do is merge those libraries into their software. Maybe if they spent less time doing stupid crap like adding lyrics to my music, it would be a feature instead of a drawback. I’m not willing to pay for lyrics in my music. Hardware transcoding, I’d pay for. And guess what? How I spend my money is my business. Maybe you should try not sending people to Emby, I don’t think Plex’s employees would be too happy to see their potential revenue leaving just because some forum-poster took it upon himself to defend them.
I have to agree that most of the features added are of no consecuense to VIDEO. (the trailers one might be cool in the first world with fast internet tho).
I find it weird that PLEXPASS users who i had seen as the people who had access to experimental stuff first have no option to follow “maybe hard/poweruser instructions” to download something or set something up, and then get the option to choose the EXTRA experimental whatever (currently the default player/transcoder is named experimental) and get access to this.
I myself, have a decent (albeit old :P) first generation overclocked i7-920, that many times strugles to stream to my chromecast (i only download 720p or sometimes 1080p stuff). I have a mini pc with a much newer (but weaker) intel processor that has quicksync support.
I use plex in my livingroom TV that has a PC behind it, so i could use plex there, but no luck when i go to bed… so my mini pc only has sickrage/couchpotato for downloading stuff and then i have automatic processes to copy my stuff back to my “server” (gaminig pc), for plex T_T
It would be much better (And cheaper on my electricity bill) if quicksync was an option.
Maybe i will check emby, but it pains me cause i already payed for plexpass.
Use that PlexPass to go start a conversation in the top-secret forums! If they still won’t answer and won’t work on it, see if you can get a refund. I’m thinking about emby right now and on their blog they say they added quicksync support in November 2015. Clearly it is possible. Plex should have QuickSync, AMD’s VCE, and Nvidia’s NVEC for the price they’re charging!
Will have to find the original request, cause duplicated feature request are deleted (or so a sticky says), and i saw nothing related wo quicksync or hardware encoding browsing the first 3 pages of the feature request / support forum.
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
PMS has always been closed source (since 2009/2010 when it was released), and I would say that over the years I have never heard them talking about making it open source like they have done with Plex Media Player. And I assume that a feature like this (that will not even work on all platforms) is not going to sway them into changing their model.
As mentioned in this thread (and others), they are looking into making this a reality, but going another route. It will take time, but it will likely come to fruition.
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
PMS has always been closed source (since 2009/2010 when it was released), and I would say that over the years I have never heard them talking about making it open source like they have done with Plex Media Player. And I assume that a feature like this (that will not even work on all platforms) is not going to sway them into changing their model.
As mentioned in this thread (and others), they are looking into making this a reality, but going another route. It will take time, but it will likely come to fruition.
They have not released any kind of actual information about this. Just “we’re looking into it” bs. Also, it is pretty universal platform-wise. Hardware encoding solutions from AMD, Intel, and Nvidia all work on Windows/Mac/Linux. Emby already has QuickSync working in their server software across all platforms. Why would this be any more difficult for the Plex team?
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
PMS has always been closed source (since 2009/2010 when it was released), and I would say that over the years I have never heard them talking about making it open source like they have done with Plex Media Player. And I assume that a feature like this (that will not even work on all platforms) is not going to sway them into changing their model.
As mentioned in this thread (and others), they are looking into making this a reality, but going another route. It will take time, but it will likely come to fruition.
They have not released any kind of actual information about this. Just “we’re looking into it” bs. Also, it is pretty universal platform-wise. Hardware encoding solutions from AMD, Intel, and Nvidia all work on Windows/Mac/Linux. Emby already has QuickSync working in their server software across all platforms. Why would this be any more difficult for the Plex team?
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
PMS has always been closed source (since 2009/2010 when it was released), and I would say that over the years I have never heard them talking about making it open source like they have done with Plex Media Player. And I assume that a feature like this (that will not even work on all platforms) is not going to sway them into changing their model.
As mentioned in this thread (and others), they are looking into making this a reality, but going another route. It will take time, but it will likely come to fruition.
They have not released any kind of actual information about this. Just “we’re looking into it” bs. Also, it is pretty universal platform-wise. Hardware encoding solutions from AMD, Intel, and Nvidia all work on Windows/Mac/Linux. Emby already has QuickSync working in their server software across all platforms. Why would this be any more difficult for the Plex team?
Have you actually read through this thread?
Yes. And I have yet to see an answer to that question - if Emby already has this ability, which has been built into ffmpeg for around 6 months, why can’t Plex do it?
@RedSocks157 said:
They have not released any kind of actual information about this. Just “we’re looking into it” bs. Also, it is pretty universal platform-wise. Hardware encoding solutions from AMD, Intel, and Nvidia all work on Windows/Mac/Linux. Emby already has QuickSync working in their server software across all platforms. Why would this be any more difficult for the Plex team?
The only caveat is that only for windows, you can use quicksync out of the box, or so i read @ emby forums
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
PMS has always been closed source (since 2009/2010 when it was released), and I would say that over the years I have never heard them talking about making it open source like they have done with Plex Media Player. And I assume that a feature like this (that will not even work on all platforms) is not going to sway them into changing their model.
As mentioned in this thread (and others), they are looking into making this a reality, but going another route. It will take time, but it will likely come to fruition.
They have not released any kind of actual information about this. Just “we’re looking into it” bs. Also, it is pretty universal platform-wise. Hardware encoding solutions from AMD, Intel, and Nvidia all work on Windows/Mac/Linux. Emby already has QuickSync working in their server software across all platforms. Why would this be any more difficult for the Plex team?
Have you actually read through this thread?
I have to side with redsocks, what whas said here is just PR response.
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
PMS has always been closed source (since 2009/2010 when it was released), and I would say that over the years I have never heard them talking about making it open source like they have done with Plex Media Player. And I assume that a feature like this (that will not even work on all platforms) is not going to sway them into changing their model.
As mentioned in this thread (and others), they are looking into making this a reality, but going another route. It will take time, but it will likely come to fruition.
They have not released any kind of actual information about this. Just “we’re looking into it” bs. Also, it is pretty universal platform-wise. Hardware encoding solutions from AMD, Intel, and Nvidia all work on Windows/Mac/Linux. Emby already has QuickSync working in their server software across all platforms. Why would this be any more difficult for the Plex team?
Have you actually read through this thread?
Yes. And I have yet to see an answer to that question - if Emby already has this ability, which has been built into ffmpeg for around 6 months, why can’t Plex do it?
So then you read this:
Sorry to disappoint, but we’d rather wait until we can provide a complete solution than rushing to support one specific case (no scaling, no interlacing, no subtitle burning, on Windows only), only to have to replace that code later.
That is why they are not doing it. That is a very clear answer, with extremely little PR.
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
PMS has always been closed source (since 2009/2010 when it was released), and I would say that over the years I have never heard them talking about making it open source like they have done with Plex Media Player. And I assume that a feature like this (that will not even work on all platforms) is not going to sway them into changing their model.
As mentioned in this thread (and others), they are looking into making this a reality, but going another route. It will take time, but it will likely come to fruition.
They have not released any kind of actual information about this. Just “we’re looking into it” bs. Also, it is pretty universal platform-wise. Hardware encoding solutions from AMD, Intel, and Nvidia all work on Windows/Mac/Linux. Emby already has QuickSync working in their server software across all platforms. Why would this be any more difficult for the Plex team?
Have you actually read through this thread?
Yes. And I have yet to see an answer to that question - if Emby already has this ability, which has been built into ffmpeg for around 6 months, why can’t Plex do it?
So then you read this:
Sorry to disappoint, but we’d rather wait until we can provide a complete solution than rushing to support one specific case (no scaling, no interlacing, no subtitle burning, on Windows only), only to have to replace that code later.
That is why they are not doing it. That is a very clear answer, with extremely little PR.
And yet, its possible in Emby for the last 6 months. They haven’t even attempted to make it an option, or an advanced feature for experienced users. It would be huge for TONS of users around here - especially those of us who can’t afford a Xeon server.
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
PMS has always been closed source (since 2009/2010 when it was released), and I would say that over the years I have never heard them talking about making it open source like they have done with Plex Media Player. And I assume that a feature like this (that will not even work on all platforms) is not going to sway them into changing their model.
As mentioned in this thread (and others), they are looking into making this a reality, but going another route. It will take time, but it will likely come to fruition.
They have not released any kind of actual information about this. Just “we’re looking into it” bs. Also, it is pretty universal platform-wise. Hardware encoding solutions from AMD, Intel, and Nvidia all work on Windows/Mac/Linux. Emby already has QuickSync working in their server software across all platforms. Why would this be any more difficult for the Plex team?
Have you actually read through this thread?
Yes. And I have yet to see an answer to that question - if Emby already has this ability, which has been built into ffmpeg for around 6 months, why can’t Plex do it?
So then you read this:
Sorry to disappoint, but we’d rather wait until we can provide a complete solution than rushing to support one specific case (no scaling, no interlacing, no subtitle burning, on Windows only), only to have to replace that code later.
That is why they are not doing it. That is a very clear answer, with extremely little PR.
And yet, its possible in Emby for the last 6 months. They haven’t even attempted to make it an option, or an advanced feature for experienced users. It would be huge for TONS of users around here - especially those of us who can’t afford a Xeon server.
So you are saying that Emby server can use Quicksync on other platforms than Windows? That goes against what the Emby prerequisites mention. I would be interested to know how they solved that.
@AlexDua said:
Ok, final question regarding this. Is there anything we can do to help Plex make this a reality? Other than pay subs? Should we petition Intel, Nvidia or AMD on anyone else on behalf of Plex regarding the license issues (which I don’t care to wrap my mind around now)? I think most of us here are not just being “trouble” customers screaming I want my super size fries now. I myself am in the category of, hey I see this trend here, and I see the direction of tech. I think Plex should ratchet this up a few notches since it will take time to do. And by the time it is done it might be a do or die situation not so much for Emby or any other guys using it. But a lot of hardware is going to be aimed in this GPU centered approach. The NAS appliances just coming out now are starting to focus on GPU’s ,not clock speed or cores. I think most of us want this not just because we want it now but, we want it because we love Plex and want to keep using it and support it. And if Plex needs to raise the price to help here, that is fine. I think most of us will be willing to pay for it, as long as we get good feedback and features we want enabled, even if it takes time.
I totally understand secrecy and not revealing major issues to customers, but I think being more open and giving more feedback as was done today is a good step. Not only to help us feel that we are listened to but for us to feel the pain of how making this great software is a pain. Some people perhaps need to know this is not easy especially with the fact that we all have to sleep and there are so many hours in the week. More feedback is always a plus. Even if the question is raised over and over, as some of us are new here and didn’t see the past posts. Thanks again.
I’m not sure what we can do. The real problem here is that Plex has closed source code, so nobody else is going to have access to it. Let’s say we could get AMD to help Plex integrate code for it’s VCE hardware encoder. AMD is not going to do it for free, because Plex is not open source. And even if they would do it for free, Plex wouldn’t let them because their code is closed.
Ffmpeg already has support for gpu encoding in it, since like mid-2015. Plex just refuses to include this code in PMS. They aren’t utilizing anything remotely close to a recent version of ffmpeg.
PMS has always been closed source (since 2009/2010 when it was released), and I would say that over the years I have never heard them talking about making it open source like they have done with Plex Media Player. And I assume that a feature like this (that will not even work on all platforms) is not going to sway them into changing their model.
As mentioned in this thread (and others), they are looking into making this a reality, but going another route. It will take time, but it will likely come to fruition.
They have not released any kind of actual information about this. Just “we’re looking into it” bs. Also, it is pretty universal platform-wise. Hardware encoding solutions from AMD, Intel, and Nvidia all work on Windows/Mac/Linux. Emby already has QuickSync working in their server software across all platforms. Why would this be any more difficult for the Plex team?
Have you actually read through this thread?
Yes. And I have yet to see an answer to that question - if Emby already has this ability, which has been built into ffmpeg for around 6 months, why can’t Plex do it?
So then you read this:
Sorry to disappoint, but we’d rather wait until we can provide a complete solution than rushing to support one specific case (no scaling, no interlacing, no subtitle burning, on Windows only), only to have to replace that code later.
That is why they are not doing it. That is a very clear answer, with extremely little PR.
And yet, its possible in Emby for the last 6 months. They haven’t even attempted to make it an option, or an advanced feature for experienced users. It would be huge for TONS of users around here - especially those of us who can’t afford a Xeon server.
So you are saying that Emby server can use Quicksync on other platforms than Windows? That goes against what the Emby prerequisites mention. I would be interested to know how they solved that.
I believe currently it is a really funky tweak, but it’s better than nothing right? The AMD solution is open source currently, and since I use an old APU in my server that is what I would most appreciate. I’m not sure about the status on Intel’s QS code, and NV is almost certainly closed source unfortunately.
It’s just incredibly frustrating how long this feature has been requested and how many people have asked, and yet there has been zero progress made. Not even a real response or status update from a dev recently.
@RedSocks157 said:
I believe currently it is a really funky tweak, but it’s better than nothing right? The AMD solution is open source currently, and since I use an old APU in my server that is what I would most appreciate. I’m not sure about the status on Intel’s QS code, and NV is almost certainly closed source unfortunately.
A funky tweak doesn’t sound like something devs should spend time on.
And as for Quick Sync (which this thread is about) on Mac, there does not seem to be anything anyone can do about it as Intel has not made the appropriate API´s available. I would love to read something about that if it proves me wrong. But I have found no evidence of me being wrong about that.
It’s just incredibly frustrating how long this feature has been requested and how many people have asked, and yet there has been zero progress made. Not even a real response or status update from a dev recently.
How can you even say that? Not even half a day has gone by since a dev responded. If you are referring to anything before November (which is the last time before today a dev responded) then yes, this feature request has taken a back seat due to the lack of a possibility to do this. It wasn’t until late summer that ffmpeg added support for this for one platform. There were tons of other things that tons of people wanted added in the mean time.
You would not believe how many times I have read a version of this in this very forum: “I can’t believe the incompetence of Plex, they have not added the absolutely crucial feature X and Y”. Everyone having different views on what is important. Yes, it is frustrating not to have your pet peeve worked on. I for one would rather see this not being added at all if that meant I was getting my pet peeve solved. That is how little I care about this compared to the feature I lack. I would trade in all other features for getting a better subtitle solution in place. Me being able to hit a button in the OSD and getting presented with subtitles from different sites from which I can download with the press of a button.
Sorry to disappoint, but we’d rather wait until we can provide a complete solution than rushing to support one specific case (no scaling, no interlacing, no subtitle burning, on Windows only), only to have to replace that code later.
That is why they are not doing it. That is a very clear answer, with extremely little PR.
That is too much pr for me… or really really old and not usefull to the actual results NOW…if i have to believe emby users, quicksync is ROCKING…
@atrus said:
So you are saying that Emby server can use Quicksync on other platforms than Windows? That goes against what the Emby prerequisites mention. I would be interested to know how they solved that.
Emby has that out of the box for windows, and for all/some linux distros, people have to either compile or download ffmpeg from some of the many available places (that is what i learnt from the last 5 pages of the emby thread about this, and posted before HERE). Nvidia is out of the question tho.
wont bother quoting the last 2 posts from @RedSocks157 and @atrus , but as far as i could see, it is NOT a funky tweak, it requiries little work to incorporate it (unless plex is not using stock/up to date ffmpeg), and it is available OUT OF THE BOX for windows, you need to get your ffmpeg in linux, and no idea on mac.
EDIT: better subtitle support, and also the option of NOT transcoding compatible video on chromecast when showing subtitles, is almost as high on my book as hardware video transcoding
Sorry to disappoint, but we’d rather wait until we can provide a complete solution than rushing to support one specific case (no scaling, no interlacing, no subtitle burning, on Windows only), only to have to replace that code later.
That is why they are not doing it. That is a very clear answer, with extremely little PR.
That is too much pr for me… or really really old and not usefull to the actual results NOW…if i have to believe emby users, quicksync is ROCKING…
@atrus said:
So you are saying that Emby server can use Quicksync on other platforms than Windows? That goes against what the Emby prerequisites mention. I would be interested to know how they solved that.
Emby has that out of the box for windows, and for all/some linux distros, people have to either compile or download ffmpeg from some of the many available places (that is what i learnt from the last 5 pages of the emby thread about this, and posted before HERE). Nvidia is out of the question tho.
wont bother quoting the last 2 posts from @RedSocks157 and @atrus , but as far as i could see, it is NOT a funky tweak, it requiries little work to incorporate it (unless plex is not using stock/up to date ffmpeg), and it is available OUT OF THE BOX for windows, you need to get your ffmpeg in linux, and no idea on mac.
Maybe I wasn’t reading in the right place then. So it only requires a little additional work? Seriously, this should be in Plex yesterday. Plex costs $50 more and doesn’t even have a hint of an implementation of this.
Sorry to disappoint, but we’d rather wait until we can provide a complete solution than rushing to support one specific case (no scaling, no interlacing, no subtitle burning, on Windows only), only to have to replace that code later.
That is why they are not doing it. That is a very clear answer, with extremely little PR.
That is too much pr for me… or really really old and not usefull to the actual results NOW…if i have to believe emby users, quicksync is ROCKING…
@atrus said:
So you are saying that Emby server can use Quicksync on other platforms than Windows? That goes against what the Emby prerequisites mention. I would be interested to know how they solved that.
Emby has that out of the box for windows, and for all/some linux distros, people have to either compile or download ffmpeg from some of the many available places (that is what i learnt from the last 5 pages of the emby thread about this, and posted before HERE). Nvidia is out of the question tho.
wont bother quoting the last 2 posts from @RedSocks157 and @atrus , but as far as i could see, it is NOT a funky tweak, it requiries little work to incorporate it (unless plex is not using stock/up to date ffmpeg), and it is available OUT OF THE BOX for windows, you need to get your ffmpeg in linux, and no idea on mac.
Maybe I wasn’t reading in the right place then. So it only requires a little additional work? Seriously, this should be in Plex yesterday. Plex costs $50 more and doesn’t even have a hint of an implementation of this.
it is not null/no work, they have to do stuff, but the heavy lifting was done in ffmpeg.
But i also read here that plex uses either their custom modified ffmpeg that is not made from a current source, or just the normal one, but an old version. Dunno why
@RedSocks157 said:
I believe currently it is a really funky tweak, but it’s better than nothing right? The AMD solution is open source currently, and since I use an old APU in my server that is what I would most appreciate. I’m not sure about the status on Intel’s QS code, and NV is almost certainly closed source unfortunately.
A funky tweak doesn’t sound like something devs should spend time on.
And as for Quick Sync (which this thread is about) on Mac, there does not seem to be anything anyone can do about it as Intel has not made the appropriate API´s available. I would love to read something about that if it proves me wrong. But I have found no evidence of me being wrong about that.
It’s just incredibly frustrating how long this feature has been requested and how many people have asked, and yet there has been zero progress made. Not even a real response or status update from a dev recently.
How can you even say that? Not even half a day has gone by since a dev responded. If you are referring to anything before November (which is the last time before today a dev responded) then yes, this feature request has taken a back seat due to the lack of a possibility to do this. It wasn’t until late summer that ffmpeg added support for this for one platform. There were tons of other things that tons of people wanted added in the mean time.
You would not believe how many times I have read a version of this in this very forum: “I can’t believe the incompetence of Plex, they have not added the absolutely crucial feature X and Y”. Everyone having different views on what is important. Yes, it is frustrating not to have your pet peeve worked on. I for one would rather see this not being added at all if that meant I was getting my pet peeve solved. That is how little I care about this compared to the feature I lack. I would trade in all other features for getting a better subtitle solution in place. Me being able to hit a button in the OSD and getting presented with subtitles from different sites from which I can download with the press of a button.
Subtitles are already supported in numerous ways. This hasn’t even been touched. And seriously, a huge increase in encoding power would make a big difference for a ton of users. Weighed against a small increase in ease of use for a few users who NEED subtitles, I think it’s pretty obvious which is more pressing.
It’s not lack of ability. They just don’t care. It won’t sell any more apps, because its a server side improvement and PMS is free. The technology is clearly there already but they have no motivation to include it.
Ok, Here is what QNAP does using their software, which if I am not mistaken is a flavor of Kodi and or perhaps Emby. I am going to try Emby once they have the 64bit version out on my AMD based Qnap Nas. :
Which video formats support hardware acceleration?
Applied Models:
• All NAS Series
Answer:
The following formats support hardware acceleration. Software decoding will be used for formats not mentioned below. The performance of software decoding will be limited to the system performance, and some video formats may not be played smoothly during On-the-fly transcoding. If this situation arises, consider using offline transcoding.
So the question is, why can Qnap do both Intel and AMD? Their core OS is not Windows either. And with their solution you can do multiple streams. Yes they are not as good as Plex in terms of features and interface but it allows transcoding without killing the CPU.
