Normal
Hello Jay The timeshift file contraints are effectively applied on a per user basis.As such, it doesn't really matter how many tuners you have. The more important figure is how many clients you have timeshifting concurrently.Each client that is timeshifting a channel could use up to [timeshift file size] * [max number of timeshift files] worth of space.If you only have one client timeshifting at any given time then I would set the constraints based on that. In other words, you could set the maximum number of timeshift files to 31 (deduct 256 MB for overhead). That would use your full 8 GB.If you had two clients with identical use patterns, you'd need to drop to 15 (31 / 2, round down). etc. mm
Hello Jay
The timeshift file contraints are effectively applied on a per user basis.
As such, it doesn't really matter how many tuners you have. The more important figure is how many clients you have timeshifting concurrently.
Each client that is timeshifting a channel could use up to [timeshift file size] * [max number of timeshift files] worth of space.
If you only have one client timeshifting at any given time then I would set the constraints based on that. In other words, you could set the maximum number of timeshift files to 31 (deduct 256 MB for overhead). That would use your full 8 GB.
If you had two clients with identical use patterns, you'd need to drop to 15 (31 / 2, round down). etc.
mm
