Preset Applied to Caption to Graphic Uses Wrong End Point

[Stan Jones]

See post in regular forum, demonstrating this in Release 23.5.0 and providing more detail:
https://community.adobe.com/t5/premiere-pro-bugs/upgrade-caption-to-graphic-does-not-work-with-prese...

Steps to reproduce:
1 Create presets for effect (I used Gaussian blur) with a) Anchor to Out and b) Scale.

2 Create caption with duration of 5:29 (really anything other than 4:29)

3 Select and Upgrade Caption to Graphic

4 Apply either Preset. 

 
Result: The new graphic text duration is 5:29, but the keyframe for the outpoint is 4:29, not 5:29
Expected: The outpoint would be 5:29.

A preset with Anchor to In works. Anchor to Out does not work. Scale does not work.

See the link above: Changing the default still image value changes the end point value. A caption duration of 4:29 works, without regard to the preference setting.

Stan

 System info
    Application: Premiere Pro (Beta) v24.0.0.14
    OS: Windows v10.0.19045, RAM: 63.80 GB GB, CPUs (logical): 16

[KYLER HOLLAND]

Thanks for sharing! Hopefully we can get a fix sometime in the future. Stay creative.

[jstrawn]

As I mentioned in the related topic in the main forum, we have verified that there is indeed a problem specific to Captions that were upgraded to Graphics. I have created internal report for the problem so that developers can take a closer look at it. As always, I can't comment on how soon a fix might actually happen.

UPDATE: This has been fixed internally. It shoudl be available at the next beta build... Pr24.0xBeta017 or higher.
Please note: This will not fix graphics that were already upgraded from captions in earlier builds. But any captions that you upgrade to graphics from here on will have the fix.

[Stan Jones]

@jstrawn,

Thanks for the update!

As always, your presence in the forums is appreciated very much.

Stan

[Stan Jones]

@jstrawn,

I discovered a draft post in which I confirmed the fix in Beta 24.0.0.17. But I never posted it, and do not find any notes.

I have now confirmed the fix in 24.1.0.2. I used only my Gaussian Anchor Out test.

Thanks to you and the team for this.

Stan