[Will Bartlett]

haha I edited my response after figuring it out while you were responding to me; looks like I came to roughly the same conclusion. Appreciate your reply and initial help – THANK YOU!

[Will Bartlett]

Amazing! Thank you Dan for your help (you make this community thrive)!

To complete the animation, I have the lower thirds animating out with another two keyframes at the end of the comp (Duplicates of the first two keyframes then time-reversed)

Keyframes 1 and 4 are the same, and keyframes 2 and 3 are the same. If anyone else needs the code for this; here’s what I ended up with after Dan’s help above to get more than the 2 key frames to work:

t1 = key(1).time;
t2 = key(2).time;
t3 = key(3).time;
t4 = key(4).time;
v1 = key(1).value;
v2 = thisComp.layer("control").effect("Slider Control")("Slider");
v3 = thisComp.layer("control").effect("Slider Control")("Slider");
v4 = key(4).value;
if (time < t2) {
  ease(time, t1, t2, v1, v2);
} else {
  ease(time, t3, t4, v3, v4);
}

[Will Bartlett]

That works, thank you!! The only issue now is I have CC Force Motion Blur on the adjustment layer as well, and now that the sliders are connected, it has changed the gradual motion blur showing up on the footage below the adjustment layer.

Originally without the sliders, the motion blur would start from keyframe 1 and gradually become more until the 2nd keyframe (Since the scale was increasing from 100% to 250% for example). And then from keyframe 3 to 4, the motion blur would gradually be less (Since the scale was going from 50% to 100% for example).

Is there a way to keep the motion blur looking the same as it was before the sliders, while the sliders are active?

I appreciate your help – Anyway I can return the help? Channel to sub to? Accounts to follow?

Best,

[Will Bartlett]

Ok, Thank you! Appreciate it

[Will Bartlett]

Thank you for your reply and for the suggestions!

The shape layer has the anchor set to the left middle side (So it can expand to the right).

Yes, key 2 and key 3 are the same.

Will try this out, thanks!

[Will Bartlett]

Here is your fix after a long and annoying back and forth in an Adobe thread, hope it helps:

I can confirm that deleting this file on the user account that’s preventing Adobe Premiere Pro will work to fix the problem:

C:\Users\YOUR USER FOLDER\AppData\Roaming\Adobe\Common\Essential Sound/SharedTags

If you can’t get there, go to any open folder and at the top under View;check show hidden files.

This file will NOT delete just by right clicking and deleting it. It will say it cannot be deleted because it’s in use. Even with closing all Adobe related files in task manager, it still was unable to be deleted because ‘System’ is using it.

You have to force delete it either through your command prompt, or by installing a program that does it for you.
I used a free program called lock hunter: https://lockhunter.com/download.htm
https://lockhunter.com/download.htmAfter you install lockhunter, you can right click the SharedTags file and go to ‘What is locking this file?’.
Then lock hunter will open and if you open the ‘system’ dropdown, it will reveal the SharedTags file.
Select the SharedTags file (Not system)
Hit the delete button below.
It will tell you that you STILL can’t delete it because it’s in use, so it will ask if you want to delete it when you restart the computer, say yes.
After the restart, it will say successfully deleted.
You’ll now be able to start Premiere pro.
Premiere Pro CC will automatically put back in a new SharedTags file into the Essential Sound folder, but this time since the computer didn’t crash while in Premiere (yet), that file didn’t get corrupted, meaning all is good, until the next crash, which you’ll then need to redo this process.