I don’t know about Juice, but that’s not what I was referring to. You can’t keep the drives spinning if there is nothing going on. I was referring to the hibernation/sleep mode. The delay is not caused by the drives spinning up from idle to active, it’s from sleep/hibernation to active. By not letting your NAS set your drives to sleep/hibernation mode, they can spin up faster and prevent this delay. The power savings of using this sleep/hibernation, to me, is not worth the delay of waiting for the drives to come out of that mode.
With the controls I have - there is no way to spin down the drives without putting them to sleep. Bringing them back up from sleep - takes way too long. If they are, in fact, spinning down when not reading/writing - I have no way to know if that’s actually happening (but it would be fine, if it were).
I only have a couple of WD Externals and that software doesn’t have a lot of options. I can’t spin down my local drives without putting everything to sleep. That’s not going to happen either.
One of my NAS’s is a WD My Cloud EX4100 with four WD Red drives – what I’m talking about is when Drive Sleep kicks in via the energy save option. When the drives are ‘asleep’ and plex makes a call to play something it takes a few seconds to wake up all 4 drives and sometimes then the time for the item is presented as 2:00:00.
I think @anon18523487 is onto something with the transcoder. Thinking about it some more from my experience it does seem to happen when the client is transcoding but I cannot say with 100% certainty.
From a deep sleep my WD My Books come alive in 10-15 seconds - an eternity.
IF they’re spun down when I call on them now - I’d never know it. As far as I’m concerned access is instant. At least that’s what I see. (makes me think they’re spun up and ready - could be wrong).
I think the WD My Books have 1 or maybe 2 drives at most. The number of drives could be a factor here as I have 4 in RAID5 setup on my NAS.
I have two - a single 8tb red in each one, so yea, different animals. The only option I have on power saving is sleep and that’s unacceptable for me. 15 seconds from cold to working is way too long for me.
If the time were extended to cover the ‘wake up’ - it wouldn’t affect me, so I wouldn’t mind.
@anon18523487 may need some ‘wake-up’ times to report to HQ with. For me 10-15 seconds from cold to working.
1 Like
My WD’s wakeup and spin up in about 12 or 13 seconds so about the same
again, that’s literally what I’m talking about. unRAID is putting these disks to sleep, idle, spun down, hibernation, whatever you want to call it. unRAID calls is spinning up a disk and spinning down a disk. this is what I’ve seen thousands of people refer to it online through my 20+ years in the tech industry.
if you have a special word for it, fine. you obviously know what I’m referring to so I don’t understand the need to be pedantic
using a stopwatch on my phone, started right when I click the play button of a video that is on a drive that is sleeping, spun down, idle, hibernating, whatever you want to call it.
it’s taking me ~13 seconds from the press of the play button to the beginning of it starting to play the episode
I get the issue. I’ll see if I can reproduce and then confirm it’s the delay causing the issue. If that is the case, I’m sure something can be done.
I appreciate the help.
For what it’s worth. I also use the Plex Media Player Windows program and the web player on the same network (so it’s accessing the same content on the same drives and waiting the same amount of time for them to spin up) and I don’t see the issue on those players.
So it does seem to be isolated to just the Android application itself rather than the PMS software (or the network for that matter).
Thanks again
@Endda its not just android, I see this using a WebUI via a browser.
Based on what has been said above its probably transcoding related , I bet the Media Player for Windows is not transcoding the content which is why you don’t see it on that client. Android is most likely transcoding.
I have the exact same issue, however it only occurs when I am using the web app playing in Chrome on Windows 10. When I use the iOS, PS4, or Apple TV apps all is well.
Same here. I’m using a FUSE mount to play content from though.
Adding a +1 for this issue occurring in WebUI. Has been a consistent issue after moving my Plex install over to Unraid (Docker). Sounds like that is similar setup with others in the thread so may be a factor.
I have also been having the same issue. Constantly a problem on videos less than 2 hours or more than 2 hours. I cannot seem to get them to show the correct time. Makes some movies unwatchable without directly accessing my files instead of using the Plex player.
I am very hopeful for a fix to this.
+1 been seeing these same issues for the past few years. Similar server and HD setup as others. Happens with TV shows showing as 2 hours. Hard stops movies that require transcoding at 2 hours. Usually restarting the show or movie corrects them. Had my movie hard stop at the 2 hour mark on AppleTV tonight. I have searched for a fix over the years, only to stumble on forum posts like this one where everyone is aware of the problems but nobody has a fix yet.
Also hoping for it to resolved soon.
@anon18523487
Would additional log files be helpful at this point, or do you all have enough to work the issues?
I’ve been seeing this a LOT recently, as in 10-20% of the shows I watch.
Any progress on it? I’m using a W2016 server and never had the issue this bad until around 1-2months ago.
I’ve been paying for the year sub for … years ;), never noticed this issue as bad. Might have had it happen once every 6month or something but never daily.
Just wanted to bump this as well. I’ve been having this happen for a few months and it also seems to be getting worse. I’m running mine on PC which is never set to hibernate (as the original thread appeared centered around).
I also have this issue in the web player, running Plex 1.19.4.2935 on macOS.
