Participating Frequently

Question

Errors with R3D files in M1 MacBook Pro

Forum|Forum|4 years ago
February 2, 2022
7 replies
8287 views

Hi,

I edited the trailer for a documentary project on my old Intel iMac on Mojave this past August with no issue. The majority of the footage in the project is R3D files. I recently started editing the full-length film (same footage) with a new MacBook Pro with M1 Max, Mac OS 12.2, and Premiere 22.1.2, and I'm now getting a number of issues.

-Most importantly, I'm getting corrupted frames (see below) on export, and sometimes when just opening a sequence or pausing in the timeline.

-When loading Multicam clips in the source monitor, I see the two correct camera angles displayed while paused, but as soon as I hit play, it displays the B Cam (second video track) twice.

This is of course really troubling as I start a long-form edit, and hoping there's a fix on the way asap. A couple of notes/attempts I've made to fix it:

-This so far is only affecting the R3D files in the project, all archive plays/exports normally.

-I edited another project on this same setup that was shot on Blackmagic cameras (.braw files) without issue.

-I've created ProRes proxies of all R3D files, and I'm now using those for playback and during export (unfortunately). This seems to have improved, but not entirely solved, the issue.

-I had some success rendering using Software Only, though once had to create a new sequence, copy/paste from the original, THEN export using Software Only to fix it.

This is being edited in a large Premiere Production, and I'm dreading the prospect of having to dust off my 2015 iMac and XML all of my sequences back into an old version of Premiere to finish this project. Any help greatly appreciated!

This topic has been closed for replies.

FILIP BOBAN

Participant

RED RAW AND PREMIERE DESTROYED MY MACBOOK PRO M1 MAX CHIP

Hey Nicktheclark,

I have some news to share about that issue. I have been working with R3D Raw when I got my new MacBook Pro with the M1 Max Chip back in 2021.

I have done a lot of work with it using BlackMagic Raw and big projects using LrC, Photoshop, Illustrator, and a bunch of other Creative Cloud apps with my MacBook Pro. Everything was fine; the M1 Max chip was incredible and had zero issues until I started working with R3D Raw files since I bought myself a KOMODO.

I worked with 6k ELQ files, and after the first project in Premiere, I started having the same issues. At first, I thought there were some kinds of bugs. I started searching the web just like you. I didn't find any solution, so I just kept on restarting Premiere because it fixed the problem until it didn't. After that, I had issues rendering RED RAW in general. The next thing to happen is that Lightroom started showing the same issues as Premiere when rendering. Files were corrupted, and some just came out fully black. My export didn't work at all! I started panicking because I had a foreshadowing. I started solving the Media Encoder export issues with rendering on software only. I fixed my Premiere preview issues by running Premiere fully on software, which means I had to run it on Rosetta 1 back then. I fixed the Lightroom export issues by changing it also to export using software only. Those were the only working fixes that I had, but it wasn't a fix; it was a really annoying and very, very slow solution to a problem that shouldn't be existing. Shortly after, they announced that they would remove Rosetta, and that's when I had no chance of working with my Mac because clearly, the full capacity of my chip wasn't there anymore. So I visited a bunch of Apple stores when finally one guy had the necessary knowledge to help me out. We ran a bunch of tests for 6 hours, and he came up with just one answer. Premiere in combination with R3D Raw simply destroyed one part of my M1 chip, the "GPU" part. Normally, you could fix the problem by resetting GPU VRAM, but since the new silicon chips don't have VRAM because CPU and GPU is one and the same, there was no workaround. (from what I know, VRAM is a type of memory specifically dedicated to the graphics card or GPU in a computer. VRAM is used to store and quickly access graphical data such as textures, frame buffers, and other visual elements that are essential for rendering images on a display.) Even a full reset didn't work because the problem was a hardware issue that was unreachable without installing a different OS on my Mac because iOS is not possible to fix this problem.

In summary:

- M1 Max Chip was irreparably damaged by R3D RAW and Premiere Pro
- Average Performance of my Mac was throttled down to 30%
- Apple support is not able to fix the problem without exchanging the chip for a new one.

