indexing after reboot

[longneck]

If I reboot my computer after a recording has finished but before the show is inserted, then it never shows up. How do I fix that?

[patrick]

I am not sure I understand fully,

If you reboot your PC befor the recoding is inserted (indexed) how would you retrive the file? Is this what you are looking for?
SnapStream makes a temp file called sstemp If you have not recorded a show since the reboot its possible the show is still there. If the file is gone then the show is lost. (this file name is used on all recordings)

[longneck]

After recording, the file is renamed to index0.asf, right? Then the file is indexed. Then the file is renamed again to the final name, and inserted. Right?

If I restart my computer (or quit SnapStream) while the file is still named index0.asf, the show is never inserted and the next recording that happends overwrites this file and the show is permanently lost.

[rclayton]

Not to be a smart ass....but the fix is simple. Don't reboot until the index has completed. Is there a reason you 'must' do it before then?

[srigby]

Rclayton:

Your solution is similar to:

Patient: Doctor, it hurts when I move my arm.

Doctor: So don't move your arm.

Also, it can sometimes take an hour to index a large file - had this happen to me many times. Have also lost many recordings as the tmp file was deleted the next time SS was started.

Face it, their indexing process is fundamentally flawed and needs to be re-visited.

[patrick]

I have not forgotten this post. I want to check on something.

I do have a question though....

how long of a recording are you talking about that takes an hour to index? I have recorded numerous things and its never taken an hour to index the file. (well I suppose this is all relative to the speed of the PC...) However, I am interested in what takes you an hour to index. I am curious why you need reboot your PC before it finishes indexing.

Longneck has the correct information as far as what happens after the recording is finished recording. I am just confused why you would have to reboot?

rclayton has a good analogy but I actually like this one better (I am not trying to be a smart ass either I am just trying to understand why you would reboot in the middle of work being done?). If you worked for 6 hours on a project (on a PC) and then go to save your project and right in the middle of the save you reboot your PC how would you expect to have saved all the information? If I can understand why people would need to reboot before the indexing process is completed (and make the developers understand), then we can try to work out a solution for this. A lost show is a terrible thing!

[PBMax]

People have to reboot their computers. If I installed a new program and it needs to reboot then I would like to reboot now and get my work done then wait an hour for a show to index before I reboot. I have mentioned it before in my Wish list on my help page. If the program finds a temp.asf file then it will just reindex the file when found. It's suppose to delete the file when it's done with it right? That means that the show wasn't successfully indexed and should redo it. I had a problem with my computer locking up but I still wanted part of the show that recorded. This way I can see part of my show instead of missing it all.

[rclayton]

Wow, an hour to index? What length of time are you recording for? A 1 hour show for me indexes in about 10 minutes.

And back to the don't reboot and the problem is solved. I don't understand why you would be installed software at the same time your temp file was being indexed....I kinda think that's a bit of a no no....and a risk that you might lose the show.

I'm not trying to be insensitive about the problem...I hate when something goes wrong and I miss a show. But unless you are taping and indexing files all day, I don't know why the reboot (or software install) has to be done right away....

[longneck]

I don't know why I have to reboot. It doesn't matter. All that matters is that I do occasionally reboot before indexing is completed. SnapStream's behavior needs to be corrected.

In answer to patrick's question, a 1 hour show takes about 13 minutes to index on my computer, a P3 866 with 768 MB RAM.

[patrick]

I have made a note on this. I can see reasons for both sides of this.

[longneck]

Here's the compelling reason why this behavior needs to be changed...

SnapStream doesn't warn you when you shut it down that a file is still being indexed and it will be lost.

[Sean C]

I have lost a number of shows lately because of this.

Reasons for reboot: how about just a crash?? Does happen I can promise you that.
Maybe it isnt a reboot, maybe snapstream locks up.
Power outage (I live at the end of a line and it happens here fairly often - I have a UPS but it doesnt run forever)

Reason for long time indexing: How about because snapstream starts recording a second show immediately after finishing one, and being at a high quality setting takes up most of the CPU time? (actually this is another issue for me because the second recording drops frames due to the indexing of the first. I'd prefer they both waited for a quiet time to index, or a time I specify would be perfect).

Another reason for long time indexing: Because of other issues with snapstream, the only way I can record a show at 4.00am is to record a 5 hour long program. Do the math...

Regardless, it is a problem for some people, and it only has to happen to you once to be an issue. I think one of the problems is that snapstream uses the same file names for these things. If the temp file names were based on the show filename, at least they wouldnt get overwritten. And then after the reboot snapstream could just resume the files it didnt complete. Not that difficult a concept.

Incidentally, I think there is another file name in the middle of all that. I have noticed:

sstemp.wmv
index0
PVSB2.tmp
final filename...

[ May 29, 2002, 05:00 PM: Message edited by: Sean C ]

[PBMax]

bump

[longneck]

has this been addressed in Quartz?