Francesco Romani wrote: > On 11/27/06, *matt black* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > Could please tell us if using -x mpeg2,null (only mpeg2 import module) > > gives the same hangup? > no hanging... > > > Nice. Second try: can please tell us if hangup happens using vob import > modules > and selecting just ONE vob file of offending output? > > Please also report if using -L or not option change this behaviour. >
it hangs with or without -L, but importing a specific vob file *does* make it function properly, with or without -L then I tried that other file mentioned in my first post-- the_lover ... it hung. tried it with the first .vob-- hung again. what changed? I haven't changed or moved the input files, and I am using the same (cvs) transcode binaries as in my first post. Then I removed the old .ppm output files. the_lover then processes ok, sometimes... back to mulholland_drive... hmmm the more I play with it the weirder it gets... It seems that it is interacting with the output directory. Just removing the output .ppm's isn't enough. It is when I completely empty the directory that it sometimes works better. But sometimes it works ok with non-empty output directory and can overwrite old .ppm files. It seems this depends on the value of -L, and omitting -L doesn't always make it work either. Sometimes even with empty output directory it hangs with some L values. Are some values of L valid and others not? I started off with some values from dvdrip's invocation of transcode but they have gotten changed along the way. Still, bad L value (if there is such a thing) shouldn't hang it, should it? Answer that question and I'll try to run through it all again from the top. (this last session has made my head spin :) Further notes.. this all worked ok for me in the distant past... 0.6.x. Not sure if this problem started with 1.0.x or when I upgraded to glibc-2.4, gcc-4.1.1 and nptl Cheers...
