James Villeneuve
1
COW Coin
Forum Replies Created
-
Hmm. Picture profile could be the problem. When I shot that video, I wasn’t familiar enough with the camera to think of shooting the same scene in different pic profiles. I hope that’s it.
Can you tell me what PP gave you problems and what pic profiles you settled on? I’d love to know what you learned. I haven’t encountered that problem since… and I believe I changed picture profile. I’m much more comfortable with the camera now. I absolutely love it, actually. It made my shooter’s 5D look … ‘not as good’ is the only way I can describe it. The latitude is phenomenal.
Anyhow, look forward to hearing from you,
James.
-
Thanks so much for responding…
Um, I don’t think it’s a white balance issue because the baby blue ‘bloom’ has obliterated details of the sign. If you’ll take a look at the third image (the reflection) You can see the lines in the sign. When you look at the first image you’ll see that the bloom has ‘erased’ those lines. I can’t stress enough how the blue bloom area was NOT overexposed. So, aside from being a single shade of baby blue, there’s no detail either. The other indicator that makes me believe it wasn’t a white balance issue was that every other colour in my videos perfectly matched what what I saw there.
I could be wrong but the lack of detail in the baby blue ‘bloom’ has me paranoid it’s a sensor/firmware thing. I wonder if it could be a picture setting? I wish I had shot some footage on each of the picture settings so I could answer that one.
-
Thanks for your response!
I tried restoring from back up and all the media was still offline… even though the back up I chose was saved before my problem happened.
I guess I just can’t understand how a corrupted project could affect my media. I understand if my media is corrupted how it would affect my project, event or library, but this is crazy. I’m looking to understand how/why the problem would happen this way. How does FCPX’s inner workings result in a single 20 second project file corruption taking all the media offline. It was very clearly related to that project as once I removed it, everything relinked perfectly. the library is now perfectly fine. If I put the project back in… it shits the bed again.
Just… weird.
Anyhow, I also wanted to share this experience in case someone else has a similar problem. I always learn stuff on this website from other people’s problems and solutions.
-
So, to conclude my story, I finally was able to try exporting an image seq from motion into a prores 4444 codec and bring it into FCPX. It worked like a charm. So, that means that the issue has something to do with my FX guy’s outputs. I was worried that I had a bug/bad computer setup that was making all my efforts futile. My FX guy is now doing his own research into the problem to figure out what he’s doing wrong.
Many thanks to you all for taking the time to offer suggestions. It was all very helpful as I was able to learn more about FCPX while figuring out my problem.
James.
-
I did manage to get my FX guy to output video with alpha channel that finally worked in FCPX. But it was Uncompressed 32-bit ARGB and is obscenely huge. 83 MBs for less than a second of video for testing. If he had output all my materials that way it would have been something like an entire terabyte for less than 6 mins of stuff. It would probably make my aging machine explode.
Anyhow, it looks Motion is my next try. I’m going to import an image sequence with alpha and export as ProRes 4444 and see if that works.
Computers are awesome until they suck.
-
hiya. Thanks for the tip. The prores 4444 videos with alpha channel were originally exported with After Effects on a PC. I do have Motion (though I barely know how to use it). When I have time to try it, that’ll be my next move. Is it a bug you have experience often or something you have heard from other users?
-
thanks very much for the reply. I am aware that optimize media would create prores 422 and destroy alpha so I had that turned off. My guess is there is a gremlin living in my machine. It’s the only thing that makes sense at this point.
I’d love for this to just work as it would simplify my life.
-
thanks so much for the response. i’ve been working crazy days and haven’t been able to get back to this until just now.
I checked and, in fact the alpha wasn’t translating – I looked at the alpha channel in the drag down menu and the frame is entirely white rather than a white ‘cut out’ alpha channel. So something about the output isn’t agreeing with FCPX. Because my FX guy tested it on his side and said the alpha channel was displaying properly in other programs.
Just to compare, I did it with an imported image with alpha file and viewing the alpha channel clearly showed the alpha channel. So it’s just with video… dammit.
I’m thinking this might be a bug or something …
James.
-
Thanks for the help but, unfortunately, none of those suggestions worked. It took me a few days to get around to trying to solve the problem and the end result is that I wiped my system clean … problem solved. In truth, it might have been a bigger problem than simply FCP X because I realized that I couldn’t play ProRes with the Quicktime Player or quick view option in finder. So, the bottom line is that I had digital racoons rooting through my system that I had no hope of identifying.
Wiping it clean did the trick. Plus, my system is running a bit faster now.
Cheers Jeremy, thanks for your time. Keep on keeping on.
James.
-
Thanks for the reply Jeremy.
I will give Compressor Repair a shot. I appreciate the suggestion. Hopefully it works!
And regarding FCS3 – I have the system drive partitioned with one half being a SnowLeopard FCP Legacy machine and one half being Mountain Lion/FCPX machine. I assume that probably isn’t an issue since they are on separate boot drives.
My guess is that starting from scratch with a total clean reinstall of OSX and the rest of my applications will probably fix it but I was hoping not to have to do that.