David Bogie
Forum Replies Created
-
Matt, you have cross-posted this to the Adobe site and possibly other AE forums, please do us all the courtesy of coming back and closing the threads by telling us how you solved your production issues.
Are these 35mm slides? They are very small and that will complicate everything.
You must rotoscope around the actor’s fingers if your inserted images will fill the entire frame. if they just fill the film chip inside the cardboard mount, be sure your actor does not cover any of the chip.
If you’re just filling the chip, you do not need to have tracking dots on the image because the hard edge of the slide mount is easily tracked.
Suggest you purchase any of the major AE books by Angie Taylor or the Meyer kids. They have gret chapters on motion tracking. Motion tracking is really hard. Be sure to study up on this and do some tests long before you schedule your shoot.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
the stock particle systems that come with AE may not be up to the task since they do not include collision detections and swarming or flocking characteristics. You can fake these things, for sure, but it ain’t easy.
If you already know how to do flocks in a 3D app, I’d stay there. But you can also obtain lots of third party particle systems that can do flocking and clustering and respond to attractors. Try some of the AE portal sites for links to such tools. Sorry not to be able to point you directly I do not use such tools.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Aside from trashing FCP’s prefs files, such behavior usually points to OS issues or graphics card problems. You need to figure out if it happens in any other applications that pull on the CPU and GPU as hard. Start by repairing permissions (like FCP prefs trashing, can’t hurt) and then trying FCP again. You can also try booting your Macintosh from the installation disk for OS10 and running disk utilities. Can’t hurt. If it persists, you may want to go as far as resetting the page management unit button on the motherboard. Mac OS online help has the PMU instructions, I believe.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
AVI is just a wrapper. like Quicktime. it’s not a specific format or codec.
You won’t know until something breaks.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Try the OS10 forum on apple.com or here.
Creating a RAID is not easy and the procedure is full of subtle gotchas. You haven’t included any information about the drives or why you think you want to create the RAID. A 20-drive RAID-0 is, umm, a questionable setup.
Most of the threads we see about RAIDs are posted by users who are sadly misinformed. This might help:
https://www.staff.uni-mainz.de/neuffer/scsi/what_is_raid.html
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
You’ve got me totally baffled and apparently no one else can help you either.
Debugging these things is always a long series of down and dirty binary experiments, change only one aspect of the situation at a time and keep notes.I have zero experience with Avid but I have seen lots of Meridien-based posts, try searching for the authors and drop them notes offline maybe.
When your edit location shifts, does the length of the clip stay the same? If so, it’s the timebase of the sequence that’s changing, not the clip reference. Not sure what that means,, tho. If the clip changes length, there is a disparity between the apparent sequence settings and the actual content of the clip’s media file.
Can you work with a couple of clips that can be set to give exact change-of-frame-rate results? That is, if you ahve a clip that is two seconds long and it starts wright at 00:02:00:00 and you place a 20 second title clip on top of it, will it move a distance that suggests a direct relationship to a frame rate problem?
Sorry not to have the least bit of good news for you.
You may need to cross-post over on the Avid forums. Please come back and tell us what they offer.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
I liked the displacement effects at the end. Difficult to do with class.
Congratulations and I hope you got paid very well.bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Welcome to the fmaily.
Jaggies are only going to show up if you’re looking at the individual pixels.
You can see the pixels if it’s scaled up beyond reason or is in an image format that FCP cannot process natively and so you’re getting a draft image. For instance, FCP has no vector abilities natively so, unlike After Effects, it will not continuously rasterize stuff from Illustrator or vectors from PS.What’s the source of the image?
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
It’s not a bug: it is inconsistent nor does it appear on many machines.
You may have the clip selected in a hidden Finder window that is set to show previews. That would tie up the file.
We’ve also heard of this error coming up when a clip has been exported as a background in LiveType. No clean solution that I have seen, too many unrelated circumstances when we’ve seen it posted but we have seen it in on our systems.bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Could be.
No way to tell from here, sorry, and you haven’t told us where you put it.Whatever you do, don’t do anything destructive to the original until you solve this.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”