Santiago Gutierrez
Forum Replies Created
-
Good to hear Warren. Thanks for the info!
-
Ken,
Have you tried updating your filters? You specifically mention some FX Factory plugins, and they have just updated the version to 2.0.9 to deal with Snow Leopard. However, Snow Leopard breaks their AE compatibility for the moment, so keep that in mind.Santiago
-
Santiago Gutierrez
August 9, 2009 at 2:20 am in reply to: Motion 4, multi-core rendering and studio intergrationHi Eric,
I have to correct you on this point. Ron Brinkmann hasn’t worked for Apple for several years now. He left to take over as Nuke’s senior developer at the Foundry, and Nuke 5 was the first release that benefited from his expertise. Many VFX studios still use Shake today, but many of the major ones are switching over to Nuke in droves as it has a much more robust 3D system than Shake ever did, along with many other features (major speed improvements with 4k plates and cross platform availability being two others).“You really are wrong on a lot of things. You say apple didnt know anything about high end compositing? They didnt have to because they hired ROn Brinkman, developer of shake and Nuke. They had the father of compositing IN HOUSE. They didnt need to. Kill support for other platforms? You can still buy shake for Linux and you can buy the SOURCE CODE. So now studios can update, modify and write plugs in on a proprietary bases for the studio. THEY OWN TEH SOURCE CODE. The studios will never leave shake because they can just update the code as they see fit. Add what they see fir etc. Shake isnt going anywhere for awhile.”
Santiago
-
For Slideshows of any kind, I always use ImageFlow from Core Melt. It runs under the FX Factory FX Plug architecture. It creates fantastic slideshows with tons of options in minutes.
Here’s the link if you want to check it out.https://www.coremelt.com/products/products-for-final-cut-studio/imageflow-fx.html
I know it’s not free, but if you’re in a bind there’s a 15 day free trial!!
Santiago
-
Jay,
Does the computer running AE have FCP installed on it? I ask because if you captured a 10 bit Uncompressed using a Blackmagic card, it is using the Apple 10 bit Uncompressed codec. This codec is only installed with an install of FCP. So the AE machine must have that FCP install to have the correct codec loaded. In AE, when you are setting up your render que for a Quicktime output, under the Format Settings, pick Apple FCP Uncompressed 10 bit 4:2:2. That should be the same as what you originally digitized. As far as the gamma goes, when I’ve had this problem, I check the “Match Legacy After Effects Quicktime gamma” and that fixes most of them. It’s in the Project Settings. And obviously make sure you’re working at the same frame size and frame speed as your original file.Santi
-
Tom,
Wes is correct. I use the Meridien codecs all the time in a Leopard machine when using AE and rendering out for an AVID system on another machine. The codecs work in Leopard I always check the renders and they are perfectly fine. Sounds to me like you’re coming from a G5 which may have had PPC versions of the codecs and those same versions are not being replaced in your Intel machine with the new codecs. I’d run the uninstaller application for the AVID codecs (just type in ‘AVID’ in spotlight and you should see the uninstaller) Then I’d go into both Quicktime folders (user and main library) and make sure that all AVID files are removed from them. Then reinstall with the link that Wes gave you.
Good luck -
Walter,
I’ve had this occur to me as well with the HD1400 deck and 6.0.2. Most annoying when you only need to fix one shot on the master and blow away 4 in the process! This only has occurred with the 1400 for me, I don’t have any problems inserting to an A500 or Beta SP or even HDCAM.
Thanks,
Santi -
If you want to edit in FCP6 with AVID media that you digitized in .mxf format, you’ll have to use Automatic Duck’s FCP Pro Import to “see” the mxf media. Pro Import creates Quicktime wrapper files for the AVID .mxf files because FCP cannot read these on its own. You’ll be able to see your footage inside of FCP. Be aware of the limitations of this: You will not be able to edit to tape or output your sequence unless you render the whole timeline in the appropriate compressor that goes with your capture card. If you have a Kona 3 for example, you’ll need to work in a time line that is Pro Res, Uncompressed, or using another codec that is supported by your capture card for output.
Most people prefer to “recapture” the footage inside FCP to an appropriate codec that they will not have to render for regular playback. Automatic Duck will allow you to do this by taking the AVID sequence and converting it into a FCP sequence. -
Jeremy,
I’ve had this exact thing happen to me and only with the 1400. It never happens with HDCAM decks, Digibeta decks, or any others for me. Only this particular model. And I do exactly as Rich suggests. I insert the new tape, and hit rewind or play so that the tape threads and by the time I get back to the computer it’s been going for a few seconds and I don’t have problems with timecode at that point.Thanks,
Santiago -
Santiago Gutierrez
January 19, 2008 at 12:58 am in reply to: once again: when will there be a driver for Premiere Pro??Hi Walter,
Adobe actually released the Leopard update for Premiere last month. I believe the only app left without an update is the one most people actually use, AE. Here’s the link to the Premiere Leopard update.https://www.adobe.com/support/downloads/detail.jsp?ftpID=3816