[Jay Ingles]

I found these Thinking Particle Tutorials to be quite helpful. Though i am still stuck with the above problems.

https://vimeo.com/12797053

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Jay Ingles]

Hahah, thanks Dave. And yes i’ve explained the limitations in a high level fashion to the agency. I’m just firming up on the technical possibilities.

I’ve decided to retime the base/parent video and track from that. Then screens are still editable for content but not for timing.

Thanks everyone for chiming in.
Appreciated.

[Jay Ingles]

Thanks Ben, that’s great insight.

I was considering using expressions to match the remap, but anticipate some undesireable last minute issues.

I’m starting to feel more confident about locking down on some variables and precomposing the screen+video together and time-remapping that as a whole.

Not my ideal approach but i think may be the fastest solution.

Do you have any insight or problems i may be overlooking?
Thanks!

[Jay Ingles]

Thanks guys.

Ted, would you advise this method over time remapping the Main video to time, then render out and use Mocha to track. Followed by bringing back into AE and adding the screens in?

Of course this locks the edit to the VO, but at least then there isn’t hte potential issue of keyframe tracking going wrong.

What do you think, Should i lock down some variables?

[Jay Ingles]

Thanks Brian and Greg. Really good insight.

I think the plain effector with “peak velocity” should do the track. Wouldn’t have figured that out without your help.

appreciated.

[Jay Ingles]

Hey, just signed your petition.

Below is a link to a Facebook page which I hope garners enough “Likes” to send a message to Apple that the Professional Community demands an outline noting dates and features for future releases.

Final Cut Pro X: Demand for Features
https://on.fb.me/FCPX-Fb

Without pressure from the community Apple will continue to focus on the iProduct lines. If you agree with the message, please share with your networks!

[Jay Ingles]

Thanks Randy,

I got some pleasing test results with spline and Sketch and Toon. Are there any foreseeable problems with using splines and animating S&T start/stops?

Since im not An experienced c4d user, It seems that S&T may be the easiest, visually pleasing approach…no? Im concerned I might get undesireable results with Tracers/sweep nurbs that I won’t know how to remedy.

Im Also looking into Mospline.
More testing to do. Thanks!

[Jay Ingles]

Hi Dan,

Seems to work but i keep running into hundreds of “unsafe operation attempted” errors. I found this article that explains SampleImage has a flaw in it that can create this scenario.

https://forums.adobe.com/thread/693859

It suggest to add layer space transforms such as .toComp() for such operations. Likewise, when dealing with colors, always make sure to use the correct syntax to conatin all color components in arrays.

Adding that statement in creates an error and turns the expression off. I’m sure i’m doing it incorrectly but interested if you have experienced this.

Attempted this: framesToTime.toComp((f))

Thanks so much!

[Jay Ingles]

Wow, quick at responding, Thanks Dan.

I’ll give that a shot!

[Jay Ingles]

Someone helped me a couple months ago with the same issue.
I used the code below.

Note that I created a Null called “sound keys” and added a slider controller called “SoundKeys Controller”. Then i used trapcode sound keys to map the song out to keyframes.

Hope this helps!

temp = thisComp.layer("SoundKeys CONTROLLER").effect("Sound Keys")("Output 1");
[temp*thisComp.layer("SoundKeys CONTROLLER").effect("SOUNDKEYS SCALE MULTIPLIER")("Slider")]