FCPX has suddenly started crashing when trying to import media

I updated FCPX to 10.0.8 a couple of weeks ago and everything has been fine until today (I'm fully updated with Mountain Lion as well) .  Now every time I try to import media, FCPX crashes. This occurs right after I hit the "Import Selected" button -- and occurs regardless of type of media, where I'm importing it from, or how many clips.  I get a very long error message -- I've attached just the first part of it (through Thread 0) below.  The entire error message runs through Thread 37.
The only thing I did right before this happoened was to delete some old unused applications that were not even on the system HD (they were on a different internal HD - drive A).  The applications included very old versions of Final Cut and iMovie that had not been opened in a couple of years.  After I did this, FCPX suddenly started to recognize another internal HD (drive C) as a camera for the first time, and tried to import a bunch of old home movies, which it has never done before.  And ever since then it started crashing when trying to import new media -- even after I "ejected" drive C. 
Any ideas?  I'm at a total loss and in the middle of a big project for a client, and could really use some help.  Thanks!
Process:         Final Cut Pro [326]
Path:            /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier:      com.apple.FinalCut
Version:         10.0.8 (221398)
Build Info:      ProEditor-22139008018000000~1
App Item ID:     424389933
App External ID: 14685451
Code Type:       X86-64 (Native)
Parent Process:  launchd [152]
User ID:         502
Date/Time:       2013-03-31 13:00:19.713 -0400
OS Version:      Mac OS X 10.8.3 (12D78)
Report Version:  10
Interval Since Last Report:          14013 sec
Crashes Since Last Report:           9
Per-App Interval Since Last Report:  12180 sec
Per-App Crashes Since Last Report:   9
Anonymous UUID:                      11BDDCCB-5BCF-05B8-C04A-9A39067B1572
Crashed Thread:  0  Dispatch queue: com.apple.main-thread
Exception Type:  EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Application Specific Information:
objc[326]: objc_removeExceptionHandler() called with unknown alt handler; this is probably a bug in multithreaded AppKit use. Set environment variable OBJC_DEBUG_ALT_HANDLERS=YES or break in objc_alt_handler_error() to debug.
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib                         0x00007fff8d168814 objc_alt_handler_error() + 0
1   libobjc.A.dylib                         0x00007fff8d1686a0 alt_handler_error(unsigned long) + 52
2   libobjc.A.dylib                         0x00007fff8d162f35 objc_removeExceptionHandler + 92
3   com.apple.CoreFoundation                0x00007fff893ebb49 _CFDoExceptionOperation + 89
4   com.apple.AppKit                        0x00007fff86e2bbcf -[NSApplication endModalSession:] + 24
5   com.apple.prokit                        0x00000001003283c3 -[NSProApplication endModalSession:] + 45
6   com.apple.FinalCut                      0x0000000100033870 -[PEAppController windowWillClose:] + 416
7   com.apple.CoreFoundation                0x00007fff893aceda _CFXNotificationPost + 2554
8   com.apple.Foundation                    0x00007fff8575ae26 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64
9   com.apple.AppKit                        0x00007fff870c49e0 __18-[NSWindow _close]_block_invoke_0 + 260
10  com.apple.AppKit                        0x00007fff870c48b5 -[NSWindow _close] + 364
11  com.apple.FinalCut                      0x0000000100073be7 -[PEImportWindow timer] + 439
12  com.apple.Foundation                    0x00007fff85785af3 __NSFireTimer + 96
13  com.apple.CoreFoundation                0x00007fff893b7804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
14  com.apple.CoreFoundation                0x00007fff893b731d __CFRunLoopDoTimer + 557
15  com.apple.CoreFoundation                0x00007fff8939cad9 __CFRunLoopRun + 1529
16  com.apple.CoreFoundation                0x00007fff8939c0e2 CFRunLoopRunSpecific + 290
17  com.apple.HIToolbox                     0x00007fff84842eb4 RunCurrentEventLoopInMode + 209
18  com.apple.HIToolbox                     0x00007fff84842c52 ReceiveNextEventCommon + 356
19  com.apple.HIToolbox                     0x00007fff84842ae3 BlockUntilNextEventMatchingListInMode + 62
20  com.apple.AppKit                        0x00007fff86f2e563 _DPSNextEvent + 685
21  com.apple.AppKit                        0x00007fff86f2de22 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
22  com.apple.AppKit                        0x00007fff86f251d3 -[NSApplication run] + 517
23  com.apple.prokit                        0x00000001003286c5 NSProApplicationMain + 378
24  com.apple.FinalCut                      0x0000000100001e14 start + 52
I'th Mountain Lion as well.  *and FCPX 10.0.7

Update: the problem is definitely with the internal HD "drive C".  Before restarting FCPX after the last crash I unmounted the C drive -- then restarted FCPX and was able to import media just fine.  I thought I had tried this already, but I guess not.
So, what did I change with my C drive when I deleted the old apps off my A drive?  There is both an iMovie events and projects folder on the C drive -- but FCPX has never tried to import them until after I deleted the old iMovie app (I still have the most recent version of iMovie on my system drive -- but have never used it to open these old folders).  I read on another thread on this forum that if I "hid" these folders, FCPX would not try to recognize them, so I moved them to within another folder on the same drive -- but FCPX is still trying to recognize and show them when the Import Media window is launched --  and still shows the C drive as a camera.
So, what can I do to stop this from happening?
Thanks!

Similar Messages

  • FCPX 10.0.4 crashes when trying to import media

    I updated to FCPX 10.0.4 the other day and just tried to check out some 1080p24 footage I shot with my Panasonic GH2 this morning.  Some clips seem to work fine, but a couple are causing problems.  I use transfer from camera, select a clip or part of it, and select transcode to proxy.  It seems to copy it to the Original Media folder, but crashes.  Nothing ends up in the Transcoded Media folder.  I reopen FCP and it shows the clip as missing, because I have selected to use proxy media.  If I switch to Original, or try to intiate a transcode manually it crashes.  I can remove the clip manually form the Original Media folder to get going again, but same thing happens on that clip.  I just tried again without transcoding and that doesn't seem to work either.  It just doesn't like something about importing these clips.  They play back fine when I view them in the Original Media folder, so they don't appear to be corrupt.  Any ideas?
    Unforunately, I don't have another system available I can check these clips with, is there a way to roll back to 10.0.3 to try it?

    I still have the trial 10.0.3 download, but unforunately can't run it because it's expired.
    There's another guy here that seems to be having similar issues importing AVCHD (same as my GH2).
    https://discussions.apple.com/message/18147371#18147371
    I removed the problem media and was able to continue for awhile without it on my macbook air while I was away.  Now that I'm back home on my 2009 era mac mini I have since imported more footage and encoutering the same thing on this system (also, unfortunately updated to 10.0.4).  It was at a point where it'd crash everytime it opened.  After a few times it wouldn't crash on opening, but I found that if I scrolled up through the clips in the event viewer, as soon as one particular one started to appear it would crash.  The problem clips seem to probably be higher bit rate because they have more motion like steadicam or slider in front of moving trees.
    There's stuff related to AVCHD in my crash reports.  I looked inside the app package and saw this file.  I compared it to the files inside the package from the trial and it's definately been updated.  I haven't experimented yet, but I thought about trying to copy the old AVCHD plugin to the new version and see if it can handle my footage better, but I don't know what else breaks if it's expecting access to new features or something.
    0x11a9f0000 -   
    0x11ac87fef  com.apple.AVCHDPlugin (2.0.0 - 1014.5.29) <02B6EE1F-C8BA-EB46-14BE-17330045B3C8> /Applications/Final Cut Pro.app/Contents/PlugIns/RADPlugins/AVCHD.RADPlug/Contents/MacOS/AVCHD
    I've got several saved, I can post the full thing, but I know nobody likes scrolling through it all.

  • Why did IMovie 9 start crashing when trying to import from camcorder

    I have Imovie 8.0.6 and a Panasonic HDC-SD60 camcorder. I have been importing from this camera for a long time, with no problems but now, IMovie crashes whenever I push the import button. I checked and when nothing is connected, the internal camera comes up when I push the import button. I connect the Panasonic first & see it on the desktop & then open Imovie. ANy idea why it keeps crashing?

    Yes,  20 GB is very little - when you import you produce AIC  files which are much larger than the original clips.  Unless you can clear a lot more space (tens of GB) you need an external hard drive to put your iMovie media on.
    This is the  AVCHD file structure you should see from the Finder when you connect your camera like an external drive:
    First copy the clips you want to use from the STREAM folder to another folder on your hard disk.
    Next, you need to convert them from .mts to .mov format using the free program Media Converter.  You can also do batch conversions by dropping multiple .mts files onto its window.  You need to instal the Re-wrap AVCHD for Quicktime - uncompressed Audioplugin.  It is fast since it is not transcoding but simply changing the video wrapper.  The website is:
    http://media-converter.sourceforge.net/
    The resulting .mov clips will import into iMovie (this works for iMovie 9 - I'm assuming it will also work with iMovie 8.)
    Geoff.

  • Premiere Pro CC crashes when trying to Export Media

    I really hope someone can help me with this.
    I bought a brand new Dell XPS 15 because I will be studying multimedia production next year. Next week I'm registering for the art school and I'll be able to buy a CC student license. I installed the Creative Cloud Trial Version because I couldn't wait to check out the new features in Photoshop and Premiere Pro. However after working on a Premiere Pro project for several hours, the program crashed when trying the Export>Media function.
    As soon as I hit Export>Media in every project I make in Premiere Pro, the following dialog box pops up: "Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.". I'm not able to export my project, not even by using the keyboard shortcut Ctrl+M.
    I already tried reinstalling Creative Cloud, without any luck. Any idea what could be causing this? I really need this fixed before school starts, so help is much appreciated.
    Here are my system specs:
    - Intel Core i7-4712HQ processor
    - 16GB DDR3L RAM
    - Nvidia GeForce GT750M 2GB
    - 500GB SSD
    Thanks to everyone willing to take a look at my problem.

    Hi John,
    Thanks for your response. I checked all those links but I'm afraid none of those solves my problem. My GPU drivers are up to date and changing BIOS settings to fixed to disable Nvidia Optimus doesn't work as well.
    I checked Windows Event Viewer and the error shows as following:
    EventData
    Adobe Premiere Pro.exe
    8.0.0.169
    536f4f89
    MSVCR110.dll
    11.0.51106.1
    5098826e
    c0000409
    00000000000740c4
    21b4
    01cf994108252059
    C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    C:\Windows\SYSTEM32\MSVCR110.dll
    a2ad4021-0534-11e4-8260-e82aea8638f9

  • Dreamweaver cs5.5 suddenly started crashing when it starts or right after it opens...

    OMG so frustrating, my dreamweaver cs5.5 has started suddenly started crashing either during the splash screen or right after I choose a web site to work on.
    YES I have red the forums and tried EVERYTHING, deleted my preferences, made a new account, re-installed three times, editing the registry, done it ALL.    It seems to open now in a temp Guest acct with Admin privileges but I can't access any of my web site files, it's really not usable this way...what can I do?
    It crashes during this...  even though I have cleared the site cache several times.....
    How can I have this expensive of a program just not work.....HELP, I have tons to do and can't use my software!
    Please someone help!
    I even CALLED Adobe and tried to PAY for help....      this is shocking to me after spending tons of money on Adobe software..
    Thank you ahead of time.

    Here's exactly what was at the bottom of my bum css file:
    /* Extra small devices (phones, less than 768px) */
    /* No media query since this is the default in Bootstrap */
    /* Small devices (tablets, 768px and up) */
    @media (min-width: @screen-sm-min) { ... }
    /* Medium devices (desktops, 992px and up) */
    @media (min-width: @screen-md-min) { ... }
    /* Large devices (large desktops, 1200px and up) */
    @media (min-width: @screen-lg-min) { ... }
    So they were completely empty...I just stuck them in there because I wanted to add stuff in there...not sure what I will do now..
    Interesting just FYI this is a web site which is utilizing Bootstrap...so these MQ came directly from the getbootstrap.com web site...

  • Photoshop Elements 12 Organizer Crashing When Trying To Import Photos

    Just downloaded and started using PSE 12 Editor and Organizer about a week ago.  (An upgrade fron PSE11).  Today for whatever reason, when trying to import any file, say from my desktop or a download foler, the list of locations to import appears for a second, then disappears. I am unable to do any other action and have to quit or force quit.  In PSE Editor, I am able to open a file, but when trying to save it, I get an error that "Could not complete your request due to a Program Error".  I use a Mac and just recently upgraded to OS Maverick.  Anyone having the same issue or can suggest a potential fix?  I also tried using PSE 11 and run into the same problem.  Thanks.

    It's very important to delete the existing preferences on upgrading to Mavericks.
    You want
    com.adobe.PhotoshopElements.plist
    Adobe Photoshop Elements 12 paths
    Adobe Photoshop Elements 12 settings
    and then for the organizer anything like com.Adobe.Elements Organizer.12.0.plist. You'll find at least two files with the number for the organizer entered differently.
    Those files are all in your user>library>preferences folder. Here's how to see it in 10.9:
    http://www.cultofmac.com/251544/mavericks-makes-it-way-easier-to-access-your-library-folde r-os-x-tips/
    While you're in there go to the Saved Application States folder and clean out anything related to PSE.
    Repair permsisions and try again.

  • My Photoshop Elements 11 has suddenly started crashing every time I try to open it.

    I've tried repairing the catalog and I'm told alternately that it doesn't need to be repaired and that it can't be repaired.  I've tried to create a new one, but the program still crashes when I open it.

    You should probably post your question in the iTunes discussions:
    http://discussions.apple.com/category.jspa?categoryID=149

  • Crashing when trying to import files!

    I used the betas with out issue.
    Now I am trying to import some of my older photographs. But it keeps crashing throwing up
    A) Microsoft Visual C++ Runtime Error
    Runtime error!
    Program: C:\...
    Promptly followed by
    B) lightroom.exe application error
    The exception unknown software exception (0x40000015) occurred in the application at location 0x781346b6
    Click ok to terminate this program.
    Quite annoying not being able to import photo's in to a photo management suite.
    Some additional information, all images are apx 640x480 all in jpg, and if I go back in and run it again slowly I can get the whole folder imported, but I have thousands of pictures from this old camera.
    Hope someone can shed some light, and hoping all these crashes are not going to corrupt my database!.
    Erik

    Hi Erik --
    I unfortunately can't say for sure if one of them is this one, but we have cornered a few crash bugs on Windows related to some peculiar values for certain metadata found in some JPEG files and at least one of them is related to a feature that was added after the last beta, which makes me hopeful it might be the one you are seeing.
    What kind of camera are these files from? Is there a place you could post a couple of example pictures? I'd like to be able to confirm with greater certainty that we've fixed the bug you're seeing here.
    Thanks for the feedback and sorry for the inconvenience!
    Dan Tull
    Lightroom QE, Adobe Systems

  • Framemaker 10 crashing when trying to import formats

    I have been having trouble with Framemaker 10 (most recent version 10.0.2.419) crashing when I try to import formats from one .fm file to another, or more often a group of other files.
    I am using Windows 7 64-bit for an OS. The documents are all unstructured. The files are small (less than 10 pages in general), no extensive formating or graphics. If I am importing to a group of files in a book, its 6 or fewer files. I have something like 13 crash reports over the last month, so its not a seldom occurance.
    At least a few of the crash reports have also mentioned errors 6382424, and 6383085.
    That is all the information I can think of.
    Is there someplace I can look up the erorr numbers that are getting reported to me when Frame crashes? I would do self-diagnosing and attempt fixes, but I am having a very difficult time finding information to allow that.
    Any help is appreciated.

    Too bad about those error codes. I guess I can only use them to determine if I have the same problem over and over or brand new problems.
    The files are nearly all unqiue text, and if not it was importated without formatting (edit > paste special > unformatted text) or washed through a pure text app like Windows notepad.
    Since you mentioned it, I've see the MIF-wash suggestion. I'll give it a try.

  • Call Recorder ++ has suddenly started crashing & wont open

    ‎I have written to the App developer's tech support 4 times in a week now without the courtesy of a reply so.i thought I would try this board for help. 
    The app in question is Call Recorder ++ by Ajani InfoTech Private Limited. Version 2.0.0.1
    The app has stopped working. It won't even open. 
    I am running a BlackBerry Z30 (OS 10.2.1.3247 )
    I have many recorded calls. 
    When I try to open the App I get a black screen with the black BlackBerry logo then after 10 seconds or so the app crashes and it sends me back to my home screen.  
    I note the same developer has just released an app called  Call Recorder 10 for BlackBerry ver 2.1.1.1   I' I'm wondering if they shut down Call Recorder ++
    My trouble shooting steps have been to un install the app, do a hard re boot, reinstall it then do another hard re boot before opening it. The app still crashes.  
    I then un installed the Voice Recorder++ and installed their free version of Call Recorder 10 (their new one) I get the Same crash issue. 
    I know where the calls are stored. Using file manager there is a folder called Voice and a sub folder called voice recorder. The recordings are there but all out of order. 
    I've re installed Call Recorder ++ after un installing the New Call Recorder 10. Still no joy.    NOTE; this is my only app crashing so I would hate to do a device re boot.  
    I'm turning to this thread for trouble shooting steps before having to do a re boot of the  OS. The app worked fine until last week. 
    Can anyone propose some trouble shooting steps? Perhaps there is an app to folder issue? I notice on un-install the folder is still there so maybe I can copy those recorded calls to.my desktop and delete the voice and call recorder sub folder?    
    Maybe there is a conflict between the app and the folder it created on install? 
    Funny thing is when I get or make a call I hear a buzz in my ear indicating recording has started then I get a notification that the call recorded so it's still working in the background. I had to delete it so it wouldn't eat my storage memory. 
    Thanks in advance for any help. 
    Z30STA100-5/10.2.1.3247
    Frank

    The crash dumps will be helpful but lets try the following first:
    > Enable the hidden Admin Account on Windows 8 ( Ref :  http://www.howtogeek.com/howto/windows-vista/enable-the-hidden-administrator-account-on-wi ndows-vista/ ) This kb doc instructions will work on Windows 8.1 as well
    > Disable all Non-Microsoft Startup Services. (Ref : http://helpx.adobe.com/x-productkb/global/disable-startup-items-services-windows.html )
    > Disable all the Antivirus softwares like CA, Norton,Mc Afee etc. temporarily from the computer.
    Reboot and try launching Acrobat in the new enabled Admin user account and check.
    Let me know if this worked for you.
    Regards,
    Rave

  • Quark 9.3 has suddenly started crashing

    My Quark 9.3 has been fault-free until now. Every time I try moving a text box or using drag-and-drop, it crashes. I have read elsewhere that Mavericks could be to blame. Is this likely and, if so, how do I uninstal it. It's driving me potty and means I can't do any layout work. Help please!

    Hi Virgodriver,
    you can't simply uninstall Mavericks, you either have to start fresh or hopefully have created a backup or clone beforehand which you can use to revert.
    Here's a small tutorial how to do that best:
    http://www.planetquark.com/2013/11/05/best-practise-how-to-safely-test-os-x-mave ricks-before-using-it-for-production/
    If you want to stay with Mavericks, then I recommend updatign to QuarkXPress 9.5.4 (free for v9 users), as this adds Mavericks compatibility.
    Thanks
    Matthias

  • Photoshop CS3 has suddenly started crashing on start - VersionCue.framework is missing

    I have been using CS3 for years on my Mac without issue. Tonight it's suddenly produced this error message and will not run:
    I have looked for this VersionCue thing all across my computer but cannot find it. The AdobePatcher downloaded from the website refuses to run saying it cannot locate the product to be updated.
    Re-installing Photoshop isn't possible as I upgraded to CS3 from 7 and 7 does not run on Intel Macs. I only have an upgrade version of CS3.
    Is there no way to obtain VersionCue by itself? For such a vital componant it seems to be awfully hard to track down and/or fix.

    That's the extremely frustrating thing. My external HD corrupted a short while ago and couldn't be fixed (it was out of warranty). I've only just been around to set up a new one with it being a busy time of year. So therefore I had no current backup at the one time when I actually needed a backup. So therefore: No backup.
    I've checked to see if anything else vital is missing but it's not. I guess I won't know unless anything else goes awry.
    Is there no way to just obtain this VersionCue component individually?

  • Mail crash when trying to import inbox from thunderbird

    hey,
    i am trying to convert all my operations to native programs, i am currently using ThunderBird as my mail client but want to move over to mail. when i go to import my inbox i manage to find it and when it starts to import it crashes! i am assuming it is because i have over 4,500 e-mails that are split over to folders about even. i want to know how can i solve this, basically all i want is to open up mail and have everything there not in a separate folder that has all my imported e-mails, i want it as if i have been using mail from the start.
    all help would be appreciated
    MacBook Pro   Mac OS X (10.4.9)  

    Hi Farid Shahin.
    Verify/repair the startup disk (not just permissions), as described in the following article, in case there is something amiss in the filesystem:
    The Repair functions of Disk Utility: what's it all about?
    You’d get better results using Eudora Mailbox Cleaner to do the conversion.
    Eudora Mailbox Cleaner requires rebuilding the imported mailboxes in Mail afterwards. Instead of rebuilding them one by one, you can re-create the entire index as follows:
    1. Quit Mail if it’s running.
    2. In the Finder, go to ~/Library/Mail/. Make a backup copy of this folder, just in case something goes wrong, e.g. by dragging it to the Desktop while holding the Option (Alt) key down. This is where all your mail is locally stored.
    3. Locate Envelope Index and move it to the Trash. If you see any other “Envelope Index”-named file there, delete it as well.
    4. Open Mail. It will tell you that your mail needs to be “imported”. Click Continue and Mail will proceed to re-create Envelope Index — Mail says it’s “importing”, but it just re-creates the index if the mailboxes are already in Mail 2.x format.
    Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder. That is, ~/Library is the Library folder within the user’s home folder, i.e. /Users/username/Library.

  • Iphoto 11 crashes when trying to import

    I have been importing fine but just now iPhoto 11 shuts down/crashes. this happens when i just select the import from the menu and don't even get a chance to select the target destination. I have looked on forums and it talks about 3ivx file to delete, i cannot find that file also i import from my desktop or dropbox which is synced to my macbook i do not use 3rd party software to get images from a device to my MacBook.
    Please assist as this is driving me nuts.
    Peter

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Step 1
    For this step, the title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if iTunes crashed, you would enter "iTunes" (without the quotes.)
    Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    ☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    ☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
    Step 2
    In the Console window, select
              DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
    (not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste topost the entire contents—the text, not a screenshot.
    I know the report is long, maybe several hundred lines. Please post all of it anyway.
    If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
    Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

  • DVD Studio Pro Crashes when trying to import file

    Hey all,
    Hope you can help me because this is driving me crazy!
    Whenever I try to import .ac3/.m2v files to DVDSP, the program crashes. The strange thing is that it is happening only when I try it on one particular file. I seem to be able to import anything else but the audio/video files I really need!  I've tried re-compressing, and re-naming the file, I've also tried importing the file on a different computer, but nothing seems to work.   I haven't tried reinstalling since it seems to work with other files and I've tried it on separate computers.
    I'm using Final Cut 7 with Snow Leopard
    Here's the first part of the report:
    Process:         DVD Studio Pro [1315]
    Path:            /Applications/DVD Studio Pro.app/Contents/MacOS/DVD Studio Pro
    Identifier:      com.apple.dvdstudiopro
    Version:         4.2.2 (431.40)
    Build Info:      DSP-4315400~54
    Code Type:       X86 (Native)
    Parent Process:  launchd [105]
    Date/Time:       2012-08-10 07:45:07.946 -0400
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:          18354646 sec
    Crashes Since Last Report:           58
    Per-App Interval Since Last Report:  5731 sec
    Per-App Crashes Since Last Report:   7
    Anonymous UUID:                      5565D110-70D4-4F1B-BF1A-072C2D138FF3
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000261
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   com.apple.QuickTime                0x9a8d1dd8 PrivateQTGetMoviePlayabilityState_priv + 62
    1   com.apple.QuickTime                0x9a8d1d8a QTGetMoviePlayabilityState_priv + 33
    2   ...ickTimeComponents.component     0x9448dac8 internalDoAction + 9849
    3   ...ickTimeComponents.component     0x9447cde9 _MCIdle + 61
    4   ...ple.CoreServices.CarbonCore     0x99f72dcc CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
    5   ...ickTimeComponents.component     0x944786a0 _MCComponentDispatch + 111
    6   ...ple.CoreServices.CarbonCore     0x99f6b51f CallComponentDispatch + 29
    7   com.apple.QuickTime                0x9a8d1d3e MCIdle + 37
    8   com.apple.QuickTime                0x9a8cfc25 QTOMovieObject::SendCommand(unsigned long, void const*) + 899
    9   com.apple.QuickTime                0x9a8b337a DispatchQTMsg(void const*, unsigned long, unsigned long, unsigned long, QTOGenericObject*) + 240
    10  com.apple.QuickTime                0x9a8b31de QTObjectTokenPriv::SendMessageToObject(QTMessagePriv*, unsigned long) + 178
    11  com.apple.QuickTime                0x9a8b2745 QTObjectTokenPriv::DispatchMessage(QTMessagePriv*, void const*, __CFAllocator const*, unsigned long, unsigned long, ComponentMsgParam*, unsigned long, unsigned long) + 1249
    12  com.apple.QuickTime                0x9a8cf894 QTSendToObject + 98
    13  com.apple.QTKit                    0x90b811e6 QTObjectTokenExecuteCommand + 83
    14  com.apple.QTKit                    0x90b62b51 -[QTMovie_QuickTime idle] + 303
    15  com.apple.QTKit                    0x90b065ec +[QTMovie_QuickTime idleAllMovies:] + 308
    16  com.apple.Foundation               0x93458484 __NSFireTimer + 141
    17  com.apple.CoreFoundation           0x91eada3b __CFRunLoopRun + 8059
    18  com.apple.CoreFoundation           0x91eab3c4 CFRunLoopRunSpecific + 452
    19  com.apple.CoreFoundation           0x91eab1f1 CFRunLoopRunInMode + 97
    20  com.apple.HIToolbox                0x90e2fe04 RunCurrentEventLoopInMode + 392
    21  com.apple.HIToolbox                0x90e2fbb9 ReceiveNextEventCommon + 354
    22  com.apple.HIToolbox                0x90e2fa3e BlockUntilNextEventMatchingListInMode + 81
    23  com.apple.AppKit                   0x962bf595 _DPSNextEvent + 847
    24  com.apple.AppKit                   0x962bedd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
    25  com.apple.AppKit                   0x965381c9 -[NSApplication _realDoModalLoop:peek:] + 720
    26  com.apple.AppKit                   0x96537945 -[NSApplication runModalForWindow:] + 273
    27  com.apple.AppKit                   0x967cbad3 -[NSSavePanel runModal] + 420
    28  com.apple.dspinterface             0x00047c4f -[DSPXProjectBinModule importAsset:] + 500
    29  com.apple.AppKit                   0x962fda26 -[NSApplication sendAction:to:from:] + 112
    30  com.apple.prokit                   0x0047e414 -[NSProApplication sendAction:to:from:] + 127
    31  com.apple.AppKit                   0x963dd255 -[NSControl sendAction:to:] + 108
    32  com.apple.AppKit                   0x963d8d02 -[NSCell _sendActionFrom:] + 169
    33  com.apple.AppKit                   0x963d7ff9 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 1808
    34  com.apple.AppKit                   0x9642d6ed -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 524
    35  com.apple.prokit                   0x004c321e -[NSProButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 539
    36  com.apple.AppKit                   0x963d6a4f -[NSControl mouseDown:] + 812
    37  com.apple.AppKit                   0x963d4a58 -[NSWindow sendEvent:] + 5549
    38  com.apple.prokit                   0x004a69f0 -[NSProWindow sendEvent:] + 264
    39  com.apple.dspinterface             0x000afc63 -[DSPXDocumentWindowClass sendEvent:] + 777
    40  com.apple.AppKit                   0x962ed60b -[NSApplication sendEvent:] + 6431
    41  com.apple.prokit                   0x00481040 -[NSProApplication sendEvent:] + 1901
    42  com.apple.AppKit                   0x96281253 -[NSApplication run] + 917
    43  com.apple.prokit                   0x004813f6 NSProApplicationMain + 326
    44  com.apple.dvdstudiopro             0x0000354d 0x1000 + 9549
    45  com.apple.dvdstudiopro             0x00002cf6 0x1000 + 7414
    Thread 1:  Dispatch queue: com.apple.libdispatch-manager
    0   libSystem.B.dylib                  0x9062c382 kevent + 10
    1   libSystem.B.dylib                  0x9062ca9c _dispatch_mgr_invoke + 215
    2   libSystem.B.dylib                  0x9062bf59 _dispatch_queue_invoke + 163
    3   libSystem.B.dylib                  0x9062bcfe _dispatch_worker_thread2 + 240
    4   libSystem.B.dylib                  0x9062b781 _pthread_wqthread + 390
    5   libSystem.B.dylib                  0x9062b5c6 start_wqthread + 30

    In FCP, export the file in 4 different chunks.
    In Compressor, convert each chunk to ac3/m2v.
    Import each chunk into DVDSP.
    Do they ALL cause problems or is it only one chunk?
    If only one chunk, there is something wonky with the video in that segment.
    Divide it up and go through the same process until you identify the offending source video. Once identified you have a couple of options -
    1. Cut it out and try to stich the material around the hole.
    2. Try using Digital Rebellion's ProMediaTools to see if it can fix the problem.
    3. If the original media was in a different format, go back to the original media, reconvert it and replace the bad segment.
    x

Maybe you are looking for