Boris2016 wrote Szalam wrote But AE has always just cached what it could and then played it. I've never considered it a problem.
The point of posting this stuff is to identify limitations within AE and bring it to Adobes attention to see if they can fix it. To post 'oh thats always been broke but we're used to that' is not so much use. |
Apologies. That's what I was saying too. I'm sorry I didn't make that clear enough. I was trying to say that I think I and most AE pros are just so used to this behavior that we don't even think about it. I mean, that's how AE's worked since...well, since I started using AE back on version...4...I think? And we're on 14.1 now. so I'm very, very used to it!
It would probably be useful to have something show up in the Info panel at least to say, "Hey, we've built the preview this far, but you're out of RAM for more." (But worded differently, of course.)
Boris2016 wrote It's also not true - Adobe 2015 onwards had a huge redesign of the rendering process, which Adobe spent a lot of time telling us why it was so great and why we no longer needed to cache things. For it not to work as it should for me is a problem. |
It's actually not all that different. And it still caches things; Adobe never said it didn't cache things. I mean, look at the options in the panel; it talks about caching right there.
That being said, it can play back certain types of video files without needing to cache them. That is a very recent change that came with 14.0 (I think - it might have been 13.8), but everything else it still renders frames which are cached in RAM and then it plays them back. The big difference is that you can still poke at stuff while AE is rendering. Not so useful, in my opinion, for changing stuff while a preview is running (although, I have done that), but VERY useful in that I can keep working on something without being stuck waiting for the comp panel to refresh. The important "great" stuff about the new preview is that the renderer and the UI are running on separate processing threads in your computer. But how it actually behaves as far as being a RAM preview isn't all that different in regards to the issue you're describing. As I mentioned, the behavior you describe is exactly the way it's behaved since the early days.
It's not unusual for certain comps to be able to preview 30 seconds while others are only able to preview 2 seconds on the same computer because some things take up a lot more RAM when caching. Now, if you open the project you're working on now in CC 2014 and it previews the whole thing than we have a bug in how the software is working. But, if it's just the normal way preview works, than it's a bug in the UI inasmuch as it's not designed well enough for people to understand what is happening. I mean, they're aware that some people stumble on this point. There's even been a FAQ about it. (Which was updated back in 2014, but hasn't been updated with info on the new previewer and its parlance.)
16
Replies
AdChoices