Any progress in squashing this bug? Most of my projects require animations timed to audio files, so this is really taking its toll on my workflow.
We'll post information when we have some to share.
That's no solution at all. On many projects, losing the ability to scrub audio basically eliminates your ability to work (it's like telling Illustrator users to just "avoid using the pen tool.")
I would be a little more understanding that it's taking you so long to fix this really major bug if I wasn't paying $50 a month for this software!
This is ridiculous. Adobe can not release a software with a bug so big. If I have some delay in the delivery of my projects, I will sue Adobe. We want an urgent solution!
Who want to export to work in a previous version can not, because the Abobe After just be releasing buggy to downlad, ie, all versions of Afer I'm testing are with this problem in my Mac OSX 10.9.4, including the After CS6!
We need an urgent solution, I am unable to work right having to close and open the After every two minutes
This problem also occurs in compositions without audio!
It was pretty frustrating when I ran into this issue and reported it a while back. When I first converted my project, I managed to do a bunch of edits in AE CC 2014 before the problem became more aware that it was a serious issue (it was a slow leak). I didn't want to have to go back to the previous version and redo the many edits I did. So, I stuck with the issue and managed to get through it. I had my memory monitor opened so that I can check when I need to save before a memory peak occurred and constant errors would popup preventing me from saving.
It seems that the memory leak was somewhat random every time I started AE CC 2014. Certain times, very little memory would fill up. At other times, it would fill up instantly. So, it was basically sort of toughing through it and yet I was still able to make use of the audio scrubber feature with caution.
Hopefully this will be patched by the time I have to work on another AE project so that I can stay up to date rather than having to have multiple version of the same product installed. I always get the feeling that the more you have installed on your machine the slower it becomes. I like to keep it clean and lean.
Thanks for looking into the issue, Adobe. Although, it surprises me that such a nasty bug from such a useful feature was overlooked. It makes me wonder how thorough Adobe's 2014 product QA process really was.
I didn't want to have to go back to the previous version and redo the many edits I did.
You could have used the "Save As CC" command and saved it back to version 12 with all the changes you had made.
This page explains how to install the old versions for anyone who needs to drop back to CC, but had uninstalled it.
Ah thank you! I was under the impression that you couldn't go backwards once converted. Didn't know there was actually an option for CC 12 saving. Thanks!
I think what it is, is that I am used the compatibility mode with Photoshop and assumed that if there isn't an option for compatibility, there's no way of saving back to an older version. That's probably how I got the impression.
> This problem also occurs in compositions without audio!
There are many ways to encounter this message, many of which are not due to bugs in the application or the operating system; some of the causes are due to "normal" use, such as mistakenly starting a RAM preview when the current-time indicator is already at the end of the work area, but the From Current Time option is enabled.
On this thread, we're discussing one specific cause of this message, which is due to a memory leak when scrubbing (dragging the current-time indicator) to preview with audio.
If you're encountering this message in a different scenario, please start a new thread to discuss that.
Agree with @Kdinello and @Parrotface, this issue is a massive setback for us animators and is making work almost impossible. It is unacceptable to just suggest resolving it by closing and restarting After Effects, I am having to do this literally every 2 minutes now and its driving me nuts aside from costing me serious work time. I even went as far as doubling the RAM in my machine, assuming that the new version was just more memory hungry... you can imagine my disappointment when the problem persisted.
As others have pointed out this is major bug that needs to be sorted out asap. The most frustrating part is that this is a brand new issue that I had never encountered before the recent CC 2014 update. I shouldn't have to redownload an old version of the software and convert all my project files to be able continue working. Really hope this issue is resolved soon, its been about a month since the CC 2014 roll-out I believe, and I know I'm not the only one suffering with this.
Is there at least a time frame for when we might expect a resolution for this even though you don't have "something to share" at the moment? I have half as much hair on my head as I did about a month ago and clients breathing down my neck. I love the new keying features, but the new RAM "feature" I can do without.
I wish Adobe the best of luck finding a resolution to this problem. God help us all in the meantime.
This problem is happening in all CS6, CC and CC 2014 versions in my Macbook 13, 4G, Retina (Maverics).
I have another iMac running Lion and without CS6 upgrade and this problem does not happen.
Now, in my new iMacbook tried installing these 3 versions and the problem happens all the time.
Eu uso o After a 6 anos e dessa vez as atualizações das versões não estão adiantando.
I've opened another post about this issue and got no answer. The Abode is doing what about it? How do I know if this problem happens only on projects that have audio? Just tell me to write another post to escape the problem?
And there's no use saying that the problem is my computer because it is new.
I bought a new Macbook two weeks, I have just installed and After I tested all versions are appearing this problem. The detail is that all versions are up to date.
I think Adobe has failed to keep upgrading to Maverics, is not possible. Is impossible to work, turning off After every two minutes!
Have you tried installing programs to free up memory and it did not work!
As the message 'frames 2' is the title of this post, I'll keep posting here, none of the updates worked in Maverics.
I will file a lawsuit against Adobe in my country, the Abode not help me, is a lack of respect for the user.
I received the error as well and I was able to fix my problem with simple fix after calling an adobe representative.
First these are my specs
Geforce GTX 650 Ti
AMD FX(tm)-8120 eight-core Proccessor
What I was asked to do was see how much RAM I allocated to After Effects, I had 13 gigs of Ram, Find out how much you are allocating by searching under EDIT_PREFERENCES_MEMORY & MULTIPROCESSING. See how much ram is available for AE. You can change the Number under RAM RESERVED FOR OTHER APPLICATIONS. The adobe rep informed me that for "someone reason After Effects Prefers Even numbers and to change my allocated RAM to an even number and to turn off AE Multiprocessing"
Now it's running smoothly and I can Scrub all day long. This worked for me in my situation, but try making RAM AVAILABLE FOR AE an EVEN NUMBER!
> The adobe rep informed me that for "someone reason After Effects Prefers Even numbers and to change my allocated RAM to an even number and to turn off AE Multiprocessing"
Please give me the case number for your interaction with Adobe Technical Support so that I can follow up with the person with whom you talked. The advice that you were given makes no sense to me; there is no reason that leaving an even number of gigabytes free for other applications will work better than an odd number.
I had the following settings set and had the RAM filling up quickly issue at random times.
- RAM reserved for other applications = 2
- Render Multiple Frames Simultaneously = Checked
-- Only for Render Queue, not for RAM Preview = Checked
Have you tried running After Effects different times to see if your success is persistent? The memory leak is an issue where it's worse (or only happens) in certain instances.
I'm not currently working on a AE project at the moment to see how your solution works for me. I have other tasks to take care of for a while.
Adobe Case Update : 0185806987 : Ashish P
This error message problem hit me hard. I can barely work. In addition to this issue, another issue started at the same time, RAM previews and audio previews (period key) sometimes speed up the playback or slow down the playback.
I also am experiencing the same problems in CS6, CC and CC2014 on Mac OSX 10.9.4. Quitting every other Adobe app open does help - mainly Photoshop and Premiere, but working that way is ridiculous. Hope this gets patched soon.
Mine is on a 3.33 6-Core "Mid-2012" running OSX 10.9.4 with GTX 680 (official version) and 32GB RAM.
I have the same problem wit my PC (i7 3770 CPU @3,4Ghz and 16Gb RAM + SSD and 660GTX) so I don't think that is only on Mac system.
But when I reboot the software, I can do a PREVIEW RAM... how understand it?
Is this problem only happening with NVIDIA cards then? Has anyone with another card experienced this same issue? That would at least narrow it down a little bit. Sounds like it may be GPU related somehow...
Restarting the software seems to "solve" the memory leak issue temporarily.
> Is this problem only happening with NVIDIA cards then?
This has nothing to do with the GPU.
As I said above, this bug is due to a memory (RAM) leak when scrubbing (dragging the current-time indicator) to preview with audio.
It's not just NVIDIA cards, it also happens on my ATI. It's not GPU related. It's a memory leak as Tim stated in the first post of this thread. And yes, restarting AE will get things working again, but only until the leak fills up all available RAM allotted to AE. Then the error pops up when you try to RAM preview, or worse, locks up AE to the point you have to force quit. You're best off going back to AE CC (v12) if you like to scrub audio. (See the comments above on how to do that.) Otherwise, you'll find AE CC2014 (v13) virtually unusable. Looks like v13 was an unlucky number for Adobe.
Is this going to be addressed with an update anytime soon?
> Is this going to be addressed with an update anytime soon?
We have a preliminary fix in testing now. The best estimate that I have for when an update will be released with this fix is more than one month and less than two months from now.
Ho do I explain that to my client, who needs the finished article this weekend? Brilliant.
I just want to say that I'm experiencing this issue since 2 months ago. At that time I actually bought a new Mac Pro and was really excited to start using the powerful machine and produce some videos. Suddenly all my excitement changed to disappointment because of this issue!
So what is the alternative? Apple Motion 5? I actually bought it already and started to learn it. However, I still want to use AE and I hope you fix this issue really soon.
I think this issue is "a loosing customers issue" and needs to be resolved really quickly.
All the best fixing the issue and I'm waiting for the coming update.
The "reliable" alternative is to go back to using CS6 or CC on 10.8.x it seems. If you have a system clone and NEED to scrub audio constantly, then it might be worth considering. If you don't have a system clone, you'll need to reinstall the OS and likely have to do a clean install to have success with it.
I'm working around it, but it's really interfering with my typical workflow. These same issues are present in CC for many people (as well as CC 2014), so I'm not sure if simply going back to the old version will do the trick for you. Not really sure if this was introduced with a 10.9.x update, or if it's completely related to the CC 2014 release.
Would agree that it's a pretty serious issue, however as the critics say - we're all locked into the subscription model now, so we're kinda stuck and at the mercy of updates and patch releases. Hope it's released sooner than the around 6-week time frame that they're expecting.
1 person found this helpful
This post turned out longer than I expected, so in short let me say that:
1 - I understand everyone's frustration
2 - Suck it up, don't scrub audio as much or just go back to CC(12) if you need to, and your frustration will go away.
I disagree that the reliable alternative is CS6 on OSX 10.8 as bsbeamer states above. And MAB991, Apple Motion 5 will never be considered an alternative in my opinion, but good for you for trying it out.
I've been using CC (12) on 10.9 once I saw that combo was working, and it's always been stable for me. Once I saw this thread, I've switched back to CC (12) from CC2014 and I feel like a normal human being again and my wife has even started talking to me again. I get it. The bug sucks and it sucks the productivity from your ability to work. But seriously, just go back to using CC (12), it should still be on your computer after the CC 2014 install. And if it's not, just download it from Adobe and install it. There are instructions above on how to find it.
I understand everyones frustration, I was there myself. I broke the cardinal rule of "NEVER UPDATE IN THE MIDDLE OF A PAYING PROJECT." I only have myself to blame for that one. I knew about the rule and I broke it. I really wanted to use some of the new keying features for my project. I did, and they were awesome. But once I got into the more motion graphic intensive areas of my project and audio scrubbing, the bug became a problem. I had already done a lot of work in CC2014 so opening up my older version of the project was not an option. Use the "Save As CC (12)" option in the save menu to get your project back into CC (12). More info on that in the comments above by Szalam.
And weren't we "stuck at the mercy" of Adobe for updates and patches before the subscription? I certainly know I wasn't writing code for AE to make it better.
Adobe dropped a shiny new tow in front of us to play with. Some of us grabbed it, started playing with it, and it cut our finger. We cried for a minute. Then went back to our old, trusty toy and started having fun again. You can play with the new toy now if you're careful; or you can wait for the sharp edges to be removed and play with it then. It's your choice.
Hi all, just wanted to say, I am currently working on an award show for TV and have been scrubbing audio in AE CC 2014 18.104.22.168 without issue. Why am I not having the memory leak problem?
Would like to help if I can.
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: 12-Core Intel Xeon E5
Processor Speed: 2.7 GHz
Number of Processors: 1
Total Number of Cores: 12
L2 Cache (per Core): 256 KB
L3 Cache: 30 MB
Memory: 64 GB
Boot ROM Version: MP61.0116.B05
SMC Version (system): 2.20f18
Illumination Version: 1.4a6
System Software Overview:
System Version: OS X 10.9.4 (13E28)
Kernel Version: Darwin 13.3.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Secure Virtual Memory: Enabled
Time since boot: 1 day7:24
No, not in my case the problem is occurring in CS6 CC and CC 2014!
No, not in my case the problem is occurring in CS6 CC and 2014 CC.
I am already in contact with the support in my country, but this not working.
If 30 days go by I will file lawsuits against Adobe.
I'm avinsando it makes time already opened a post about the problem and the Abode is silent.
Moral damages will be great, and I will ask compensation proportional to the values I charge my clients.
No, not in my case the problem is occurring in CS6 CC and 2014 CC.
Wait, has After Effects ever worked for you? If so, what changed?
If you're having the problem in all three programs, something is wrong with your system and not with Adobe's software. Most of us are using CS6 and CC without the problems you're describing.
I am having the same problem on the new CC 2014 version. RAM preview requires 2 or more frames.... Have to restart AE every 20 minutes. What a pain. I used to have this problem when using CS6 but CC seemed to get rid of it to my relief. Now it's back! So I tried to take it home to work and guess what - it won't open on my older version of CC....So I downloaded CC 2014 on my new Mac laptop and exactly the same problem. It's unworkable. What a waste of time.
I agree that we should be compensated for the time wasted. I am managing an animation studio and trying to stay on top of new technology has become a huge issue especially when it doesn't work. Adobe I love you but you're bringing me down...
- Open your file in CC2014
- Go to "File"
- Save As
- Save a Copy As CC (12)
Close AE CC2014, then open your new file you just saved in AE CC (12)
Word has it, the bug will be fixed in the next month or 2.