[Dave Smith]

Ah, thanks for that. Ok so things are clearer now… really appreciate all the feedback!

[Dave Smith]

Ok so it seems my confusion is coming from a lot of loose terminology out there mixed with my yet to be formed understanding. If none of the following is incorrect, I think I understand now…

– Rec 709 is the ‘standard’ colour space.

– Log is not a colour space, it’s simply a term that refers to a shooting profile that records data logarithmically (which has the benefit of more containing more data that can be brought out in post for greater effect).

– Log footage can be used with even better results in a wider gamut colour space like Rec 2020 (provided the display device can show that colour space).

– when I see a LUT that “converts” log-to-rec709… it’s not really converting anything, it’s just nondesctuctively applying a ‘look’ to the footage.

Ok so with that, and somewhat back to my original question… how do you know when a clip is recorded with the log profile? Or any profile for that matter? Do you “just know” as part of the recording-editing process or talking to the cameraman? In my situation, as the one person doing it all, I certainly would know… but what if I came across footage I didn’t shoot? For example, when I use my still camera for jpg photographs I can see in my editor which shooting profile was used, like ‘vivid’ or ‘natural’ or ‘muted’ etc. I assume ‘log’ in video can be likened to ‘raw’ in photography.

Thanks for the reply!

[Dave Smith]

Curious… I downloaded Compressor and see in the Inspector > Video Properties the source Color Space is Rec. 709*. If that’s the case maybe the Mavic is not recording D-Log like it should be…. either that or I’m misunderstanding how D-Log clip information should appear in FCPX.

I’d still like to figure out how to confirm source footage colour space in Final Cut though… any ideas there?

[Dave Smith]

Are you worried that “The products contain components that can compromise your data and share your information on a server accessed beyond the company itself.”… ie. by the chinese government? If yes then yes, if no then… yes. Probably won’t affect you in any direct way in the near term, but by now we all know how data can be used to gain advantage in a multitude of ways. One must assume this is happening if you, at the end of the news chain, are hearing about it. The question now would be similar to one of ‘responsibility’… ie. if you care about furry animals is wearing a mink coat hypocritical? Wearing clothing made by kids in a sweatshop something you support? Still use facebook even though cambridge analytica style targeting is a real thing? etc etc etc…. we are hemorrhaging data on a personal level and have no idea how it’s collectively being used, for better or for worse. Knowing humans need for superiority, I have zero confidence this data would be used ‘solely’ for the good of the product (or mankind).

Food for thought: how many times have you seen a person flick a cigarette butt on the ground… then someone else call them on it, “hey! you think the world is your garbage can??”. I’ll bet 99% of the time if smoker returns the call-out with a “well if you care so much, YOU pick it up”… the person would walk away in a huff cursing the smoker. Folks care about ideals but when it comes time to put money where mouth is, people are people… gov’ts and corporations and advertisers know this.

Point is, the solution to this type of problem is action with strength in numbers. Use mob mentality to your benefit. Either by demanding transparency as a consumer base (which you might not trust anyway), or voting with your dollars and buying from a company whose ethical standards you approve of. As individuals we can worry all we want, but to make a difference (like those with the data from millions can) there has to be a movement at scale.

[Dave Smith]

I get the feeling this has to do with final cut library/project defaulting to the rec 709 color space, not wide gamut. So perhaps I’m recording dlog but importing shows footage as rec 709. If that’s the case I wonder how one would know the native color space of a particular clip… might have to make my way over to the fcpx forum. =\

[Dave Smith]

To the previous poster… I do not have background render turned off (assumed it was on for good reason)… but in my quick tests turning it off instantly has a positive effect. Will have to toggle that back and forth as I keep working to confirm.

@Joe Marler thanks for the info… didn’t realize this build is thee build. Does this mean there aren’t multiple builds per app version? ie. the next time the build changes we will move up a version to 10.4.8?

Thanks for the Chrome tip; I tossed Chrome after years of usage just one month ago for it being a general resource hog all the way around (plus the privacy problems didn’t help its case).

Re: Activity Monitor… I was aware that the Used, Cache, etc. were global… that’s why I also posted the value in the FCPX Memory column… at +90gb and climbing it seemed out of sorts with the global values. However, I think I now realize that value is referring to total data processed by the app… so +90gb and climbing shouldn’t have made me think it was a problem. That was my misunderstanding. There was never any red or orange in the Memory Pressure readout so I don’t think it was a RAM issue now, but I’ll keep an eye one that.

Your point about the plugins is something I hadn’t looked into. The only plugin I have is the Coremelt Everything Bundle (SliceX/TrackX etc)… they sent me a dropbox link to an unreleased version 507 ‘a’ on Sept. 25, but I see now they have a new version out as of Oct 11. on their website 507 ‘n’…. wow, ‘a’ to ‘n’ sounds like lots of versions in a short time! Anyway, I’ll try this new version too.

Let me see if these few changes make a difference… thanks for all the help!!

[Dave Smith]

Wow this is great, I hadn’t thought of that at all… I will have to take some time to re-read your post a few times and give it a try. Thanks a lot for taking the time to read through my problem and write back a full response…. it is appreciated immensely!

[Dave Smith]

Well, I went in and did the replacement manually anyway. Would be good to know for sure if there’s a way to accomplish that task automatically with a new version of a clip though.

As a side question… is it recommended to deal with audio as first step before importing footage to FCPX in order to avoid this type of problem? How do folks deal with audio changes outside of final cut pro after importing if it becomes necessary?

[Dave Smith]

Yes I agree, this is much easier said than done. I posted in the After Effects forum and think it’ll be the same story any path I take. =\

Lessons learned:

1. ‘just fix it in post’ is a legitimate gripe
2. set design, set design, set design

Thanks for the feedback!

[Dave Smith]

Thanks for the leads. One drive is NTFS and the other exFAT… I’ll should move data off and format as APFS . The storage properties are what got me last time, they were not set correctly, have that solved now. What did work was the copy instead of move, after completion I verified with reveal in Finder, then deleted the original event. That’s great, thanks again for the help!!!