Render queue multiple frame ranges
A few versions ago Adobe broke AE's render queue. Now all jobs' frame ranges reflect the current In/Out markers making multiple render jobs useless unless you manually edit the render settings > custom frame range PER queue job. I can't see how this is at all useful in any situation and I would much prefer to be able to queue multiple frame ranges than render the current frames multiple times, making a complete1 mess2 of3 your4 output5 folder6.
Please revert back to how it worked before it became broken.
Thank you for filing this report.
There were no intentional changes to the behavior of rendering frame ranges in the Render Queue. We need more information to understand the problem you are describing.
Can you provide us with a project with items set up in the queue that do not render as you expect? It will help to have a clear picture of what you are doing, what you expect the result to be, and what result you are actually getting.
Post a link to your files here, or if you prefer not to post publicly you can send it to firstname.lastname@example.org. (If you send to that address: A) Do not send .zip files, they will be blocked; renaming to .thisisazipfile is OK. B) Post a comment here when you have sent the email. I need to manually check that inbox.)
Roei Tzoref commented
this behavior actually was always like that AFAIK. i.e the default is to update the range of the workarea in all the render queue tasks unless you click custom.
checking on my oldest Ae version - CS6 shows the same behavior. send a render queue at some of the workarea, change the workarea, send another - the workarea changes in all the render tasks and not just the last. the only way to "force" it to accept the changes is to click custom workarea and ok.
Adam Morris commented
Another vote to fix this please! I thought I'd just queued up 12 different renders based on the work area I'd set for each when adding to the render que. Only to find the current working area is overriding all of them! Please fix this. It's totally counter-intuitive and a very annoying regression
Alexander Anguix commented
Yes... please fix this already!!
Philip Tyrer commented
Urg... 2020 and this is still an issue. I forgot about it and have queued up multiple frame ranges across many comps and now I have to go back through and not only redo the render queue, but also work out what was changed and likely sit through the renders one at a time.
This bug is really frustrating!
Philip Tyrer commented
Hi Tim. Thank you for responding. Here is a project that hopefully explains the issue well:
Let me know what else I can do to help.