Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

RED APPLE WORKFLOW INSTALLER V18.0 (Apple Silicon support)

Mac mini M1 with 16 GB memory, 11.3 (beta) Big Sur, Red Workflow 18, and having the issues described. Also on a MacBook Pro M1 with the same specs.
 
Steve Sherrick said:
But this new one? Well, in the attachments the crisper image is while the footage is paused, the pixelated image is when it's playing back. Doesn't even look like normal pixelation, very distorted and weird.
Click to expand...

Jon Dishler said:
Also, when playing 8k footage (Helium) in viewer under better performance it looks totally wonky like some weird blocky interlaced look. Switching to better quality makes the image look good, but it stutters badly (as sort of expected but thought the optomization to M1 might help).
Click to expand...

Robert Hofmeyr said:
And it is not just better performance playback - proxies created by FCP come out blocky as well. See attached screenshot. This happens when GPU Decode is OFF in Redcode prefs. Turning it ON fixes the problem but increases the transcode time dramatically.
Click to expand...

We've gotten reports this is fixed on macOS 11.2.2. Which version are you on, and if lower, can you upgrade to the latest?
 
Jon Dishler said:
I reported the following over 6 months ago and Red put it on their known issues list and said it would be fixed with the next release, it is not. The setting of a LUT in camera should be imported with the IPP2 settings but it is not and used to be.
Click to expand...

LUT should be auto applied, unless you have FCP copying media on import in to the library. That's not something we control and has to get fixed in FCP. If you're seeing issues when you leave the media where it is and 3D LUTs then please provide a detailed step-by-step and email me a sample clip (my email is my first name at red.com)

