FCPX color wheels problem

Hi all, back on my old problem, now I have converted mts files with edit rewrap as you have recommended on this forum, and they work well with fcpx 10.4 and high sierra.
but when I select the clip in the timeleline and make a color correction with color wheels in the appropriate panel as in attachment 1, at the end I get the clip as in attachment 2 and also on the second monitor full screen I see this colored grain, if I deactivate the color correction in the panel then the clip returns to normal.
can someone tell me why? and what should I do to eliminate this problem?
thank you

If really your whole screen looks as in your "monitor3" attachment, then I don't know the reason.

You said this was happening with the Color Wheels. But not with the Color Board? Then the solution is to use the latter instead. For rec_709 (you shoot AVCHD, right?), the wheels show a "mysterious" behavior anyway, and I'd rather wait for 10.4.1 before I use them.

Generally, AVCHD can be a pretty threadbare signal that can fall apart quickly if treated with the new tools excessively. It's better, for instance, to use a color mask for selective (=secondary) corrections. All color tools have this. You can select a hue, a luma- or a saturation range with the color pickers, but only with the masks you can feather it (softness slider). The color mask basically is like the HSL qualifier in Resolve, where you can specify a "blur amount" for the selection.

And: be subtle to color, not aggressive.

ok thanks but then is a problem of fcpx 10.4 and not high sierra?
does the same problem happen to you too?
thank you

For troubleshooting your issue, we need more information. Right now, judging from your "monitor3" attachment, in which the screen looks torn in the middle: this has not been reported elsewhere afaik, so it most probably has neither to do with High Sierra nor 10.4. Rather it might be something about your display connections / configuration, who can tell?

You also wrote about the Color Wheels specifically. Please try and report if the same happens with the Color Board too.

On the other hand, it is possible and actually very easy to make the whole image very noisy. With raised shadows and midtones you can make the so-called noise floor visible. AVCHD tends to be the least forgiving acquisition codec for underexposure. But would happen with RAW footage in very high bit rates also. The main purpose of judging CC in full frame is to determine the limits. How far can you push values before your adjustment destroys the image?

The thing with the Color Wheels and rec_709 projects is that adjusting for contrast is supposed to be a three-step procedure: Find the brightest part, then the darkest part, then bent the line between them to brighten or darken the midtones. With the current Wheels version, that's not possible. You only get there in increments, which also means that you don't get a smooth gradation curve but one with unnecessary 'knees'. So in short: no wheels until further notice!

I forgot to say that always on high sierra and always mts files but with fcpx 10.3.4 everything works fine without any problem.

Europe? Italy? PAL-zone?

Could be the "i" bug.

10.4 does not correctly interpret AVCHDs field order (allegedly, I've read this somewhere). If you shot 25p, many AVCHD cameras store that as PSF, some kind of pseudo-interlace. 10.4 apparently doesn't read the flag.

The solution then would be to wrap or transcode to ProRes externally and then import that in FCP X.

But you wrote in your thread opening that you already wrapped. Back to square one.

yes, I've already tried to convert to 422 but with fcpx 10.4 and not before.
so I will do a test converting to prores with editready and then amount on fcpx 10.4 and I do a test, let's hope it works.
I'll let you know, thanks for now.

I did a test converting first the MTS files in apple prores 422 with edit ready and then imported on fcpx 10.4, and I must say that the thing is improved but still the problem remains, in the sense that with the rewrap files the whole clip is disturbed while with file prores 422 converted before, only some parts are disturbed, ie the clip jerks, sometimes you see the noise and then disappears and then reappears.

click wrote: I forgot to say that always on high sierra and always mts files but with fcpx 10.3.4 everything works fine without any problem.

I'd stick to 10.3.4 then, for the time being. Lame advice, I know, but there is only so much time and effort I'd invest in troubleshooting.

and I think that maybe I'll come back to fcpx 10.3.4 for the moment while waiting for some future update of fcpx to 10.4.1.

But I have to say apart from this problem ocn fcpx 10.4 all the rest seems to work well, so I could continue to use it not using the color wheels, until the problem is resolved by apple.

thank you for helping me

click wrote: But I have to say apart from this problem ocn fcpx 10.4 all the rest seems to work well, so I could continue to use it not using the color wheels, until the problem is resolved by apple.

This is weird.
*Only* the wheels?

Continue to use 10.4 then. But with the Color Board.

we confirm fcpx 10.4 I only have problems with the color wheels because the rest works well for me.
thank you

click wrote: … confirm fcpx 10.4…

… and your hardware specs?
'Hackintosh' or regular Mac, which one?

Karsten Schlüter wrote:

click wrote: … confirm fcpx 10.4…

… and your hardware specs?
'Hackintosh' or regular Mac, which one?

I use a Hackintosh

click wrote: I use a Hackintosh

Configuration-related then. Lucky that that the problem is limited to one tool. Try to make your 3d monitor an AV out (which it apparently isn't now). Should be easy with either HDMI from your graphic card or BM Decklink Mini Monitor. Will this solve the problem? Don't know, there can still be 'driver issues' and the like, but it's worth trying.

click wrote: …I use a Hackintosh

Have to confess: I'm not surprised… :silly:

…until the problem is resolved by apple.…

What makes you believe, Apple has any interest to solve your problem, on a - in their perspective - illegal platform ??

Axel wrote:

click wrote: I use a Hackintosh

Configuration-related then. Lucky that that the problem is limited to one tool. Try to make your 3d monitor an AV out (which it apparently isn't now). Should be easy with either HDMI from your graphic card or BM Decklink Mini Monitor. Will this solve the problem? Don't know, there can still be 'driver issues' and the like, but it's worth trying.

ok

Karsten Schlüter wrote:

click wrote: …I use a Hackintosh

Have to confess: I'm not surprised… :silly:

…until the problem is resolved by apple.…

What makes you believe, Apple has any interest to solve your problem, on a - in their perspective - illegal platform ??

sorry, you're right, I did not think about it.
then it could be the fact that I do not use an original mac the problem that I find myself?
yet from yosemite to sierra I never had problems.
and perhaps forbidden to talk about hackintosh in this forum? in that case I apologize.

click wrote: …and perhaps forbidden to talk about hackintosh in this forum? in that case I apologize.

btmk, it is NOT verboten…
(alone how many Hackintoshers hijacked the BruceX thread…)
Just my very personal POV, don't like this… romanticizing of DIY hardware (says the tinkerer, the no-budget hobbyist!).

From perspective as a boards Mod, it would nice, to add 'Hackintosh' in the starting OPs… we discuss here a problem 'all day long' which most probably has its roots in a non-standard-conform set-up*…-

A fast reader/googlebot just catches 'problem' and "Apple should fix it!" - … nope.

* trouble with Hackintoshs is, just because it worked in the past or on a 99% identical set-up allows not future prognosis … keyword 'Apple custom baked coprocessors'

Anyhow. Just my 5¢ …

sorry