Soren Laulainen
My feedback
-
2 votesNeeds More Info · 2 comments · After Effects » Workflow & interoperability · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Soren Laulainen
shared this idea
·
-
28 votes
An error occurred while saving the comment Soren Laulainen
commented
Yeah, we're using that right now for setting our render filenames. But any text strings we enter into the template here often have to be renamed when we create a new version or start a new project, which sort of defeats the purpose. Best we can do is create presets for each project, but that can quickly get cluttered. This request is to be able to add our own custom properties to the list of available properties so we can avoid hardcoding text strings into the Custom template. Then the presets can be more about which properties are going into the filename (and in what order), instead of defining what those properties are.
Soren Laulainen
shared this idea
·
-
8 votesSoren Laulainen
supported this idea
·
-
6 votesNeeds More Info · 5 comments · After Effects » User experience/interface · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Soren Laulainen
commented
Could possibly be the same as this issue:
https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/41563915-render-queue-output-to-uses-an-old-file-name-andAn error occurred while saving the comment Soren Laulainen
commented
I encountered this bug in After Effects v17.5.0.
Not sure how exactly it gets into the bugged state, but you need to create your own File Name and Location Templates (FNALT). Mine used the "projectFolder" token as well as ..\, "compName", "dateYear," "dateMonth," etc.
When it is bugged, AE will assign the same filename and render location to every comp you add to the Render Queue. It doesn't matter what the comp is named. It doesn't matter which project file you have open. It doesn't matter which FNALT is set as the default. You have to select a different FNALT from the dropdown menu to "fix" the output name/path before rendering each comp.
Upon some investigation, it seems this bug only happens when a certain Output Module (OM) template is being used. Not sure what the relationship is -- it's possible for me this is the OM that was set as the default when I first created my own FNALTs?
After changing the default Output Module to something different, AE starts to use the default FNAL correctly. If I switch back to the first OM, it starts being buggy again. See attached video.
Related/dupe issue:
https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/36084937-bug-report-file-name-and-location-template-keepsSoren Laulainen
supported this idea
·
-
16 votesSoren Laulainen
supported this idea
·
-
248 votesSoren Laulainen
supported this idea
·
-
570 votesSoren Laulainen
supported this idea
·
-
1,137 votesIn Progress ·
AdminVictoria Nece
(Sr. Product Manager, Motion Graphics and VFX, Adobe DVA)
responded
Multi-Frame Rendering is now available in After Effects public beta. We’re starting with Render Queue export, and will add support for preview, AME, MOGRTs and beyond in subsequent releases.
This is a significant update to the After Effects architecture. Unlike older versions that rendered multiple frames by creating copies of the application, this is true multithreaded rendering. The render pipeline has been optimized from end to end, enabling After Effects to use your system to its full potential.
We know how important rendering faster is to you. That’s why we’ve taken the time to do this right, and build a strong, high-performance foundation for the future. We appreciate your patience, and would love to hear how Multi-Frame Rendering is working on your hardware and with your projects.
You can learn more about this multi-year effort here: https://blog.adobe.com/en/publish/2021/03/10/multi-frame-rendering-now-in-after-effects-beta.html
Soren Laulainen
supported this idea
·
-
1 vote
An error occurred while saving the comment Soren Laulainen
commented
Crash log attached
Soren Laulainen
shared this idea
·
-
6 votes
Thank you for reporting this bug. Our team is investigating the cause of this problem.
This problem occurs when rendering from the After Effects render queue using premultiplied alpha. If you change the alpha mode to straight (in the Output Module Settings dialog, set the Color option to Straight (Unmatted)), the problem does not occur.
Soren Laulainen
supported this idea
·
-
3 votesSoren Laulainen
supported this idea
·
-
3 votesSoren Laulainen
supported this idea
·
-
4 votesSoren Laulainen
supported this idea
·
-
3 votes
An error occurred while saving the comment Soren Laulainen
commented
Adding this as a related idea which could solve this issue:
https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/42547753-add-customizable-tokens-properties-to-render-queueSoren Laulainen
supported this idea
·
-
2 votes
An error occurred while saving the comment Soren Laulainen
commented
Adding this as a related idea which could solve this issue:
https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/42547753-add-customizable-tokens-properties-to-render-queue -
2 votesSoren Laulainen
shared this idea
·
-
3 votesSoren Laulainen
supported this idea
·
-
1 voteSoren Laulainen
shared this idea
·
Hi John, I'm able to reproduce this in AE v18.0.1
OS: Windows 10 Home
CPU: i3-10100
RAM: 32GB
GPU: Radeon RX 5700 XT
This doesn't seem to happen if a user selects the output template and immediately hits Render -- an overwrite warning occurs then. However, if the user selects the output template, then clicks the filename to open the OS file browser popup, clicks Save (the location doesn't matter), the [projectPath] property gets removed from the filename. If the user then clicks Render, it overwrites the existing file without warning.