Joe Marler
22
Apple Final Cut Pro X Coins
38
COW Coins
Forum Replies Created
-
If your client is in the performing arts, they must have seen Youtube clips showing on-screen timecode. During post-production that is how decisions are made. It is always HH:MM:SS:FF.
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
If done before import, the utility QtChange can rewrite the MP4 timecode so FCP can read it. It is super-fast and does not re-encode or even rewrap: https://www.videotoolshed.com/handcrafted-timecode-tools/qtchange/
The redundant C000…mp4 filenames are another problem. It is vastly better to batch rename those with a globally unique name before importing. A simple method is just append each filename with an underscore and a 4-digit incrementing “uniquefier”, such as _0001. Of course you must keep track of the highest number used, and use +1 before the next import. That can be done with Finder’s rename feature using the “format” option. There are also other more sophisticated third-party file-renaming tools such as “A Better Finder Rename”: https://www.publicspace.net/ABetterFinderRename/index.html
It is vital the end-to-end workflow be validated before you commit to a major project. You can’t just assume everything will work. E.g, even if the ingest timecode and non-unique filenames were handled, there is the issue of whether subsequent clip exports in various codecs from various tools will maintain the clip timecode. I had a situation last year where proxy generation on an AWS cloud server would not maintain clip timecode that FCP could read.
-
Just taking a wild guess since we have no info on your versions or machine, but there was a bug in FCP 10.7.0 on Intel Macs (not Apple Silicon) that could cause a crash when using color wheels. It was supposedly fixed in 10.7.1.
-
For markers in the Event Browser, you can hover your mouse over those and see your marker info. Simply enable View>Browser>Skimmer Info.
If you assigned custom names for those markers, you can then search them using the search bar above the Event Browser.
You can create a Smart Collection that filters on markers by doing File>New>Smart Collection, name it, then double-click on that in the sidebar to enter the smart collection criteria. Press the + key and assign “Markers”. Thereafter clicking on that Smart Collection will show all clips in the Event Browse containing markers.
To create a library-wide smart collection (IOW one that searches through all events in the library, not just the current event), select the library in the sidebar, then do File>New>Library Smart Collection.
If you toggle to List View (OPT+CMD+2), the Event Browser will show more info about each clip. If you press OPT while spinning down the disclosure triangle by the event name, it will unfold all ratings and markers on all clips. You can then scroll down and see all your marker names.
If you have many clips without markers, just use your marker smart collection to filter only on markers. Then with the Event Browser in List View, you can see the distilled version of clips only containing your markers and read the names.
-
Kyrina, the 3rd-party MacWhisper utility can not only transcribe with high accuracy to an SRT file, but it can also translate at the same time. You can easily produce English and Spanish SRT files, import those to FCP via File>Import>Captions, and flip between them. Each one automatically becomes a separate audio role, visible in the timeline index. You switch subtitles by opening the Timeline Index (SHFT+CMD+2 toggles), then press “Roles”. The English and Spanish subtitles will have a separate button to enable or disable them. I’ve used MacWhisper extensively and it works well: https://goodsnooze.gumroad.com/l/macwhisper
The latest version has an optional translation feature using the DeepL AI tool. It supposedly produces higher-quality translations than the built-in MacWhisper translation. That is a paid upgrade but you get 500,000 words per year free.
I think the most recent update to MacWhisper requires Ventura.
Another item I recently found (but have not tested) is SRT Importer 2, which lets FCP import SRT captions as titles. That’s in case you want the flexibility of a subtitled presentation vs the more restrictive caption display options. In theory, if the SRT output of MacWhisper was good enough quality, you could then convert it from captions to subtitles. FCP SRT Importer 2: https://ulti.media/fcp-srt-importer-2/
There is a new plugin from FxFactory called “Transcriber”. It supposedly does AI-based translation and optional conversion to subtitle format (not just caption format). I have not tried this yet: https://fxfactory.com/info/transcriber/?fbclid=IwAR1hpl9FUI-boHmbpk4Ofqpd17c45TTlxrQZS8oER-2fy3bq8oQzT3nXa2Y
-
I don’t think this has anything to do with FCP or video editing, but you could possibly follow some of the advice in this series of articles. If you need further help, you could probably get better advice on a MacOS forum.
https://www.makeuseof.com/mcafee-virus-pop-up-scam/
https://www.makeuseof.com/remove-quick-search-tool-hijacker/
-
Thanks, Ben. We gave him the same answer over on Apple FCP forums. Tom and I could not reproduce the problem.
https://discussions.apple.com/thread/254791414
-
The issue is when the black timeline thumbnails happen, does the multicam have footage on the MONITORED ANGLE? When you select a monitoring angle in the angle viewer, you are telling FCP “show me only this angle in the viewer”. Inside the multicam there may be footage at the playhead position — but if that footage is not on the monitored angle, it will show black thumbnails in the main timeline.
You can see the effect in real-time by clicking on different angles in the angle viewer. The moment you click another angle, the timeline thumbnails will change to that angle. If at some point in the timeline there is no footage for the monitored angle inside the multicam, the timeline thumbnails will go black.
Some camera codec formats have metadata that identifies the camera and you don’t need to label the camera in the inspector. However many (maybe most) do not, so it’s always necessary to label all the clips from each camera or recorder with a camera name or angle name in the inspector — before creating the multicam clip. Then the multicam will assemble correctly, it won’t have that “stair step” appearance, and you won’t see large black regions in the timeline.
-
Doug, you are correct! The thumbnails shown on the timeline will switch based on the selected monitoring angle. If monitoring an angle where the parent clip stretches across the timeline, then no timeline thumbnails will be black. If monitoring an angle (yellow box in angle viewer) where it’s a short parent clip, then only that short length of the timeline will have thumbnails. The others will be black. That is expected.
You’re right the OP’s case was only two cameras and was not assembled properly when the multicam was created. In turn that was likely caused by not labeling the clips correctly with a camera name or angle name in the inspector. E.g, cam 1 for the long clip and cam 2 for all the short clips.
-
This is just a guess, but I think the timeline thumbnails are not deleted by deleting render files. Also I think the multicam clip has separate thumbnails vs those for the parent clips. It might be possible for the multicam thumbnails to be corrupt or missing, yet the thumbnails for the parent clips to be OK.
There is no FCP command to delete thumbnails but you can do it manually by using Finder (carefully). Go inside the library package, Render Files folder and delete the two folders Thumbnail Media and Peaks Data. Restart FCP. See if that makes the multicam thumbnails reappear.
There was a fix in FCP 10.6 about thumbnails would sometimes not appear in the browser or timeline. So people running FCP versions before 10.6 might see that.