Michael Hancock
Forum Replies Created
-
[Jeremy Garchow] “What other codecs are in that folder besides Avid?”
These:
[Jeremy Garchow] “The nice thing about Adobe Media Encoder is that you can create watch folders so that every time you get a render, you can drop it in the folder and have AME have a go at it.”
Good call. If we were running off a shared storage system I’d set this up immediately, but we’re still on individual storage and just pull files over the network. I’m going to test both the watch folder in AME and create a Compressor Droplet to see which works better for us.
Again, thanks for your help.
—————-
Michael Hancock
Editor -
[Fabrizio D'Agnano] “However, I do not think is a problem with ProRes in general, but just FCPX latest version conversion. “
I think you’re probably right too. Hopefully testing it with EditReady will let you know for sure if it’s FCPX doing the conversion that’s introducing the glitches, or something else.
—————-
Michael Hancock
Editor -
I downloaded the codecs from your link version 2.3.7 – they’re an old version). Still got the shift on High Sierra and Sierra.
Updated the codecs to the latest version (2.7.3) – and the shift is still there. I’m going to make a droplet that recompressed the DNxHD to ProRes and just do that for now. Thanks again.
—————-
Michael Hancock
Editor -
Thanks. I nuked all the Avid codecs, restarted for good measure, rendered a DNxHD .mxf from After Effects (via Media Encoder), and imported it into FCPX. It imports, but the screen is black. Likely because I removed the Avid codecs!
After Effects and the other Adobe products can read the file just fine since DNxHD is native to them now, and levels on the render match the AE project. I’m going to redownload the Avid codecs and reinstall them, then I’ll reimport.
Do you know what version of the Avid codecs you have installed on your system?
—————-
Michael Hancock
Editor -
[Simon Ubsdell] “There is nothing more guaranteed to get developers wanting to ignore you (and worse) than when you call it that without having the full picture.
“If only we had the full picture from someone that would actually know what’s going on. Like, from Apple, maybe? ☺
Did they learn nothing from the launch of FCPX, about launching a product that’s different from everything else out there, without any info to explain the whats and whys?
—————-
Michael Hancock
Editor -
Thanks for testing all this. Very frustrating that I’m not getting the same results as you!
As far as I know I don’t have any other codecs installed (I did a clean install to High Sierra just prior to Christmas). The Avid codecs were installed when I installed Media Composer First, which I installed to make sure I got the latest codec pack (and to test it to see just how crippled their free software is).
Is there a specific place codecs are installed to? I’ll look in my Application folder for an uninstaller too.
—————-
Michael Hancock
Editor -
Thanks Jeremy for testing this and for uploading your files.
I downloaded your files and am still seeing the shift on my MacPro (High Sierra and FCPX 10.4). I also tested them on an iMac running Sierra and FCPX 10.4 and I still see the shift, which is really strange, since you’re on Sierra and aren’t seeing it.
Here are the files I made in AE2018 for testing. I have both Quicktime files and MXF.
The RGB Ramp should be 0-255, and Legal should be 16-235. On my system, the RGB looks like it gets changed to 16-235, and the Legal gets the same shift, making it really washed out. Do you see the same on your system?
—————-
Michael Hancock
Editor -
I definitely sounds like FCPX is adding the glitches during its conversion process.
FCPX doesn’t natively support AVCHD files, so by importing them directly from the AVCHD card structure it’s doing a conversion to ProRes in the background. There’s no way to avoid this if you keep the AVCHD package structure in place. That’s why, when you pull the .mts files from the card structure and directly import those, you don’t see the glitches. It’s the raw file.
Do you have EditReady? If you do, rewrap your footage to .mov, so you can directly import it into FCPX without a transcode, and without having to dive into your package contents. See if the issue is still there. If you don’t have it, there’s a trial you can download so you can run some tests. You could also use EditReady to transcode your footage to ProRes to see if it’s just the conversion to ProRes in general that’s causing the issue, or FCPX’s conversion in the program.
https://www.divergentmedia.com/editready
—————-
Michael Hancock
Editor -
Update as I continue to test this:
The levels are read correctly in Premiere Pro and Resolve. FCPX is the only program reading them wrong.
As another test I dropped the DNxHD files into Media Encoder 2018 and recompressed them as ProRes files (matching the source files on all other parameters). They now import into FCPX with the right levels!
It looks like there is something in the DNxHD metadata that FCPX is reading and interpreting wrong? Anyone know how to change the levels flags in a Quicktime file without having to recompress it?
—————-
Michael Hancock
Editor -
Yep. I just checked the App Store again and there’s nothing to update. The ProApps update was installed Dec 19, 2017.
—————-
Michael Hancock
Editor
