pyraxic 0 Posted December 7, 2018 Posted December 7, 2018 I am running openmediavault with RX 570 4gb. I have enabled AMD AMF for transcoding but it doesn't seem like Emby is using it. `top` shows ffmpeg taking 100% cpu Wanted to find out if I can use AMD transcoding?
Luke 42077 Posted December 7, 2018 Posted December 7, 2018 Hi there, can you please attach the emby server and ffmpeg log? thanks.
pyraxic 0 Posted December 7, 2018 Author Posted December 7, 2018 (edited) https://pastebin.com/KGNN0B2e https://pastebin.com/LZJ3Wx5T Edited December 7, 2018 by pyraxic
Luke 42077 Posted December 7, 2018 Posted December 7, 2018 In this example the video is being stream copied, which means no video transcoding is occurring. So this example is actually inapplicable.
pyraxic 0 Posted December 7, 2018 Author Posted December 7, 2018 It would still use 100% cpu with ffmpeg process?
Luke 42077 Posted December 7, 2018 Posted December 7, 2018 ffmpeg will always try to go as fast as it can and use all resources available. that's just the way it works. we're introducing a throttle feature with the next release so stay tuned for that.
pyraxic 0 Posted December 7, 2018 Author Posted December 7, 2018 I tried running a UHD movie and it is extremely choppy and shoots my system load to 3. I am attaching the logs to see if I am doing something wrong. https://pastebin.com/n9i4gh4R https://pastebin.com/PJh7sL60
Luke 42077 Posted December 8, 2018 Posted December 8, 2018 Then I think you will enjoy the throttle feature with the upcoming 3.6 release of the server: https://emby.media/community/index.php?/topic/62657-36040-transcode-throttle-is-back/ Thanks.
pyraxic 0 Posted December 8, 2018 Author Posted December 8, 2018 So this has nothing to do with transcoding even playing UHD?
Luke 42077 Posted December 8, 2018 Posted December 8, 2018 In this example, no transcoding is occurring we are still using ffmpeg to repackage the media info a different container. ffmpeg will always want to go as fast as it can by using all available resources, so this is where I think our throttle feature will help you quite a bit. When ffmpeg gets really far ahead of your current watching position, it will dynamically slow the process so that it uses less resources, and then go at a slower pace from there on out.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now