Hey there people,
I am working on a project in the new Audition CC. It is a sound mix project for a film, so I have the video playing in the corner etc. So, here's the problem... I only get 10 minutes to work within the program before it tries to access all 24GB of RAM that I have. I opened Task Manager and watched it climb higher and higher until Audition itself crashed and I lost my progress. That was the first time. The second, third and fourth times I was able to save everything while I watched all the terror unfold in my task manager window. I must say I was looking forward to the 64 bit advantages, but this is just crazy. I really need to finish this project!!!
I'm not quite sure what you mean. You are only able to edit for 10 minutes before a problem occurs? Or when you start building after the 10 minute mark, then it starts to have problems?
Can you send the sesx file as an attachment to email@example.com? No media, just the session file. I'll take a look and see if I can reproduce the problem. This is on Windows, correct?
I can second this issue, almost identically. Audition CC starts OK and then just goes out of control, using all the RAM and bringing performance to an usuable. I am working with huge projects (24 tracks of 48 Khz 24-bit files) with a lot of effects and processing, but I never had issues in CS6.
I notice this thread is over a month old, have you had any luck?
I am just about to enter a new project which will require the same work load as before. So I will keep you posted... To be honest, unless there was a bug fix for it, it is almost certain the same thing will occur again. It is really annoying.
I am having same problem and did the same thing you did. I have windows 7 64 bit 12 GB of RAM. As the video and audio play the memory load rises and it eventually just crashes. Must have something to do with the video aspect because it isn't an issue when only audio is involved.
I can confirm that using Audition alone on W7 doesn't do alarming things with RAM at all - never has. So this is almost certainly either a joint use issue as suggested, or a problem with whatever's playing the video.
I've only tried playing video once like this, and it was fine. It wasn't a large file though, so not really a thorough test.