Kevin Camp
Forum Replies Created
-
you would only get better performance if you use opengl accelerated effects and features… if you are currently are not using opengl (and most prefer not to, it is a little tweaky in ae), then spend you money on more ram, particularly on your quad core (you would like 2gb per processing core when cs3 is released).
also i believe your dual core macs (agp graphics) already have the best cards available. and i don’t think any of the mac agp cards support opengl 2.0 which you would need to get full opengl benefits in ae (things like accelerated anti-aliasing and blending modes). so you would probably never want to use opengl on those macs (who doesn’t want antialiasing???).
on the quad core, you could update to the ati x1900 (there is a special one for the g5 with pci express slots). it does support opengl 2.0 and all the opengl accelerated effects and features in ae. it’s only about $400-500, but i still think i’d spend my money on ram for that machine.
if you still have money to spend and if you really wanted the best opengl performance, you would want to have a graphics card for each monitor. you would only need the best card for the monitor that would be rendering the preview, the other card could be a lesser card (on the agp macs it would have to be a pci or pcix card, since they only have one agp slot). on the quad, you may be able to use the old nvidia card as the second card… although i’m not sure if having to load drivers from two manufacturers would be a problem.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
it would seem that the issue is probably the frame rate. select one of your comps in the project window. then, from the compostion menu, choose composition settings and set the frame rate to the same frame rate as the original footage.
if you are rendering with render settings other than ‘best settings’ (default), then make sure in the render settings that the frame rate is set to the same as the comp (and footage)settings. you might even make sure that the output module for sorenson 3 is also set to the same frame rate (although i believe that setting may be over ridden by render settings).
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
they are fat binaries… they contain both powerpc and intel mac applications.
mac applications did this about 10-15 years ago too, back when they made the change from the old 680xx motorola chips to the powerpc chips in the mid 90s. there used to be a way to separate the fat binaries back then… essentially deleting the half you didn’t need to save disk space. i haven’t heard much about that this go around, but it probably can be done.
-
yeah, that’s a pretty unusual workflow… but it kind of fits what you were describing with unusual horizontal lines. ae must have been interlacing the render first then scaling it to fit the ntsc pixel. scaling interlaced footage will create issues with the fields similar to what you described.
-
this is sounding pretty odd…
i’ve worked with p2 footage from hvx’s that were transcoded to qt dvcpro via fcp and avid many times, and i haven’t seen ae misinterpret the qt mov. are you sure you can’t see any interlacing?
-
dan ebbert created an expression that may work for a plugin like beam, which could allow you to connect two photos with a line in 3d space.
his expression was used to create 3d corner pinning, allowing the corners of the 2d plugin to move in 3d space… in the case of beam it would only be the 2 points linke to 3d layers (like the anchorpoints of your photos perhaps).
anyway, here the link his page at motionscript.com if you want to check it out.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
possibly, but it it is often due to interlacing… if you render in fields and you credit don’t move in whole fields (even numbered whole pixel increments) then you’ll get bad jittery effect. the anti-aliasing effect can be solved too by forcing or limiting the movement to whole pixels.
dave laronde a great job describing a process to create a flicker free if you want to search the cow… and i created an expression based on it that can be downloaded at http://www.mercuryjones.com/aepresets.html. there are a few controls for creating the movement for field rendering along with sliders for front and end padding.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
are you working with the original p2 files in fcp, and using fcp to transcode the p2/mxf files to quicktime dvcprohd?
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
yes, i agree… i think the sound of the term ‘film-like’ is what is so appealing to video guys, but i bet cinema guys would love to get the kind of frame rates video is getting. 30fps…60 fps… sharper cleaner, better detail… why wouldn’t they.
24p has been a real pain, if you can stay 24p throughout, you’re ok. but if you don’t get started out that way, or someone wants to through in some 30i footage from a previous shoot or old b-roll… then it falls appart, and you wish everything was 30 fps.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
dave’s 24p ae workflow is good, but i honestly think you need to adjust your 24p workflow.
it sounds like you are editing 24p footage with the pulldown in place… i don’t think it is good practice to be working with a pulldown. if you have 24p footage, you should remove the pulldown and do your editing & effecting in 24p. it is usually easy to capture and remove the puldown at the same time. when your all finished with your 24p project, render or export the final piece in 29.97 with a pulldown.
if you edit footage that has a pulldown, you will end up screwing up the pulldown cadence, and that can be very problematic…
Kevin Camp
Designer – KCPQ, KMYQ & KRCW