Luckily, I had AppleCare+, and I only had to pay 200€ for a new chip. Since then, I never ever tried working with RED RAW on this Mac again. I have a big PC at home where I do the necessary work, but RED and Apple is no good combo since the new chips came out. Now they released Rosetta 2, and today is the first day where I'll try to work with RED RAW again on this Mac.

Wish me luck! I hope this could help. Cheers

FILIP BOBAN

Participant

Also note that IOS WILL NOT RECOGNIZE NOR SHOW ANY SIGNS OF ERRORS with a failing M1 GPU MEMORY PERFORMANCE since it is not capable to run a diagnosis regarding this issue. It's a sofware/hardware communication issue that is so unique that its not fixable.

N

nicktheclarkAuthor

Participating Frequently

Hi all,

Just wanting to follow up on my original post here (after a few more months of suffering these glitches). I've FINALLY come across what seems to be a solution for me on this particular project: I tried flattening all multiclips and un-nesting prior to export, and that has elimated these output errors.

SO, this seems to be some sort of deep corruption occuring when RED clips on M1 are nested in any way. Glad I can prevent the errors in this case, but still hoping it's not an ongoing issue, b/c completely flattening every sequence before export is obviously unsustainable.

ALSO, I guess just so I don't get too comfortable, the flattened, otherwise glitch-free export I did, did have a few frames of corruption over a plaeholder graphic. Checked out the attached. That background image is not a green solid...

R Neil Haugen

Legend

Check out their Adobe Long-form and Episodic Best Practices Guide which is finally, a decent pro-level look at using PrPro. Including setup, potential gotchas from nested sequences and merged clips, and how to 'turn-over' to other apps.

Yea, there's a number of things that require flattening a sequence prior to export. Especially with AAF/XML/EDL workflows, but for other things too.

Neil

Everyone's mileage always varies ...

N

nicktheclarkAuthor

Participating Frequently

Thanks @R Neil Haugen , this looks like an awesome resource.

Absolutely, I've always flattened and/or replaced multiclips/nests prior to turnovers, especially for AAF/XML/EDL, whether long form or short. Safe to say that it shouldn't be necessary for a run-of-the-mill H.264 export of a rough cut, though. If it was, I'd never multiclip anything.

I'll also say, now that I've discovered this, this isn't the first time that upgrading Premiere has terminally broken multiclips for me, so I know that they can definitely be a serious technical thorn. And unfortuntely, I'm on this project for at least the rest of the year, so I don't want to risk updating again in hopes that it's been solved.

nicklauss47074881

Participant

I am having the same issues! Very frsutrating and not much literature on the problem. This is the only post I could find on the matter...

marcw23771270

Participant

Having the same issue on Macbook pro M1Max Monterrey Premiere 22.1.2. The only fix that I've found outside of Software only render is to edit the project on my M1 and revert back to my imac pro for export and final render. We run on a shared server, so not much time lost there. No issues at all on that machine. The new processor is smoking when it comes to processing the R3D raw files and I haven't had to create proxies which is a huge time saver, but... This is a major issue. So are you guys seeing this as an APPLE issue or Adobe? Just curious where the fix is going to come from and when.

R Neil Haugen

Legend

Hey, that's frustrating. The performance between one new M1 and another within this app is mindboggling. Hoping they get this sorted out.

Neil

Everyone's mileage always varies ...

G

georgeb26063905

Participant

I'm getting the same issues. Komodo R3D footage. Imported as R3D, not proxied and then exporting as H.264 or ProRes. I get crazy glitches like the OP on specific clips in my sequences. Very frustrating, as same project works fine on an iMac Pro 2018.

R Neil Haugen

Legend

Both the LGG (LiftGammaGain) and BlackMagic forums have posts about the same things. And those are Resolve users, so it's clearly something about the M1s at this point in time.

Awesome numbers for M1s in ProRes, really bad issues with RED and some Sony & long-GOP formats.

Hopefully that will get sorted by Apple soon, but it seems to be across apps.

Neil

Everyone's mileage always varies ...

N

nicktheclarkAuthor

Participating Frequently

Ah, that's interesting.

