Auto GK Timeout while indexing

[pidhead]

I would like to test file mode on a HD capture I have, but I keep getting this message during the indexing step:


[9/9/2004 1:27:47 AM] AutoGK 1.54b
[9/9/2004 1:27:47 AM] OS: WinXP (5.1.2600).2
[9/9/2004 1:27:47 AM] Job started.
[9/9/2004 1:27:47 AM] Input file: Oceans_Eleven_cut.ts
[9/9/2004 1:27:47 AM] Output file: C:\video\Oceans_Eleven.avi
[9/9/2004 1:27:47 AM] Audio: AC3 Audio on PID 0x191
[9/9/2004 1:27:47 AM] Subtitles: none
[9/9/2004 1:27:47 AM] Codec: XviD
[9/9/2004 1:27:47 AM] Target size: 2047Mb
[9/9/2004 1:27:47 AM] Started encoding.
[9/9/2004 1:27:47 AM] Demuxing and indexing.
*************************************
EXCEPTION: Job aborted due to time out.
*************************************
[9/9/2004 2:07:47 AM] Job finished.


Since it is a very large 12 G source file, I think it should take this long, even more so because I am using an old PII 633 as my processing machine -- and loading the file from a network share...

Is there any way to increase the timeout? Seems like 30 minutes might be an arbitrary number rather than an actual inidication that the software stopped responding. I think I might need more like 90 minutes for this step.

Thanks.

[len0x]

Can you manually load TS file into DGindex and time how long it would take to index it? I do agree that for transport streams timeout should be larger that for normal DVDs, but you can't change that at the moment. But I'd like to have an estimate.

P.S. You do realize that encoding will take quite forever on your PC :)

[pidhead]

yes, I think it is safe to say my PC is the worst case scenario for this process. I have loaded manually and selected save to d2v. Is that the right option?

It is counting down from 1:20:00, but we'll see how that goes when it is done.

I tried this once before on Gordian Knot, and it took 4 days to produce an avi. That's ok though, that's all this machine does.

I'll post again with the final count.

Thanks!

[pidhead]

Final time was 1:22:59

Would there be any negative impact of setting the timeout value too high?

Thanks.

[len0x]

Originally posted by pidhead

Would there be any negative impact of setting the timeout value too high?


The feature was introduced because from time to time DGIndex just starts and does nothing which prevents the queue to be processed properly (the longer timeout the more time you waste, instead of doing encoding next item). Now that I think of it - I could check if there is something left to execute and only then force timeout (that should solve at least your problem).

[len0x]

OK, you can try version 1.55 - if single encode is running then there is no timeout now.

[pidhead]

Awesome, thank you very much.

I hate to ruin it for other people, so if at some point the timeout becomes a configurable option thats enabled by default, that would be fine with me too.

Thanks a bunch!

[java007]

Just want to add a note about the identical problem I encountered. The solution - do not use a directory or file name with a "-" (dash).

e.g.,

MY_BIG_FAT_RIPPED_MOVIE-IFO generates the error

MY_BIG_FAT_RIPPED_MOVIE_IFO works fine

Simple, once you know what not to do! :)

[len0x]

I believe current version of AutoGK checks for "-IF" sequence in the name and disallows it (its a command line switch for DGIndex).