limit disk usage by frontend
Posted: Sat Dec 30, 2017 2:19 pm
Hi, I'd like to request a couple of features that I think should be reasonably simple to implement.
Background:
My household consists of four people, my parents, myself and my sister. Currently we have two televisions equipped with old freeview (not HD) HDD recorders. One of these (used by my parents) runs from a roof mounted aerial, the other (used by my sister) has an indoor aerial. My access to TV involves recording programmes on my parent's box and then after they've gone to bed using a capture device to copy them off and then deleting them to free up space.
Reason for implementing MythTV
The OTA signal is really poor where we live, meaning that my sister's aerial needs to be positioned millimetre perfect or she loses channels or the picture gets messed up. My bedroom on the other side of the house has no signal whatsoever. My parent's system works fine unless a pigeon decides to crash land on the aerial, in which case there is momentary signal disruption which recovers shortly afterwards.
There is no cable service here and my dad does not wish to pay for a sky subscription.
The two boxes we are using are showing their age, with my parents' one occasionally exhibiting weird behaviour and has had to be factory reset on at least one occasion. Dad has decided they need replacing, and he'd like a networked system so there's only one recorder box running from the roof mounted aerial and the indoor aerial can be retired.
Implementation details
The system would be based around an AMD APU backend with a TBS quad tuner DVB-T2 card. There would be 3 frontends, one running on the backend machine (at least to start with) and the other two being networked computers.
The Request(s)
My sister is an obsessive recorder of TV. She records everything, her current box is permanently full. We need a means to limit the amount of disk space she is able to use on the backend (and possibly the number of tuners she can use) otherwise no-one else in the house would ever be able to record anything. She will only ever use her own frontend.
On a related note, limiting the view of the record schedules and recorded programs list by default to only show recordings scheduled/recorded by the frontend currently viewing the list. While being able to see the entire collection would be useful on occasion, most of the time my sister's crap would swamp the lists and make it a pain to find anything else.
My Theory
I think this could be implemented by having a frontend table with a unique id and possibly the static ip of the frontends to identify the frontend, and a column storing the disk limit. Then add frontend id in a column against the recordings and recording schedules, when a recording is scheduled an sql query is performed summing the filesizes of recordings made by that frontend id and if its at or above the limit, block the recording with an error. limiting list viewing would be a simple matter of WHERE `frontendid`= id
I could probably do this myself for mythweb if it wasn't object oriented.
Background:
My household consists of four people, my parents, myself and my sister. Currently we have two televisions equipped with old freeview (not HD) HDD recorders. One of these (used by my parents) runs from a roof mounted aerial, the other (used by my sister) has an indoor aerial. My access to TV involves recording programmes on my parent's box and then after they've gone to bed using a capture device to copy them off and then deleting them to free up space.
Reason for implementing MythTV
The OTA signal is really poor where we live, meaning that my sister's aerial needs to be positioned millimetre perfect or she loses channels or the picture gets messed up. My bedroom on the other side of the house has no signal whatsoever. My parent's system works fine unless a pigeon decides to crash land on the aerial, in which case there is momentary signal disruption which recovers shortly afterwards.
There is no cable service here and my dad does not wish to pay for a sky subscription.
The two boxes we are using are showing their age, with my parents' one occasionally exhibiting weird behaviour and has had to be factory reset on at least one occasion. Dad has decided they need replacing, and he'd like a networked system so there's only one recorder box running from the roof mounted aerial and the indoor aerial can be retired.
Implementation details
The system would be based around an AMD APU backend with a TBS quad tuner DVB-T2 card. There would be 3 frontends, one running on the backend machine (at least to start with) and the other two being networked computers.
The Request(s)
My sister is an obsessive recorder of TV. She records everything, her current box is permanently full. We need a means to limit the amount of disk space she is able to use on the backend (and possibly the number of tuners she can use) otherwise no-one else in the house would ever be able to record anything. She will only ever use her own frontend.
On a related note, limiting the view of the record schedules and recorded programs list by default to only show recordings scheduled/recorded by the frontend currently viewing the list. While being able to see the entire collection would be useful on occasion, most of the time my sister's crap would swamp the lists and make it a pain to find anything else.
My Theory
I think this could be implemented by having a frontend table with a unique id and possibly the static ip of the frontends to identify the frontend, and a column storing the disk limit. Then add frontend id in a column against the recordings and recording schedules, when a recording is scheduled an sql query is performed summing the filesizes of recordings made by that frontend id and if its at or above the limit, block the recording with an error. limiting list viewing would be a simple matter of WHERE `frontendid`= id
I could probably do this myself for mythweb if it wasn't object oriented.