I did some tests with my problem R3D footage in Resolve, and it didn't have the same issues in playback or export that I'm seeing in Premiere. Wasn't extensive, but at least initially was error-free.

I've now entirely erased and reinstalled MacOS on my system, disonnected R3D files from my Premiere project (so that it's ONLY referencing ProRes proxies), export using Software Only, and I still get these glitches left and right. Worst editing experience I've had in as long as I can remember. I do hope this gets run up the ladder at Apple/Adobe, and resolved asap.

Warren Heaton

Community Expert

@nicktheclark @Tim Sekiguchi

I tried to reproduce this using sample R3D files from Red's website (https://www.red.com/sample-r3d-files) using Premiere Pro version 22.2.0 (Build 128) on an M1 Mac mini running macOS 11.6.2.

There's a HELIUM 8K S35 clip, V-RAPTOR 8K VV clip, DRAGON 6K S35 clip, and V-RAPTOR 8K VV clip. Each is imported via the Media Browser with a Sequence created from the HELIUM 8K S35 clip (Editing Mode set to Custom with Video Preview Format set to I-Frame Only MPEG). Lumetri Color is applied to each clip and the non-8K clips are set to frame size.

Exporting with Adobe Media Encoder version 22.2 (Build 64) using H264 Match Source - High Bit Rate and H264 Vimeo 480p SD Wide works as expected.

If anyone would like to download the project to test on their M1 MacBook Pro for troubleshooting purposes, I’m happy to provide a download link. It’s about 7.5 GB. If the problem can be reproduced with files that are easier to move around, we can get it to the Premiere Pro Engineers.

N

nicktheclarkAuthor

Participating Frequently

Hey Warren,

Thanks so much for following up and testing this out. Our systems are close. I'm on Premiere/AME 22.2 (Build 128) and MacOS 12.2.1. Would be wild if it was an Easter Egg in Monterey!

I'd be happy to check out your project if you want to send a link. Would be great to get it to Adobe engineers.

Thanks!

T

Tim Sekiguchi

Participant

I'm having similar problems with R3D files recorded on the V-Raptor. I'm also using the latest M1 Max with latest version of premiere. I edit with proxies and my exports turn out fine, but when I go to online everything and export, there are consistently glitches.

The only solution to this so far as been to export using software encoding, which takes a little longer but ultimately gives you the clean finished product.

Also, on another note, when I've previously exported on older computers, the estimated file size was usually very accurate... when using Hardware Encoding, the file sizes come out to be 10 - 20% smaller than the estimated size... however, when using Software Encoding, the estimated file size and actual file size are the same. In other words, using software encoding is actually giving me LARGER files - I wouldn't have thought the encoder would have made that big of a difference.

Also, hi @mattchristensen !

Warren Heaton

Community Expert

@Tim Sekiguchi

Is your workflow to import R3D, edit R3D, and then export to H264? If so, is the Edit Mode for your Sequence set to Custom, Red Cinema, or something else?

N

nicktheclarkAuthor

Participating Frequently

@Tim Sekiguchi Sorry to hear you're having similar issues, but it sure does feel good to not be alone, haha.

Editing with proxies and rendering out using software only has helped me solve this about 75% of the time, but I still get the glitchy frames on export sometimes - even when forcing proxy export WITH software only!

@Warren Heaton10841144 , based on your earlier suggestion, I changed all of my sequences from RED cinema to Custom w/ ProRes Proxy to match my proxy files. Similar to the above, has helped but not solved the issue.

My DP has the same workstation and recently did a clean OS/Adobe CC install on his MBP, which also seemed to help. That may be my next step, but I'm dreading it.

R Neil Haugen

Legend

Ouch! That's ... painful.

Maybe @mattchristensen might be able to pop in and advise?

Neil

Everyone's mileage always varies ...

N

nicktheclarkAuthor

Participating Frequently

Yeah, not a fun one. Thanks for the bump, Neil!

R Neil Haugen

Legend

Hey, I don't do much red, but do from time to time. Normally it goes fine, sometimes I get a puzzler. But nothing like this ... so yea, hoping Matt or someone will pop in. Maybe @Warren Heaton10841144 too ...

Neil

Everyone's mileage always varies ...

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded