Huge FCPX project

I just finished a wedding and shot about 50GB on my Canon 60d.  After all is said and done with one 5min project completed, the total space (including raw files) was over 300GB!  This seems outrageous.  What's going on here?

gc2989 wrote:
… What's going on here?
two things:
You - probably - did convert on import the highly compressed original media to optimized; proRes is about ~40GBs/h.
and:
http://help.apple.com/finalcutpro/mac/10.1/?lang=en#ver68a8c250
on edit, 'tons' of rendering occured; esp. when performing 'trial'n error-editing', incredible amounts of 'inbetweens' are produced.
Do some good housekeeping, as described in the link above.-

Similar Messages

  • FCPX Projects & Events HUGE GBs!

    I have a new Mac Pro, just started using Final Cut X.
    My FCPX Projects & Events is 300GB but I only have 3 current projects, containing 70GB.
    What's happening? Is the render cache hiding old files/renders?

    Thanks Russ! Never noticed "Show Package Contents" before.
    In one current project, I have a few folders, one of which is "Original Media" and another is "Transcoded Media". I'm not sure what Transcoded Media is about, but it appears that it creates High Quality versions of my original clips at way larger file sizes.
    For example, my first original clip is 21.1 MB, and the Transcoded one is 9.8GB!
    What's weird is that my 7th original clip is 1.27GB, and the Transcoded isn't much bigger at 3.85GB.
    What is this all about? Do I need these things?

  • ADVICE needed - FCPX projects -- FCP7 workflow (not X27)

    Hey all,
    I need some sage advice.
    I have been working on a huge project for over a year now on location in Bosnia.
    All footage has been shot on the 5D mrk3 and c300 cameras.
    My FCPX Workflow
    While on location I was importing / organizing / syncing / labeling and adding subtitles into FCPX.
    - I have each camera in it's own event and project.
    - I have the video synced (using Plural Eyes) with the Zoom audio files.
    - I have added subtitles from my translator using Annotation edit.
    - I have then used the TimeCode generator to give the entire sync'ed, subbed "master timeline" a consistent reference throughout and so I always know exactly where that clip lives in the "master timeline" once I start editing.
    - Lastly I have added the "file name" using the Text "right" generator in FCPX so I always know what day it is.
    I would then create a separate compound clip for all the video from that day, the external audio, and the subtitles. (so that is 3 Compound clips. (see pics below)
    Add the TimeCode and right text generators...
    Select all and make it all a C. Clip... I did this so nothing would shift.. the Subs would be in sync and the timecode would always be the same no matter how and where the footage was used....
    My Question / Challenge
    OK so now my producers have found an editor and this editor needs to edit this project in FCP 7.
    I am in Chicago they are in Berlin... I will join them in Berlin but want to do as much prep work in the 1.5 months leading up to my travel date here in Chicago.
    They have all the footage and FCPX projects and events and now need to get them into FCP 7
    the app X to 7 does not import FCPX generators and has some quirks importing text (I am not sure how it will handle my subs as we are just beginning the import / converting process)
    What I don't want is to loose all the good work that I have done on my end to be organized and I absolutely NEED the subtitles included with the sync'd footage.
    Does anyone have any advice and / or know where I can turn to figure out what to do in this situation?
    the viewer with subs, timecode, and file stamp
    the timeline broken apart
    the timeline as compound clips

    @ Russ H
    Yeah I thought of that too...
    Just using the flatened verssion as a reference file that can be enabled and disapbled as necessary hoever like you pointed out that is "not ideal" AND would actually be pretty time consuming as I am dealing with
    45 Days of footage totalling 200+ hours...
    So it actually takes about an hour to render and export each 3-4 hour days of flattened footage.
    But that may be the best soltuion of the not so great options I have in front of me...
    @Meg The Dog
    Thanks, and yes I will be doing all of that sans the assistant editor.
    One of the largest issues is that I am not a FCPX expert so I can't do that...
    AND the budget is a bit tight to hire a second editor for this job PLUS it is in Berlin (I am in Chicago)
    So while I will be there for the editing process the lead / post time is going to be pretty tight and I need to make sure that all the footage is online, sync'd, subbed and ready to go once I step off the plane.
    I agree that in an ideal situation your suggestion would be best if the budget allowed for it...
    Message was edited by: sConvey

  • How can you tell FCPX project files in a deleted trash recovery program

    Hello All
    Did the unthinkable and trashed a FCPX project folder I need.....and emptied the trash.
    I immediatly went into recovery with program ''Stellar Phoenix...'' and was able to recover loads of files.
    Since they are now ''generic'' labeled, I can't decifer which one is the FCPX project file.
    Does anyone have a method to determine which is which in a recovery situation.
    Some further info....
         recovered files are organized in folders by types:
                   OSX 10.6
                   graphics
                   documents
                   apps......sub folders to include: ''c source...plist....apple scripts....etc
                   video
                   audio
                   archive
                   and a few more..
    It seems apparent that it's not going to be video,audio. graphics...etc
    but I was thinking ''apple scripts'' as a project is just instructions for the timeline movie, right?
    anyway, have a lot of searching to do and no real map on what I'm looking at here.
    Anyone had an experience like this and can shed some light?
    ...greatly appreciate it
    Thanks!

    Monty,
    Within FCP, there is a menu item called "Media Manager" (depending on what version you are in). This would be worth your while to look into. It basically organizes your project by moving/archiving any used assets of a project and leaving out un-used assets. It saves a ton of disk space.
    For example, say you have a 5 minute clip with an in/out point that is just 30 seconds. Media Manager will "archive" just that 30 seconds, not the entire clip. There is even a setting that you can add additional "handles" time to the front andd back of the clip if you think you may need to add or change transition.
    Do a google search. I was just watching a few Youtube videos on this myself.
    Jonathan

  • I have lost an fcpx project. when i search it, i'm directed to a backup file, but it's just (gibberish/code) text.  how can i retrieve/restore my project?  HELP!!!???

    i have lost an fcpx project. when i search it, i'm directed to a backup file, but it's just (gibberish/code) text. 
    i think i was asked to install an update (something to do with libraries?) before i started working, but i didn't do the update.
    don't know if this has anything to do with problem.
    how can i retrieve/restore my project?  HELP!!!???

    juddfromsherman oaks wrote:
    i have lost an fcpx project. when i search it, i'm directed to a backup file, but it's just (gibberish/code) text.
    The backups for your version are date-time stamped as the name and with an extension of .fcpproject. They look like this.
    The original project is named CurrentVersion.fcpproject.
    You need to replace the CurrentVersion with the backup file and rename it to be CurrentVersion.fcpproject.
    With FCPX closed, I suggest you move the original to the Trash, but not empty it. Then promote your backup one level higher in the project folder hierarchy (to be at the same level that the original previously occupied. Then rename the backup.
    Open up FCPX, which should now recognize your project.
    Russ

  • If I replace memory sticks, will this affect ongoing FCPX projects?

    Mid-year 2010 iMac with only 4GB memory (2x2). Computer running Extremely slow while editing, surfing web, everything! Nothing on the hardrive - already dumped everything onto external HD's months ago - but it just keeps getting slower. Today - patience ran out.
    Just purchased 16GB memory (4x4).
    Main concern - if I remove the 2x2GB memory sticks/cards, could this affect the current FCPX projects I am working on?
    This may be a dumb question to experts, but my anxiety of losing these projects drives me to ask this important question before leaping.
    I am grateful for any help and/or advice given!
    Also - any other tips about helping your Mac run faster is always appreciated.
    Thanks!

    I feel sure that hwoever sold you your ram, first reasearched this. Look under the apple menu/about this mac to see how much Ram & its speed on your mac.
    Have a look at this link. 
    http://eshop.macsales.com/shop/apple/memory/iMac
      Try editing only after you start up your Mac. If you gotta go online, check your e-mail, play with FaceBook, etc. - do that then reboot to edit.
    I also suggest deleting any startup items that you don't NEED to start up at LOGIN:
    apple menu/system preferences/users & groups/log in items.
    I downloaded a little app called System Pal from the App Store so I can see in real time what is using Ram & the CPU. Works for me.
       So much of Final Cut Pro X takes advantage of the I7 chip & Vram. Unless you are having OS or software issues, your Mac is doing the best it can. Generally, I try to stay with App versions that are designed with my hardware.
       I suggest using FCP X tutorials to learn the program really well. If you become a great editor, you will be able to afford a new machine in no tiime.
    Goood Luck

  • While working on FCPX project, power failed. Power on, restarted, opened FC, Project Library shows blank icon, no clips. Click on icon, nothing happens. Haven't done back-up. Can project be recovered?

    While working on a FXPX project, there was a power failure. Power back on, restarted FCPX, project name in Project Library is a blank icon, nothing happens when I click on it. Believing back ups were automatic and continuous, I made no back up. Can the project be recovered?

    Years of fine internet use via WIFI then randomly it starts dropping then one day (weeks later) it is no longer accessible at all and even saying "No hardware installed" when I click on WIFI icon at the top right on screen. Here is how I finally fixed it!:
    For six months I wallowed in this problem and had to connect my macbook pro to the internet via ethernet cable which as you can image was very restrictive :/
    I have had numerous laptop technicans befuddled by this WIFI problem and most concluding with how my WIFI card must be broken and that I will need to buy a new one. The last suggestion I had on the matter was to buy a USB wifi dongle.
    So I ended up buying this one, http://www.asus.com/nz/Networking/USBN10_NANO/Unfortunately my macbook pro didn't want to read the install disc and it didn't autorun so it didn't work. After reading more forums I saw that you could download the program from the net and sure enough it worked.. BUT STRANGER when I took the USB dongle out the WIFI was still working!! The program appears to have reminded my four year old macbook pro that it is indeed WIFI capable.
    So to find this miraculous program its located herehttp://www.asus.com/nz/Networking/USBN10_NANO/HelpDesk_Download/
    Same link as above just under SUPPORT>Driver&Tools
    You then click on a file when its downloaded and a file called MAC will appear, then click on install. Within 5 minutes you should have your WIFI back. My macbook pro crashed again today but without having to get the shortest ethernet cable you've ever seen out again - I was able to install the program again and WIFI was up and running once more. Moral of the story - didn't need to spend any money to fix this and not even using the USB dongle.
    So happy!! Hope it works for you too!
    This also worked on a MacBook that lost its WIFI when a user accounts password was changed and the keychain password wasn't known to them - another random way to lose WIFI apparently

  • Best place to store FCPX projects?

    I wanted to find out where is the best place to store FCPX projects? I import the footage/audio to a external harddrive, but save the projects/render files to computer harddrive. Should I save the projects to the external harddrive where the footage is? Or does it even matter?

    See this post from this forum.
    https://discussions.apple.com/message/16411405#16411405

  • Importing fcpx project back into fcpx and having trouble

    Please Help Me.
    So I shared a project from Final Cut Pro X to my desktop so that it was the "Title" - Mac and PC.mp4 file. Then I put the project and all the event files onto an external hard drive and deleted the project and the event files from my computer. Since I did that, the mp4 files disappeared, and now I'm trying to retrieve it, so I plugged in my external hard drive to my computer, and tried to get the project back into Final Cut so I could export it properly this time. But although the project imports back into FCPX, it says all the files are missing. I'm trying to put the event files back into FCPX as well, but it doesn't seem to be synching with the project and now I'm scared that I'll either never be able to have this video again or I'll have to do a serious amount of manual re-editing to retrieve it. It seems that if I have the project file and all the original video files from each event, why would it not be able to be retrieved? Is there something I'm doing wrong or some other way I can retrieve this project and/or get my mp4 file back? Should I be putting the event files in a specific place? Please someone, anyone, help me and let me know if you have any useful advice asap.
    Thank you. 

    here are the warning signs I get when trying to format......
    Warning: The directory ‘/private/tmp/501’ will not be included in the final disc.
    Warning: The file ‘objcsharing_ppc4294967294’ found in the VIDEO_TS folder will not be included in the final disc.
    Warning: The file ‘objcsharing_ppc501’ found in the VIDEO_TS folder will not be included in the final disc.
    Warning: The file ‘objcsharing_ppc92’ found in the VIDEO_TS folder will not be included in the final disc.
    Warning: The file ‘VOB_DATA.LAY’ found in the VIDEO_TS folder will not be included in the final disc.
    Warning: The file ‘WESLEY_GROUPS.layout’ found in the VIDEO_TS folder will not be included in the final disc.

  • FCPX Project Render Settings - Can you edit in h.264 and Transcode/render only used clips on timeline to Prores during render?

    I have a question on the PROJECT RENDER settings in FCP X. It’s seems to me that one could theoretically import and edit entirely with original h.264 video files without needing to Transcode to ProRes422. Once you’re done with your edit and want to get the added benefits of COLOR GRADING in ProRes422 color space, it seems that FCPX will automatically render your edit in ProRes422 according to these preferences. In that case, a color grade could be applied to the whole edit, and be automatically transcoded/rendered into ProRes 422 during the render process. After rendering, what would show up on the viewer and what would EXPORT would be the rendered Prores files and not the original h.264 files. This saves a lot of time and space of transcoding ALL your media, and in theory should enable you to edit NATIVE video formats like h.264, with automatic benefits of ProRes during render.  I'm assuming the render may take longer because FCPX is having to convert h.264 video files to ProRes422 while rendering. This may be one drawback. But will you your color grade actually use the 4:2:0 color space of the h.264 native media, or will it utilize 4:2:2 color space, since the render files are set to render to ProRes422 ? Can anyone please confirm that this theory is correct and optimal for certain work flows?? Thanks!

    Thanks Wild. That's what I thought - in that the render files would be converted to ProRes422 codec. So do you or anyone else think that there is an advantage to having the 4:2:0 original file be processed in a 4:2:2 color space?
    Yes there is an advantage, any effects and grading will look better than in a 4:2:0 space.
    Most professionals online seem to think so. Also - will rendering of heavy effects and color grading take longer using this method because it's having to convert h.264 media to ProRes during render?
    Yes, it will definitely take longer.
    Can anyone verify from a technical standpoint whether editing and color grading in this workflow will see the same benefits as having transcoded the h.264 media to ProRes in the first place?
    Same benefits from a final product view point, you lose on rendering time though and if you have lots of effects things will seem slow as it will have render everytime from the h264 file rather than a Pro Res file for every change you make. This may be fine on a higher end mac but I'm sure just pummels an older lower end mac as to being almost useless.

  • How can I separate FCPX projects and events on external drive?

    Hi there!
    I'm working on a Mac Pro with two drives. One drive contains the OSX and the second drive I use to store video media. I'm running FCPX 10.0.4.
    The Mac Pro is used in a teaching environment (i.e. creative suite, FCPX, iMovie, etc).
    Each tutor has their own user account for their own students (i.e. Fish account for one tutor, Mouse account for another tutor). Each user account is specially setup for the apps that that particular tutor teaches.
    With FCP7 I setup individual capture folders on the second drive for each user account. The FCP7 capture scratch for each tutor was set to a specific folder on the capture drive...i.e.
    capture/fish/final_cut_pro_documents/
    or
    capture/mouse/final_cut_pro_documents/
    The issue with FCPX is that if you capture to a second drive it saves the Events and Projects to the Root of the drive. This means that all captured/imported video footage from all of the user areas will be saved in one location and will be bunched together in the FCPX events and projects list.
    Workaround 1:
    A workaround would be to capture all footage to the OSX bootable drive so that all Events and Projects are stored in the individual user Movies folder, but I'm wary of using one drive to run the OS and High Def video footage for drive speed issues.
    Workaround 2:
    Another workaround would be to partition the capture drive into separate partitions for each tutor, but then one tutor may fill up their drive quicker than others and then I''d have to repartition the drive to allow for more space! (bearing in mind we have 17 Macs all setup in the same way!)
    Workaround 3:
    I've also tried making symbolic links from each user Movies folder to a specific location on the capture drive, but no luck. 
    Does anyone know of a workaround which might work?
    With many thanks in advance,
    Lawrence

    Hi Tom,
    Firstly, thank you for your reply.
    From your experience, can you setup Event Manager X to automatically hide all events and projects except those edited on a specific user account...for all user accounts...or is this something a new student would have to do manually before starting a new project?
    Many thanks in advance,
    Lawrence

  • Is it possible to fix a corrupt FCPX project?

    here is my crash detail:
    Process:         Final Cut Pro [226]
    Path:            /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
    Identifier:      com.apple.FinalCut
    Version:         10.0.3 (192356)
    Build Info:      ProEditor-192350600~1
    App Item ID:     424389933
    App External ID: 5878386
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [145]
    Date/Time:       2012-03-25 15:54:04.457 -0400
    OS Version:      Mac OS X 10.7.3 (11D50)
    Report Version:  9
    Interval Since Last Report:          524351 sec
    Crashes Since Last Report:           17
    Per-App Interval Since Last Report:  343264 sec
    Per-App Crashes Since Last Report:   13
    Anonymous UUID:                      5BB4EB19-3BCE-4DF8-AFBF-2C3D21AC5B3F
    Crashed Thread:  14  BGTask: MEBackgroundLoadManager  Dispatch queue: com.apple.root.default-priority
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    Background exception: 'Unexpected exception' --> { (
              0   CoreFoundation                      0x00007fff8ad85fc6 __exceptionPreprocess + 198
              1   libobjc.A.dylib                     0x00007fff8972dd5e objc_exception_throw + 43
              2   CoreFoundation                      0x00007fff8ae102a9 -[NSException raise] + 9
              3   Flexo                               0x00000001008df709 FFApplicationHandleExceptionThatShouldNotBeIgnored + 153
              4   Flexo                               0x000000010084c204 -[FFBackgroundTask main] + 884
              5   Foundation                          0x00007fff825f86d8 -[__NSOperationInternal start] + 705
              6   Foundation                          0x00007fff8260b936 ____NSOQSchedule_block_invoke_2 + 124
              7   libdispatch.dylib                   0x00007fff865578ba _dispatch_call_block_and_release + 18
              8   libdispatch.dylib                   0x00007fff86558799 _dispatch_worker_thread2 + 255
              9   libsystem_c.dylib                   0x00007fff8ca9a3da _pthread_wqthread + 316
              10  libsystem_c.dylib                   0x00007fff8ca9bb85 start_wqthread + 13
    objc[226]: garbage collection is OFF
    abort() called
    Thread 0:: Dispatch queue: com.apple.main-thread
    0   libsystem_c.dylib                       0x00007fff8cade54c OSAtomicCompareAndSwap64Barrier$VARIANT$mp + 8
    1   com.apple.CoreFoundation                0x00007fff8aceae17 CFRelease + 551
    2   com.apple.CoreFoundation                0x00007fff8acef432 __CFBasicHashDrain + 450
    3   com.apple.CoreFoundation                0x00007fff8ad290a6 CFDictionaryRemoveAllValues + 310
    4   com.apple.CoreFoundation                0x00007fff8adabc88 parseTag + 392
    5   com.apple.CoreFoundation                0x00007fff8adac2be parseTag + 1982
    6   com.apple.CoreFoundation                0x00007fff8adac2be parseTag + 1982
    7   com.apple.CoreFoundation                0x00007fff8adac2be parseTag + 1982
    8   com.apple.CoreFoundation                0x00007fff8adac2be parseTag + 1982
    9   com.apple.CoreFoundation                0x00007fff8ada9d4c parseXML + 7436
    10  com.apple.CoreFoundation                0x00007fff8ada7c8f CFXMLParserParse + 415
    11  com.apple.procore.framework             0x0000000100160cdf PCXMLReadStream::parse() + 31
    12  com.apple.prochannel.framework          0x0000000102793f1e OZChannelBase::configureWithState(__CFData const*) + 68
    13  com.apple.prochannel.framework          0x00000001027ea207 -[CHChannelFolder configureDescendantsWithChannelState:] + 60
    14  com.apple.Flexo                         0x0000000100bfedeb -[FFEffectStack initWithCoder:] + 1387
    15  com.apple.DeepSkyLite                   0x0000000101e54056 -[DSSyncContext load:persistentObject:] + 125
    16  com.apple.DeepSkyLite                   0x0000000101e58b8f -[DSObject DSObjectInitWithInvocation:] + 260
    17  com.apple.CoreFoundation                0x00007fff8ad72ff4 ___forwarding___ + 756
    18  com.apple.CoreFoundation                0x00007fff8ad72c88 _CF_forwarding_prep_0 + 232
    19  com.apple.Flexo                         0x0000000100a27a4d -[FFAnchoredObject _addUserEffectsFromEffectStack:toArray:] + 45
    20  com.apple.Flexo                         0x0000000100a27a04 -[FFAnchoredObject _shallowEffects] + 116
    21  com.apple.Flexo                         0x0000000100a2b0e4 -[FFAnchoredObject _assetRefs:includeAnchored:activeOnly:] + 68
    22  com.apple.Flexo                         0x0000000100a2b3f8 -[FFAnchoredObject _assetRefs:includeAnchored:activeOnly:] + 856
    23  com.apple.Flexo                         0x0000000100a2b2bf -[FFAnchoredObject _assetRefs:includeAnchored:activeOnly:] + 543
    24  com.apple.Flexo                         0x0000000100a27c91 -[FFAnchoredObject assetRefsIncludingAnchored:activeOnly:] + 81
    25  com.apple.Flexo                         0x0000000100c11d7c -[FFSequenceProject assetReferences] + 156
    26  com.apple.Flexo                         0x00000001007f366c -[FFProject mediaReferences] + 76
    27  com.apple.Flexo                         0x00000001007f5efb -[FFProject _updateOfflineReasonsForQuality:] + 267
    28  com.apple.Flexo                         0x00000001007f756f -[FFProject mediaAvailable] + 127
    29  com.apple.Flexo                         0x0000000100c8e909 -[FFProjectOrganizerModule updateCell:forNode:] + 441
    30  com.apple.Flexo                         0x0000000100c8b7ea -[FFProjectOrganizerModule _assetsChangedNotification:] + 506
    31  com.apple.CoreFoundation                0x00007fff8ad7575d -[NSObject performSelector:withObject:] + 61
    32  com.apple.Flexo                         0x00000001006fc8cf Observers::Notify((anonymous namespace)::Notification const&) + 303
    33  com.apple.Flexo                         0x00000001006fd427 +[FFNotificationCenter postNotification:] + 199
    34  com.apple.Flexo                         0x00000001006fb703 +[FFNotificationCenter postNotificationName:object:userInfo:] + 67
    35  com.apple.Flexo                         0x00000001007f3260 -[FFProject _deferredAssetChangedNotification] + 96
    36  com.apple.Foundation                    0x00007fff82630d88 __NSFirePerformWithOrder + 382
    37  com.apple.CoreFoundation                0x00007fff8ad45bd7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
    38  com.apple.CoreFoundation                0x00007fff8ad45b36 __CFRunLoopDoObservers + 374
    39  com.apple.CoreFoundation                0x00007fff8ad1ace9 __CFRunLoopRun + 825
    40  com.apple.CoreFoundation                0x00007fff8ad1a676 CFRunLoopRunSpecific + 230
    41  com.apple.HIToolbox                     0x00007fff883d031f RunCurrentEventLoopInMode + 277
    42  com.apple.HIToolbox                     0x00007fff883d75c9 ReceiveNextEventCommon + 355
    43  com.apple.HIToolbox                     0x00007fff883d7456 BlockUntilNextEventMatchingListInMode + 62
    44  com.apple.AppKit                        0x00007fff86979f5d _DPSNextEvent + 659
    45  com.apple.AppKit                        0x00007fff86979861 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
    46  com.apple.AppKit                        0x00007fff8697619d -[NSApplication run] + 470
    47  com.apple.prokit                        0x000000010030b3a6 NSProApplicationMain + 387
    48  com.apple.FinalCut                      0x0000000100001568 start + 52
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib                  0x00007fff8a673e06 __select_nocancel + 10
    1   libdispatch.dylib                       0x00007fff8655931e _dispatch_mgr_invoke + 251
    2   libdispatch.dylib                       0x00007fff8655814e _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c274 _pthread_cond_wait + 840
    2   com.apple.progl.framework               0x0000000101b04029 (anonymous namespace)::threadFunc(void*) + 61
    3   com.apple.procore.framework             0x0000000100165cf0 PCThread::startup(void*) + 18
    4   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    5   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 3:: com.apple.flexo.throttled-scheduled-io
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c274 _pthread_cond_wait + 840
    2   com.apple.Flexo                         0x000000010088c808 Synchronizable::Wait() + 56
    3   com.apple.Fig.provider                  0x000000010812e2d8 0x108100000 + 189144
    4   com.apple.Flexo                         0x000000010089560a Thread::RunHelper(void*) + 42
    5   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    6   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 6:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 7:: CVDisplayLink
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c2a6 _pthread_cond_wait + 890
    2   com.apple.CoreVideo                     0x00007fff8678c63f CVDisplayLink::waitUntil(unsigned long long) + 279
    3   com.apple.CoreVideo                     0x00007fff8678baa5 CVDisplayLink::runIOThread() + 559
    4   com.apple.CoreVideo                     0x00007fff8678b85d _ZL13startIOThreadPv + 148
    5   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    6   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 8:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 9:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 10:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 11:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 12:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 13:: CVDisplayLink
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c2a6 _pthread_cond_wait + 890
    2   com.apple.CoreVideo                     0x00007fff8678c63f CVDisplayLink::waitUntil(unsigned long long) + 279
    3   com.apple.CoreVideo                     0x00007fff8678baa5 CVDisplayLink::runIOThread() + 559
    4   com.apple.CoreVideo                     0x00007fff8678b85d _ZL13startIOThreadPv + 148
    5   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    6   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 14 Crashed:: BGTask: MEBackgroundLoadManager  Dispatch queue: com.apple.root.default-priority
    0   libsystem_kernel.dylib                  0x00007fff8a673ce2 __pthread_kill + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a7d2 pthread_kill + 95
    2   libsystem_c.dylib                       0x00007fff8ca8ba7a abort + 143
    3   com.apple.Flexo                         0x00000001008df807 FFApplicationHandleExceptionThatShouldNotBeIgnored + 407
    4   com.apple.Flexo                         0x000000010084c204 -[FFBackgroundTask main] + 884
    5   com.apple.Foundation                    0x00007fff825f86d8 -[__NSOperationInternal start] + 705
    6   com.apple.Foundation                    0x00007fff8260b936 ____NSOQSchedule_block_invoke_2 + 124
    7   libdispatch.dylib                       0x00007fff865578ba _dispatch_call_block_and_release + 18
    8   libdispatch.dylib                       0x00007fff86558799 _dispatch_worker_thread2 + 255
    9   libsystem_c.dylib                       0x00007fff8ca9a3da _pthread_wqthread + 316
    10  libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 15:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 16:: com.apple.helium-unit
    0   libsystem_kernel.dylib                  0x00007fff8a673bf2 __psynch_mutexwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca971a1 pthread_mutex_lock + 545
    2   com.apple.Helium.HeliumRender           0x0000000102e6bd82 hg_pthread_loop(void*) + 98
    3   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    4   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 17:: com.apple.helium-unit
    0   libsystem_kernel.dylib                  0x00007fff8a673bf2 __psynch_mutexwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca971a1 pthread_mutex_lock + 545
    2   com.apple.Helium.HeliumRender           0x0000000102e6bd82 hg_pthread_loop(void*) + 98
    3   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    4   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 18:: com.apple.helium-unit
    0   libsystem_kernel.dylib                  0x00007fff8a673bf2 __psynch_mutexwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca971a1 pthread_mutex_lock + 545
    2   com.apple.Helium.HeliumRender           0x0000000102e6bd82 hg_pthread_loop(void*) + 98
    3   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    4   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 19:: com.apple.helium-unit
    0   libsystem_kernel.dylib                  0x00007fff8a673bf2 __psynch_mutexwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca971a1 pthread_mutex_lock + 545
    2   com.apple.Helium.HeliumRender           0x0000000102e6bd82 hg_pthread_loop(void*) + 98
    3   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    4   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 20:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 21:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 22:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 23:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 24:: MIO Mounting Thread
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c2a6 _pthread_cond_wait + 890
    2   com.apple.Foundation                    0x00007fff82639a80 -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation                    0x00007fff82603252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proapps.MIO                   0x0000000101777cdc -[PluginLockPair scanPaths] + 284
    5   com.apple.Foundation                    0x00007fff8260a74e -[NSThread main] + 68
    6   com.apple.Foundation                    0x00007fff8260a6c6 __NSThread__main__ + 1575
    7   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    8   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 25:: MIO Mounting Thread
    0   libsystem_kernel.dylib                  0x00007fff8a6726b6 semaphore_wait_trap + 10
    1   com.apple.AVCHDPlugin                   0x0000000127126d67 semaphore_wait(viona_semaphore_t*) + 55
    2   com.apple.AVCHDPlugin                   0x00000001271352a8 WinPort::DoMessage(long, long) + 264
    3   com.apple.AVCHDPlugin                   0x00000001270bd201 DDP_OpenPlayerWithPath + 1265
    4   com.apple.AVCHDPlugin                   0x0000000127141149 FDVDProcessor::FCDVDManager::OpenPlayer(unsigned char, unsigned char) + 1113
    5   com.apple.AVCHDPlugin                   0x0000000127144519 FDVDProcessor::FCDVDManager::OpenAVCHDMediaFile(FSRef&) + 1529
    6   com.apple.AVCHDPlugin                   0x00000001270d4944 FAVCHDOpenMediaFile + 52
    7   com.apple.AVCHDPlugin                   0x0000000127049de5 0x127047000 + 11749
    8   com.apple.AVCHDPlugin                   0x00000001270497bb 0x127047000 + 10171
    9   com.apple.AVCHDPlugin                   0x0000000127049322 0x127047000 + 8994
    10  com.apple.proapps.MIO                   0x000000010177730e -[PluginLockPair mountPath:] + 286
    11  com.apple.proapps.MIO                   0x0000000101777d0c -[PluginLockPair scanPaths] + 332
    12  com.apple.Foundation                    0x00007fff8260a74e -[NSThread main] + 68
    13  com.apple.Foundation                    0x00007fff8260a6c6 __NSThread__main__ + 1575
    14  libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    15  libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 26:: MIO Mounting Thread
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c2a6 _pthread_cond_wait + 890
    2   com.apple.Foundation                    0x00007fff82639a80 -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation                    0x00007fff82603252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proapps.MIO                   0x0000000101777cdc -[PluginLockPair scanPaths] + 284
    5   com.apple.Foundation                    0x00007fff8260a74e -[NSThread main] + 68
    6   com.apple.Foundation                    0x00007fff8260a6c6 __NSThread__main__ + 1575
    7   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    8   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 27:: MIO Mounting Thread
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c2a6 _pthread_cond_wait + 890
    2   com.apple.Foundation                    0x00007fff82639a80 -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation                    0x00007fff82603252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proapps.MIO                   0x0000000101777cdc -[PluginLockPair scanPaths] + 284
    5   com.apple.Foundation                    0x00007fff8260a74e -[NSThread main] + 68
    6   com.apple.Foundation                    0x00007fff8260a6c6 __NSThread__main__ + 1575
    7   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    8   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 28:: MIO Mounting Thread
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c2a6 _pthread_cond_wait + 890
    2   com.apple.Foundation                    0x00007fff82639a80 -[NSCondition waitUntilDate:] + 371
    3   com.apple.Foundation                    0x00007fff82603252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
    4   com.apple.proapps.MIO                   0x0000000101777cdc -[PluginLockPair scanPaths] + 284
    5   com.apple.Foundation                    0x00007fff8260a74e -[NSThread main] + 68
    6   com.apple.Foundation                    0x00007fff8260a6c6 __NSThread__main__ + 1575
    7   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    8   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 29:: com.apple.dvdplayback-DDPTask
    0   libsystem_kernel.dylib                  0x00007fff8a673d52 __read_nocancel + 10
    1   libsystem_c.dylib                       0x00007fff8ca94c25 _sread + 19
    2   libsystem_c.dylib                       0x00007fff8ca95166 __srefill1 + 30
    3   libsystem_c.dylib                       0x00007fff8ca95a2e _fseeko + 769
    4   libsystem_c.dylib                       0x00007fff8ca95acb fseeko + 79
    5   com.apple.AVCHDPlugin                   0x00000001271ecea4 CClipInformationFile::GetStreamData(unsigned char*&, unsigned long&, unsigned char, unsigned short, unsigned int, unsigned int) + 308
    6   com.apple.AVCHDPlugin                   0x00000001271fb20b CClipInformationFile::CreateStreamMetaData(CCFDictionary&, unsigned char, unsigned short, unsigned int, unsigned int) + 107
    7   com.apple.AVCHDPlugin                   0x00000001271acb7b CPlaybackControlEngine::GenerateClipObjects() + 10171
    8   com.apple.AVCHDPlugin                   0x000000012717c95f BDMVDiskPlayerFactory::CreateDiskPlayer(WinPortServer*, VDR*, GenericProfile*, DVDDiskType, BDMVFileSystem*, unsigned char, CDDiskPlayerClass*&) + 127
    9   com.apple.AVCHDPlugin                   0x00000001270ba149 DDPScheduler::Message(long, long) + 3881
    10  com.apple.AVCHDPlugin                   0x0000000127134422 WinPortServer::ProcessMessages() + 1042
    11  com.apple.AVCHDPlugin                   0x00000001270b8753 DDP_Init + 723
    12  com.apple.AVCHDPlugin                   0x0000000127126570 ST20Thread::Run(PThreadRunParams*) + 32
    13  libsystem_c.dylib                       0x00007fff8ca9a768 _pthread_body + 59
    Thread 30:
    0   libsystem_kernel.dylib                  0x00007fff8a67267a mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff8a671d71 mach_msg + 73
    2   com.apple.CoreFoundation                0x00007fff8ad126fc __CFRunLoopServiceMachPort + 188
    3   com.apple.CoreFoundation                0x00007fff8ad1ae64 __CFRunLoopRun + 1204
    4   com.apple.CoreFoundation                0x00007fff8ad1a676 CFRunLoopRunSpecific + 230
    5   com.apple.CoreFoundation                0x00007fff8ad2a38f CFRunLoopRun + 95
    6   com.apple.qmaster.do                    0x000000011f0a6461 swamp::CRAdReceiver2::ReceivingThread::runOnce() + 187
    7   com.apple.AECore                        0x00000001084cb49f aecore::CThread::runThread() + 35
    8   com.apple.AECore                        0x00000001084c9470 threadProc(void*) + 9
    9   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    10  libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 31:
    0   libsystem_kernel.dylib                  0x00007fff8a6726b6 semaphore_wait_trap + 10
    1   com.apple.AVCHDPlugin                   0x0000000127126d67 semaphore_wait(viona_semaphore_t*) + 55
    2   com.apple.AVCHDPlugin                   0x0000000127134a10 WinPortServer::FlushMessages(WinPort*, unsigned int, int) + 1344
    3   com.apple.AVCHDPlugin                   0x0000000127126570 ST20Thread::Run(PThreadRunParams*) + 32
    4   libsystem_c.dylib                       0x00007fff8ca9a768 _pthread_body + 59
    Thread 32:
    0   libsystem_kernel.dylib                  0x00007fff8a6726b6 semaphore_wait_trap + 10
    1   com.apple.AVCHDPlugin                   0x0000000127126d67 semaphore_wait(viona_semaphore_t*) + 55
    2   com.apple.AVCHDPlugin                   0x0000000127134a10 WinPortServer::FlushMessages(WinPort*, unsigned int, int) + 1344
    3   com.apple.AVCHDPlugin                   0x0000000127126570 ST20Thread::Run(PThreadRunParams*) + 32
    4   libsystem_c.dylib                       0x00007fff8ca9a768 _pthread_body + 59
    Thread 33:: com.apple.dvdplayback-CPresentationEngine
    0   libsystem_kernel.dylib                  0x00007fff8a6726b6 semaphore_wait_trap + 10
    1   com.apple.AVCHDPlugin                   0x0000000127126d67 semaphore_wait(viona_semaphore_t*) + 55
    2   com.apple.AVCHDPlugin                   0x0000000127134a10 WinPortServer::FlushMessages(WinPort*, unsigned int, int) + 1344
    3   com.apple.AVCHDPlugin                   0x0000000127126570 ST20Thread::Run(PThreadRunParams*) + 32
    4   libsystem_c.dylib                       0x00007fff8ca9a768 _pthread_body + 59
    Thread 34:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 35:
    0   libsystem_kernel.dylib                  0x00007fff8a674192 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff8ca9a594 _pthread_wqthread + 758
    2   libsystem_c.dylib                       0x00007fff8ca9bb85 start_wqthread + 13
    Thread 36:: com.apple.helium-texture-finish
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c274 _pthread_cond_wait + 840
    2   com.apple.Helium.HeliumRender           0x0000000102e51c27 textureFinishThread(void*) + 183
    3   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    4   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 37:: com.apple.coremedia.scheduledfileio
    0   libsystem_kernel.dylib                  0x00007fff8a673bca __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x00007fff8ca9c274 _pthread_cond_wait + 840
    2   com.apple.CoreMedia.ProAppsSupport          0x000000010029fc3d WaitOnCondition + 14
    3   com.apple.CoreMedia.ProAppsSupport          0x000000010029fe09 FigSemaphoreWaitRelative + 167
    4   com.apple.CoreMedia.ProAppsSupport          0x000000010029df16 FigScheduledFileIOThread + 5109
    5   com.apple.CoreMedia.ProAppsSupport          0x00000001002a0d16 figThreadMain + 397
    6   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    7   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 38:
    0   libsystem_kernel.dylib                  0x00007fff8a673df2 __select + 10
    1   com.apple.AECore                        0x00000001084cb4cc aecore::CThread::runThread() + 80
    2   com.apple.AECore                        0x00000001084c9470 threadProc(void*) + 9
    3   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    4   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 39:: com.apple.CFSocket.private
    0   libsystem_kernel.dylib                  0x00007fff8a673df2 __select + 10
    1   com.apple.CoreFoundation                0x00007fff8ad63cdb __CFSocketManager + 1355
    2   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    3   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 40:: com.apple.appkit-heartbeat
    0   libsystem_kernel.dylib                  0x00007fff8a673e42 __semwait_signal + 10
    1   libsystem_c.dylib                       0x00007fff8ca4edea nanosleep + 164
    2   libsystem_c.dylib                       0x00007fff8ca4ebb5 usleep + 53
    3   com.apple.AppKit                        0x00007fff86bb0c73 -[NSUIHeartBeat _heartBeatThread:] + 1727
    4   com.apple.Foundation                    0x00007fff8260a74e -[NSThread main] + 68
    5   com.apple.Foundation                    0x00007fff8260a6c6 __NSThread__main__ + 1575
    6   libsystem_c.dylib                       0x00007fff8ca988bf _pthread_start + 335
    7   libsystem_c.dylib                       0x00007fff8ca9bb75 thread_start + 13
    Thread 14 crashed with X86 Thread State (64-bit):
      rax: 0x0000000000000000  rbx: 0x0000000000000006  rcx: 0x0000000122274b48  rdx: 0x0000000000000000
      rdi: 0x000000000000e607  rsi: 0x0000000000000006  rbp: 0x0000000122274b70  rsp: 0x0000000122274b48
       r8: 0x00007fff73ac2fb8   r9: 0x0000000000000000  r10: 0x00007fff8a673d0a  r11: 0xffffff80002d8220
      r12: 0x00000001012e5688  r13: 0x000000013c10e328  r14: 0x0000000122275000  r15: 0x000000012f5fc020
      rip: 0x00007fff8a673ce2  rfl: 0x0000000000000206  cr2: 0x0000000105a08000
    Logical CPU: 0

    The reason it is pointless to submit the crash log here is because nowhere does it tell you which clip, which title/event/generator/transition, or any other named portion of your project FCPX died in. It is literally no help whatsoever to you, only to Apple engineers trying to debug the software. When it crashes, fill out what you were doing when it crashed 'cause even *they* need a hint!  All we can discern is that FCPX crashed on Thread 14 on BGTask: MEBackgroundLoadManager and right before that was a call for a dynamically linked library. That could be anything... but my guess would be an "effect" (possibly with a corrupt font.) If you knew which effect you were "playing with" when FCPX crashed (or even if you simply moused over one), you could go in and remove it temporarily; restart FCPX and (if you get that far) delete the "red-screen alert" item from the project. If there was a corrupt font involved -- get rid of it! (You can analyze fonts in Font Book) and afterwards, you can re-add whatever effect was removed. [For clips, you can take them "offline" temporarily by moving them out of the event folder... I don't recommend this course of action, I don't believe the "base video" would ever be an issue if it were transcoded on or before import... only trying to use H.264 "raw" would be something that might "choke" FCPX.]
    In my experience, the things that bring down FCPX: corrupt fonts used for any text (FCPX will die immediately even if you pass over them with the mouse on your way to selecting something else - you might not even know which font that was either); Motion effects I'm developing that push the envelope a little too far (but that would be just for me I try to make sure they're stable before releasing them to the public -- but this implies other 3rd party effects that might not be so stringently checked out); and not much else. [Other possibilities I usually place "outside of FCPX" - such as launching other memory hungry apps while FCPX is open... etc. Poor(er) memory management in other apps might overwrite RAM buffered data and cause a "fault"...]
    If you *know* what exactly offended FCPX, there are (usually) steps you can take to remove the offending "software" and upon reopening FCPX, FCPX will make necessary substitutions (defaulting fonts, putting up the "red alert" screen, etc...)
    **OR** much easier: use Andy's tip about getting to the last backup. (Tip: if you do have corrupt fonts, using backups all the time isn't really going to help you that much.)
    [You would think that after over 20 years of dealing with bitmapped, PostScript and Truetype fonts Apple would have developed a way of "intercepting" problems that arise... but NOOOOOOOO! We are *still* at the mercy of corrupted fonts. PS - Ditto for Motion!   (ok, i'll be gettin' down from my soapbox now...)]

  • Is there a way to loop my FCPX project?

    I am working on a project and I want to make this project loop.  Is there a way to loop the entire movie in FCPX so that it will do this on it's own? 
    Also is there a way to make it play automatically when put into a machine?
    I don't know what software everyone else is using these days but I used to use/LOVE IDVD Studio but it doesn't seem to be available in the Apple Store anymore.  Does anyone have a good recommendation for me to burn DVDs?  IDVD was so easy and fun to use.  Any help would be appreciated.

    Looping is a playback-feature - FCPX is an editor …
    cmd-alt-L in QTplayer = looping
    most 'players' (VLC, iTunes, … ) offer a loop playback.
    iDVD was part of iLife and runs on MacOS10.8. too (here it does)
    Use any older Installer disk (iLife or original 'grey' ones of older Macs) to custom-install iDVD only
    if no disk avail: purchase a BOXED version of iLife …
    to auto-loop a movie in iDVD, just drag the movie into the auto-start box, shown in the 'structure' view of iDVD.
    there are tons of 'DVD-makers' avail at AppStore - no first hand experience here with any, I once a year have to burn disks => iDVD ...

  • FCPX Project won't open

    Hi,
    I recently updated my fcpx after doing this one of my projects won't open. In the route project file an additional current version file has been produced it reads as follows - CurrentVersion.fcpproject-journal - Now. When I delete it FCP will open and try to read the project file but it then just wont open fcp at all it just stays on the screen saying reading project.
    Can anyone help?
    Tom

    Interesting…2 of everything.
    Close FCP. In the Finder, go your project folder and open it. Take the "normal-looking" back-up and move it one level up in the folder hierarchy, so it's at the same level as the CurrentVersion file – like so.
    If there is another oback-up (assuming there are two as in the event) take it and the the two CurrentVersion.fcp files and hide them – as Ian recommended – in a temp folder.
    Take a screen shot of your back up file in case you need to change the name back later. Change the name of the moved back up file to CurrentVersion.fcpproject.
    Open FCP and try to open the project.
    Russ

  • Is it possible to export part of the FCPX Project from timeline

    Is it possible to export a selection from the FCPX timeline or do I have to export the entire project and then edit it in another program.

    andynick wrote:
    Goldfish wrote:
    FCP7 was much better for this:
    Yes - but you don't mention the billion ways in which FCP X makes FCP 7 totally obsolete.
    Andy
    I didn't think it was relevant to the thread.
    I'm simply encouraging the return of a few features that were left on the cutting room floor - no harm in that.
    I O markers and chapter markers are a few of them and routinely a topic of discussion. It's not just me.
    For the record I'm a big Fan of FCPX. It has many of the features that I said, for years,  should be added to FCP7 -  and I took a lot of heat over the years for pointing out the deficiencies in FCP7.
    When a new editor comes to the forum and asks "why can't i do this really simple thing" , I think it's better to acknowledge his observation and encourage constructive feedback to Apple rather than implying that he was stupid for knot figuring out a convoluted work-around for something that should exist in the program.
    If your post had started with "here's a work around…." rather than " takes seconds…"
    and you had finished with "…hopefully we'll see I O markers in a future update…"
    Rather than "…Ctrl+Zs to get back to previous state." you never would have heard a peep from me.
    I just find the apologist mentality difficult to ignore. No offense intended.
    best regards,
    g
    PS - I also think "totally obsolete" is a bit of a stretch.

Maybe you are looking for