Adam Morris
My feedback
-
149 votesAdam Morris
supported this idea
·
-
106 votesAdam Morris
supported this idea
·
-
7 votesAdam Morris
supported this idea
·
-
43 votes
An error occurred while saving the comment Adam Morris
supported this idea
·
-
42 votesAdam Morris
supported this idea
·
-
5 votes
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 aebugs@adobe.com. (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.)
An error occurred while saving the comment 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
Agree. This behaviour should be the same as in Premiere. It's a real pain when working with multiple audio clips and you're trying to align things to certain beats