Opening project crashes Color
Other projects work just fine, it's only this particular one that causes the program to quit whenever I open it. Any suggestions before I redo the whole project?
Grades are saved so it's not the end of the world, but what a pain!
The only thing I have to add to this discussion is more confusion. I'm working on two different MacPro machines. One is a Dual-Core Intel Xeon running OS 10.5.8 with 8GB of RAM a ATI Radeon HD 3870 with two monitors with an Intensity Pro Card and the other is a Quad-Core Intel Xeon running OS 10.6.2 with 10GB of RAM and a ATI Radeon HD 3870.
Neither of which can run Color with it crashing. I can usually get through Color loading all of the thumbnails in the timeline but as soon as I move the cursor on the timeline it crashes. Both machines respond the same and both are using different media, editing different projects.
I opened up a project on the Quad-Core that was from the previous Color version and it opened fine and I was able to work with it.
Here is the first part of my crash log, which is no easier for me to understand than women.
For the record, I have tried just about everything that has been mentioned in these forums, including the yelling at the systems, but to no avail. Can you not pull from external hard drives when working in color? I used to. I just don't get what's happening.
Process: Color [525]
Path: /Applications/Color.app/Contents/MacOS/Color
Identifier: com.apple.color
Version: 1.5.1 (578)
Build Info: Color-5780000~8
Code Type: X86 (Native)
Parent Process: launchd [372]
Interval Since Last Report: 699344 sec
Crashes Since Last Report: 6
Per-App Interval Since Last Report: 1132 sec
Per-App Crashes Since Last Report: 3
Date/Time: 2010-03-02 11:10:04.515 -0700
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: 3E6EC544-6F33-40EC-B09C-4CA4C983E2C2
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000008
Crashed Thread: 0
Similar Messages
-
Im using premiere element 9 getting serious error occurred force to close can't open project crashes
Im using Mac and recently when openning projects in premiere 9 i get serious error occurred force close. It was working and my computer crashed and new hardware was installed. I was able to do one project before this started. I can edit and complete my video but cant burn or reopen the project without get the error message and closes. How do i repair?
What was it that Meatload said, "two out of three ain't bad... ?"
Glad that two Projects burned properly.
Before you trash that one Project, I would do this little exercise:
Move all of your Assets (your Media files) to another folder, so that PrE cannot find them. That part is much easier, if you set up your Project in its own folder structure, with sub-folders containing all media used.
Then Open that Project. In the loading process, you should get a dialog screen, asking "Where is file ______?" At that point, navigate to the new location, that you Moved the files to. PrE will then re-link to that first file, and then survey the PREL (Project) file, and re-link to every file used in the Project. If the media is in several sub-folders, you will need to repeat that navigation to the respective sub-folder.
Then, test the Project to see if that re-linking has "fixed" things.
If not, then the Project is probably corrupt.
Good luck, and let us know how it goes.
Hunt -
I have two projects in my Flash Builder Package explorer that are closed. When I try to open either of them the system works for about 5 seconds and then the window application says not responding. And it will stay in a not responding state for at least 10 minutes, as I did a force quite after that 10 mins.
I tried to look through the logs in .metadata but did not find anything pertaining to the crash.
I created a new project and closed it and opened it and everything was fine. Obviously there is something wrong with the two closed projects I have, but I can't figure out what. Can anyone help?
I was able to get "fix" the problem by just creating a new project from my SVN repo, but I would still like to know a solution to the original problem.
Thanks,
Bryncould be. could be. there is definitely a bug in there somewhere, but it's going to be 10x more difficult to debug if you can't even open the project. this should give you a chance to get in there and make some changes, then see if the compiler continues to choke and hone in on the problem. if you can narrow it down, submitting a bug report would help everyone.
oh, and i do agree that, ideally, FB should never crash .
- e -
Photo app crashing when opening projects
Every time I try to go into the projects I created using phot and its predecessor, the app crashes and closes
Have you tried to repair the Photos library?
Try to repair your Photos library using the First Aid Tools:
Make a backup copy of your Photos Library on an external drive.
To repair hold down the alt/option and the command key simultaneously while double clicking thePhotos application in the Applications folder to launch the First aid tools. Hold down both keys firmly and long enough, until the First Aid panel will appear.
The select "Repair ...".
Can you create and open projects, if you create a new test library? Launch Photos while holding down the alt/options key. Import a few photos and try to create a book or another project. Does that work at all, if you use a different library? -
Logic Pro X crash while opening project
Hello all,
Using Logic since 9 came out. Saw that X was released so I figured I'd do it right...new SSD OS X drive, clean install of Mountain Lion 10.8, maxed out my 12 core Mac Pro with 64 GB ram, downloaded the new Logic Pro X, re-installed my Native Instruments Komplete 8 bundle. I've been using it trouble-free now for about a week, and loving the update. Until now.
One of my projects crashed and now it won't re-open.
I tried re-booting.
I trashed my preference files and restarted.
I can open Logic Pro, and other project files OK. I opened the Audio Units Manager and disabled ALL plugins, Quit Logic and restarted. Still crashes when opening this project file.
If it's not the plugins, and Logic is working fine otherwise, it must be something to do with a particular audio file within the bin. So I moved the Audio Files folder to my desktop and Skipped the locate files option. Still crashes.
All software is up to date. Any suggestions? Here's the most recent crash report, after disabling all plugins and moving the audio files:
Process: Logic Pro X [1264]
Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X
Identifier: com.apple.logic10
Version: 10.0.1 (2911.42)
Build Info: MALogic-2911042000000000~1
App Item ID: 634148309
App External ID: 15875534
Code Type: X86-64 (Native)
Parent Process: launchd [145]
User ID: 501
Date/Time: 2013-07-29 01:34:04.730 -0700
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10
Interval Since Last Report: 19612 sec
Crashes Since Last Report: 20
Per-App Interval Since Last Report: 1933 sec
Per-App Crashes Since Last Report: 9
Anonymous UUID: 440AE3AB-E35C-970B-F4A5-4A31E5AC7F78
Crashed Thread: 26 SeqTimer
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000001055b9000
VM Regions Near 0x1055b9000:
__LINKEDIT 00000001055b0000-00000001055b9000 [ 36K] r--/rwx SM=COW /Applications/Logic Pro X.app/Contents/Frameworks/MAGFFoundation.framework/Versions/A/MAGFFoundation
--> MALLOC guard page 00000001055b9000-00000001055ba000 [ 4K] ---/rwx SM=NUL
MALLOC metadata 00000001055ba000-00000001055cf000 [ 84K] rw-/rwx SM=PRV
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff96e3e78e mach_wait_until + 10
1 com.apple.CoreServices.CarbonCore 0x00007fff8f20a226 MPDelayUntil + 12
2 com.apple.CoreServices.CarbonCore 0x00007fff8f2193cf Delay + 70
3 com.apple.logic10 0x00000001013c3de4 0x100f9a000 + 4365796
4 com.apple.logic10 0x0000000100fa0abd 0x100f9a000 + 27325
5 com.apple.logic10 0x0000000101112861 0x100f9a000 + 1542241
6 com.apple.logic10 0x0000000101162135 0x100f9a000 + 1868085
7 com.apple.logic10 0x000000010145118c 0x100f9a000 + 4944268
8 com.apple.logic10 0x000000010141eafc 0x100f9a000 + 4737788
9 com.apple.logic10 0x00000001014233cb 0x100f9a000 + 4756427
10 com.apple.logic10 0x000000010142350d 0x100f9a000 + 4756749
11 com.apple.AppKit 0x00007fff9039f348 -[NSDocument _initWithContentsOfURL:ofType:error:] + 135
12 com.apple.AppKit 0x00007fff9039eff4 -[NSDocument initWithContentsOfURL:ofType:error:] + 262
13 com.apple.AppKit 0x00007fff907c7765 -[NSDocumentController makeDocumentWithContentsOfURL:ofType:error:] + 332
14 com.apple.logic10 0x0000000101533d5e 0x100f9a000 + 5872990
15 com.apple.AppKit 0x00007fff907d21f3 -[NSDocumentController(NSDeprecated) openDocumentWithContentsOfURL:display:error:] + 824
16 com.apple.logic10 0x0000000101446afa 0x100f9a000 + 4901626
17 com.apple.Foundation 0x00007fff9360a9cf -[NSBlockOperation main] + 124
18 com.apple.Foundation 0x00007fff935e0926 -[__NSOperationInternal start] + 684
19 com.apple.Foundation 0x00007fff935e80f1 __block_global_6 + 129
20 libdispatch.dylib 0x00007fff902a3f01 _dispatch_call_block_and_release + 15
21 libdispatch.dylib 0x00007fff902a00b6 _dispatch_client_callout + 8
22 libdispatch.dylib 0x00007fff902a50c8 _dispatch_main_queue_callback_4CF + 275
23 com.apple.CoreFoundation 0x00007fff9339bb4c __CFRunLoopRun + 1644
24 com.apple.CoreFoundation 0x00007fff9339b0e2 CFRunLoopRunSpecific + 290
25 com.apple.HIToolbox 0x00007fff99599eb4 RunCurrentEventLoopInMode + 209
26 com.apple.HIToolbox 0x00007fff99599c52 ReceiveNextEventCommon + 356
27 com.apple.HIToolbox 0x00007fff99599ae3 BlockUntilNextEventMatchingListInMode + 62
28 com.apple.AppKit 0x00007fff90486533 _DPSNextEvent + 685
29 com.apple.AppKit 0x00007fff90485df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
30 com.apple.AppKit 0x00007fff9047d1a3 -[NSApplication run] + 517
31 com.apple.AppKit 0x00007fff90421bd6 NSApplicationMain + 869
32 com.apple.logic10 0x000000010141da69 0x100f9a000 + 4733545
33 com.apple.logic10 0x0000000100f9cc34 0x100f9a000 + 11316
Thread 1:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff96e40d16 kevent + 10
1 libdispatch.dylib 0x00007fff902a2dea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff902a29ee _dispatch_mgr_thread + 54
Thread 3:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 4:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x00007fff96e3e686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96e3dc42 mach_msg + 70
2 com.apple.CoreFoundation 0x00007fff93396233 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation 0x00007fff9339b916 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation 0x00007fff9339b0e2 CFRunLoopRunSpecific + 290
5 com.apple.Foundation 0x00007fff93589546 +[NSURLConnection(Loader) _resourceLoadLoop:] + 356
6 com.apple.Foundation 0x00007fff935e7562 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 7:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x00007fff96e40322 __select + 10
1 com.apple.CoreFoundation 0x00007fff933daf46 __CFSocketManager + 1302
2 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
3 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff96e3e686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96e3dc42 mach_msg + 70
2 com.apple.CoreFoundation 0x00007fff93396233 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation 0x00007fff9339b916 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation 0x00007fff9339b0e2 CFRunLoopRunSpecific + 290
5 com.apple.Foundation 0x00007fff935ec7ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
6 com.apple.Foundation 0x00007fff935ec69b -[NSRunLoop(NSRunLoop) runUntilDate:] + 78
7 com.apple.logic10 0x0000000101177d1f 0x100f9a000 + 1957151
8 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
9 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff96e3e686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96e3dc42 mach_msg + 70
2 com.apple.audio.midi.CoreMIDI 0x00000001029f3970 XServerMachPort::ReceiveMessage(int&, void*, int&) + 96
3 com.apple.audio.midi.CoreMIDI 0x0000000102a0fb23 MIDIProcess::RunMIDIInThread() + 243
4 com.apple.audio.midi.CoreMIDI 0x00000001029f4c2c XThread::RunHelper(void*) + 10
5 com.apple.audio.midi.CoreMIDI 0x00000001029f480f CAPThread::Entry(CAPThread*) + 175
6 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 10:: ExtendedAudioFileScheduler::WorkerThreadProc
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAFiles 0x0000000104590c23 ExtendedAudioFileScheduler::WorkerThreadProc() + 115
3 com.apple.music.apps.MAFiles 0x00000001045908d9 ExtendedAudioFileScheduler::WorkerThreadProc(void*) + 9
4 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
5 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 11:: ExtendedAudioFileScheduler::WorkerThreadProc
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAFiles 0x0000000104590c23 ExtendedAudioFileScheduler::WorkerThreadProc() + 115
3 com.apple.music.apps.MAFiles 0x00000001045908d9 ExtendedAudioFileScheduler::WorkerThreadProc(void*) + 9
4 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
5 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 12:: com.apple.audio.IOThread.client
0 libsystem_kernel.dylib 0x00007fff96e3e686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96e3dc42 mach_msg + 70
2 com.apple.audio.CoreAudio 0x00007fff94155c1c HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned int, unsigned int, mach_msg_header_t*, bool, unsigned int) + 98
3 com.apple.audio.CoreAudio 0x00007fff94155baa HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 42
4 com.apple.audio.CoreAudio 0x00007fff94153fe9 HALC_ProxyIOContext::IOWorkLoop() + 1161
5 com.apple.audio.CoreAudio 0x00007fff94153acf HALC_ProxyIOContext::IOThreadEntry(void*) + 83
6 com.apple.audio.CoreAudio 0x00007fff941539a7 HALB_IOThread::Entry(void*) + 75
7 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 13:: ProcessThread1/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467cc53 MD::CallProcessThread1(void*) + 563
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 14:: ProcessThread2/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467cf01 MD::CallProcessThread2(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 15:: ProcessThread3/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467d191 MD::CallProcessThread3(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 16:: ProcessThread4/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467d421 MD::CallProcessThread4(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 17:: ProcessThread5/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467d6b1 MD::CallProcessThread5(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 18:: ProcessThread6/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467d941 MD::CallProcessThread6(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 19:: ProcessThread7/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467dbd1 MD::CallProcessThread7(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 20:: ProcessThread8/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467de61 MD::CallProcessThread8(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 21:: ProcessThread9/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467e0f2 MD::CallProcessThread9(void*) + 578
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 22:: ProcessThread10/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467e381 MD::CallProcessThread10(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 23:: ProcessThread11/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467e611 MD::CallProcessThread11(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 24:: ProcessThread15/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467f051 MD::CallProcessThread15(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 25:: FileIOThread
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x0000000104698765 0x10466c000 + 182117
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 26 Crashed:: SeqTimer
0 com.apple.logic10 0x0000000101243260 0x100f9a000 + 2789984
1 com.apple.logic10 0x000000010124dffa 0x100f9a000 + 2834426
2 com.apple.logic10 0x000000010124bad7 0x100f9a000 + 2824919
3 com.apple.logic10 0x0000000101249ca7 0x100f9a000 + 2817191
4 com.apple.CoreServices.CarbonCore 0x00007fff8f219a43 TimerThread + 134
5 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 27:
0 libsystem_kernel.dylib 0x00007fff96e40322 __select + 10
1 com.apple.logic10 0x00000001017f6e64 0x100f9a000 + 8769124
2 com.apple.logic10 0x000000010140121d 0x100f9a000 + 4616733
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 28:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 29:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x00007fff96e40386 __semwait_signal + 10
1 libsystem_c.dylib 0x00007fff9227d800 nanosleep + 163
2 libsystem_c.dylib 0x00007fff9227d717 usleep + 54
3 com.apple.AppKit 0x00007fff9066b838 -[NSUIHeartBeat _heartBeatThread:] + 543
4 com.apple.Foundation 0x00007fff935e7562 __NSThread__main__ + 1345
5 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 26 crashed with X86 Thread State (64-bit):
rax: 0x00000001055b8ff0 rbx: 0x000000000000fc80 rcx: 0x0000000000000800 rdx: 0x0000000000000000
rdi: 0x00000000ffffffff rsi: 0x000000000000fc80 rbp: 0x000000011a3c0c20 rsp: 0x000000011a3c0b40
r8: 0x3ffffffeffffffff r9: 0x0000000102099000 r10: 0x00000000000000e5 r11: 0x80000000000000f0
r12: 0x00007fac9436a000 r13: 0x0000000102099000 r14: 0x0000000109b4efa0 r15: 0x00007fac9e3cdb50
rip: 0x0000000101243260 rfl: 0x0000000000010287 cr2: 0x00000001055b9000Alcologic wrote:
Hello all,
One of my projects crashed and now it won't re-open.
I tried re-booting.
I trashed my preference files and restarted.
I can open Logic Pro, and other project files OK. I opened the Audio Units Manager and disabled ALL plugins, Quit Logic and restarted. Still crashes when opening this project file.
Hi, it looks like a Project file corruption from what you are writing.
Let's try one more thing before going any further!
We will disable the Audio Drivers:
Hold down Control immediately (NOT TOGETHER) after clicking Logic in your Dock.
A dialog will open :
Press "Don't".
Does the problematic project open? -
Premiere pro crashes when opening project
Premiere pro project crashes when opening. I have an imac running OS 10.7.3 (8GB Ram, AMD Radeon HD 6970 2048mb) and have Premiere Pro 5.5.2. I have had 2 projects that I have worked on for hours and saved numerous times and then when I closed pp and tried to reopen the file the screen goes white and then crashes. Please help.
Ann, THANKS for replying!
If I open a brand new project, which I could do before, and then IMPORT a previous project, it works and I can edit and export the project. However, it did crash upon trying to save it and I still can not just open a previously created project. When I do I get an error message that Says: "Premiere has encountered an error and needs to close down. We will attempt to save your project."
Do you or anyone else have any ideas? -
Frequent crashing when opening projects
10.5.8, LP 9.0.2, Mac Pro 8-core 6GB RAM
Logic frequently stalls/crashes when opening projects. This happens most often with projects that have lots of sampler instruments (primarily VSL), but some of the time with no samplers at all. The loading window generally hangs on Vienna Instruments with projects that have them, and on Space Designer with projects that don't.
The project this happens most frequently with is an orchestral template I'm creating. It has about 25 instances of Vienna Instruments (totalling 1.34GB worth of samples), a few channel EQs and one instance of Space Designer. Other projects that have caused the crash include about 10 native software instrument plugins, 1 Akoustic Piano and 10-15 native effect plugins. I consulted VSL tech support who said the problem was most likely with Logic. I'm inclined to agree, since the problem happens with and without any Vienna Instruments, and Vienna Ensemble Standalone has no problem loading templates with a lot of samples.
Does anyone have any suggestions to troubleshoot? Has anyone had similar experiences? Thanks.Well, this has happened to me too. To the point where I've lost all the work, because Logic can't open the original project or the "crashed" copy it creates. Happened again with a new project I'm working on, albeit on a much more modest laptop system.
Annoying. Makes me think about switching DAWs...what else can you do if Logic can't be trusted. -
FCP 6.02 Crashing when opening Project
Hi,
Going bananas trying to work out why a project I have been working on for 6months now causes FCP to crash when opening. I can open other projects fine, but when I try and open a project with all media offline I get the same issue.
All drives are external and I have space on both local and external disks.
I have tried opening the project from the autosave vault - which should work - to no avail.
I have now reinstalled Final Cut Studio 2 with no change to the above.
Any help would be appreciated.
Thanks
pThanks Shane,
I was running all the latest apps - Qt 7.3, FCP6.02 OSX 10.411, did all the updates etc.
By erasing FCP and compressor I was able to get the project to open, but exporting through compressor kept crashing - which was an original fault that started happening before the project crash issue.
Not wanting to waste any more time I did a complete erase and re-install of my computer, and after spending close to half a day doing it I think it's been worth it - though I'm going through the testing phase - although as it stands the project has been loading and compressor has been working properly (will test more though).
I was using a couple of plugins that I downloaded from Apple's website: FX plugins manager of sorts, and I was using a filmic filter from that set which I think may have been corrupting the whole project.
I will keep testing though...
p -
When I open audiobin, Logic8 project crashes......
Hi all,
When I attempt to open the audiobin, my Logic8 project crashes......
I have 2 recording studios and the project behaves the same on both of them.......
thoughts?
SvKProcess: Logic Pro [6419]
Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Identifier: com.apple.logic.pro
Version: 8.0.2 (1502.22)
Build Info: Logic-15022200~9
Code Type: X86 (Native)
Parent Process: launchd [116]
Date/Time: 2008-07-28 20:01:40.821 -0700
OS Version: Mac OS X 10.5.4 (9E17)
Report Version: 6
Exception Type: EXCBADACCESS (SIGABRT)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 libSystem.B.dylib 0x9542ab9e __kill + 10
1 libSystem.B.dylib 0x954a1ec2 raise + 26
2 libSystem.B.dylib 0x954b1428 __abort + 97
3 libSystem.B.dylib 0x954b1490 flockfile_debugstub + 0
4 com.apple.logic.pro 0x002b37ff 0x1000 + 2828287
5 libSystem.B.dylib 0x9542909b _sigtramp + 43
6 ??? 0xffffffff 0 + 4294967295
7 com.apple.logic.pro 0x0004dd99 0x1000 + 314777
8 com.apple.logic.pro 0x004ad425 0x1000 + 4899877
9 com.apple.logic.pro 0x004ab352 0x1000 + 4891474
10 com.apple.logic.pro 0x004cee1b 0x1000 + 5037595
11 com.apple.logic.pro 0x004c8a24 0x1000 + 5012004
12 com.apple.logic.pro 0x00558064 0x1000 + 5599332
13 com.apple.logic.pro 0x00514d33 0x1000 + 5324083
14 com.apple.logic.pro 0x00514dd5 0x1000 + 5324245
15 com.apple.logic.pro 0x00516024 0x1000 + 5328932
16 com.apple.logic.pro 0x004ebeef 0x1000 + 5156591
17 com.apple.logic.pro 0x00015278 0x1000 + 82552
18 com.apple.logic.pro 0x00015bf6 0x1000 + 84982
19 com.apple.logic.pro 0x00015cf7 0x1000 + 85239
20 com.apple.logic.pro 0x00016111 0x1000 + 86289
21 com.apple.logic.pro 0x002d9eba 0x1000 + 2985658
22 com.apple.logic.pro 0x002d3ae2 0x1000 + 2960098
23 com.apple.logic.pro 0x002d3d8a 0x1000 + 2960778
24 com.apple.logic.pro 0x002d3c9c 0x1000 + 2960540
25 com.apple.logic.pro 0x002d3fc0 0x1000 + 2961344
26 com.apple.logic.pro 0x002d4d4e 0x1000 + 2964814
27 com.apple.logic.pro 0x002d50f0 0x1000 + 2965744
28 com.apple.logic.pro 0x002d5405 0x1000 + 2966533
29 com.apple.logic.pro 0x002d747d 0x1000 + 2974845
30 com.apple.logic.pro 0x004d9a94 0x1000 + 5081748
31 com.apple.logic.pro 0x005c3473 0x1000 + 6038643
32 com.apple.AppKit 0x901b0fe7 forwardMethod + 113
33 com.apple.AppKit 0x901b0fe7 forwardMethod + 113
34 com.apple.AppKit 0x901b0fe7 forwardMethod + 113
35 com.apple.AppKit 0x901b0fe7 forwardMethod + 113
36 com.apple.AppKit 0x901b0fe7 forwardMethod + 113
37 com.apple.AppKit 0x901b0fe7 forwardMethod + 113
38 com.apple.logic.pro 0x004ca997 0x1000 + 5020055
39 com.apple.logic.pro 0x004d993a 0x1000 + 5081402
40 com.apple.logic.pro 0x005c33f4 0x1000 + 6038516
41 com.apple.AppKit 0x900f1431 -[NSApplication sendEvent:] + 2941
42 com.apple.logic.pro 0x004df8a6 0x1000 + 5105830
43 com.apple.logic.pro 0x004d968e 0x1000 + 5080718
44 com.apple.logic.pro 0x004df87e 0x1000 + 5105790
45 com.apple.AppKit 0x9004ee27 -[NSApplication run] + 847
46 com.apple.prokit 0x0214be5a NSProApplicationMain + 325
47 com.apple.logic.pro 0x00003942 0x1000 + 10562
48 com.apple.logic.pro 0x00003869 0x1000 + 10345
Thread 1:
0 libSystem.B.dylib 0x953bc4a6 machmsgtrap + 10
1 libSystem.B.dylib 0x953c3c9c mach_msg + 72
2 com.apple.CoreFoundation 0x941ef0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x941efd54 CFRunLoopRun + 84
4 com.apple.DVCPROHDMuxer 0x19a1b0fb AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 297
5 libSystem.B.dylib 0x953ed6f5 pthreadstart + 321
6 libSystem.B.dylib 0x953ed5b2 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x953bc4a6 machmsgtrap + 10
1 libSystem.B.dylib 0x953c3c9c mach_msg + 72
2 com.apple.CoreFoundation 0x941ef0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x941efcf8 CFRunLoopRunInMode + 88
4 com.apple.audio.CoreAudio 0x92c9d464 HALRunLoop::OwnThread(void*) + 160
5 com.apple.audio.CoreAudio 0x92c9d300 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x953ed6f5 pthreadstart + 321
7 libSystem.B.dylib 0x953ed5b2 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x953c368e _semwaitsignal + 10
1 libSystem.B.dylib 0x953ee36d pthreadcondwait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x94f0e432 glvmDoWork + 162
3 libSystem.B.dylib 0x953ed6f5 pthreadstart + 321
4 libSystem.B.dylib 0x953ed5b2 thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x953bc506 semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x953ee84f pthread_condwait + 1244
2 libSystem.B.dylib 0x953f00d3 pthreadcond_timedwait_relativenp + 47
3 ...ple.CoreServices.CarbonCore 0x942da2fe TSWaitOnConditionTimedRelative + 246
4 ...ple.CoreServices.CarbonCore 0x942da0de TSWaitOnSemaphoreCommon + 422
5 ...ple.CoreServices.CarbonCore 0x9430ae28 TimerThread + 74
6 libSystem.B.dylib 0x953ed6f5 pthreadstart + 321
7 libSystem.B.dylib 0x953ed5b2 thread_start + 34
Thread 5:
0 libSystem.B.dylib 0x953c368e _semwaitsignal + 10
1 libSystem.B.dylib 0x953c3456 usleep$UNIX2003 + 61
2 com.apple.AppKit 0x900bc979 -[NSUIHeartBeat _heartBeatThread:] + 2042
3 com.apple.Foundation 0x90af9f1d -[NSThread main] + 45
4 com.apple.Foundation 0x90af9ac4 _NSThread__main_ + 308
5 libSystem.B.dylib 0x953ed6f5 pthreadstart + 321
6 libSystem.B.dylib 0x953ed5b2 thread_start + 34
Thread 6:
0 libSystem.B.dylib 0x953bc4e2 semaphorewaittrap + 10
1 libSystem.B.dylib 0x953ee92d pthread_condwait + 1466
2 libSystem.B.dylib 0x95434371 pthreadcondwait + 48
3 com.apple.logic.pro 0x001159f7 0x1000 + 1133047
4 libSystem.B.dylib 0x953ed6f5 pthreadstart + 321
5 libSystem.B.dylib 0x953ed5b2 thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x954b143f ecx: 0xbfffc7cc edx: 0x9542ab9e
edi: 0x2a10d5a0 esi: 0x19d56c30 ebp: 0xbfffc7e8 esp: 0xbfffc7cc
ss: 0x0000001f efl: 0x00000282 eip: 0x9542ab9e cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x8388d000 -
PrE 4 Opens, Then Crashes When Project Loads
I realize that Premiere Elements 4 is old, but I still like and use it for all my projects. Here's my problem: I've been running PrE 4 for months on my new 64-bit Win 7 HP laptop, but only today it started going bonkers. It opens just fine, but when I open a project, it minimizes the PrE window as soon as it loads. Even though I've tried re-opening the window, it refuses to return to full screen.
I've tried compatibility to Vista and even XP, running under administrator priveleges, but to no avail. Is this a result of a newly-installed program or a virus? I'd love to get back to editing...Thank you for the info.
There is one thing that I need clarification on - do you mean that you can no longer Open a New Project, one that is empty? If so, then you can ignore the test below, though we might come back to that, if we can get PrE to Open a New Project.
When you say "raw AVI files," are these DV-AVI's, a particular form of AVI? This ARTICLE will give you more background on file formats.
You mention WMA Audio files. Like an AVI file, those can contain a lot of different stuff, but more on that in a moment.
With Win7-64, 4GB RAM is about what Win7 needs to run, and that does not leave a lot of excess for programs.
Now, Projects can become corrupted, or unstable, due to many things. Assets in a Project can become problematic. One way to test a Project for "bad" Assets is to make sure that PrE is closed, and then "hide" the Assets from PrE. As the Project file, the PREL, does not contain any of the Assets, but only follows absolute Paths to those Assets, this is farily simple. How one has structured their Assets folders can greatly simplify this task, or can cause a bit of work. It sounds as though your Project is pretty simple so far, and should not be difficult to follow these steps for testing:
With PrE closed, go to the folder(s), where the Assets are located, and Move the folder(s) elsewhere. Remember, the PREL uses absolute Paths,so that original Path will no longer apply. At this point, I would also separate Assets by type, say with Video files in a "Video" folder, Still Images in a "Stills" folder and Audio files in an "Audio" folder. You will see why in a moment.
Launch PrE, and Open the problem Project.
One will be confronted with a message dialog box, asking "Where is file ______?" Since we moved those Assets, we need to help PrE find them. Just navigate to the Moved folder, where that first Asset is located. The dialog screen offers a Finder, but since you Moved things, you should have that info handy. Locate the first file, that PrE is asking for.
Once you find it, PrE will do two things: establish the new link, and then look in that folder for any other Assets, used in that Project, and link to them also - pretty neat, eh?
Since we separated our Assets by type, if the first type, say Video, loads fine, we can rule those out. If the Project crashes here, we have found at least one problem.
When PrE comes to the next Asset, that dialog screen will reappear, and we will do the same thing - locate the file, that PrE is asking for, and again, PrE will re-establish the link to it, and search that folder for any more Assets. If all goes well, we can probably rule out those Assets as an issue.
This will repeat, until either the Project loads, or until the Project crashes, or hangs. If that happens, we have narrowed things down to one Asset type. This is why we separated them - it makes troubleshooting Assets much easier. Note: Titles are written in XML code, in the PREL, so nothing tangible exists for them, at this point.
Whatever you do, do NOT choose Save, and especially if you decide to Skip Media, or Cancel. Only do a Save_As,so as to NOT overwrite your original PREL. Never overwrite an original PREL, if you are having issues.
Please report on this test. Does the Project fail with a particular Asset type? If so, what is that Asset type?
If you have quite a few Assets of that particular type, you can redo the test, by moving, say half of those Assets again, and running the test again. If the Project crashes with either the first half, or the second, you are getting closer.
Good luck,
Hunt -
for some reason, all of my FCPX projects are crashing FCPX ... HELP!!
Create a new event and import a quick time movie file. Create a new project. Does this new project crash the app?
Russ -
Need to render everytime I re-open project in PP3
My problem:
On a particular project, I need to re-render everything everytime I re-open project even after I have saved and closed project.
I also experience SERIOUS ERROR crashes or simply PP3 freezes while trying to render whole timeline, I need to render in chunks.
The project file is a single timeline 2:45 minutes long with only the clip on timeline in project; it's CFHD low res clips (not corrupted) and there's quite a lot of CF cross-fades in timeline (it's a trailer) with about 5-6 clip color corrected that need to be rendered.
My specs are:
PP3 + AspectHD v5.2 build 105
dualmonitors with Ultramon 2.6
AMD ATHLON x2 4600+
4 GB SDRAM2 733 Mghz (dual channels)
MATROX APVe
ASUS SLI-DELUXE
Sound Blaster X-FIHello Frederic,
I am having the same issue. I am also using AspectHD v5.2. The timeline which I am having this issue has many effects and also has some imported Photoshop files. Another aspect of this is that when I try and play the timeline the play-head jumps to the end of the timeline. If I render the clip it plays fine. Except when I exit Premiere and then open it again the renders are lost and I'm back at square #1. I have been struggling with this since November and am not sure how to fix it. I know you were hoping for an answer (as am I) but thought I would just chime in to let you know someone else is also having this issue --- for what it's worth... -
Hello everyone,
I hope someone can help me.
I am using AE CC/Windows 7 on a Dell computer, 32 GB RAM, 64 bit op system, processors: Intel (R) Xeon (R) CPU x5670 @ 2.93 Ghz 2.93 Ghz (2 processors).
So far I had worked on many projects with no problems and then a few weeks ago the project crashed non stop. The problem was overcome when I got rid of all MP3s and converted them to RAM. Again this was an issue I didn't have in the past and I don't recall changing anything.
Now it seems it is impossible for me to export/render out a project into a Quick time file or even AVI. If its quick time I get this message: After Effects unable to render error an output module failed. The file may be damaged or corrupted -1610153464 and if I am trying to export with AVI I get this message: AE unable to open projects in the background 26:: 142)
This is happening with different projects.
I read the forums and heard that the problem may be a Bug with quicktime and H.264? I never had a problem with it before but again when I try to export AVI I get this error message:
AE unable to open projects in the background
I have a feeling it is quick time related. I have uninstalled and reinstalled QT but still get the problem. It will open old QT files no problem. I tried to download a bug fix update as one post suggested but I think I have the latest which is why it didn't work.
This particular project has a couple of quick media H.264 files. Do I need to convert them? Are they the cause for all of this?
I am sorry I really tried to look for answers in the forums before contacting you here but I cannot find a reason for all this mess, which again only appeared a few weeks ago with no problems for months...if someone can point out an area where I can start looking, I would really appreciate it. Thanks in advance.update: I converted all the H.264 footage which were in the project to WMV. And I was able to test export with AVI and it turne dout fine (like 10 seconds). However I still got the Error message: "After Effects unable to render error an output module failed, a filme may be corrupted or damaged. Error-1610153464 " when I tried to export H.264 QT..
I don't know what to do now, how can a problem which did not exist suddenly come up. How can I export a QT file? with AVI it will be massive!
Many thanks
Amanda -
Project crashing caused by Memory?
I am having a program crash problem with Final Cut Pro when working with any number of projects (big or small). One large project (33MB), I cannot even open without FCP crashing. +*When I say crash, I mean that the program quits without notice and all windows disappear immediately without warning (i.e. no spinning beach ball or frozen windows). A dialog box then appears oon screen telling me that FCP quit unexpectedly and offers me a report or send Apple a message.+
This is my set up: I am running Final Cut Pro HD on a Dual 2.3 GHz PowerPC G5 with 4GB RAM with Mac OS X (10.4.11). My OS and all apps live on a 230 GB Internal start-up HD (159GB available) and my projects and all related assets live on a 500GB external Seagate high speed USB 2 Drive (14GB available). No other USB 1 devices are on the bus.
In order to correct the problem did the following in this order:
1- Used FCP Rescue to trash and reset FCP. No effect
2- Used Mac's Disc Utility to Repair Disk Permissions and Repair Disk (both run twice). No effect
3- Copied project file to main start-up drive in order to eliminate possible issue with linked asset. Project crashed FCP at launch.
4- Reformatted start-up Drive and performed clean install of OS and FCP. No Effect. Project still caused crash at launch.
Non of these seemed to work, so I started with a auto-saved backup of the project. I saved it as a separate copy with a new name. It opened without a crash, yet all media clips needed to be reconnected. Hooray! So, I started reconnecting media. As I do this, I reconnect small bunches of clips at a time and click save. During this long process, the program crashed again. So, I restarted FCP and the project opened without crashing. I continue to reconnect media as before. Now it takes half the time to crash again. I use FCP Rescue to trash prefs and restart FCP again, but as the program loads the project, it crashes before it can finish opening the project.
It seems to me that each time FCP crashes with a project open, it damages the project file somehow to the point that it will not open at all. Even after purging program preferences and attempting to reopen the crashed project file. Is this possible? Is there some other cause for projects to crash and or not open this way?
Now I am wondering if it is hardware causing the crashes leading to the corrupt files. I ran Apple's Hardware test and the MAC passes both the fast and long test. I also downloaded Temperature Monitor to check memory temp for overheating. It is running between 74-77˚C (165-170˚F), a few degrees higher during a render test. Does anyone know if this memory temp is an issue or what acceptable tolerances are for the G5 with FCPHD? I am out of ideas and hope that someone out there might have some ideas. +Any advice is appreciated.+It sounds like you may have a piece of corrupt media (or several pieces of corrupt media). First of all, usb is not recommended for working with fcp. Don't think it's the source of your problem, but...
First, generally speaking, project files should reside on your startup disk and all media on other drives.
Are you using any nonstandard codecs or formats?
Are all your drives formatted macosextended? You might want to run diskwarrior on all drives.
Once the above are eliminated, try this. Copy your fcp project file to your startup drive and disconnect the media drive. Open fcp and launch the project. All media will be offline. Save your project. Reconnect your media drive, and launch fcp and the project. Gradually reconnect your media until you find the problem clips. -
Adobe Premiere Elements 0.9 project crash, HELP!
This is the first time I am using these forums, so I hope I posted this in the right sektions.
I need help and solutions for a Project which constantly crashes on my Adobe Premiere Elements 0.9. This program has been awesome and helped me create some projects and videos successfully, up until.... well for about 3 days ago when my latest project crashed when I had just antered and checking the storyboard etc, triggering a "Serious Error" message and then it shuts down. I try again and again, but everytime I try to put something (any sound or video etc) on the storyboard and start working etc the same damn "Serious Error" message and then allways shuts down. It's allways this same and only project (which has worked fine before) that crashes like this...
In an attempt to first solve the problem myself I went through the Premiere Elements 9 files and deleted finnished projects and automatic saved process on projects etc, but still won't work even better... The funny thing is that when I open another project (a finnished project I left saved just in case) and go through the storyboard there and messes around a little and such, it won't crash nor trigger the same message as my latest project. And that program even has some effects on every footageclip on it too, but still it works fine. Haven't touched the program or the program until and since yesterday night to give it some rest but it still won't work, the project just keeps crashing like when and since it first started a few days ago.
I have also read through and tried some things from this Help/Troubleshoot page:
http://helpx.adobe.com/premiere-elements/kb/troubleshoot-damaged-projects-premiere-element s.html
I have so far been doing 1 and 2 of the "Beginning Troubleshooting", otherwise I have been reading it all and such. I am also kinda afraid to do the 3 of the first quests because I worked so hard on this project and even tough it just keeps crushing, I'm afraid to lose it. Other, I have deleted audios and such from my filegallery on my Adobe Premiere Eements, stuff I don't need anymore because its projects are already done. After I did that I also tried to create a new project just for testing. The amazing this about this is that this the new created project I created works just fine, I could do all kinds of the stuff, effects and advanced editing which I did on the same project before it started crushing. Tough I didn't save that test-project since I didn't find a reason to since it worked so good. And so the thing is that I can start and create a new project and start working and do usual stuff on it with no problem, same when I open up another project and do stuff, it all works just fine! It is just this one and only project that keeps crushing with this "Serious Error" message, all the time... Does anybody else have, or has had the same problem? What could the problem and error be and how to fix it?
This crushing project do has some effects on every footageclip/videoclip on it, to set the right mood for the musicvideo I'm making. I am making a musicvideo, and I haven't even done the half of the project/video. The song I am making this musicvideo with is about 00:07:32 in length, and (tough this detail may have no influence or meaning) the music is Symphonic Metal. The actual file of the song is 6,96 MB in size. This is also not the first time I've done such projects with such long songs on this same program either, one of my last videos I managed to successfully make and create a musicvideo with a song which was about 13 minutes and 30 seconds in length, and I also used effects on pretty much every videoclip on that project too.
The current filesize so far on the actual project.prel-file of my project that keeps crushing is 9.73 MB.
I am also using Adobe Premiere Elements and doing this troubleing, crashing project on a PC, a Fujitsu Windows (I believe Windows 7, or even updated to a newer version?). It has a regular ATI-card. The computer also has 2 modems and there's still some pretty GB amount free on them. The PC's main system also has a RAM in 6.00 GB and the operative system is the 64-bites.
In short, the PC should just fine be able to handle Adobe Premiere Elements 0.9 and all its projects, just as it has handled it all before plus all my PC games at that. So it must be something with my Adobe Premiere Elements and that specific project which is the problem, but what is the problem and the serious error and how to fix it?
Could it help to save and create the actual video in this crashing project, delete that project then start a new project, upload and put in the videofile of the crashing project in that new project and then continue from there?
In either cases, I need help with this. Please, help!Thanks so much for your reply, Steve!
Even tough I trust you guys enough here on the official Adobe site/forums to answer those questions as best I can, I am at the same time not very fond of giving away too much information because of safety. I understand I have to If I'm to recieve the accurate answers and solution, but as this is the internet you can never know. But again, I trust you guys enough on here and thus I'll try to answer those questions as best I can, even tough I am not very good with such stuff about computers. The PC I am using is also not only mine, it is the family computer also which me and my whole family uses.
The operating system on my computer (according to the computer propotions etc) is a 64-bites operating system and the computer/PC is also a Windows 7 Home Premium.
The processor the computer/PC have is a Intel(R) Core(TM) i5 CPU and the RAM is 6.00 GB. However, (and I hope I make this understandable because the computer/PC is in swedish)the subscore of RAM in the computer's Performance-Classification/Ranking is 7,5. The processor subscore is 7,3 per second. And the free space? Well, we have two modems, let's say a modem A and a modem B. Adobe Premiere Elements 0.9 is set to save all its stuff etc on modem B, while modem A is the main modem and spaces all main stuff and other things of the computer/PC. Modem A has about 314 GB of free space, while modem B has 207 GB of free space. Modem A's capacity is a total of 489 GB in which 175 GB has been used, the modems filesystem is a NTFS. Modem B is also a NTFS filesystem and its capacity is a total of 439 GB in which 232 GB has been used. And the Disk Cleanup? I believe my that latest ran it for about a few weeks ago. We also have a CCleaner also. But about the Disk Defragmenter, I have no idea. What exactly does a Disk Defragmenter do?
You mean, entering my project that keeps crushing and simply rename it by using "Save As"? If that is what you mean, I dunnow If that actually worked. When I still tried to do stuff and edit the crashing project (tough as said, it hardly took any changes and process before it triggered that message) and then crashed and shut down, and I opened up the program again (trying to open the same project that way), it asked me If I wanted to re-create the missing process from the last crash of the same project. I tried it and it automaticly was renamed to a for example Project.copy. But when I tried to work with that it was to no futher success, the project kept crashing. I haven't renamed the project by "Save As" tough, but I doubt it'll work, I even tried to rename the actual project file in the Adobe Premiere Elements files but nope... the project keeps crashing. But also about the same question, "Save As" under a new name but in its own folder? You mean the actual project folder or Adobe Premiere Elements preview folder of the projects?
My camcorder is pretty old by now, have had it since I turned 15, it has worked pretty good since then. Its model is a Sony Handycam, Carl Zeiss Vario-Tessar OPTICAL 20x. Even tough the last thing maybe doesn't say anything, this is all I know about my camcorder, except that it is a model no. DCR-HC17E PAL. But in that Project which keeps crashing, there are only a few actual camcorder clips used as I am making a Game-MusicVideo and most of the footage of the Video-game (actually a PC game) I'm making a musicvideo of is downloaded from Youtube mostly from a guy I asked permission for to download his recorded footage of the game. I used a Youtube downloader called ClipConverter. As I don't have a SD card I cannot make this footage myself. But some footage I recorded on my camcorder, but If I can find high quality clips and get them, I will. The other footages is actual official trailers of the PC games which also was downloaded from the net. But I can give you the stuffs filetypes and hoping that may help. The downloaded footage which was downloaded by this ClipConverter, are MP4 files. The other stuff (which were official trailers) and most of them are also MP4 files, the others are QuickTime-film files. Many of these downloaded footages and trailers are also in HD quality, at least some of them I think.
The actual filetype ofthe footage I myself recorded with my camcorder are, well.... it says Videoclip in the file. Maybe it is AVI?
The project settings? You mean the settings you set at first when starting as a new project? The general settings are, in editingsettings it is AVCHD 270p square pixel. This is kinda hard for me to tell since everything is in swedish in my program. But these settings has worked perfectly before, same with all files, footages and videoclips I have been using, also all the soundfiles etc. Even the actual crashing project worked perfectly before it started crashing... So why does it so suddenly start crashing now?
The audio is a song I copied directly from its album and CD into the computer/PC and it seems to be in WMA format in filetype.
And lastly, no I haven't rendered the timeline of the project ever, not even on my other projects. What does the rendering do and is useful for? I have very little knowledge of it. Other, I keep the Timeline mode open all the time because I can edit my videos much better with it, but perhaps that editing method make little influence of the actual problem.
Other, yesterday when writing the post and topic, I forgot to mention that I restarded my computer right after I created a new project, that testing project. When finnished with the testing I restarted the computer. Since then I haven't touched the crashing project since now tonight, when checking its settings for this post. I am also right now trying to create and save the actual videofile of it, saving it on my computer. I'll soon see If it's successful without any crashing interruptions, plus that the video itself works and is smooth when I'll play it on Windows Media Player like all the rest of my other videos. I do this just in case I must create a new project to be able to continue with my musicvideo, as the first part of it I worked very hard on.
Other and again, I am still puzzled about why this is even happening, that this project which worked perfectly fine before, just suddenly starts triggering that "Serious Error" message and crashes. And in this program which worked so perfect before. Has this happened to anyone else before? Has anyone else experienced the same issue I have? Is this a knowledgable issue which has solutions and ways to fix it?... :/
Maybe you are looking for
-
A small logical problem in LSMW for MM01...
I need to create a LSMW for MM01 transaction, wherein I have to check the initial four digits of the material as 'ORCL'. If initial four digits of the incoming material are 'ORCL', then create this material as it is. Else replace these four digits wi
-
Running SQLPLUS script from command prompt on SUN
We are making a migration from VMS to SUN ( SunOS 5.10) and from 9i to 10g. We have encountered an unanticipated problem with running scripts from the command line in SUN(SQLPLUS execution from the command line). All of our packages have a naming con
-
I'd like to with one or two buttons presses be able to record a voice note and then have the mp3 or wav file of that voice note automatically attached to a specific (one only) email that is then sent. Is this possible, if so how hard would it be ? If
-
Qty withdrawn is not updating in prod order.
Hi gurus, Qty wihdrawn is not updating in prod order , when i issuing raw material through tcode mb1a 261 movement type. What could be the possible reasons.Pls suggest. Thanks in adv. Sudarshan
-
Is there anyway I can get rid of voice delay in AIM video chat?
I can't stand hearing my own voice on AIM. This is via headphones or speakers. How do I get rid of this?