[Paul Benson]

Not sure about the best, but Premiere Pro has some presets that worked fairly well for me. They matched the YouTube recommendations for size and compression (mp4 for video).

Pauley

[Paul Benson]

Seems like you have isolated it fairly well.
We can rule out Premiere, since it also fails with WinDV and DVCapture.
We can rule out the camera, since it happens with two cameras.

That leaves the tape, the cable, or your 1394/USB card.

Pauley

[Paul Benson]

I may have found something. I think I can use layer.numProperties and then the layer.Property(index) to go through the properties of a layer. Then go through the keys, using an index, to adjust as needed. That is what I was originally trying to do; maybe I had a syntax error.

Thanks for your help, guys.

Pauley

[Paul Benson]

Thanks Chris,
it is heartening to see that others encountered the same problem I am seeing. This keyframe nudge script explicitly states each property, which was one of the options I wanted to avoid.

It looks like I have two options:
1) Explicitly state as many properties that I can think of (I would like to include effects). This would be a PITA and has some issues around me not handling future or third party properties.
2) Force the user to select the keyframes they would want adjusted.

Both techniques could fall prey to keyframes that can’t be adjusted by script.

I think I’ll make a feature request to Adobe. How would you all prioritize these?
1) Method to expand/contract layer (while adjusting keyframes)
2) Method to expand/contract a group of keyframes
3) Method to select all keyframes of a comp/layer/effect. This would allow the ability to crawl through keyframes with selectedKeyframes.
4) Attribute for all keyframes (selected or not) in a comp/layer/effect to allow looping through all of the keyframes.

I think #4 would be the most useful and generic.

Pauley

[Paul Benson]

Thanks Dan,
at least I know I’m not missing something obvious. The rd_GimmePropPath script is a good source for the properties I may need to crawl through. It is also interesting to see different people’s coding styles. I thought this would be fairly simple…

As for moving the keyframes, I felt the easiest method would have been to read the keyframes for a property into an array, then delete them all, and then add them back (with their adjusted time) to the same property. Then go to the next property as needed.

However, your comment about some keyframes not being readable put some kinks into that plan…

Maybe I’ll just ask the user to select the keyframes they want to be adjusted and copied to the other layers. Then I can use the selectedKeyframes attribute. I hate to do that, though, since I hate having code dependent upon so many user actions, and then it still may have difficulty if the user selects keyframes that I can’t read from a script.

I’ll have to ponder.

Thanks again,
Pauley

[Paul Benson]

Thanks Dan. I’ll stop worrying about it, then.

Pauley

[Paul Benson]

Wow, this is timely. I just started scripting today with the extendscript tool and noticed no AE object model. Glad to see I’m not alone.

Pauley

[Paul Benson]

Clicking and dragging should work. Not sure what the issue is there. A possible workaround would be to select the entire image, copy it, and then paste it into the other image.

Pauley

[Paul Benson]

Thanks Dan. The problem with google is that my search results always gave back links to basic array methods and properties. Now I know how to properly phrase my search with “associative arrays”. Your post should help me narrow down my search.

Thanks,
Pauley

[Paul Benson]

Hmmm, well I’m still trying to wrap my head around it, but I did find this explanation.

You can access ReflectionInfo objects in a Reflection object’s properties and methods arrays, by name or index:

obj = new String ("hi");
obj.reflect.methods[0];
obj.reflect.methods["indexOf"];


I assume this is not unique to ReflectionInfo objects. I’m still trying to visualize this. Seems like a nice shortcut to get the the parameters/properties you want.

Pauley