David Bogie
Forum Replies Created
-
No way to know without lots more information or looking over your shoulder but it is usually associated with not having the right tracks selected for the edit, trying to place a new clip on top of a locked track or it’s just FCP freaking out. FCP is just as likely to throw up a completely bogus error message. Save your work, relaunch and see what happens.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
See the Apple product pages for FCP.
Depends on what you mean by “smooth,” your origination format, desired output, level of collaboration with other applications or editors, your budget, and version of FCP.bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
It was shot that way. Incorrect use of the timecode function.
Be sure to read the manual for your camera very carefully before the next shoot.bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
You’re not going to be happy at all.
FCP’s HD capabilities were mostly hype but no one has really seen (and then told us about) the new quads in action with full rez 1080.Look at the Apple AR sites for their HD-capable FCP rigs and note carefully the external hardware they build the systems around. Spend hours on the phone with the Kona people.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Sorry, I’ve never had a nest go out of sync. Even with as many as eight tracks in the upstream sources.
But my recent project showed how poorly FCP tracks nests and render files. So I’ve gone back to how we used to do things in the olden days: Export nested sequences and import them as movies. I use low rez render settings on these till they’re golden and increment the versions with an alpha character. Not what you wanted to hear, again, my apologies for not being able to offer anything immediately helpful.Can you revert to a previously saved version of your project from the Vault?
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Dumb-ass programming on the part of those FCP coders. Really poor quality control.
5.0.3 seems to have fixed it but I just might be mousing more carefully these days.bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
[Walter Biscardi] “Instead of concentrating on all this “Gee Whiz will you look at all the new features” it would be nice for the FCP team to actually keep basic functionality working.”
Amen, brothers and sisters.
Forget new features no one cares about or make a second application called, umm, Final Cut Pro Ultimate.
Fix the sh)(t that’s never worked.
Fix the sh)(t that gets broken between revs.
Gimme what every other NLE has had for five or more years. Gimme an elegant and slick interface that doesn’t require thinking about which drug the designers were on when they imposed some weird feature on the rest of us. Gimme stability. Gimme edit to tape. Gimme Firewire timecode. Gimme a way to turn off a track without losing days of renders. Gimme a world without AutoSelect. Gimme. Gimme.Lord, I am sooo glad I’m not trying to do the stuff you guys are trying to do. I’m just assembling about ten layers of video, Motion and LT with 6 audio tracks in standard DV on a new, max’d out Dualie 2.7 G5. Sluggish as snot on a cold day. Wait wait wait. Today I really miss my old Media 100.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
The error FCP is throwing up probably has nothing to do with the actual issue so forget it. Unless, of course, the one or two files directly referenced are corrupt. No way to know, really.
About all you can do is try eliminating the obvious or anything you have a gut feeling about. Make a copy of the project and play with the copy. Delete or turn off a couple of tracks. See what happens. Try selecting all fo the audio trakcs and grouping them into a nest.bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
> The problem is that my menus have short bursts of pixilization on them.< This isn't a very helpful description. The term "menu" in DVDSP can refer to images created locally within the app or imported from anywhere on the planet. "Pixelation" is just about meaningless without describing the context and the way in which it appears or comes and goes. bogiesan This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
The control is contextual. In FCP, you need to be in a bin and control-clicking on a column heading. Dunno about FCE.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”