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 :)

I AM REALLY GETTING CRAZY PLEASE HELP!

L

Luca Volpe

Well-known member
Joined
Jan 1, 2016
Messages
385
Reaction score
0
Points
0
Location
UK
Website
www.lucavolpe.com
PLEASE GUYS READ HERE, I HAVE SOME UPDATE ABOUT MY ISSUE WITH FCPX....so....
As some of you remember I had problem importing in the latest FCPX 10.3.1 files R3D it was appearing the PINK frames (you can only scrub but as you stop all is PINK)...I thought was Color Finale that was doing some kind of conflict...so I removed it and today I decided to reinstall FCPX.
Also I reinstalled the red workflow from red.com
And nothing happened...same problem (see picture!)
Here is what I don't understand:
1. The file 8k from Red Epic W, works perfectly in red cine, so is NOT my GPU actually it works quite fast in red cine x.
2. I also downloaded 8K Helium files from red.com and I have the same problem, so is NOT my camera....
3. If I import in FCPX a files from SCARLET W it works great!
So at this point...I really don't know what can be!
If someone can help will be this the best Christmas gift!! :)
Thanks a lot
Luca
 

Attachments

  • problem.jpg
    problem.jpg
    10.8 KB · Views: 0
  • sierra.jpg
    sierra.jpg
    14.1 KB · Views: 0
This appears to be an FCPX and/or OSX and/or GPU implementation issue. FCPX customer support is your best bet perhaps. Might oddly be a RAM related thing on the GPU even/system resources thing. Hard to say.
 
This happens to me every so often. I find if I have a title overplayed with colorfinale or something like that, it's usually the issue. Delete any title effects and replace

steve
 
Antony Newman said:
I will delete this post shortly.

... Is anyone else getting redirected to Spam sites when clicking on URL links in REDUser?
(eg click on the link in the above post)

(Just trying three different computers --> same result)

AJ
Click to expand...

Yep. Just happened to me as well. 
 
Phil Holland said:
This appears to be an FCPX and/or OSX and/or GPU implementation issue. FCPX customer support is your best bet perhaps. Might oddly be a RAM related thing on the GPU even/system resources thing. Hard to say.
Click to expand...

Philip I installed again fcpx and removed color finale..same issue...but the odd thing is that if import a scarlet w files works perfect. Also in redcine my 8k files are giod...no idea where and how to check...
 
Luca Volpe said:
Os sierra latest update
Click to expand...

To be completely honest, if Apple has switched their processing in Final Cut Pro X to Metal - then that could possibly be your issue right now. Prior to the newest 10.12.2 update, I was running Metal for processing in Adobe Premiere - just for the sake of speed testing their "Apple" interpretation of OpenCL. Everything worked fine until the newest update for reading RED RAW footage. Not sure if this is Apple's problem or RED's in this instance.

While running Metal processing in Premiere on 10.12.2 - whenever I'd hit play... the video would glitch and split into three parts, with two small similar videos playing side-by-side atop and a very interlaced video combing across the bottom.

My assumption is that if it's happening in Premiere - it's bound to glitch in FCPX as well. Granted, not sure if it is Metal at the helm of FCPX now - but I absolutely believe the newest updates in Sierra don't seem to play nice with RED RAW.
 
Answer from other 'A'.

Graphics drivers & Language allow the CPU to direct the GPU.

OPENCL is a universal language that is powerful, but has a large overhead.
CUDA is Nvidia's specific language that more efficiency maps to their own GPU architecture.
METAL is Apples 'recently' created language that is a low overhead / high efficiency way of controlling their GPUs hardware.

For Apples mobile - GPUs Metal absolutely screams (Low overhead and Exact Hardware acceleration for the instructions).
For Apples desktop - the low overhead Metal driver is still much faster than OpenCL.

Each year Apple is taking tasks in the Operating system written for CPU and rewriting & optimising it for GPU (Metal). As Apple control the hardware, OS, FCPX, GPU language - they can in theory optimise the end to end performance in ways that Intel and Microsoft cannot.

Apple is and has been expanding its SoC (Chip design) capabilities for Mobile, and for the first time has added compatibility into MacOS (Sierra) for ARM (in addition to the x86 Intel chipset that it has been for many years).

