Hi Francesco, on 20 Aug 07 at 08:04, you wrote: > On Sun, 2007-08-19 at 20:14 +0200, Christoph Bartelmus wrote: >> Can someone at least confirm whether the problem still exists in the >> most recent transcode version? Is it likely that the problem is in >> transcode itself or should I look at libavcodec or some other library?
> this looks more a libavcodec issue than a transcode issue. At least, > the message come from libavcodec. Client code (transcode) isn't > changed much in the meantime, so the most probable thing is a > libavcodec issue. I considered submitting a bug against libavcodec, but the strange thing is that this problem is only reproducible using transcode. I tried to convert the file using this command which should be analogous to the transcode command line I use. > ffmpeg -pass 1 -i clip.avi -s 384x288 -vcodec xvid -b 600k \ -aspect 4:3 -acodec mp3 -ab 96k -bf 1 run1.avi > ffmpeg -pass 2 -i clip.avi -s 384x288 -vcodec xvid -b 600k \ -aspect 4:3 -acodec mp3 -ab 96k -bf 1 run2.avi I don't see the "slice end" message and actually the resulting avi looks fine. Also when I play the clip.avi with ffplay, I see no problem. All programs use the same version off libavcodec, so the difference must be in the way transcode is using it. Cheers, Christoph
