I've been playing around a little with PE 11, and had several crashes and hangs for the last couple of hours:
- hangs when rendering the timeline using the enter key
- crashes when re-opening a project: Adobe Media Core CS6 has stopped working (Adobe QT32 Server.exe, QuickTime.qts 184.108.40.206)
- sometimes getting 'unknown error' when 'sharing' this project as a high quality i
I can manage to re-open the project if i clean my rendered files and media cache, but it's extremely annoying.
I believe it's related to one of the video i'm using, a prores APCN 1920x1080 29.97fps.
I have no problems opening/viewing it using any tool on my computer, or by using the Organizer.
If i rename the directory which contain this specific video, try to open the project and remap the missing file with a H264 version instead of prores, it crashes right away.
The current virtual memory size and private bytes doesn't seem strange/excessive, and i'm also okay on the system commit charge.
I'm running up to date PE 11, and re-installed latest Quicktime just to be on the safe side.
I do not have any other memory/resources consuming software running in the background.
My specs: Win7 ultimate 32bits completely up to date, 4gb, i7 940, GT 620
Any idea what could be causing this?
- C: system / PE 11 / paging disk / SATA ~200GB free (~30MB/s i'd believe)
- Z: PE's media cache / PE's scratch directories / projects and resources / eSATA ~500GB free (~20MB/s i'd believe)
Really hope this kind of setup is not the cause of a crash in the QT32 server that is.
One thing i forgot to mention: i can 'share' and burn the project in AVCHD... (while i can't preview-render it using the enter key without a crash or hang, just got a new one in MSVCR90.dll)
Thank you for the I/O info. With that second eSATA, and the free-space on each disk, I do not see what would be a problem there.
Take a look at this FAQ Entry: http://forums.adobe.com/thread/792580?tstart=0
It starts with a checklist on getting PrE set up properly, then goes into detail on tuning one's computer and OS. Finally, it has links to troubleshooting articles, with more links to tools to help in that process. Be sure to check out "Finding Clues," with the use of the Event Viewer. There might be some clues there, that will be helpful.