Log in

View Full Version : IMDb movie info


tommc
14th December 2003, 01:57
Using DVD2SVCD & TMPGEnc over the last year and sticking as closely to the basic 'off the shelf' settings I've manged quite nicely to collect a nice library of SVCD movies with very few setbacks. Reading the forum here has helped, checking out various 'help' manuals also, but nothing is smooth and I would like comments on the movie info import thing. I understand the the 'cover' pic has been long gone, no biggie but I used to be able to import the info without a problem, something I didn't bother with for some time until recently. On my last attempt, after some months of ignoring it, I searched for the movie title without a problem but on hitting 'ok' I got the following; 'list Index is out of bounds (3)', mysterious to me! The question is not what that means, although I wouldn't mind a quick easy answer, but rather it is should it still work? I'll figure it out, if required, but it would be nice to know if it still actually works. The only real change in hardware was a switch to a router/dsl for Internet access, the rest is mostly the same.

r6d2
14th December 2003, 04:10
Hi, tommc, and welcome to the forum (even though you seem to have registered more than a year ago, this being your first post is a long wait) ;)

The index list out of bound stuff has been sort of coming and going, but I have not seen it since the last version. Please make sure you have it (you forgot to mention your version).

Also, the picture can be gotten manually from Amazon.It sucks, but worth it IMHO.

Swin
17th December 2003, 01:16
Hi, along the same lines (and hence no new post), I have a question about IMDB possible problem.

It is a long time since I have needed to backup any DVD's and since buying a couple the other day, I decided to roll out DVD2SVCD again and back these up. Before I did anything I checked for a latest version and downloaded and installed ver 1.2.1 build 3

When trying to receive information from IMDB, DVD2SVCD shows me the screen listing the various movie title options, but after clicking on the relevant title, then jumps to 100% cpu utilisation and simply shows the "Fetching Movie Info" Dialog. I can see that a certain amount of information gets transfer to the main DVD2SVCD program (such as casting and additional info) but the rest remain unfilled.

Any suggestions on what this problem may be?

Swin

r6d2
17th December 2003, 02:58
I've seen that too. It happens randomly in my case. I just shut down and start DVD2SVCD again and retry. No idea of the origin, but this workaround may be of use.

I have not reported it since it seldom occurs and I cannot reproduce it at will.

tommc
17th December 2003, 03:36
Ah well, a year here, a year there, it all flashes by so quick when you're having fun, right? Thanks for the notes back, I'm using version 1.2.1 build 2 if that helps at all. I do try to keep it up but as you can guess, unless there's a particular incident to grab your attention the other 2 gazillion programs take some time too. :-) It looks like it works erratically at best so I'll not sweat it too much for awhile and hope a fix arrives like magic from that virtual mystical source we all look to for enlightenment.

Swin
18th December 2003, 14:32
Well, I have managed to solve my problem of DVD2SVCD crashing during the IMDB updtae and below is this particular solution that may or may not prove useful.

I have been using several different methods of trying to make a bit or cash over the internet. One of these was to use a survey company called OpiStat that supply you with a free copy of Norman Antivirus software. Unfortunately that also install a little tracker program that routes your internet traffic through there server (spyware many call this). Well I actually knew about this but if there was a chance to make a couple of quid, I'll do it, I'm skint!

DVD2SVCD crashed with an application fault in NMTRACER.DLL, the library that is used by OpiStat and there perant company Netvalue. Even though I had disabled the OpiStat program from auto starting, this DLL was still in use and being used to route traffic. Removeng OpiStat from my system cured the problem. PS, during the 2 months I have spent signed up to this particular program, I havn't made a dime!

Other people may find similar programs or routines that cause this type of problem.

Swin

r6d2
18th December 2003, 15:40
:goodpost: :helpful:

tommc
19th December 2003, 02:26
There's an interesting possibility, interference by another program, in your (Swin) case a bit of spyware. I'll see what I can find in that direction. Thanks for the info, maybe with a few more clues the problem can be resolved on a general basis. ttfn

Swin
19th December 2003, 13:53
It maybe very tricky to nail down. The only reason I managed to work it out is because the DVD2SVCD process crashed and an error was written application log. From this it showed that the dll in question caused the problem.

DLL's are a pain as they are simply used by applications and it is a little difficult to know what is being used, when and why. Shutting down processes or services doesn’t necessarily mean that a rouge dll isn't in use somewhere - as it was in my case. I wonder if anyone else out there with a little more system programming knowledge than I can help in suggesting a way of tracing such items.

Also remember that in my case, I believe it was a connection problem to the database itself via my Internet connection at the OS level that was the problem - nothing to do with DVD2SVCD or its operation - which could be even harder to trace. What you need is some kind of baseline, like a fresh system install, to figure out what is getting used and then compare to your system. How do you do that, err, don't ask me!

Swin

tommc
26th December 2003, 19:19
I carefully scanned and removed a couple of ad/spyware programs I had missed on earlier checks, removed a couple of no longer wanted small programs and rounded of by upgrading to the very, very last build and presto it works once more. I should have used a more step by step analysis to be able to determine the exact problem but at least I can state it is now working. I suspect it was one of a couple small utility programs I removed but nothing conclusive. My apologies for the sloppy shot gun approach but I do this all day and went the lazy way on my own system, this time of year spare time is tight.