[Chad Greene]

That looks good except it is Windows only. We are all Mac.

Chad Greene : Mahoney Media : Minneapolis, Minnesota : 2×2.66 GHz 6-Core Intel Xeon, 12GB Ram, OS 10.11 FCPX, Kona-LHi

[Chad Greene]

[John Pale] “There are fewer codecs supported than before. “

Hmm I wonder if there is a workaround. For the last 5 years we have been filming for a documentary series, then importing to FCPX (rewrapping the media). Now we are talking about letting new editors rough cut in Premiere (where they are more comfortable), but currently they can’t see our media and it would take a huge effort to rewrap back to .mxf or transcode to something else.

If I can get this Apple flavored codec to work with Premiere, then our editors can choose what tool they want.

[Chad Greene]

Greg here is a 3 second .mxf file straight off the camera and that same shot rewrapped as a .mov file.
https://drive.google.com/drive/folders/1LABBKHjUa5Eesy0FsHHXkTIeP_JrWkbD?usp=sharing

Here is what I see when I import into Pr.

[Chad Greene]

It is strange that the codec works in X but not in Pr.

I brought the same file in to X, Resolve and Premiere. X and Resolve can see and play the file. Premiere can not. It doesn’t sound like an uninstalled codec. What am I missing?

Chad Greene : Mahoney Media : Minneapolis, Minnesota : 2×2.66 GHz 6-Core Intel Xeon, 12GB Ram, OS 10.11 FCPX, Kona-LHi

[Chad Greene]

I am sorry Dave. I had the codec only in the title of this post. But here is more detail.

Final Cut Pro X sees the original .mxf file as “XAVC Intra 422/10 Class 300”
and the rewrapped .mov file as “XAVC 4K 24p”

Chad Greene : Mahoney Media : Minneapolis, Minnesota : 2×2.66 GHz 6-Core Intel Xeon, 12GB Ram, OS 10.11 FCPX, Kona-LHi

[Chad Greene]

I am guessing you are transcribing this yourself because you don’t want to spend money? We do a ton of transcription and have found Rev.com to be a fantastic service for a ridiculous price. $1 per minute ($1.25 with timecode) and super fast turnarounds.

Chad Greene : Mahoney Media : Minneapolis, Minnesota : 2×2.66 GHz 6-Core Intel Xeon, 12GB Ram, OS 10.11 FCPX, Kona-LHi

[Chad Greene]

Ya, I discovered that late last night. Some of my custom text generators lost their keyframes.

I also discovered that importing a project xml into an empty library makes the proxies go offline which is a big deal for us.

Ultimately I have decided that I can’t trust the XML for heavily edited projects. But they are great for events and simpler handoffs.

Chad Greene : Mahoney Media : Minneapolis, Minnesota : 2×2.66 GHz 6-Core Intel Xeon, 12GB Ram, OS 10.11 FCPX, Kona-LHi

[Chad Greene]

Testing Sound Control with their 14 day free trial. It is working! Thank you Noah. You made my day.

Chad Greene : Mahoney Media : Minneapolis, Minnesota : 2×2.66 GHz 6-Core Intel Xeon, 12GB Ram, OS 10.11 FCPX, Kona-LHi

[Chad Greene]

Oh my! I have been annoyed by this volume problem for years and looked for a solution multiple times. Sound Control looks very promising. Have you used it with Final Cut?

Chad Greene : Mahoney Media : Minneapolis, Minnesota : 2×2.66 GHz 6-Core Intel Xeon, 12GB Ram, OS 10.11 FCPX, Kona-LHi

[Chad Greene]

I just had to do this, only I also wanted the keywords added to the file names in the finder. It was a bit of a process that included “Producer’s Best Friend” and “A Better File Renamer”.

1) Export XML of Event
2) Run through “Producer’s Best Friend”
3) Open in Excel (or in my case Google Sheets). Sort by original file name, then copy all FCPX clip names.
4) Paste new FCPX clip names into Text Edit with one name per line.
5) Use “A Better File Renamer” to completely rename the files based on the names on the text file.

I did this to 37 events and 7,500+ clips last week with good success, though it took a while.

Chad Greene : Mahoney Media : Minneapolis, Minnesota : 2×2.66 GHz 6-Core Intel Xeon, 12GB Ram, OS 10.11 FCPX, Kona-LHi