Chris Brandt
Forum Replies Created
-
I had this issue, as well, and can’t find any newer posts (though there are two older posts), and (since OP never followed up to confirm the fix,) just wanted to confirm that is was an issue with FCP 7.
It has nothing to do with SD. I output an original 1440×1080 HD project (with text overlays) through compressor to three file sizes. The 1920×1080 was fine. The 1280×720 and 720×405 files both looked fine EXCEPT for any text overlay. The original video image was not squeezed, but the text was. Very odd.
I did not find a fix within compressor, but I’m writing to confirm (for anyone else who may have this issue in the future) that the exporting through QT may be the fix. For myself, I just used the 1920×1080 file, dragged that into compressor, and ran it through the other sizes, and it “fixed” the problem.
I’m still interested to try and troubleshoot why it’s doing it through Compressor, though. When I have some spare time next century. 😉
-
I know this is an old issue, but since it’s one of the top Google hits for this problem, I’m responding here. Christopher McDonnel’s solution got me looking in the right direction:
Under the Final Cut Pro drop down menu, go into “Audio/Video Settings”
In the “Summary” tab, set Sequence Preset to “HDV – 1080p30” (or whatever your footage was shot in), in Capture Preset select “HDV”, and in Device Control Preset select “HDV Firewire Basic”.
Video Playback = None
Audio Playback = Default—-
Everything worked great with those settings. -
Could you apply a filter with some distortion effect, and set key frames to get an adequate effect?
If not, it does sound like you’re trying to do animation that would require at least a few different variations on the shape. Is it just wriggling in place, or is it moving across the screen? The length of each image (probably less than one second, but at least two frames) will depend upon how quickly you want the fish to be moving, but you could probably get away with just six or seven different images, and just repeat them.
-
Nevermind, I suppose. I sort of figured out the fix, after finding other posts about this that suggested sequence settings not having the pixel ratio properly set.
It wasn’t the pixel ratio, but something to do with the 1920×1080 footage being set in a 1440×1080 sequence. I had to reset the sequence to 1920×1080, which didn’t do anything to the images, but added horizontal length to the FCP preview window. Then in Compressor, to output at 960×540 (for internet viewing) I had to crop to 16:9, and this got rid of the extra space on the left and right.
What I don’t really get, is that if I kept the sequence at 1440×1080, and output at 1920×1080, everything looked fine. But I couldn’t set it to 50% nor input 960×540, or the distortion would occur in the final output file.
Anyhow, problem solved. Just confusing.
-
I’ve had this problem many times, before, and the culprit has always been an m2v file located in the FCP sequence. I’d check for corrupted files in your sequence.
-
What file format are you exporting to? For DVD I normally export to m2v and aiff, then convert the aiff to ac3 (reduces the audio file size by a great deal).
Also, what are you sampling your created files on? The same system you’ll be screening them on? I’ve noticed that the DVD player and monitor system I used for playback can make a great deal of difference.
-
Just a more detailed follow-up on Brian’s post (even though it’s several months old), since I was looking for the same info, and this was one of the first Google links. I then had to do a further search for the details. 🙂
After creating and extruding the text, in the main menu, go to Objects > Deformation > Wrap. In the Objects list, nest the Wrap in the Text. In the Wrap Object window, under the Object tab, change the setting from Cylindrical to Spherical, and adjust the various measurements until the wireframe matches your Sphere. Then in the main menu, go to Objects > Modeling > Boole. Place the Extruded Text Wrap into the Boole.
That worked for me. Thanks, Brian, for putting me on the right path. 🙂
My only suggestion would be to save this for last, as the Boolean really slowed down further editing capabilities (by like five to ten times slower).