If Apple decided to enter the GPU market for MacOS - their Metal drivers would be able to make use of their own hardware too.

As most of the heavy lifting these days is in the GPU, a Metal backed MacOS + Apple GPU + Hurricane-like Apple multicore CPU may present a cost efficient prospect.

With companies Already releasing Apple bespoke (Apple Touch Bar) software, the Apple rather than Windows version of the software is likely to become more 'sexy', and the desire for Bootcamp to run x86 software reduces (because the Windows version becomes a 2nd class citizen).

As the MacOS code is generally created in XCode (Appled development system), and XCode compiles automatically according the Metal hardware acceleration of the device the code will run on, and XCode can also compile to X86 and ARM .. some people believe Apple will transition to ARM CPUs with METAL optimised GPUs (that support OPENCL).

AJ
 
Wow AJ thanks for the reply but it looks chinese for me �������� I justnwould like t know why this is happening!
 
Reinstalled fcpx + red workflow and removed color finale and plug ins...always the same problem...but works with scarlet w files and red cine works great with my 8K files from epic w.... Im kind of giving up....
 
From a troubleshooting perspective, my first query is why the issue is limited to 8K Helium R3Ds - while other flavors of R3Ds are unaffected. If it was related to Metal/RED Raw processing errors, I'd expect it to be more universal.

1) Is it the "helium-ness"? Is there some aspect of the file structure, graphics libraries/flags, etc that FCP-X/Metal reads differently than Dragon/M/MX R3Ds?

2) Is it the 8K size? Assuming the latest FCP-X build is capable of large rasters, then what about frame buffers and/or amount of VRAM on the GPU? I believe there is a toggle in FCP-X that allows you to switch between A) lower res for scrubbing, full res when parked - AND - B) lower res (1/4, 1/16) all the time. I think the full res when parked is the default, so see if you can change that in preferences.

3) RedCineX-Pro may "force" the GPU into a more universal OpenCL processing mode than FCP-X which is trying to implement Metal routines (to optimize speed) that perhaps create issues?

Cheers - #19
 
FWIW, I have Sierra, FCPX 10.3 and an Epic-W Helium I have tested at all flavors, as well as Weapon Dragon and Scarlet-MX. I also use color finale where applicable and I have zero issues. I think Phil is right when he points to a possible RAM issue.
 
If is a RAM issue how can I test it? Everything works good inmy Imac 2013 and also quite fast when I import 4K prores. There is anyway to check on the mac? Thanks guys for the help
 
RAM is tricky business. I have had bad RAM that passed tests that I had available to me, but failed at a QC level at Apple. You could take it to Apple and have them test it. I should also have said that I have an old laptop, early 2011, that I put an SSD into and 16 gigs of RAM. It went back to Apple for a GPU issue (which they fixed for free...out of warranty for 4 years) and they put in another SSD and found bad RAM, putting back in only 8GB. (all of this was free...) In any case, this old machine runs FCPX 10.3, Color Finale, REDCINE-X Pro and with .R3Ds on the boot drive, has none of the issues that you are experiencing. FWIW.
 
Scot Yount said:
RAM is tricky business. I have had bad RAM that passed tests that I had available to me, but failed at a QC level at Apple. You could take it to Apple and have them test it. I should also have said that I have an old laptop, early 2011, that I put an SSD into and 16 gigs of RAM. It went back to Apple for a GPU issue (which they fixed for free...out of warranty for 4 years) and they put in another SSD and found bad RAM, putting back in only 8GB. (all of this was free...) In any case, this old machine runs FCPX 10.3, Color Finale, REDCINE-X Pro and with .R3Ds on the boot drive, has none of the issues that you are experiencing. FWIW.
Click to expand...


Do you have Sierra on it, latest update?
 
I would put sierra on an external bootable disk with only FCP X installed.
Then, boit your mac from the new clean install too see if you have any problems.

Also. I would remove all ghird party codecs from the QT codecs in tge library. I think you have a codec in there that might be creating a vonflict.
 
You must log in or register to reply here.
Back
Top