ebr 16169 Posted July 31, 2016 Posted July 31, 2016 Do you have the server log that goes along with that app log you sent me? It was July 29 at 13:24.
Ando 0 Posted July 31, 2016 Posted July 31, 2016 Hi I'm having the same problem on Galaxy note 4 phone using Android Emby App ...it's not releasing the tuner. Server CPU at onset is 5% at viewing CPU is 50% after making a bandwidth change it jumps up to 90% , closing of Emby app on phone the CPU stays engaged at about 50% on server. Is there any help for this
Luke 42077 Posted July 31, 2016 Posted July 31, 2016 Hi I'm having the same problem on Galaxy note 4 phone using Android Emby App ...it's not releasing the tuner. Server CPU at onset is 5% at viewing CPU is 50% after making a bandwidth change it jumps up to 90% , closing of Emby app on phone the CPU stays engaged at about 50% on server. Is there any help for this Hi, welcome. There is always help. The first thing to do is follow the instructions in how to report a problem, then we'll do our best to get you squared away. Thanks!
mit3gt 6 Posted August 1, 2016 Posted August 1, 2016 (edited) Do you have the server log that goes along with that app log you sent me? It was July 29 at 13:24. The server log was to big to upload so I started over. I just sent you the log from the nexus player a couple of minutes ago. User is test. I tuned to channel WXYX. Here is the server log: server-63605264358.txt Edited August 1, 2016 by mit3gt
homerfan 3 Posted August 2, 2016 Posted August 2, 2016 Hi all, hoping to chime in here when I get a chance. Currently on the train to work. I seem to have a similar issue but, this whole time I thought the culprit was ffmpeg. Last week I changed my build to to an Intel processor and enabled Intel QSV hardware transcoding. Since then, I only see this issue when a device transcodes a live stream. I have to then log into my windows machine and manually kill the ffmpeg process. I'll upload some logs as soon as I get to work.
ebr 16169 Posted August 2, 2016 Posted August 2, 2016 Please try again when you get beta .28. Thanks.
ebr 16169 Posted August 2, 2016 Posted August 2, 2016 Hi all, hoping to chime in here when I get a chance. Currently on the train to work. I seem to have a similar issue but, this whole time I thought the culprit was ffmpeg. Last week I changed my build to to an Intel processor and enabled Intel QSV hardware transcoding. Since then, I only see this issue when a device transcodes a live stream. I have to then log into my windows machine and manually kill the ffmpeg process. I'll upload some logs as soon as I get to work. This is more than likely something else - unless you are talking about ServerWMC and this app specifically. Transcoding or not should not matter.
mit3gt 6 Posted August 2, 2016 Posted August 2, 2016 (edited) Please try again when you get beta .28. Thanks. That seems to have done the trick! Great work. Live TV is almost complete. Now the only issue I have is that pesky time shifting. Any chance we will be seeing this in an upcoming beta in the near future? I'm all about transcoding if that's what it takes to make it work. Edited August 2, 2016 by mit3gt 1
McChen 7 Posted August 3, 2016 Author Posted August 3, 2016 i can also confirm that the .28 beta fixes the problem, tuners are once again releasing properly
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