My energy rates have skyrocketed in the last couple years (+40%) and so I have set both my NAS to hibernate after 30 minutes (there are several times throughout the day where one or both of them turn on unexpectedly, so I want them to turn off “quickly”, and yes, I’ve done everything I can to avoid unexpected wakes. Also, my usage is too erratic to set up a schedule). Unfortunately, this means that about every time I come to Infuse, I have to wait for my devices to wake up. The Infuse timeout is too short and I get the error pop up and have to restart playback. Please increase it. Since everyone may have different hibernation, wake up times, I suggest having a variable setting for timeout from 30 seconds to five minutes.
Just curious have you timed your NAS from the wake packet to when it’s ready? I was wondering how much time is “average” for NAS wakes.
Hi, I recently replaced an old self built NAS which never hibernated with a Synology which does (and uses much less energy when asleep).
My tvOS Infuse library is fed by Jellyfin with library mode on.
I’ve never had playback issues in Infuse with the old NAS, I imagine because the hard drives didn’t idle.
With the Synology, if it’s hibernating and I open Infuse, navigate to a movie/show, hit play - I get a spinning orb for about 5 seconds followed by the message ‘An error occurred loading this content’:
If I close the message and hit play again it loads fine. I assume because the Synology was woken with the first request.
I’ve seen other similar threads which have suggested adding the server MAC address into the Advanced section of the Share to send a WOL request. But this isn’t available for Jellyfin shares.
Could the timeout be extended/add a retry on the first play attempt to allow the Synology to wake up and serve the content? Or any other ideas?
To cover the wake times after I’m in Infuse I just adjusted the hibernation time to 3 hours. That keeps the drives awake for most videos and if it’s longer than 3 hours then I need a break anyway so the spin up time doesn’t matter.
As to the spin up when I launch Infuse I usually check the activity indicator on the home screen and wait till it settles down. Then all seems to work.
I think extending the timeout may be chasing a moving target for the devs, since potentially users could have all different spin up times due to hibernation time settings, drive types, number of drives, type of raid selected, NAS background cleanup running etc that could be adding to the length of time till the NAS is ready.
I will say that after extending the time to 3 hours I rarely if ever get the error message since other things hit the NAS also throughout the day so that has helped keep the drives available in that respect also.
This can be a variable setting 1-5 minutes or something.
3 hrs would help or you can set up a schedule to wake it at specific times.
Unfortunately with energy costs as high as they are, I’ve set mine to hibernate after 30min. So it would be nice to have a longer timeout.
I moved your posts to this suggestion thread.
Don’t forget that you need to click the like button on the first post in this thread to show your support for this suggestion! 
1 Like
It seems that the current timeout is 25 seconds or so. My devices wake anywhere from 35 to 45 seconds. So for me, I think 1 minute would be a good amount.
1 Like
That’s about where I’m at also. I wonder if it differs for those that have the deep sleep mode in addition to the hibernation.
Mine is a freshly set up NAS, and all power settings are at default. Just checked and HDDs hibernate after 20 mins. But I’ve had no issues once playback starts.
I only really have an issue on first use of the day on the weekend or after work weekdays. In both of these cases 3 hours wouldn’t work - it’s usually been at least 12 hours since last use. At that point hibernation isn’t worthwhile at all. As munpip214 mentions, with high energy prices and just gernally being sensible with energy use I’d rather not switch hibernation off.
I also did some further testing:
- Ensure Synology is hibernating, hit play in Infuse, then using the Siri Remote exit back to the show/movie info screen before the error pops up. Then as soon as possible hit play - it plays fine. So the timeout increase doesn’t have to be long.
- On Windows with MPV player… Opened file explorer showing a movie file stored on the NAS. Waited for the NAS to hibernate. Then dragged the file from explorer into MPV. The NAS woke up and the file played. It took a little while whilst it waited for the NAS to start serving, but no errors. Subsequent attempts were instant as expected.
- On iOS I added my shares via NFS. Same timeout issue, this was just to rule out Jellyfin libraries being the cause.
In the Windows and MPV test above I timed it at about 15 seconds. This was from dragging and dropping the file to playback starting.
1 Like
Same here, once playback starts I’m good to go for that session
1 Like
I’ve been thinking about this too, instead of setting timers on Infuse, I imagine it could just “keep alive” the connection to the server by pinging it periodically even when it’s not streaming, just when Infuse is open, playing or not. Is this feasible @james ?
At the moment my workaround for this issue is to set the streaming cache the shortest as possible (I believe it’s “Legacy” or “Memory only”) so Infuse reads from the server more or less continuously instead of caching the whole file on the ATV’s storage. I believe with a timeout of 30 minutes on your server, you should almost never run into this issue again, unless you pause content for longer than that.
I’m using a Synology DS1618+ with DSM 7.2.1, and just to be clear, by “hibernation” it seems what you mean is actually turning off the NAS, right? You can also “hibernate” the hard drives so they just spin down. Synology doesn’t have a hibernation or sleep modes like on Windows, just disk spindown and power off/on.
I used to let it turn off after 20 min (10 min spindown + 10 min wait), and it would turn on with WOL from my phone or the Apple device (using SMB or WebDAV). It takes about 1 minute, so both the streaming and the library sync were timing out, and so I disabled WOL in Infuse by erasing the MAC address from the config and instead had to wake it manually 1 minute before I wanted to use Infuse. To avoid this hassle now I’m only hibernating the disks, and they wake in a short enough time that I’m not getting timeouts when starting streaming or library sync.
FWIW my DS1618+ with 6x20TB shucked WD drives consumes 30W in spinned-down mode and about 60-62W when streaming. Ideally Synology would have a S3 sleep mode like Windows but it seems NAS OSs don’t like offering that cause they’re “supposed” to run 24/7.
For me it’s just HDD hibernation. I don’t poweroff.
I’ve not measured mine yet, the tech specs for the 1522+ with 5 disks show 52.06 watts (Access), 16.71 watts (HDD Hibernation). My old NAS was an HP MiocroServer N54L with 4 disks, which didn’t hibernate the disks and it used a constant 47 watts.
If you really want to go down the rabbit hole with NAS information I found a site that can ruin your sleep cycle (your personal sleep cycle, not your NAS).
I have found that enabling the hibernation logs can actually cause some unwanted wakes.
In my case, the HDDs wake fast enough that Infuse doesn’t time out. Around 13-15 seconds it seems. I do wish the DS1618+ idled in the neighborhood of 16-20W though or less. I also don’t like the fans running 24/7 even when idle power is not a big issue.
Cheers, I only enabled to investigate this issue. But will remember to disable again.
Interesting. When I measured (post 9), I got about 15 seconds. But I get timed out on both iOS + NFS and tvOS + Jellyfin. Might do some further testing.
Side note I love my Shelly relays.
Further test, this time on tvOS using the VLC app. Connected to the NAS using NFS. From pressing play whilst the HDDs were hibernating to playback starting took 26 seconds. And more importantly - it didn’t time out like Infuse does.
Significantly longer time than my Windows test. However, this time I was watching the NAS and the HDDs were definitely hibernating when I hit play on the remote. I don’t have line of sight with my Windows machine - I’m going to retest that. There’s a chance I already woke it before testing playback.