Kevin Camp
Forum Replies Created
-
here’s a thread from a few days ago where someone was asking about dvcprohd and windows. the third or so down discussed raylight and pp interaction… from what i gather, raylight will convert to another codec/format.
read up on the firestore, i think that when you shoot 24p to firestore, it will leave the duplicate frame in… that’s not a problem, but you’ll need to be aware of that to deal with it somewhere along the line (conversion, import, etc.). raylight may handle that, i’m not sure.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
is it washed out more than selecting expand 601 levels in the interpret footage settings would bea able to compensate for?
are you only seeing this in ae thru video preview in the panasonic? or is it also in the render when imported into the nle? it could be a setting issue in the video preview pref, make sure it’s set to use the correct output mode.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
what are your capture settings? what codec are you using to capture? do you have any capture issues from that device with sd or 720hd?
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
rebooting should have purged everything, so i doubt that purge all will help…
if you want to troubleshoot quicktime, try removing all the qt components from library>quicktime and users>(user name)>library>quicktime. (don’t through them away, just put them somewhere else)
you can even try removing the qt and ae prefs from the users>username>library>preferences folder.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
at this point, the easiest fix may be to shoot just blood splattering/dripping on the floor, edit that correctly and it should work well.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
if that’s not it, make sure caps lock isn’t on… it will prevent the preview window from updating (rendering). it’s easy to have happen if you’ve been typing with the caps lock on.
if that’s not it, try edit>purge>all and move the timeline slider to see if the preview will update.
if that doesn’t help, try a reboot…
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
there are preferences for both… one is ‘label colors’ the other is ‘user interface colors’. in the user interface colors you can also choose ‘effects label colors’… by unchecking that and dimming the panel background, you can generate more contrast between the background and labels.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
you will need a utility or a nle that can convert the p2 (mxf) files to the codec that you will be working in (ae can’t read the mxf files). i’ve heard that raylight from dvfilm is a good utility, but there are several others. avid will work with mxf natively, from there you could export to another format.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
to avoid quality loss, you generally would like to export clips that will be effected in ae to a lossess or uncompressed format. most people choose the lossless animation codec, but tiff, targa and png sequences will work well too.
however, your hd clips will be huge… if you don’t have the disk space, you can pull clips (or copies of the clips) directly from the capture/scratch folder that fcp put the transcoded mov files in when it converted them from the p2 (mxf) files at import. or look into getting a reference movie out of fcp for the clips you need. fyi, ae will work better (by better, i mean quicker and easier) with the lossless codec or an image sequence than with dvcprohd due to intraframe/temporal compression, but it will work with dvcprohd.
if you’re ae work will be ‘basic motion graphics,’ you may be best off to produce the graphics in ae, render as lossless with alpha (choose straight-unmatted in the output module settings) and then composite those in fcp. that way you’ll avoid any further loss in the dvcprohd footage (remember even if you render lossless out of ae, fcp will still convert to dvcprohd at import, so any original footage will be compressed again). you can use footage for placement, just remove/hide it before render. if you have to render fully composited clips, still render to the lossless codec, or an uncompressed image sequence.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
yep, ‘z’ would be position[2], or to use the current value for z, value[2]. so your final part of the expression would look something like this [value[0],y,value[2]]… this would link only the y property to your slider, allowing free positioning of x and z for your page layer.
you would use brackets to define an array, like [x,y,z] or [120,-50,400]. several layer properties are defined by arrays, position, scale and anchor point are common. but there are also many expressions that use multiple variables in an array to derive a value. i’ve recently started exploring these.
you will also use brackets after a property that would be defined as and array, like position, to specify a particular value of the array. so position[0], would specify the position value of x (first value of the array) of a given layer, scale[1] would specify the vertical (or second) scale value of a given layer.
thus, value[1] would specify the current value for the second array value of that particular property, so value[1] for position would return the y postion of that particular layer.
if you’re like me, and have no programming background, expressions have a slow learning curve. look at the help menu or manual for expressions, also the scripting guide on the install disc has more info, but neither give great explanations fro non-programmers. dan ebbert’s motionscript.com is a very good resource and where i’ve learned most of what i know…. he really needs to come out with a book.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW