EXTREMELY ANNOYED - Where Is Automatic Expire Set?

[acanthis]

I was using using SnapStream 2.0 (paid for) but I'm on the verge of uninstalling it after an experience today!

Where the hell is the setting to auto-expire recordings?

I can find nothing anywhere in the administration interface to set it! I didn't even know the damn program did it!

I come home today and find that SnapStream has decided to delete one of my recordings. I know it was SnapStream because it says so in the log file!!!

Where is this setting? Why is it set by default to delete a recording just 3 days old - a recording that I haven't even watched yet!

This is BAD BAD BAD! A program should NEVER EVER delete user data files without first warning the user, or without the user having explicitly configured that action. NEVER! There is no excuse. No exception.

Now - where is this dreadful setting configured? For the moment, SnapStream has been disabled, and without an answer, there'll be an immediate uninstall and a refund request.

Sincerely,

A customer seething with RAGE!

[amit]

The auto expire setting can be configured for each store. If you go into configure->stores, edit each store you have and set the maximum space and minimum free space settings to 0. This will ensure that no shows are automatically deleted.

[PBMax]

This setting should be defaultly set to zero and have the user define this setting. That way the user doesn't lose shows. This should be incorporated in the next build.

------------------
Current Projects:
Rav4MP3
Snapstream Support Page

[acanthis]

Originally posted by amit:
The auto expire setting can be configured for each store. If you go into configure->stores, edit each store you have and set the maximum space and minimum free space settings to 0. This will ensure that no shows are automatically deleted.

Sorry, but that is simply not true. I had already found those settings at install time and had set them both to 0, precisely to avoid this kind of thing. Yet, even with these set at zero, SnapStream still decided to delete the file.

Anyway, that isn't my point. My complaint is that the program made a decision for me and deleted one of my files without my permission, or without even advising me that it had done so! That is simply not acceptable. At the very least this behaviour should be explicitly configured by the user. For example, I should be able to say that I want new recordings aborted rather than deleting existing ones if there is insufficient space. Especially as you can't undelete the lost file because the indexing process has just trashed the clusters that the file occupied before SnapStream decided to delete it!

There should also be a "Protected" or "Read Only" attribute on recordings. If set, SnapStream can never delete them - only the user.

You won't convince me otherwise on this. The program's default behaviour is wrong, and it should be changed. And if you don't mind, I'll make the decision which recordings to delete from my machine, and when to delete them! Then I'll have nobody to blame but myself if I get it wrong.

[amit]

We will test this autmatic expire in house. There might be a bug associated with this. There is a "protected" tag in snapstream which will allow a show never to be deleted by snapstream. This option is called "Create fixed content" and is located in the advanced recording section of the a new recording or edit recording.