It’s possible you’re exporting to a format that your Mac can’t play back very well? Maybe try going to another format and see if the problem persists?

I’m afraid this isn’t possible. A sequence of commands would do what you want, something like jump to next marker, move back five seconds, mark in, move forward ten seconds, mark out, favorite, but it’s not totally straightforward. You’d need a third party app to wrap that together. Command Post might be able to this, or help you do it. It might be worth asking this question on the Command Post Facebook group? Good luck!

If you need to integrate to an existing workflow, it will probably be Adobe-based. If you work alone, it depends if you need some of the specific features of one program or another. Photoshop is certainly the industry standard, but that doesn’t necessarily matter.

Unfortunately you seem to have hit an edge case with a third-party upgrade that didn't work with the new file system, APFS. While Apple should probably sell a boot drive upgrade themselves, every time you install a non-standard part there's a small risk of incompatibility, immediately or down the line. It's not really the third-party SSD manufacturer's fault, because APFS hadn't been released when that drive was released. It's good Apple were able to eventually help you, but there's always a risk, and you got unlucky. I don't mean to sound flippant — I've had similar issues myself! I've upgraded boot drives and GPUs in my (older) Mac Pro, and while they usually worked OK, there are lingering issues. For example, I don't have a boot screen with my third-party GPU, so I can't use recovery mode or easily boot to alternative drives, and I can't return to the original GPU because a colony of ants made a home there. Infested with bugs, for real. :) These days, I mostly focus on external upgrades, which are faster and cheaper than before. To avoid further issues, you could buy an external Thunderbolt enclosure for your new drive, pop it in there, then reinstall the original boot drive. You can then leave the external drive permanently connected. The new Mac Pro might have the same limitation regarding the boot drive (not sure yet) but at least you will be able to install additional internal drives (via PCI) rather than replacing the existing drive. Apple have listened to pro needs, and the new system will be far more open to upgrades. It took a while, but the situation has improved.

Apple have some official advice about failed exports here: https://support.apple.com/en-au/HT207791 Here’s also another page with help: https://www.fcpx.tv/tutorials/shareexport.html If the problem is with missing media, try making a new library and dragging just your final project into it. Needed media will copy across and you might be able to spot the problem. It’s also worth noting that you’re on a really old version of FCP X, and while updating in the middle of a project can be dangerous, not updating for years opens you to serious problems too.

Course author here, and yes, that’s going to be difficult to correct, because it’s such a drastic change. In general you can’t correct color to “normal” when the original source video is so heavily tinted. To try, you would apply a color correction, likely color wheels because of the Hue control, and correct at the start, then add a keyframe. Move a few seconds along, then change the settings to correct it again, and repeat all the way along the clip. That should improve things but won’t be perfect. Usually people will forgive odd lighting in an environment like this though.

Hi, course author here. Normally, when you use the Cross Dissolve as you've done here, it would do what you want; the entire screen should *not* go black as is shown. I think what you're seeing is a result of the specific fade-out mask effect you've used — but I can't be sure. There's a good chance that it's interfering with the crossfade, and if you use a Graduated Mask effect instead, the whole thing should work properly. Otherwise, you could try using the Opacity fade handles in the Video Animation editor, as mentioned in the manual linked above. Select the top clip, press Control-V to open Video Animation, press the small icon to the top right of the Opacity section, then drag the fade handle on the right edge in to the left.

Course author here. It turns out that you can get slightly sharper output if you edit 4K material in a 4K timeline and then export 1080p from there. However, if you scale the video at all (punching in) then the sharpness advantage disappears. The difference is fairly minor, but you may be able to see it.

If you're experiencing crashes with entirely new libraries and new clips, then you could have a lower-level issue. Have you tried creating a new user account and exporting from there? If that works, you've got some kind of preference problem on your existing user. Otherwise, if it's a more mundane problem with your library, try to delete generated project files with the instructions at #3 here: https://blog.frame.io/2016/09/13/recognize-fix-common-problems-fcpx/ Lastly I would note that you're on an older version of FCP X — 10.4.8 is the current release. This could be the problem, or contribute to it. You can still run 10.4.8 on macOS Mojave if Catalina would cause problems.

Very strange, but glad you've sorted it out. I suspect you've hit a weird edge case, but I also suspect this particular bug won't be fixed, as the current release of FCP X requires macOS 10.14.6 or later. Let Apple know if you can, though?