DVD2AVIdg CLI crash

[len0x]

We probably can't really figure out what's going on without Neuron2 but I was wondering if someone has any experince in working with CLI versions of DVD2AVI (not only DG version) on old dual systems (say with PII/PIII < 500Mhz). I have already quite a few bug reports that on those systems DVD2AVIdg is not working at all if started from command line. From gui everything's fine. Any thoughts?

[hakko504]

You had a quite interesting question in this thread (http://forum.doom9.org/showthread.php?s=&threadid=62795&perpage=40&pagenumber=8):Originally posted by len0x
I'm obviously not familiar with the code, but isn't it suppose to be same code for gui and for cli excution ?with an even more interesting answer:Originally posted by neuron2
Yes, but it wasn't, and I expect that the DVD2SVCD version has the same problem (if not, it must be down to 1.76 versus 1.77.3 differences). When you use the menus, after loading the VOB, DVD2AVI executes a decode thread with LOCATE_INIT and the thread kills itself after decoding the first picture to put in the window. That thread also decodes the sequence header and sets up a lot of variables. Then when you do the save project it executes another decode thread with LOCATE_RIP. But when you do the CLI operation, the LOCATE_INIT decode thread is not executed, and only the LOCATE_RIP decode thread is executed. My changes, which are now working, run both the LOCATE_INIT and LOCATE_RIP threads just as you would when operating through the menus.Most likely, these threads does not execute(*) correctly when put on a dual system and therefor DVD2AVI does not work correctly. (*) or possibly thread handles and ID's are confused by the fact that they are on separate processors.

[len0x]

good point, but funny thing is: DVD2AVIdg doesn't have any probs on modern HT systems, which suppose to behave like proper dual systems. To me it looks like a combination of duality and old processor (may be SSE related issue or something like that).

[stax76]

I wonder if the -IF switch supports multible files with comma in the filepath. When I remember right it don't. Some authors of DVB and capture programs didn't notice so far many programs have problems with complicated file paths. They attach comma separated time stamps to the file paths :scared: