plug in bug in fcpx 10.1.1 with 5KHD files

getting this with several plug ins (refine, film convert, beauty box) in fcpx 10.1.1 with red raw 5KHD files....image gets cropped and a strip of the left side gets adde don to the right....i have been in contact with film convert and beauty box, they mentioned they had seen it before, looks like a fcpx bug....of course apple does not know anything...



edit: i keep trying to add a screenshot to this and select the file and insert it, but it does not show up?

I think you need to talk to the third party software provider. What should Apple know about what they're doing.

well that is what i am doing....and all the plug ins i am working with show the same problem.....so it's not just one software provider....

So it's a common error probably caused by a change in SDK. Hopefully they'll come up with a solution soon. What are they saying?

i provided them with some 5K footage and hopefully they can figure something out....problem is the same with all these plug ins, don't know if others as well, these are the ones i am using...

I have just tested this.

Here's a raw 5K R3D clip on a 5K timeline:



Here's reFine applied to it:



Here's Beauty Box applied:




No issues whatsoever, so definitely not an FCPX bug. Are you sure you have the latest versions of the plugins?

-Ronny

Also, does the hardware (GPU) seem to be robust enough to deal with 5K?

hmmm....thanks for that ronny....i think i know that footage, i think it is from the red one? what are the pixel dimensions? the files i am working with are 4800x2700....
my hardware runs the files without any problems at all....i also have a red rocket, but even without i don't really have any issues (on lower quality of course)....the problem shows up the second i add the plug ins i mentioned.....
have done several un and re installs, even set up a new user and ran fcpx "fresh" with different footage....same thing.....
i tried the same footage and plug ins in resolve and don't have any issues there....

Hey Paul,

That's indeed some 5120x2560 R3D sample footage I had laying around. I cannot post any client clips, but I don't see any problems with these plugins on current RED 4K footage I'm working on.

Keep us informed on your progress with this issue.

-Ronny

just got off the phone with a very helpful apple tech… we played around for a while…but could not get rid of it…i guess the issue is with how fcpx work wit certain files and certain plug ins…they can’t do anything, all their effects work fine…he did acknowledge that it is strange to have 3 different plug ins show the same problem…does not really help me though….

Yes, I agree this is strange. I don't know if this is possible for you, but if you could send me a couple of seconds of a clip that is giving you trouble I could test it on different machines here. My private e-mail address is ronnycourtens(at)mac(dot)com.

-Ronny

Be sure to fill out the FCPX feedback page right away, also! Give them the details!

downloaded that clip as well and am getting the same issue...
something is strange....

Yes, it is. As I have mentioned in PM I have downloaded your original R3D footage and had no issues with it on different systems. There definitely is something weird going on on your machine. Just a wild guess: do you see the same problem with the RedRocket disconnected?

-Ronny

same result with rocket on or off.....
just got a response from filmconvert....after looking at my logs, they mentioned it might be a conflict between the fcpx and ofx (for resolve) plug ins....

That could indeed explain why everything you have tried does work for me. We have no machines running both FCPX and Resolve, we run Resolve on separate color grading workstations with dedicated grading monitors. So I cannot have any conflicting FxPlug/ofx plugin versions. Thanks for the heads-up.

-Ronny

so here is the latest.....
film convert works IF the rendering is set to GPU render ...CPU render shows the issue...and GPU render is sloooooow compared to CPU, so not really an option for me....
beauty box does not even pretend to run in GPU render so that is out....
both developers mentioned that this IS a bug (known to apple) in the OS and time will tell...
i am for now left to find a workaround...thanks for everybody's help....