Thanks for the reply mm1352000.
In Windows 10 there is an issue with NAS not visible onder network section. You can find a lot about it on the net. Sure this is not TV Servers fault, but i did not said it was.
I like to have an other option than going deep into the database.
I used the NAS option because my TV Server is going to hibernation when it's not used and it keeps it playable for clients. But most recent technology makes this maybe less important as energy usage by HTPC's are decreasing, i have to think about that.
On 41 Watt usage i can maybe add a recording disk in the HTPC. OS is on SSD.
B.t.w. i never had, for >8 years an issue with latency. Timeshifting was always on SSD and Recording on the NAS. I have Gigabit ethernet cable network and Qnap NAS.
It's not a case of "going back". Tuner settings simply aren't imported. So, you can't set the recording folder that way.An export and adjusted import with paths (\\NAS\SHARE) was also not working, each time it would go back to the old, not working, recording path (X:\).
That's strange, as this is implicated on import page that it exports and imports settings. If you check after import the new settings are there. Obviously they aren't saved as i found out.
Can you please explain exactly what you consider "this issue" to be?Please fix this issue MP Devteam by making it possible to enter a path manualy by text instead of a selection box.
Obviously I understand what you're asking for. However I want to understand your perspective better:
Currently I respectfully object to your proposal for the reason that entering a path manually is error prone (typos etc.). In this context errors are serious because they directly lead to failed recordings. Failing to record is one of the worst things TV Server can do from a user perspective.
- why you think the change is necessary
- why your NAS/share(s) is not visible in the "network" section of Windows Explorer (which is not TV Server's fault)
- etc.
I also keep in the back of my mind that recording (or time-shifting) directly to network shares is not recommended in the first place. The increased file access latency can cause hard-to-debug problems such as glitches in recordings and/or live TV. Seeking (and channel changes) will be slower. So I ask myself: do we really want to make it easier to record to NAS?
In Windows 10 there is an issue with NAS not visible onder network section. You can find a lot about it on the net. Sure this is not TV Servers fault, but i did not said it was.
I like to have an other option than going deep into the database.
I used the NAS option because my TV Server is going to hibernation when it's not used and it keeps it playable for clients. But most recent technology makes this maybe less important as energy usage by HTPC's are decreasing, i have to think about that.
On 41 Watt usage i can maybe add a recording disk in the HTPC. OS is on SSD.
B.t.w. i never had, for >8 years an issue with latency. Timeshifting was always on SSD and Recording on the NAS. I have Gigabit ethernet cable network and Qnap NAS.
Last edited: