Activity
‎Mar 17, 2025
02:27 PM
1 Upvote
I strongly support all Captions updates! Haven't seen much discussion on keyframes, so I wanted to make the official ticket. Captions, emojis, and keyframes are the 3 pillars that I think would be well received by many users.
... View more
‎Mar 17, 2025
02:04 PM
Hello @bbb_999! Understood about migrating the existing APIs first. Hope that this feature request & the supporting threads are helpful for prioritization. Trying to get this one added to the top of the list after 1:1 parity 🙂
... View more
‎Mar 17, 2025
12:56 PM
The PPro UI allows editing keyframe handles to set custom easing curves in Effect Controls Panel. Currently, PPro scripting only allows Linear, Hold, and Bezier keyframes: During migration to UXP, please add API support for custom bezier interpolation on keyframes. This would enable developers to build more robust presets, plugins, and extensions to automate keyframe creation & light motion graphics in PPro. It would also allow devs to build custom easing panels, with easing presets, and a better curve editor. These products are extremely popular for After Effects: Flow, Ease Sync, After Ease, etc. You could model the API after AE's KeyframeEase object. Here are threads of people requesting this exact feature and related issues: https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-scripting-keyframe-interpolation/m-p/14329722#M486407 https://community.adobe.com/t5/premiere-pro-ideas/make-keyframe-handles-pin-horizontally-upon-holding-shift/idi-p/14255176 https://community.adobe.com/t5/premiere-pro-ideas/easy-ease-keyframe-interpolation/idi-p/15183340 https://community.adobe.com/t5/premiere-pro-discussions/keyframe-controls/m-p/13042007 https://community.adobe.com/t5/premiere-pro-ideas/edit-keyframe-velocity-numerically/idi-p/14015167
... View more
‎Mar 17, 2025
09:52 AM
Hi Abhi, Properties panel is a great addition and I like editing multiple clips properties. I have a feature request to edit multiple identical MOGRTs from the Properties panel. We currently have to edit one by one. Here's the FR post: https://community.adobe.com/t5/premiere-pro-beta-discussions/properties-panel-gt-multiple-clips-selected-gt-mogrts/m-p/15215895#M11442
... View more
‎Mar 17, 2025
09:50 AM
1 Upvote
I'm writing to request editing multiple identical MOGRTs at once from the Properties panel. Why? There are many cases where I have multiple copies of a MOGRT in my sequence, and need to update colors, effects, fonts, etc. for all of them. Currently we have to do this one at a time for each MOGRT. When there are 3, 4, or dozens of copies of a single MOGRT this is extremely time consuming. How will the idea help your workflow? When I have multiple copies of a single MOGRT in my timeline, I would like to select all MOGRTs and edit their MOGRT properties (sliders, color controls, etc.) at once in Properties panel. Properties panel already recognizes "Multiple clips selected" and allows editing Transform & Crop at once. Please add the MOGRT properties. Limitations If the user selects multiple MOGRTs which are not the same, I understand not showing MOGRT props. But when they are all identical, we should be able to edit them all at once.
... View more
‎Mar 06, 2025
07:03 AM
1 Upvote
As mentioned by several people already, try Captioneer: https://captioneer.com It has several advantages over Submachine and a few thousand active users.
... View more
‎Mar 03, 2025
10:44 AM
1 Upvote
Hey, this is a great direction! Please check the Style Bandit plugin: https://aescripts.com/style-bandit/ I built it to Copy/Paste text formatting between Text Layers. The most-recently copied text style is saved to a .json and can then be pasted across comps, projects, AE versions, etc. This plugin released in 2023 and added features as the text scripting API has expanded. 2,000 users There are many cases where I want to copy + paste the text style, and not the Source Text contents. Consider adding a built-in "Paste Style" option. I'll happily sunset the plugin once this is a native feature to AE. Thx
... View more
‎Feb 17, 2025
05:48 PM
1 Upvote
Thanks for the reply @VictoriaNece! That is a wild custom function to see working. And glad you caught the tutorial 🙂 I've seen some other home brewed functions. But specifying every value individually and mapping to the methods is the verbose part. I was envisioning something like: const styleA = thisComp.layer("Style A").text.sourceText.style;
const styleB = thisComp.layer("Style B").text.sourceText.style;
text.sourceText.style
.setStyleAt(styleA, 0, 10)
.setStyleAt(styleB, 11, 5)
... View more
‎Feb 06, 2025
10:30 AM
@rajmeetsingharora, here is a tutorial on the basics of Text Style expressions and the new per-character features in 2025. You can watch this tutorial to learn how to build mogrts with text styles, link text animators, and how to automatically style specific words: https://www.youtube.com/watch?v=yG8UbiKKeYw
... View more
‎Feb 05, 2025
09:15 PM
12 Upvotes
Text style expressions are fantastic! But chaining many methods together is verbose. Idea: Similar to getStyleAt(), I would like a setStyleAt() method. I want to create a style that contains a bunch of methods, and apply that style to a range. This method should apply a predefined Text Style object to a specified range and optional time. Parameters: Text Style object, index, time text.sourceText.setStyleAt(style, 0, 0) How will the idea help your workflow? I find myself chaining many style methods together and needing to individually apply all methods to the same ranges. This creates many lines of code for 1 "look". Example: text.sourceText.style
.setFillColor(effect("Color Control")("Color"), startIndex, numChars)
.setFont("Impact", startIndex, numChars)
.setTracking(5, startIndex, numChars)
.setAllCaps(true, startIndex, numChars) Benefits of Feature: If setStyleAt() method takes in a style object as a param, we can create multiple text layers with unique styles and pass each style into the method. In this way, you can create a "mixed" text style with varied ranges (ex. collage-style text). Use createStyle() to hold style attributes, and then apply all attributes to a range with setStyleAt() This allows you to define a style & reuse it, perfect for templates Enlist support! Vote on this fix~!
... View more
‎Feb 05, 2025
09:01 PM
1 Upvote
Thanks @Kevin-Monahan . This quirk is easy to repro on any machine and documented in https://ae-expressions.docsforadobe.dev/text/style/#textstylesetjustification. I chose to classify as a bug (not a feature idea) because the current implementation is unintuitive. It feels like an accidental oversight while building text style expressions.
... View more
‎Feb 05, 2025
08:35 PM
6 Upvotes
Issue: setJustification() is broken if it is set after setText(). Solution: Allow setJustification() to control paragraph alignment, irrespective of setText(). Adobe After Effects version number 25.xx Operating system Mac/Win Steps to reproduce This expression controls the Justification from a Dropdown Menu control and ignores the layer's Properties > Paragraph settings. var myString = "myText" + "\r" + "on a new line";
var menu = effect("Dropdown Menu Control")(1);
var myArray = ["alignLeft", "alignCenter", "alignRight"];
text.sourceText.style
.setText(myString)
.setJustification(myArray[menu - 1]) If you reverse the order of the final 2 lines, the Justification does not update from the Dropdown Menu but can still be controlled from the layer's Properties > Paragraph tab. var myString = "myText" + "\r" + "on a new line";
var menu = effect("Dropdown Menu Control")(1);
var myArray = ["alignLeft", "alignCenter", "alignRight"];
text.sourceText.style
.setJustification(myArray[menu - 1])
.setText(myString) Expected result The order of these text style methods should not matter, because they are affecting 2 different properties (i.e. text string contents & paragraph alignment). If setJustification() is being used, it should be the sole control of the justification. You should not be able to override setJustification() from the layer's Properties > Paragraph tab. Actual result Described above, the justification is ignored. How will the idea help your workflow? It is common to combine both setText() and setJustification() in AE templates. Users are unlikely to stumble upon the correct order of operations organically, and would expect setJustification() method is broken. Fixing this bug should not break older workflows and simply allows more flexiblity & ease of use moving forward. Enlist support! Vote on this fix~!
... View more
‎Jan 29, 2025
03:04 PM
1 Upvote
100% agreed. Please hide if "Show Tool Tips" preference is turned off
... View more
‎Jan 14, 2025
08:43 AM
This is one of those ancient features that should have been fixed years ago. Replacing media and maintaining in/out points feels the bare minimum for NLEs
... View more
‎Jan 10, 2025
11:53 AM
Issue - above Adobe Premiere Pro version number: 25.1.0 Operating system - Windows 10 19045.5247 System Info: CPU, GPU, RAM, HD: irrelevant Video format: irrelevant Workflow details: Team Project + Enhance Speech Steps to reproduce - (Very important!): Create a Team Project with multiple users Edit a sequence and use Enhance Speech on audio Publish changes, close project Reopen project Enhance Speech processes as a "user" and locks you out of the sequence because it has been "edited by a blank user" No way to remove Enhance Speech, because the sequence and attached nests become locked to View Only Only workaround is to duplicate the sequence and edit the duplicate. This sequence then bricks the next time the project is opened. Expected result - Not this Actual result - Above
... View more
‎Jan 10, 2025
11:11 AM
1 Upvote
Can't use Enhance Speech with Team Projects. The sequence becomes locked to (View Only) because Enhance Speech begins processing and counts as a user. Once it it finished processing, Team Projects thinks that a real user made some change and locks users out of it. Bricks a sequence. Awesome.
... View more
‎Dec 08, 2024
10:44 AM
1 Upvote
#innovationweek
... View more
‎Dec 08, 2024
10:39 AM
1 Upvote
+1000 #innovationweek
... View more
‎Dec 07, 2024
01:52 PM
2 Upvotes
Please change render order of Intrinsic Crop. It should operate the same as putting the "Crop" effect on as the first effect on a clip. Here is what the render order should be. Intrinsic Crop > Other Effects > Motion Why? Crop is normally the first effect applied. Other graphic adjustments are then made: transforms, blurs, glows, shadows, rounded corners, etc. Anytime I want to add other effects, Intrinsic Crop becomes useless (Nesting the clip as a workaround sucks). As it stands, 90% of the time I start with Intrinsic Crop and then have to switch to the Crop effect and redo the crop. Main Example Crop > Transform is one of the most common effect stacks. Transform effect allows Motion Blur (Motion > Position does not) Try using Intrinsic Crop and then using a Transform effect. Currently, the entire effect stack renders and then the Intrinsic Crop is applied. In other words, the image moves INSIDE the crop. This same argument applies for Drop Shadows, Glows, Rounded Corners, etc. Upvote if you agree
... View more
‎Dec 07, 2024
01:47 PM
1 Upvote
Please add keyboard modifiers for Intrinsic Crop in the Program Monitor via direct manipulation. These should work even if user is in the "Transform" mode. Mac: Hold ⌘ or ⌥ and click and drag an edge to freely crop the selected clip Add Shift to constrain proportions Win: Hold Ctrl or Alt and click and drag an edge to freely crop the selected clip Add Shift to constrain proportions
... View more
‎Dec 06, 2024
09:17 AM
1 Upvote
Alrighty then, my piece is spoken. We'll see if users get confused now that it's out
... View more
‎Dec 06, 2024
08:59 AM
Hi Mike, thanks for the explanation. This implementation is inappropriate for the vast majority of use cases. Crop is almost always the first applied effect to image/video. If a user wants Crop to render last, they can choose to put Crop at the bottom of an effect stack. It's not a 50/50 use case. It's a 90/10 use case where Crop is used first. Intrinsic Crop is currently more confusing to users and less useful than the crop effect. That's why I say it should be switched.
... View more
‎Dec 05, 2024
12:11 PM
4 Upvotes
This is awesome. I would like the Advanced Preferences + Lines to be sticky. Please default to the user's last used settings, so we don't have to open the dropdown + change the sliders every time we Translate/Create Captions.
... View more
‎Dec 05, 2024
12:07 PM
"Remove Gaps" is now a built-in feature to Captioneer. Here's several years of Reddit and Adobe Community posts complaining about the current implementation. https://community.adobe.com/t5/premiere-pro-discussions/help-me-find-a-way-to-remove-the-gap-between-subtitles/m-p/14862015#M529020 https://www.reddit.com/r/premiere/comments/10uk8sk/is_there_any_way_to_close_all_subtitle_gaps_at/?rdt=40883 https://www.reddit.com/r/premiere/comments/xqzpuz/any_subtitle_experts_out_there/ https://www.reddit.com/r/premiere/comments/1gfn1om/no_gaps_in_captions/ https://www.reddit.com/r/premiere/comments/1copihw/does_this_hotkey_exist_do_i_need_to_build_a_script/ https://www.reddit.com/r/premiere/comments/1cirigy/holes_in_captions/
... View more
‎Dec 05, 2024
11:51 AM
I've used this alot now, and this should be a cool feature. But the render order is wrong. Why? A crop is normally the first effect applied to an clip. Other graphic adjustments are then made: transforms, blurs, glows, shadows, rounded corners, etc. As it stands, every time I reach for Intrinsic Crop I then have to switch to the Crop effect. Main Example Crop > Transform is one of the most common effect stacks. Transform effect is used heavily because it allows Motion Blur (Motion > Position does not). Try using Intrinsic Crop and then using a Transform effect. Currently, the entire effect stack renders and then the Intrinsic Crop is applied. In other words, the image moves INSIDE the crop. Same argument applies for Drop Shadows, Glows, etc. Easy Solution It should operate the same as putting the "Crop" effect on a clip. Here is what the render order should be. Intrinsic Crop > Effect Stack > Motion
... View more
‎Oct 24, 2024
06:03 AM
@Oleh BetterMe Yes, you can set expression text direction (LTR/RTL) with: style.setDirection("left-to-right");
style.setDirection("right-to-left");
... View more
‎Oct 12, 2024
06:08 AM
1 Upvote
@Stan Jones the old dialog for File > Export > Captions does not have this problem and respects MRU. I experience this issue across both Mac and PC. Text panel > Captions > Export > SRT always defaults to project folder.
... View more
‎Oct 12, 2024
05:50 AM
Super cool feature! Love that the pop-up shortcut works anywhere in the UI. Also love that it works for multiple layers at a time. How do you feel about the default Shift+Tab shortcut? Currently we don’t support changing or removing the keyboard shortcut for Quick Set Anchor. Please let us know if this negatively affects your workflow. Fine default, but 100% needs custom keyboard shortcuts. Do you prefer the Properties Panel or the Shift+Tab shortcut? Shortcut > Prop panel Do you want the same sort of functionality for 3D Layers? How do you imagine that looking? 100%. I imagine each Anchor Point corner matches the corner points visible on the layer's bounding box. Z value could either be the front or the middle-depth of an extruded layer. Is there any confusion if you've already applied a rotation to your layer? Yes it's confusing. It would be nice if this anchor point shortcut took into account the Rotation of the layer. Either "just do it" or rotate the pop-up orientation to match the layer's rotation. Ex. if a layer is rotated 180* and flipped upside-down, the Anchor Point shortcut for bottom-right should target the layer's top-left point because it is visually the bottom-right. Currently it does not compensate for rotation. That said, this feature is still a win without the rotation update
... View more
‎Oct 07, 2024
08:34 PM
Have feedback for setJustification() Using this expression copies all Style settings from "Text 1", including paragraph justification. thisComp.layer("Text 1").text.sourceText.style However, the expression below copies Style settings, sets Text, and then throws away the paragraph justification set via Style. thisComp.layer("Text 1").text.sourceText.style.setText(thisComp.layer("Text 1").text.sourceText) This is inconsistent behavior compared to all the other style attributes. Doesn't make sense for Justification to be ignored, unless it is explicitly overrode later in the chain. It is also inconvenient. I kept the expressions barebones so this is clear. Request: Please match the established behavior for all Style attributes. ".style" should copy all style attributes unless overridden later in the chain.
... View more
‎Oct 05, 2024
08:21 PM
1 Upvote
+1 still an issue. Caused by Essential Graphics Panel "Browse" tab being open. Windows
... View more