i've written a util to help make ntfs links to other drives for chosen dir.
basically it pops up a chooser box with your Recordings dir in it, choose a dir/series to move off to another drive, then another popup for where to move it to, then starts moving existing data.
after it's all moved, it makes a NTFS junction from original dir to new one.
after that, it's just like a shortcut to the other drive's directory..
really helps with multiple recordings at one time, as you can spread them over mulitple drives.
and everything looks like it's still in original drive/dir.. so no adjustments necessary..
just lots of free space and less drive torture during simultaneous-records...
i'll add in command line processing so you can do it from the remote later..
right now it looks up your recording dir from config.xml and sets as root, so only those dirs to choose from..and copies everything with progress so you know how long it'll take for those long ones..
also have to check to make sure can make new dir...[can't already exist on target]
only requirement is the main recording dir be ntfs, which it should be anyways for tons of reasons..
gui is just a helper app, tech is all windows...
Now finished: been using it for months with no probs..
Made with Autoit3 so source included inside..
Moves a single dir[Series] at a time with progress, all existing recordings, and any future recordings to that dir will be in the target dir.
Only needs to be done once for each dir you wish to offload..
Can be done in advance if you create the source dir first.
Added as much error checking as i could think of, *should* be interrupt-able at any time without losing anything..Also checks for valid source/destination paths, and limits source choice to gbpvr/config.xml derived recordings dir... makes sure destination is same size as source before assuming copy is good. etc.
It can use network paths as target,as well as non-ntfs drives,[tho i'd suggest against net/fat/fat32]
Added display of existing links on startup..
Will probably add a drive list with space free on startup, and double checking paths for ntfs to lock out fat32 destinations[because of 4gig limits].
To undo a link, simply delete the link and copy the files back from the target.
While you get used to it, keep AutoRemoveMissingRecordings>false
basically it pops up a chooser box with your Recordings dir in it, choose a dir/series to move off to another drive, then another popup for where to move it to, then starts moving existing data.
after it's all moved, it makes a NTFS junction from original dir to new one.
after that, it's just like a shortcut to the other drive's directory..
really helps with multiple recordings at one time, as you can spread them over mulitple drives.
and everything looks like it's still in original drive/dir.. so no adjustments necessary..
just lots of free space and less drive torture during simultaneous-records...
i'll add in command line processing so you can do it from the remote later..
right now it looks up your recording dir from config.xml and sets as root, so only those dirs to choose from..and copies everything with progress so you know how long it'll take for those long ones..
also have to check to make sure can make new dir...[can't already exist on target]
only requirement is the main recording dir be ntfs, which it should be anyways for tons of reasons..
gui is just a helper app, tech is all windows...
Now finished: been using it for months with no probs..
Made with Autoit3 so source included inside..
Moves a single dir[Series] at a time with progress, all existing recordings, and any future recordings to that dir will be in the target dir.
Only needs to be done once for each dir you wish to offload..
Can be done in advance if you create the source dir first.
Added as much error checking as i could think of, *should* be interrupt-able at any time without losing anything..Also checks for valid source/destination paths, and limits source choice to gbpvr/config.xml derived recordings dir... makes sure destination is same size as source before assuming copy is good. etc.
It can use network paths as target,as well as non-ntfs drives,[tho i'd suggest against net/fat/fat32]
Added display of existing links on startup..
Will probably add a drive list with space free on startup, and double checking paths for ntfs to lock out fat32 destinations[because of 4gig limits].
To undo a link, simply delete the link and copy the files back from the target.
While you get used to it, keep AutoRemoveMissingRecordings>false
Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie