2009/5/27 Ambrogio De Lorenzo <ambrogio.de.lore...@alice.it> > Il giorno lun, 25/05/2009 alle 22.37 +0200, Francesco Romani ha scritto: > > > try using -y null and letting it work. Doing like that transcode would > > waste some of your CPU time and will not produce anything as output, > > BUT! if you're facing the same avilib problem outlined above, you should > > NOT get a segfault. Transcode should shut down cleanly. > with -y null transcode exit ok > > > Please provide a backtrace. Get it following the instructions here: > > http://www.transcoding.org/cgi-bin/transcode?Reporting_Crashes > > but use HG instead CVS!. > I used the 1.1.0 from the official site and recompiled > this is the backtrace > > gdb -q transcode > (gdb) run transcode -H 10 -a 0 -x vob,null > -i /dvdrip-data/CosiFanTutte_SecondoNoi/vob/001/ -w 900,50 -c 1-50 -b > 128,0,2 --a52_drc_off -f 25.000 -j 0,32,0,32 -Y -20,0,-20,0 -B 47,38,8 > -R 1 -y xvid4,null -o /dev/null -q > 2 > Starting program: /opt/transcode/bin/transcode transcode -H 10 -a 0 -x > vob,null -i /dvdrip-data/CosiFanTutte_SecondoNoi/vob/001/ -w 900,50 -c > 1-50 -b 128,0,2 --a52_drc_off -f 25.000 -j 0,32,0,32 -Y -20,0,-20,0 -B > 47,38,8 -R 1 -y xvid4,null -o /dev/null -q 2 > [Thread debugging using libthread_db > > [..]
The same here, with -y null it does not segfault. Is there any workaround for this at the moment? Any other parameters I could use or perhaps use the version in the cvs? Thanks Vini
