So, this may not really be an ffmpegX question, but it sort of is.

I had ffmpegX 0.09n installed, and, after finding some settings that work for my NTSC FILM widescreen XviD files, I created a terminal script by capturing the commands that ffmpegX was using, bypassing the GUI entirely. The script looks like this, where the variables are set to the filenames and the binaries inside the ffmpegX app. (i.e. $avi is the source file $ffmpeg is /Applications/ffmpegX.app/Contents/Resources/ffmpeg, etc.). The apparent line breaks here at the pipes are not in my actual script.

Code:
...
$ffmpeg -i $avi -y -f yuv4mpegpipe -s 352x480 -map 0.0:0.0 -r 23.976 -an - | $yuvscaler -v 1 -M BICUBIC -n n -M WIDE2STD -O SIZE_352x480 |
 $mpeg2enc -v 1 -f 8 -F 1 -a 2 -b 2300 -q 5 -I 0 -M 2 -V 230 -S 9999 -d -p -o $mpvfile && \
...
This worked like a charm with the binaries inside 0.09n. Today I upgraded to 0.09s, and I find that the same script now gives me an mpv file that is much smaller and runs at perhaps double speed (maybe it's 1.5x, but it's fast). My question is: any clue what changed between the two that broke my script?

The original video is 23.976, widescreen, and I'm targeting letterboxed half-D1 at 29.97 with 3:2 pulldown. I'd have guessed that what is happening is that it's encoding the 23.976 video and playing it back at 29.97, except that it's also losing a lot of information (the resulting .mpv file is about a quarter the normal size I used to get), so perhaps that's not actually it.

I've gone through the parameters, and they look right. ffmpeg is being told it's FILM framerate (-r 23.976) NTSC (-n), yuvscaler is letterboxing (-M WIDE2STD) half-D1 (-O SIZE352x480) NTSC (-n n), mpeg2enc is being told it is FILM 3:2 (-F 1 -p) for DVD (-f 8 ) 4:3 (-a 2). Is there a new bug in ffmpeg or mpeg2enc?

Also perhaps relevant is that I get copious "non-monotone timestamps" errors now, like this (which I don't remember seeing before):

Code:
   INFO: [yuvscaler] Frame number 1113
error, non monotone timestamps 0 >= 8887723
   INFO: [mpeg2enc] Frame end 1101     151.56 190114.64 5.7 8171.43
error, non monotone timestamps 0 >= 8895230
   INFO: [yuvscaler] Frame number 1114
Sorry for the somewhat off-topic question, but perhaps it is very easy to answer for those who are used to looking at ffmpeg and mpeg2enc parameters and are up on the updates to the underlying code.

[addendum: I played a bit with the GUI, and setting it to decode with ffmpeg (unchecking mplayer and Quicktime) produces the same command line and the same results. I tried setting and unsetting 3:2 pulldown, but it didn't improve things. Decoding with Quicktime seems to still work, although on my faster machine I must be missing a codec or something, since over there choosing Quicktime decoding for these files always results in totally black video. I'll look into that, but in the meantime, something has changed with ffmpeg's reading of XviD files, it appears]

[addendum 2: I tried replacing the ffmpeg binary in my script with the one from 0.09q, and it's back to normal, so it is something about ffmpeg that's doing this. For now, my problem is solved (by downgrading this component), but it's still worth knowing about...]