Skip to main content

Filter by idea status

10000+ Ideas

_nicdean
Community Expert
_nicdeanCommunity Expert

Figma "Auto-Layout" in After EffectsOpen for Voting

You may have noticed that Figma released Figma Motion and is gunning for animation software. Can we get Figma’s Auto-Layout in After Effects? How will the idea help your workflow? It is hard to imagine what design would not benefit from an auto-layout system. Anything with text, shapes, and images smaller than the full video frame would benefit. The simple example of “text in a box” is the most basic, but this same idea is required for animating UX/UI animation, product videos, and templates.Current workflows to mimic responsive design are to use complex expressions, 3rd party scripts, or manually create many variations.Expressions are a bad workflow for layout because they require a coding skills which most motion designers don’t have; and for those with the skills, it is still tedious to set up and “rig”. Once rigged, AE’s limited performance is further bogged down by running those heavy expressions on every single frame.Scripts and plugins are a bad workflow for layout because they must be sourced, installed, and then run per action by the user. Layouts should be manually built, procedurally calculated, and update without user intervention.Parenting is not a suitable workflow because it is too limited. It does not take into account the variable size of a parent (ex. text, a masked image, vector shape), nor can you “parent” to multiple things.Size and position layout constraints are a simple and intuitive feature already used across web dev and other design tools, and would help After Effects remain relevant in a competitive landscape of motion design tools. 

シャドウのグラデーション挙動Open for Voting

Premiere Proのエッセンシャルグラフィックスにおけるシャドウのグラデーション挙動について、ご報告と要望があります。Premiere 2024から2025頃にかけて、シャドウのグラデーションが「文字ごと」ではなく「テキスト全体」を基準に計算されるようになりました。Premiere 2025では、「塗り」をグラデーションに設定すると、シャドウのグラデーションが再び「文字ごと」に適用される挙動となり、この方法で従来のデザインを維持することができました。ところがPremiere 2026では、この挙動が変更され、塗りの設定に関係なく、シャドウのグラデーションが常に「テキスト全体」で計算されるようになっています。その結果、Premiere 2025までの挙動を前提に制作したテロップテンプレートやモーショングラフィックステンプレートで、デザインが変わってしまう問題が発生しています。もし意図しない挙動であれば、修正をご検討いただけますと幸いです。一方、仕様変更である場合は、既存テンプレートとの互換性を保ち、用途に応じて使い分けられるよう、・文字ごと・テキスト全体を切り替えられるオプションを追加していただけると大変助かります。ご検討のほど、よろしくお願いいたします。 I would like to report an issue and make a feature request regarding the shadow gradient behavior in Essential Graphics for Premiere Pro.Around Premiere 2024–2025, the shadow gradient behavior changed from being calculated per character to being calculated across the entire text.In Premiere 2025, setting the Fill to "Gradient" caused the shadow gradient to be applied per character again, allowing existing text designs to be preserved.However, in Premiere 2026, this behavior changed. Regardless of the Fill setting, the shadow gradient is always calculated across the entire text.As a result, text templates and Motion Graphics templates created based on the Premiere 2025 behavior no longer display as intended.If this behavior is unintentional, I would appreciate it if you could investigate and consider fixing it.If this change is intentional, I would like to request an option to choose how shadow gradients are applied: Per Character Across Entire Text This would help maintain compatibility with existing templates while also providing greater flexibility for users.Thank you for your consideration. 

Mike Choo
Mike ChooInspiring

Let the Pickwhip twirl down layer items on hover, as the Project Panel would if dragging to a closed folderOpen for Voting

Hey! When using the Pickwhip to reference things while writing expressions I frequently forget to twirl open the property I intend to select. This usually means that I have to exit writing the expression where I am, twirl open the property in the timeline to make it visible, then resume the expression writing / pickwhip and carry on.It would be a good quality of life improvement if while dragging the pickwhip, hovering over a twirled-up item would unfold it. The closest analogue would be dragging a file into the Project Panel - if I hover over a closed Project Panel folder for a second or so it will twirl open.I’d initially suggest that this would only be useful to have on the Expression Pickwhip - there seems to be limited functional use for adding it to the Matte or Parent Pickwhips.Perhaps a longer timeout when hovering over a layer itself compared to hovering over a layer property might be useful - that way users would be less likely to trigger un-twirling when simply selecting top-level layers, and would make the initial twirl open feel deliberate. A quicker activation when hovering over an exposed property would make sense, and be helpful if there are multiple levels to get to before exposing the property or control to be targeted.The use cases for this happen to me most often when referencing Effects for expressions. If I remember to do so I will pin open the effects panel on the appropriate layer, but I frequently forget to do so, and this update would mitigate that requirement for pre-thought, and allow more spontaneous experimentation while writing expressions.TLDR - Let the Expression Pickwhip twirl down layers when dragged and hovered over layers and properties. Adding this functionality to the pickwhip would be really valuable - it would help stay in the flow, reduce the amount of clicks needed per task, and make it easier to experiment.Cheers!

Antoine HLMN
Antoine HLMNInspiring

P: Warning about DNG increases file sizeOpen for Voting

See this discussion:   I tried the “convert to DNG” function and in INCREASED the file size. Settings were:Only convert Raw files (obviously) Delete originals after successful conversion Extension: dng Compatibility: CR 16.0 and later JPEG Preview: None Emebed fast load data: NO Use Lossy compression: NO Embed Original Raw File: NOWhile I do understand the benefit of DNG over proprietary raw, for long term support, I do not think it’s a good idea to allow an increase in file size without a warning.While the alleged open character of the dng format is a good selling point, I do not think it’s going to be an issue to open raw files in the future. Nevertheless, I appreciate that option. Therefore I think the main selling point of dng would be a higher compression yielding in smaller files.Note: I also know that a Lossy compression would obviously output smaller files, but that’s not the point. ==>Hi ​@Antoine HLMN,Thank you for taking the time to explain your suggestion in more detail.I understand your point. Your suggestion isn’t about whether DNG is useful, but rather about improving the user experience when the Convert to DNG operation results in a file that’s larger than the original RAW.For anyone interested in learning more about the DNG format and its intended use, we has a detailed overview here:https://helpx.adobe.com/camera-raw/digital-negative.htmlAs discussed in this thread, there are valid scenarios where converting to DNG can result in a larger file depending on the source RAW format and the data that needs to be stored. However, your suggestion that Lightroom could warn users before a conversion increases file size is a reasonable enhancement request.Since this is a feature request rather than a bug, I’d encourage you to post it in the Feature Requests section of the Lightroom Classic Community. The team monitoring that section regularly reviews feature requests and shares them with the product team for consideration.Including your use case and why you’d find a warning helpful will provide valuable context for the discussion.Best,Anshul Saini