Exactly. No matter what kind of laptop, even desktop, an editor uses there comes a point when a project can be so heavy or the workflow not configured optimally that the app and the computer will struggle.
I understand this... but a 7 minute clip containing footage from an iPhone 7 and sony a6300... surely that's not normal.
[doublepost=1557179230][/doublepost]
Hey mate,
First Screenshot - It says in the first screenshot that it's busy transcoding the clips. I assume you're working on a multicam clip, and in the options you've got 'create optimised media for multicam clips' selected. What you can do is either wait for it to transcode your clips, or cancel the transcode operation and disable that checkbox. If you try playing with FCPX while it's doing a heavy operation like transcoding, it gets pretty cluggy. You can try to switch to Better Performance to see if that helps, but I usually avoid transcodes while editing.
Second Screenshot - I can see FCPX is not responding and no apps are hogging the show. You said it slows down after using a present, which one are you using? Second note, BetterTouchTool is a cool app and it most probably is not a problem at all and they might have fixed these issues since I last tested it out, but last time I tried it, it was a little cluggy to use and randomly hogged system resources.
Can you throw me a screenshot of the Memory tab?
Thank you for the help. I turned off transcoding and it's much better.
The preset...sorry I meant installed titles is called slash ink- splats.
I called apple care today and the guy tried blaming the media, the external hard drive (Samsung X5 and Samsung T5, I also pointed out it happens when the videos ar eon the hard drive) , he finally got me to run a diagnostic that take 90 minutes, he said the data gets sent back to him and he will contact me tomorrow. I will update here.
Also, I noticed final cut is making crash reports on my desktop in a file it created called videoAppDiagnostics. I have copy and pasted the first part of it below. Not sure if it is helpful. It goes on for pages, but just putting the begging part below:
REPORT ONE:
Process: Final Cut Pro [1737]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCut
Version: 10.4.6 (342230)
Build Info: ProEditor-34223000026000000~1
App Item ID: 424389933
App External ID: 830604740
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Final Cut Pro [1737]
User ID: 501
Date/Time: 2019-04-18 00:05:54.437 +0100
OS Version: Mac OS X 10.14.4 (18E226)
Report Version: 12
Bridge OS Version: 3.4 (16P4507)
Anonymous UUID: E1DD1DE9-145C-877E-F06F-8ABF84E734E9
Sleep/Wake UUID: 3A8703F3-76CD-425A-88C2-F3C7CB18A719
Time Awake Since Boot: 67000 seconds
Time Since Wake: 3700 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000007f91b77f900
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1737]
VM Regions Near 0x7f91b77f900:
mapped file 00000001a8ab9000-00000001a910b000 [ 6472K] r--/rwx SM=COW Object_id=268f72eb
-->
MALLOC_NANO 0000600000000000-0000600010000000 [256.0M] rw-/rwx SM=PRV
Application Specific Information:
objc_msgSend() selector name: respondsToSelector:
x1¬ãˇ
REPORT TWO:
Process: Final Cut Pro [2654]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCut
Version: 10.4.6 (342230)
Build Info: ProEditor-34223000026000000~1
App Item ID: 424389933
App External ID: 830604740
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Final Cut Pro [2654]
User ID: 501
Date/Time: 2019-04-20 00:28:11.607 +0100
OS Version: Mac OS X 10.14.4 (18E226)
Report Version: 12
Bridge OS Version: 3.4 (16P4507)
Anonymous UUID: E1DD1DE9-145C-877E-F06F-8ABF84E734E9
Sleep/Wake UUID: 8A11CAAF-EC4C-451D-9B84-68A85AFB3F35
Time Awake Since Boot: 28000 seconds
Time Since Wake: 830 seconds
System Integrity Protection: enabled
Crashed Thread: 6 BGTask: FFRenderStateTracker Dispatch queue: NSOperationQueue 0x6000116b00a0 (QOS: UNSPECIFIED)
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000723fbc614478
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [2654]
VM Regions Near 0x723fbc614478:
Stack 000070000325e000-00007000032e0000 [ 520K] rw-/rwx SM=COW thread 63
-->
MALLOC_TINY 00007fc714c00000-00007fc715000000 [ 4096K] rw-/rwx SM=PRV
Application Specific Information:
objc_msgSend() selector name: squareFrameBounds
xAKäˇ
![]()