SuperSimpleArchiver

[pBS]

status=2 means it's a done recording...not a scheduled one...

STATUS_PENDING = 0
STATUS_IN_PROGRESS = 1
STATUS_COMPLETED = 2
STATUS_COMPLETED_WITH_ERROR = 3
STATUS_PLACE_HOLDER = 4
STATUS_CONFLICT = 5
STATUS_DELETED = 6

so do a sql query like:SELECT filename FROM recording_schedule where status = '2' ;
then eval paths, then could adjust path yourself with line from reloc.bat

i have a sqlite3 func for autoit use...let me know if you need it..
[the solutions i found weren't really built well, the one i use includes .dll inside..]

[liteswap]

Thanks - will give it a try...

[liteswap]

OK, after much labour here it is - not complete yet but it is working on my machine. The attachment includes source and executable.

It includes multiple overspill areas, and pulls its video list from the sqlite db.

To use: put it where you like, and follow the instructions on first run, which will create an ini file in the same folder as the executable. You can of course edit it later. To give you an idea of the ini file format, here's my test ini:

Code:

[Main]
FullPathLogging=True
MinPVRSpace=50
DebugMode=False
[Overspill]
Overspill1=C:\Users\[i]<username>[/i]\Documents\testOverspill1
Overspill2=C:\Users\[i]<username>[/i]\Documents\testOverspill2

Bear in mind that the debug mode entry will at some point vanish, so don't mess with it . Of most interest are:
1. MinPVRSpace: PVROverspill will keep archiving until this amount of disk space (in GB) is available on the PVR, then it will stop.
2. Overspill1... Add as many as you like manually if you wish. Until I finish the config utility, that'll be the only way, apart from deleting the ini file, that you'll be able to add more paths after the initial run.

Enjoy.
--
[ATTACHMENT NOT FOUND]

[liteswap]

PS: Now working on adding email reporting....

[pBS]

you do know you can just change the recording path and restart rec service to make it stick for instant new free space...

old shows stay where they are, but new ones will go to new rec dir...
could even change it back once some stuff is deleted...no adjustments necessary ever..

maybe make that as an option? really easy to pull off...
[knida like an 'alternate mode' with similar ends..]

[liteswap]

You mean, dip into config.xml, change <RecordingsDirectory>, restart the service and the old recordings remain live in gbpvr.db? Never tried that...

It means you could leave an app running that checks disk space available once a video has finished recording how much space is left, then switches over to overspill if minimum reached. Hmmm - how much time did I just spend writing this app? !

[pBS]

well, they both have their drawbacks...
for rec dir change, gotta restart rec service, which means can only be done in wee hours of night safely..
[check if recoording or updating first]

and obviously copying takes time...but gives you control over what goes where..
[and rec service never needs restarting..always a caution]

[gEd]

you do know you can just change the recording path and restart rec service to make it stick for instant new free space...

old shows stay where they are, but new ones will go to new rec dir...
could even change it back once some stuff is deleted...no adjustments necessary ever..

maybe make that as an option? really easy to pull off...
[knida like an 'alternate mode' with similar ends..]

I was very tempted to make the same observation but I then has some reservations and I also didn't want to p1ss on Liteswaps bonfire...

Flipping the recording drive has the obvious advantage of eliminating the copying of files acrosss drives. But when I thought about it some more, I decided that achiving away from your primary recording drive onto archive drives is probably a more effective strategy.

By flipping the recording drive (multiple times), you might eventually find yourself with multiple drives, each of which has "some" free space on it.

e.g. R: drive fills up to within say 5GB and I flip to S:. I delete recordings over time and eventually end up with 60GB of free space again on R: Meantime S:is down to 20GB free. So I flip back to R: Space on S: is slowly released (as I delete shows) and I end up with almost the same amount of free space on both drives. What would the script do then? Depending on how long you keep vs delete recordings, you may end up constantly juggling.

By archiving away to always maintain (say) 50GB on recording drive, when you archive drive fills up, you just add a new drive (or so a mass delete of all the shows you never did get around to watching).

just my £0.01

[pBS]

i hear ya, like i said, both have drawbacks, and both have benefits..
i just figured, people come for a solution, and having both would give them choice..
[and the second type is so easy to implement]
but as SSA author i do like the archiving method as well..

archiving is best when using usb or removable drives for spillover..but it requires time and cpu...
changing rec dir is only good for local full speed drives..but it's single instant action..

i wonder if there's a good way to make a warning when all space is low...
[besides email, tho that is needed]
maybe change the background of the skin or audible alerts?
[adding a 'voice' alert only requires like 2 lines in autoit ]
"Warning,Warning, Disk space is low"
or just play a wave file...

audio alerts are nice cuz they can run in background, and don't interfere with normal operations at all..

[liteswap]

Must admit, I prefer the archiving route simply because it automates things more: I see the script as a tool for a PVR rather than a PC that does a bit of media stuff on the side, so anything that lessens the interaction the user has to make with the gizzards of things is a good thing in my book .

But I'm open to ideas...an email warning of low disk space was my next project-ette...