2005-03-31, 05:40 PM
Hi Sub,
I would like to see GBPVR have more options for disk usage. Seeing how everything (seems) to be stored in an mdb file, would it be that hard to point to a different disk for different files?
Two examples:
1) Two or more storage locations. GBPVR is told to save the next recording to which ever has more free space.
2) Multiple storage locations with size allocations. Can either be based on option 1, or use disk 1 until it is at its quota, then use disk 2 until it is at its quota, etc. This doesn't need to be perfect - Ie, if you set location 1 to 40 gb and you start a 3 hour recording, it can still all go to location 1 (it need not break the recording into multiple segments). But the next recording should then go to location 2, etc.
With the increase in use of networked attached storage and external disks, anything that gives GBPVR more flexibility to use multiple locations (without the need for archiving) would be a real asset.
Thoughts?
Josh
I would like to see GBPVR have more options for disk usage. Seeing how everything (seems) to be stored in an mdb file, would it be that hard to point to a different disk for different files?
Two examples:
1) Two or more storage locations. GBPVR is told to save the next recording to which ever has more free space.
2) Multiple storage locations with size allocations. Can either be based on option 1, or use disk 1 until it is at its quota, then use disk 2 until it is at its quota, etc. This doesn't need to be perfect - Ie, if you set location 1 to 40 gb and you start a 3 hour recording, it can still all go to location 1 (it need not break the recording into multiple segments). But the next recording should then go to location 2, etc.
With the increase in use of networked attached storage and external disks, anything that gives GBPVR more flexibility to use multiple locations (without the need for archiving) would be a real asset.
Thoughts?
Josh