Anyone else have these CS4 bugs? : Adobe After Effects
This is a discussion on Anyone else have these CS4 bugs? within the Adobe After Effects forums in Adobe Tools category; Been using this new version for the past week and noticed 2 bugs and wondered if it was just me: 1) When auto-save is turned on, if the machine recently "auto-saves" you cannot save your file unless you change something or do a "save as." For example, Say it is 1 AM I've been working on a file since 11 PM and all of my auto saves have been updated at the set increments but if you look at my file, it hasn't been saved since 11:30 and right now the save function is grayed out because the auto save ...
| Adobe After Effects Adobe After Effects discussion forums |
![]() |
| | LinkBack | Thread Tools |
|
#1
| |||
| |||
| 1) When auto-save is turned on, if the machine recently "auto-saves" you cannot save your file unless you change something or do a "save as." For example, Say it is 1 AM I've been working on a file since 11 PM and all of my auto saves have been updated at the set increments but if you look at my file, it hasn't been saved since 11:30 and right now the save function is grayed out because the auto save just happened. 2) Once you send a comp to render, all of your undos are wiped. Anyone else? |
|
#2
| |||
| |||
| Both issues are known and will be addressed in a patch release. Mylenium |
|
#3
| |||
| |||
| Fantastic! Been a long time but you have come to my rescue again Mylenium! Found another thing though this morning. When I hit the render button while I have multiprocessors (render multiple frames) turned on I get a spinning beach ball pause for about 30-40 seconds before it starts rendering. When multiprocessing turned off, it starts rendering right away. Once the first render starts and I stop it and start a fresh duplicate render, the pause goes away. |
|
#4
| |||
| |||
| Reminder: Any time you think you've encountered a bug, please let us know by sending a message to aebugs@adobe.com or by filling out the form at <http://www.adobe.com/go/wish> . |
|
#5
| |||
| |||
| How many background instances do you use in your MP renders? There are some cases where it will not initiate immediately if you do not use all 8 cores and only use 6 or even less. However, these issues have no clear pattern to them, so they are hard to nail down. In any case, file a report as Todd suggested. Every bit of info helps the devs to get a more complete picture. Specific to your scenario, it would possibly be a good idea to render a clip using the per frame info option for logging. The time info contained in the log may reveal where things slow down. Mylenium |
|
#6
| |||
| |||
| Thanks. I sent a report via the website outlining these issues. The problem occurs regardless if I'm using 8 or 6 processors. But, like I mentioned before, once the comp is rendered once or I start and stop the render after the "beach ball pause" the pause goes away and only returns once I restart Aftereffects. |
|
#7
| |||
| |||
| Turn on "Show Rendering Progress in Info Panel" under Preferences -> Display and make sure you can see that panel. It will tell you when it is saving the project file and loading it into the other instances of AE. - Jonas Hummelstrand <http://generalspecialist.com/> |
|
#8
| |||
| |||
| The 30-40 second delay is awfully long to wait for background renderers to spool up. Hopefully we can make some sense of it when we read your bug report. --c |
|
#9
| |||
| |||
| The save bug is unpardonable---jesus...nice testing! Lance |
|
#10
| |||
| |||
| Lance, please understand that we all try to do our best, but it's natural that some issues slip. There is no way for anyone to test every workflow and combination of features or how they may wrongly interact with each other. A day has only so many hours and just like posting on this forum to provide help, quite a bit of testing is done by normal users like you and me who still need to work to earn a living. I'd love to do more to get better software, but Adobe doesn't pay my bills, so there you go... And just for consideration: I'm sure even you would prefer that "essentials" get fixed first like that ugly thing when Photoshop installs hosed up your hard drive... Compared to that an incorrect flagging of the file save status, which can be overridden by using "Save As" any time, seems minor. Mylenium |



