HDD power saving issue (1 Viewer)

[Pawwlik]

Hi,

sorry about my english, I hope you will understand

let's imagine you have MP videos organized this way:

title directory
------------------------------
comedy \\server1\comedy\
scifi \\server2\scifi
.
.
etc

Problem is, that everytime I enter "My Videos", all of these harddrives or network drives wake up from the sleep mode, even if I don't want to enter their directory listing, because I have only their list displayed.

So every harddrive I have connected is unreasonably woken up 20 times each day and the lifetime of the disks is significantly reduced.

My idea is - when you enter My Videos, so you need to list only the list of titles, setup in the configuration. If you enter some of the directories this is the point you need to wake up the device by requesting it's content, not before.

I have tried to setup the folders as a ftp folders, in this case the disks are not woken up during MyVideos root listing but using these ftp folders is a big pain (Need to download the files, etc) so this is not a best solution.

Please think about it if this can be fixed. Thanks!

 

[piranha]

Did you try using not a share view, but the database view (by genre, by title) as your default view? This way it should not touch the shares at all.

 

[Pawwlik]

If you have a lot of TV Series updated nearly every day, you will not want to do Configure each time to update your database.

I have described the problem from a pure logical point of view.

If you want to display a list of shares (root shares My Videos page), there's no need to retrieve their directory listings yet, you do not need them and you do not see them. So there should be a list of shares, updated from the database only.

At the moment you try to browse into one of the shares, then you need to get it's content listed. Not sooner. Do you see what I mean?

 

[piranha]

If you have a lot of TV series, you should really use the TV Series plugin to manage them.
I understand your point and agree with it. Was just giving a suggestion on how YOU could solve that problem without having devs look into it (it would be probably very low on priority of to-do list)