Duplicate recordings when archiving

[Soundman]

Hello. I have PVS configured to record all episodes of a few programs. However, I have to archive them to removable media frequently because even 0.6 terabyte is not enough to store everything.

However, when I burn them to CD/DVD, it makes SS forget that it ever recorded them, so it may grab the same episode again.

Can anyone suggest a way to prevent this?

Thanks,
Soundman

[RobertH]

other than leaving them on the disk nope

[CO_Coding_Cub]

This is something that's come up before. Users have shown interest in more advanced series options, like "Record every single airing" "Record if not currently on disk" (the current mode) and "Record if not previously recorded".

Not sure if/when SS will implement this, but it has come up in the past.

[Soundman]

Thanks for the replies. Let's hope SS addresses this in the future. Archiving to removable media seems like a natural thing to do with a product like PVS.

[Dinki]

BUMP

I'm running into the same problem. I am surprised that this capability can't be incorporated. Can someone tell me how Snapstream knows if a program has been recorded?

I've tried creating a link (shortcut) with the same name as the recorded file to try and 'fool' Snapstream into thinking that the program is still on disk, but that didn't work. Is the program information kept in a database somewhere???


HELP!
________
buy glass pipes

[WillP]

I believe that each episode has a unique ID associated with it. I think PVS adds this ID to the mpeg tag, so you would have a hard time fooling it.

If I'm wrong here, please someone correct me.

Will

[RobertH]

Yep each program has a unique (well fairly unique) ID that is stored both in the SlaveStoreCollection.xml file (updated dynamically dont bother changing it) for ease of use when checking the DB and it is also stored in the MPEG / AVI / WMV header block written to the file, the only way to fool it into thinking the show was recorded would be to leave it on disk.

[rkuo]

This will most likely be dealt with in a 3.5 timeframe. The way I think it's going to work is we'll maintain a list of "recent" recordings that we'll avoid recording and which expire after "x" amount of days.