So, I ripped a movie from DVD, which I'm editing in final cut pro. The file I have is an avi file, and in the movie inspector of QuickTime 7, it says: Format: DivX 5.0, 720 x 304, Millions, MPEG Layer 3, Stereo, 48.000 kHz FPS: 23.98 Data Size: 2.03GB Data Rate: 1628.16 kbits/s Duration: 0:02:58:20:81 (2 hours, 58 minutes) When I drop it in the clip box in FCP, it plays fine in the player, and it looks crisp and great, just like in the quicktime file. But when I take it down to the sequence and render it, the resulting video in the canvas is just not quite the same quality, nor is it the same quality when I export it back to quicktime. Here are my sequence settings: Frame Size: 720 x 304 (Custom) Pixel Aspect Ratio: NTSC - CCIR 601 / DV (720x480). No anamorphic. Field dominance: Lower (Even) Editing Timebase: 29.97 QuickTime Video Settings. Compressor: DV/DVCPRO - NTSC. Quality - 100%. I'm fine with working in 29.97 fps even though the original was 23.98, and I know that's not where the problem is, because I did a video with the same film a while ago, using iMovie, and I have that video in a quicktime file and it is the same crisp quality as an original ripped avi file, and it is 30fps. By the way, with the sequence set to 720x304, the canvas has small black bars above and below the video, and when I export it to quicktime, the video comes out at that ratio, 640x304, but the film is in the correct ratio within those black bars. One of the main issues with the quality of the rendered footage is that at the top and bottom of the image there is a sort of "edge" that can be seen within the video, if you know what I mean. I'm sure someone will be familiar with this phenomenon. I mean, it doesn't look bad at all, but it's just not like the avi file I had, and I don't see any reason why it shouldn't be able to be. Also, I've already put together 30 minutes of video.. so if the fix requires beginning editing over, I'm not interested. But I imagine that changing the sequence settings to the correct settings and re-rendering should be able to fix it... I would Really appreciate some help on this! Thanks!