Sam Zimman
Forum Replies Created
-
shoot 30p and set your Avid project to 30i. The camera will only take one full “sample of time” every 1/30th of a second and then split this into the 2 fields to create a 30i. It may sound confusing but if you shoot something with fast motion at 60i and something else at 30p and then open the clips in effects mode so that you can step thru frame by frame you will see the difference.
-
It has to do with the 601/RGB conversion. You should be importing it with the 601 color space setting. Do a test with some color bars or a ramp. RGB black is R0,G0,B0 and white is R255,G255,B255. 601 is R16,G16,B16 and R235,G235,B235.
What I normally do is output my QTs from the Avid with the RGB color space setting. This pushes the blacks down to zero and the whites up to 255. I bring that file into AE and do all my work. After the render I import with the 601 color space setting and the Avid brings black back to 16 and white back to 235.
Now I know that the new AE has color management settings so there may be a way to work in AE in 601 color space. This would be ideal because you could export same as source, do your AE work, render with the Avid codec, and then import (with the RGB setting i guess?) and there would never be a 601/RGB conversion.
Hopefully someone with a little more knowledge will weigh in on this thread and spell out the best way to work with the Avid Meridian 1:1 codec and the DNxHD codecs when it comes to AE and colorspace.
-
1080i59.94 is 1080i29.97, the difference is some people count fields and some count frames. You should exports QuickTime movie same as source and make sure you AE machine has the avid codecs installed on it. Also HD is upper field first so remember that when setting up and rendering your AE project.
-
Whenever I have flamethrower errors they have to do with reference. Try switching the internal and reference.
-
Just move the Quicktime Component.
Root/Library/Quicktime/AppleProRes422.componentYou probably have to have QT 7.3 on the new computer, but yeah it works.
-
The blacks are green and SD looks kinda eh in my opinion. According to Walter the new TV Logic is the best.
-
I think in general Motion has issues with certain graphics cards, and possibly peripherals. My problem has to deal with 3rd party effects, your might have to do with a 3rd party output device. Eh, what are you going to do? All we can do is flag the problems and home Apple fixes them in the next update.
-
Although it is not exactly the same, I have issues with my ATI X1900 and Motion on my Dual Core 2.3 G5. I’ve go so far as to reinstall my Geforce 6600, so if there is an issue I can just switch video cards and key working. One monitor is hooked up to the ATI and one to the Nvidia. If the ATI starts giving out to me I just open system preference and switch which monitor has the menu bar and the problem is solved. It’s a sucky work around, but it does prove that there is something up with ATI cards and Motion.
-
Hey Herb I have a very similar system with a very different problem. I can’t get 3rd party plug-ins to work and I think it’s a conflict between Motion and the ATI card. So that might be your issue.
Try this, just to see if it works. Download the free trial of BCC5FXPlug or Magic Bullet Looks. When I apply BCC to a clip it makes it go black. When I apply Looks and launch the plugins interface it does not pass the image through to the Looks Builder. However, both of these plugin sets work fine in FCP. Like I said previously, I think this is a conflict between Motion and the ATI card, but nothing is confirmed yet.
-
it would have a larger install basis if Apple started putting it on all their new computers. that’s the main reason I have FW800, because I can move my drive to many different computers without have to take a PCIX and/or PCIe card with me.
I doubt it will be a firmware upgrade. I think it is going to be live USB1 vs USB2. everything looks the same, but it’s more robust on the inside.