15" MBP with Vega 20 and 32GB Ram, poor video editing performance normal?

[giffut]

KERN_INVALID_ADDRESS errors can happen when files in the "/private/var/folders/" directory become corrupted. This is used for various cache properties of active running software.

Restart your macbook fresh and don´t run any software on it, then launch the terminal app and type the following command:

sudo rm -rf /private/var/folders/*

Enter your password, then restart again and redo your workload with Final Cut and check its behaviour.

 

[PowerMike G5]

Yes it's not normal. There is either a configuration problem, project problem or app problem. The hardware isn't going to struggle with that.
[doublepost=1557210612][/doublepost]

Very important to note the above. Some codecs aren't supposed to be used for editing and should be used for output. With this knowledge in mind the source material should be converted to a better codec in order to optimize the workflow.

For context, 6K RED RAW footage is captured at max 220MB/s.

This is exactly right. Just because computer technology doesn't stay still doesn't mean video codecs will.

I've been a producer and shooter/editor for almost 20 years now, so I've lived through editing so many different formats. Understanding codecs is so important to smooth workflows.

Even with maxed out machines, I still find the proxy workflow best... especially since it's been made so easy to implement these days with certain software.

 

[SoyCapitanSoyCapitan]

This is exactly right. Just because computer technology doesn't stay still doesn't mean video codecs will.

I've been a producer and shooter/editor for almost 20 years now, so I've lived through editing so many different formats. Understanding codecs is so important to smooth workflows.

Even with maxed out machines, I still find the proxy workflow best... especially since it's been made so easy to implement these days with certain software.

Yeah man. Editing with a proxy is the tried and proven method to optimize speed. Old school, goes back to the days of TARGA sequences when computers were too slow to play videos. Still works to this day, even with the changes to formats.

 

[giffut]

By the way: The G5H codec does not have a 400MB/s (Megabyte) bitrate, but a 400Mb/s (Megabit) bitrate - big difference.

All problems the OP experiences seem to be related to some mac os/final cut software error/misbehaving.

You may also try to post your problem here in this final cut user forum:

http://www.fcp.co/forum/4-final-cut-pro-x-fcpx

 

[BornAgainMac]

The problem with the more expensive builds of the MBP 15 is that it sucks at everything. You get average portability, average performance, high price, limited life, loud fans / hot. A portable laptop + Desktop is the way to go.

 

[pshufd]

The problem with the more expensive builds of the MBP 15 is that it sucks at everything. You get average portability, average performance, high price, limited life, loud fans / hot. A portable laptop + Desktop is the way to go.

I had a look at some used Mac Pros in my area. Maybe a project for the future. I hope Apple updates the Mac Pro this year or comes out with something in-between the Mini and the Pro that doesn't have an integrated screen. At the moment, though, the 2014 MacBook Pro is a champ hooked up to a 4K monitor.

 

[Flabasha]

By the way: The G5H codec does not have a 400MB/s (Megabyte) bitrate, but a 400Mb/s (Megabit) bitrate - big difference.

All problems the OP experiences seem to be related to some mac os/final cut software error/misbehaving.

You may also try to post your problem here in this final cut user forum:

http://www.fcp.co/forum/4-final-cut-pro-x-fcpx

Yes, I shouldn't have capitalized the "B", but the point remains exactly the same. Editing 400Mb/s h.264/5 is a nightmare for any laptop.

And GPU has next to nothing to do with it, as h.264/5 is mostly dependent on the processor. The OP can download "Intel Power Gadget" for free, open that up, and also open the GPU monitor in Activity Monitor, then play that file, and watch the processor redline, then throttle down for heat, as the video stutters. The GPU will only be running at 40% during all of it. When you edit ProRes, the exact opposite happens... your GPU is leveraged 100%, your CPU runs smooth and easy.

Don't edit 4K h.264/5 files if you can possibly avoid it.

Better yet, try not to shoot on that codec. It breaks so easily doing any color grading. The ONLY advantage to it is file size, and storage is dirt cheap.
[doublepost=1557248111][/doublepost]

A portable laptop + Desktop is the way to go.

Yep, or even just add an eGPU for $500 and watch your editing performance skyrocket.

 

[LeoH21]

THANK YOU ALL SO MUCH !!

Been such great help. The 4k we shot on a c300 mark ii using Apple pro res (Atomos) works fine, even when adding SFX.
I never realised the codec would play such a big part. I thought about building a thread ripper Desktop, but then didn't want to do that only to have the same problem.

Last night I was close to calling it quits with the MBP. I was encoding a bunch of GH5 files on FCPx and the MBP slowed down so much I couldn't even use safari at the same time.
[doublepost=1557264335][/doublepost]

As a veteran editor for network TV, and a (former) owner of your exact setup, I will tell you exactly what is happening.

No, your machine is not strong enough.

Reason? You are editing 400MBP/s h.265 files. All the other people here are editing lower bitrate 4K. Here's the problem... h.264/5 is a CAPTURE codec, but a TERRIBLE editing codec. And when you maximize the bitrate to 400 MB/s, it will bring almost any computer to its knees.

I know, I bought your exact model of MBP, to edit 400 MB/s GH5 files just like you, and had the same cold realization. I ended up selling my GH5, and buying a Blackmagic, which shoots to ProRes, which is cake to edit with.

So, what do you do? Here are your options.

1. Shoot a lower bitrate. Or...
2. Transcode to ProRes, then edit. Or...
3. Buy an Atomos Ninja, or similar, and shoot your GH5 files to ProRes natively.

When Apple talks about being able to edit 6K and 8K RED files natively, they're not lying... because RED doesn't shoot in h.264/5. RED shoots to ProRes, or REDCODE, both of which are vastly superior codecs to edit with.

So, the good news is, your computer is fine. The bad news is, no, you can't do that on it.

Its a good thing I have 2 Blackmagic pocket 4ks on order

 

[PowerMike G5]

THANK YOU ALL SO MUCH !!

Been such great help. The 4k we shot on a c300 mark ii using Apple pro res (Atomos) works fine, even when adding SFX.
I never realised the codec would play such a big part. I thought about building a thread ripper Desktop, but then didn't want to do that only to have the same problem.

Last night I was close to calling it quits with the MBP. I was encoding a bunch of GH5 files on FCPx and the MBP slowed down so much I couldn't even use safari at the same time.
[doublepost=1557264335][/doublepost]
Its a good thing I have 2 Blackmagic pocket 4ks on order

Yeah what codec you edit in will really define the smoothness of your editing experience. There's a reason why Apple ProRes is so popular in the industry... it's ultra high quality I-frame qualities retain maximum image quality while providing low CPU-usage (at the cost of high bit-rates). Inter-frame codecs are popular on cameras for acquisition as they compress a lot into small file sizes, but they are simply not the most ideal for post-production.

Proxy-workflows are really great if you can utilize them. Even cameras like the C300 MII do simultaneous proxy records to the SD card so you don't even have to generate them in post. You just link them to the source media and your ready to go... practically the same as editing with native media at that point!

 

[ashcairo]

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]
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äˇ

Hey mate, glad it's working faster now. To get that title to run fast you'll need to render it out. You can either do that by enabling background rendering and it'll auto-do it for you in the background when you're not editing. Or you can select the clip and hit control+r, or in the menu select render. You can see the parts which are not rendered out at the top of the timeline you'll see dots. Titles tend to be too heavy to playback without rendering out, even an iMac Pro struggles with that one. Something you can do to speed it up however is to switch to better performance, however that can make the footage look blurry while editing.