Jon Dishler said:
Finally, comparing the image with the exact same settings in FCP, DaVinci Resolve, and Red Cine-X I find that the latter two look exactly alike, whereas the FCP image looks less saturated, flatter, and about a stop more exposed. (UPDATE, WHEN I LOWER THE ISO IN THE RED SETTINGS WITHIN FCP BY 2 STOPS IT CLOSELY MATCHES THE OTHERS, WHICH MEANS THAT APPLE IS PERHAPS STILL INTERPRETING ISO BASED ON THE "OLD SETTINGS?).
Click to expand...

Can you confirm for me what Image Pipeline and Decode Transform are set to in the REDcode Preference Panel under the FCP X Image Pipeline tab? Also, when you bring such a clip in, what is shown for color space & gamma in the clip properties inside FCP?
 
Christian Fitzpatrick said:
FYI - Even this new version still have clips turning black in FCPX after a little bit. That looks unresolved.
Click to expand...

This issue was fixed in plugin 17.1 How many clips are in your project? How many R3D files (not clips) total? I assume you restarted your system after installing this latest update?
 
Brian Timmons said:
For the RED team, please look even deeper into this issue.
Perhaps consider having some of us to Beta test future RED Apple Installer bug fixes and updates.
Click to expand...

Which issue are you talking about here? RED users part of the Apple FCP beta got access to our plugin and we received no reports of issues.
 
I would be happy to test an update the current one and see if it fixes things. I was previously a beta tester for Red camera firmware.
 
Rob, the issues I’m having are the ones mentioned in Post #3 by Brian. constant spinning beach balls, VERY slow imports, generally lagging performance. Earlier versions of FCPX with R3Ds had much better performance on the same hardware. Problems seem to have begun once Apple updated their OS/FCPX and RED updated the workflow plugin. Mojave and FCPX 10.4.7 were pretty solid with R3D. Something seems to have changed. Perhaps we are talking about different issues (black frames/pixelation vs general performance issues). Is it possible that this has anything to do with GPU changes that were done in the RED Apple workflow plugin? Or is it something Apple has done on their end?
 
Yes, different problems, mine is mostly about playing 8k R3D in better performance it is very pixelated in vertical stripes, in better quality it cannot play in real time and stutters, do not see how the M1 integration has improved performance. There is also some mis-match in ISO between what is set and displayed and very different from the same file in Red Cine X or Resolve. Also, I was told that the issue of losing any applied in camera LUT when transferring files to FCP X would be fixed in this next update, and that did not happen. Adding a LUT after the fact in FCP X is not the right place in the chain.
 

Attachments

  • Screen Shot 2021-03-08 at 12.49.51 PM.jpg
    Screen Shot 2021-03-08 at 12.49.51 PM.jpg
    19 KB · Views: 0
Last edited:
Update

Update

M1 Macbook Pro 8GB here.

I can't upgrade to 11.2.2 Due to incompatibilities with Softraid and our OWC SSD Raid Boxes.

I could upgrade to 11.3 Public Beta where apparently the softraid issue is resolved, but it sounds like people are dealing with the same issues. Mine primarlly is the blocky playback in better performance with the vertical stripes etc. as I previously posted ITT.

I downgraded to fcpx 10.5.1 and at least the playback is not pixely and weird, but still have the black clips after editing for a while that requires me to restart FCPX to get them to re-appear.

Sounds like the people ITT haven't had a lot of luck with 11.3 though, so I'm hesitant to upgrade and dance this dance again now that it's semi-stable again.
 
Hi everyone,

We put out a bug fix release 18.1 that should fix the image corruption that were visible on M1 Apple Silicon macs.

Please let us know how the fix looks.

Thanks,

Rob
 
Rob - release 18.1 works fine, thanks for the update. While looking for other updates on red.com I noticed and downloaded the Red Creative LUT 1.0.2 which was just released 10 days ago. The release notes say that this fixed FCPX support, so I was happy to have this resolved as well. Unfortunately, when I installed the LUTs in my DSMC2 camera, they played in camera monitor fine, but when the footage was uploaded to my M1 MAC they were still not recognized, and ignored by FCPX latest version. Respectfully I have two questions, why does this still not work even with this recent update and why is there not a systematic way that users are notified of updates to firmware and software? I always find it by just looking at the downloads page periodically?

Thanks,

Jon
 
Rob Lohman said:
Which issue are you talking about here? RED users part of the Apple FCP beta got access to our plugin and we received no reports of issues.
Click to expand...

OK- After several months of getting the Internal Error 500 message I am now finally able to post to this thread again.

I wrote the original post that started this thread.

Are people still getting this error?
I've been way too busy to risk installing FCP 10.5.2. and am still using 10.4.8.

Hey Rob,
Greatly appreciate your involvement on this thread.

The issues I'm experiencing are-
1- Very slow performance and spinning beachballs when stepping into a RED folder when trying to import footage.
2- Much slower than normal performance when actually importing clips into a project.
3- Spinning beachballs that last several minutes.

I confirmed that other codecs performed normally so it seemed to be a R3D specific issue.

The plugin seems stable and playback was generally better than previous versions.
Actions involving working with R3Ds are VERY slow.
Trying to actually step into R3D folders in the import window, importing clips, selecting clips, or trying to move a clip in a timeline all produced the spinning beach ball for me.

I did work with the Apple FCP beta and it was indeed fine. The issues started late August with the 10.4.9 release.
Again, the issues continued with later FCP X and Apple workflow versions.

Would be interested to know if these problems still persist..

Brian Timmons
BRITIM/MEDIA
 
I just loaded 10.5.3 onto my laptop (MBP mid-2014) and FCP seems to be back to normal
when working with R3Ds.

R3Ds seem to be quick and responsive like before.

My system is still the same as previous (10.15.7 with RED Apple workflow installer V17).

The only thing that changed was my update from FCP 10.4.8 (which was the last workable version for me)
to this latest 10.5.3.

If anyone had any of the issues discussed in this thread try the latest FCP update.

Brian Timmons
BRITIM/MEDIA
 
Last edited:
You must log in or register to reply here.
Back
Top