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