Robert Garry
Forum Replies Created
-
this is the new login for mobile me. Seems to be up and running for me though I haven’t battle tested it yet. Found the link through the transition from .mac to mobile me support page.
https://support.apple.com/kb/HT1932
Bob
Dual 800 G4
Aurora Igniter
Latest OS/FCP
Gig of Ram
DSR-1800
UVW-1800
Adaptec 39160 SCSI Card
Seagate Cheetah SCSI Drives
more bells and whistles….. -
Check the Position of the elements and ensure that they are on EVEN numbers that do not have any decimals for both the X and Y axis.
Can’t remember the reason this happens but it has something to do with pixels being placed on the wrong lines or something like that.
Bob
Dual 800 G4
Aurora Igniter
Latest OS/FCP
Gig of Ram
DSR-1800
UVW-1800
Adaptec 39160 SCSI Card
Seagate Cheetah SCSI Drives
more bells and whistles….. -
I’m going to guess that you repositioned the text element in the Canvas and didn’t park the text on an EVEN number.
Check your position setting and if you see that either number is an Odd integer or has a decimal value. If it does just change that value to whatever the closest even number is.
Example:
Incorrectly positioned element:
X = 3.3 Y = 271.3
Change it to:
X = 4 Y = 272
I can’t remember if it is interlacing or pixels that are creating the problem but you will notice the same “blurriness” on still images as well. It’s really hard to see it on moving video but I have even noticed it there on detailed shots.
This workaround works for pre-FCS2 so hopefully it still works!
Good Luck
Bob -
System Preferences>International>Input Menu Tab
Click the following boxes
Character Palette
Keyboard Viewer
Show Input Menu in Menu BarYou can of course check the country you want if require access to other languages.
You should get the US flag in the Finder bar near your clock! Click this and select character palette. Cycling through the options should find you just about any character you need! Alternate fonts are available at the bottom of the screen. Click the insert button and in goes your symbol or character!
Plus you now have a handy keyboard viewer for those random symbols like
-
Set your Caputre setting in the Log and Capture window for the parameters you wish to capture. Then select the clip(s) you want to recapture and when the system prompts you choose to Ignore logged settings and instead check the the box to use the Current capture settings. This will override the logged parameters and base its’ capture off of whatever settings you have chosed in the L&C window.
Good Luck
Bob -
Use Opt + & –
This will only zoom in on the timeline and will stop you from mistakenly zooming in on your viewer or canvas windows.
Good Luck,
Bob -
That may actually help. We do use multiclips and that is something I haven’t tried. Thanks and any other suggestions would be appreciated.
Bob
-
Export your FCP sequence using compressor. There are built in formats that should suit your needs. I would suggest using the “Best Quality 90 minutes – 4:3” setting. It will by default create an MPEG of your video, an AIFF, and a Dolby 2.0 (ACM) file for you. The AIFF really isn’t needed in your case.
Once compressor is done use Toast or DVDSP to build the DVD.
It sounds like you already have the video working to some degree so I would perhaps suggest just trying the audio export first since it should only take a few minutes to output and is most likely the source of your issue.
Good Luck
Bob -
Scrolling text doesn’t give you any control over speed. It bases it’s timing on how much material it needs to scroll through and how long the clip is in your timeline.
What you can do is either use a basic text element (either in FCP or from PS/Illustrator) and then use the Origin or Position keyframes to move your text.
IIRC the Position keyframes are the only ones that can be “eased in/out” so you may want to use those.
Personally I usually do this kind of stuff in Motion as I feel there is a little more control over the movement as well as being able to “design” more elements in and around the text with near instant feedback.
-
Wondering if a good workaround might be to media manage the clips in your timeline, recut them in and then apply smoothcam?
Seems like the long way but the only other solution that really seems feasible to me is to wait until you uprez and therefore usually have to deal with only small clips.
I suppose the capture small chunks solution works…but to me and my workflow it seems like more work on the front end that I really don’t want to be thinking about. Ingest, for me, is all about looking and learning about the footage, not thinking about Smoothcam render issues.
That being said, the demo shows smoothcam analyzing in the background while you work…how sluggish does the system get? If there is minimal slowdown isn’t it a mute point? I mean there’s always something to do while it is analyzing…like surf the cow!