Black Hole
May contain traces of nut
Fair enough, but this might need some thinking about - it doesn't fit within my knowledge of how things are supposed to work. Any ideas BYTs? - refer to my comments in post 258.
When we were looking into network shares originally, people tried mounting as 'virtual folders' under My Video and ran into problems (from memory):
- It is too easy to delete the share - then the Humax client starts recursively deleting all the files on the server (possibly a NAS drive). This has happened (somebody did it twice!). It has been suggested you mount it read-only, but then you can't update the sidecar files with the resume point and bookmarks etc.
- The DLNA indexer doesn't know about network shares, so it will spend a lot of its time exploring the server and indexing it (you could turn off content sharing if you don't need DLNA streaming from the client, that would stop it - but also disable the custom decryption methods).
- Some custom packages (on the client) look for things to do by recursively walking the My Video contents, and although we might expect the DLNA indexer to have been written not to slug the processor too much we don't have so much control over the time slicing in the custom software. A convention is proposed that all folders starting "[" are exempt from being crawled, but I'm not sure this has been universally implemented. Certainly in the early days people experienced their Humaxes grinding to a crawl because of the network traffic induced.
- Some users have experienced difficulty with the Humax getting confused how much disk space it has left, with erroneous readings on the pie chart and refusing to record due to 'lack of space'.
