Whoa! Today FCPX crashed for something unrelated to BMD Desktop Video.
Process: Final Cut Pro [724]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCut
Version: 10.2.3 (276640)
Build Info: ProEditor-27664000056000000~1
App Item ID: 424389933
App External ID: 815823966
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Final Cut Pro [724]
User ID: 505
Date/Time: 2016-04-12 11:48:12.814 -0700
OS Version: Mac OS X 10.10.5 (14F1713)
Report Version: 11
Anonymous UUID: 162D488E-82D0-5A77-9E01-6CD6CDC5D94C
Time Awake Since Boot: 5600 seconds
Crashed Thread: 15 com.apple.helium.rq.gpu-ru1.vs0
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000021
What happened? I grouped a bunch of clips in a Compound Clip, and applied a global grading with Color Finale plug-in to the CC. I tweaked Wheels and Curves and I was happy with the result.
Then I went to Share my cut and Export the Timeline to ProRes422 ... and ... Crash. A meager 120MB out of 2.4GB got written to disk.
On Reloading, my Project was exactly where it was before the crash - Compound Clip created and Color applied. No need to retrace and redo my last steps! Now that is one thing I appreciate about FCPX. :))
From there I went on to Share and export again. No crash, Done.
Why can't I nest an empty Sequence? It's an odd Premiere behavior: I cannot nest an empty or a 1 frame long Sequence, it has to be at least 2 frames. OK fine.
Let's say I nest a non-empty Sequence, and then I delete some material from it, the nested Sequence still shows the entire length from when it was drop-nested.
OK so then why can't I nest an empty Sequence, with say a default duration of X frames, and adjust its length to what is needed later?
Also, if I specify a IN and an OUT to my Sequence, and then I nest it, I can extend the boundaries on the nested version.
- Original Sequence with IN/OUT @ 3:18 and 9:28, total length about 30 sec.
- Nested Sequence was nested when it was longer (42 sec.), so it's showing "missing material", Premiere is not updating to its current length. Nowhere does it show its current IN/OUT @ 3:18 and 9:28.
This behavior is counter intuitive to me. Most of the time I use nested Sequences to assemble several individual Sequences/scenes. As I modify the individual Sequences, I want the assembly Sequence of nested Sequences to update its content. It's not.
And I can't see a way to quickly hand adjust the assembly Sequence either, as it does not take into account the new IN/OUTs of my individual Sequence.
Premiere will ignore any IN and OUT set in the nested Sequence and will nest from the start of the Sequence to the end of the last clip contained in the Sequence.
The license snafu (http://humanuser.blogspot.com/2016/01/really-avid.html) has been FIXED! Or so it seems, since I can now start MC 8.4.5 8.5.1 with my OWN system ID and Activation #. Alleluia!!
Application Manager 2.5.2.160 seems to be working as it should! Previously I had to go to my Avid Master Account, (http://humanuser.blogspot.com/2015/11/avid-media-composer-842-upgrade-like-pro.html) to find the installer and download it to my computer, since clicking "Update" was not working.
Now, I click "Update", and off it goes! It's downloading now, we'll see if it goes through.
Yes it did, ah! Unlike Adobe Creative Cloud, AM does it in two steps, ONE it downloads the img installer inside: Boot/Library/Cahces/Avid/AppManager/Downloads, then TWO you must click "Install", which simply runs the img installer. OK, fine.
And... Done! Good to go! MC 8.5.1 installed, up and running, finally!
In Apple Motion (5.2.2) I use a Point or a Spot light with Falloff on a flat animated background. In the Canvas it all looks great, no banding. (There really is no banding on my display, unlike on this page where I can see some, thanks to crap Google conversion of my image.)
When I export to ProRes4444 or 422, whatever, and I play the file into QT or FCPX it has banding all over.
What the hell is this?
I have to add noise onto my background to get rid of the banding, but I should not have to do that with 10 bit output & Best settings. It's there no matter the color, more visible with blue.
After Effects outputs a CLEAN gradient in a similar setup: spot light on a flat bkg., CLEAN as it should be.
What's with the crappy Fallout Spot and Point lights? Apple FIX THIS please!
Adobe is finally giving us a proper color correction tool: Lumetri.
In CC 2015 it's accessible via the "Color" tab atop the workspace. Was it already there in previous versions in the Video Effects? It looks decent and responsive.
--- Update: As of 3-8 this issue has been fixed.
The App Store is showing an update for Motion 5.2.3 even though Motion 5.2.3 has already been installed... Annoying.
