You're right, will add a +1 there!
We are begginning to believe that "control inputs" are polled, not interupt driven. So if the CPU is 100% occupied doing something..you lose all control until it's finished.
I see, is that also why it doesn't immediately react to the Play command during fast forwarding?
I timed this and on my side its around 31 secs on an X2.
When it shows the Favorite screen if you have put it to boot default from favorites in setup, it is still busy starting up processes and network processes, I am sure it takes a bit longer then 15 secs.
Very well possible, I just "timed" it from memory. Will do a reallife timing tonight!
I have seen some more people having this effect, but as said, I don't have it while my disk in my synology are set to spin down too. I have the impression that it is heavily dependant what kind of disks are used and what the spin up time is on those before the Mede8er decides to show the message (and time out on the connection request by selecting the favorite).
Could be, mine are Samsungs Eco Greens, not the fastest disks out there. Can that time out be adjusted by just a few seconds?
Question: With what method did you create your favorites to your shares? Did you create those by browsing over network/workgroup under network, or did you use the My_shortcut under Network?
Used the browsing method.
And another question:
Have you tried to use NFS to connect to your NAS from your Mede8er and do you see the same timeout then too?
I used NFS from the start, ironically to prevent network speed issues ;-)