Luke 37009 Posted September 6, 2018 Share Posted September 6, 2018 A failing drive could cause any number of issues, yes. Link to comment Share on other sites More sharing options...
tdiguy 96 Posted September 8, 2018 Share Posted September 8, 2018 @@Luke, I saw a comment on another thread about a dedicated transcoding SSD which got me thinking. You previously said that it looked like my server was not transcoding fast enough which I dismissed because of my Xeon processor. My boot drive is on an SSD and that is also where Emby is installed. Now, when playing from my phone I am able to transcode at 480p @ 1Mbps but as soon as I bump the quality to 1080p or even just 720p @ 4Mbps I run into the streaming issue. My question is could a failing SSD be the root cause of all of these issues? It would make sense that I'm only affected on some devices and not all depending on whether the content would have to be streamed. I believe it may also explain the weird output of iostat on my zpool as well. If you have another drive in that machine it is pretty easy to change the transcoding directory / mount point and test the theory out. Link to comment Share on other sites More sharing options...
ShadowKindjal 19 Posted September 8, 2018 Author Share Posted September 8, 2018 I did and it sadly had no effect. It seems transcoding isn't an issue at all and I only have problems with playback on direct streams Link to comment Share on other sites More sharing options...
ShadowKindjal 19 Posted September 10, 2018 Author Share Posted September 10, 2018 (edited) @@Luke, I've done some more testing and would like your feedback. I know this has been a long running issue but I'm hoping this additional information may give you insight on what could be causing my issues. Right now the issues mainly seem to be limited to the Android Client. I tested playback on my Samsung Note 8 and Google Chrome both via a remote connection. The server has 150 Mbps upload, the Android phone had 70 Mbps download, and the desktop computer had 19 Mbps download. The Google Chrome browser was able to successfully play the a 18 Mbps video file via both direct streaming and transcoding down to 10 Mbps. There was no delay in start up and no freezing either. The Android client, however, was instantly able to start a "Direct Play" but would freeze about a minute into playback. Transcoding on that same video file took a long time before starting up even though it started immediately in the Chrome browser. Based on this I don't believe it's a network issue but possibly a problem with the Android Client? Would this make sense? Edited September 10, 2018 by nharmon Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 10, 2018 Share Posted September 10, 2018 It's possible, yes. Link to comment Share on other sites More sharing options...
ShadowKindjal 19 Posted September 10, 2018 Author Share Posted September 10, 2018 Should I start a new topic in the android mobile forum? Link to comment Share on other sites More sharing options...
Luke 37009 Posted September 10, 2018 Share Posted September 10, 2018 No, this is fine, thanks. Link to comment Share on other sites More sharing options...
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