[mythtv-users] Immediate autoexpire recent rec. despite plentyof old rec. to expire

warpme warpme at o2.pl
Wed Oct 30 14:26:09 UTC 2013


Dnia 30 października 2013 14:27 "Michael T. Dean" <mtdean at thirdcontact.com> napisał(a):
Also, another way to balance your recordings is to move any 
non-auto-expirable (important/planning to keep) recordings from Watch 
Recordings to Video Library--where you (and not MythTV) manage disk/file 
system placement. It's also a much better location for (TBs of) 
recordings you plan to keep long term, anyway, because it has a better 
UI for handling large numbers of videos--after all it was designed for 
exactly that purpose. See 
http://www.gossamer-threads.com/lists/mythtv/users/510542#510542 and 
http://www.gossamer-threads.com/lists/mythtv/users/519758#519758 and 
http://www.gossamer-threads.com/lists/mythtv/users/519996#519996 .
Mike
_______________________________________________
mythtv-users mailing list
mythtv-users at mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Mike,
 Thx You find time replay to this.
 
Your mythtv support is hard to overestimate!
 
Just some remarks from my side:
 I full share You view about watch recordings (WR) vs video library (VL) in respect to recordings user want so keep permanently.
 In past I was trying to use this approach and I quit it because:
 
1.AFAIK there is no mythtv UI command to do this. IIRC it might be done with help of user jobs + .py script but this .py has so many problems for me that I quit this approach
 
2.even if rec. is moved to VL - description is missed (t.b.c)
 
3.Finally and most importantly - this approach is not solving another goal I need to solve: archiving.
 
I would love to learn that above reasons are my mistakes - not current mythtv limitations.
 
While 1&2 can/will be solved, with 3 - in my case - I ended with different approach. 
Why: because keeping all permanent recordings on-line isn't optimal IMHO. 
With such approach there will be always lack of space. How many space I can have on-line - 6T, 15T, 40T....
 Why such huge on-line space - if on-line space I need is only for things which are not yet archived?.
 I watch archived things one per 6-12months. 
Providing on-line access to them with cost of on-line power, cooling costs and server I/O occupancy is for me not optimal in long-term.
 
I want ultimate solution where:
 
-user marks rec. to archive (i.e. move it to dedicated archive rec.group)
 
-when user attach ext HDD - rec will be MOVED to this library ext.HDD. User can still watch it.
 
-when user disconnects ext HDD - mythtv UI will mark all recs with 'Off-line'. When user will try watch such recording - myth will display banner "this rec. is archived". Pls connect et HDD to watch it.
 
-when user attach ext HDD again - 'off-line' marker in rec will be removed and user can watch it.
 
-when user deletes rec. in  archive rec.group then durring next ext.hdd connect it will be automatically deleted.  
I managed POC of such solution with help of udev/systemd/sh scripts and it works well from functional perspective. 
(I have 3 dedicated archive rec. groups and 5T on 3 ext HDD to store them).
 
I saw myth development is preparing ground for such scenario (.mxml import/export, etc) - which is great. 
Lets hope soon we well be closer to properly realize usage scenarios like I described :-)       
all the best 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20131030/ba052583/attachment.html>


More information about the mythtv-users mailing list