1) If the ProTools session shows mono music where it was stereo in FCPX, chances are the music clips are connected to a video clip as opposed to the "empty" Primary Storyline.
How to fix:
- Select the video clip(s) and Lift From Storyline so that the connected music connects to a Gap in the Primary Storyline.
or (faster),
- Select all the connected music clips and Create new Storyline. Make sure the newly created Storyline connects to a Gap in the Primary Storyline.
2) When using L and J cuts - or overlapping audio in FCPX, X2Pro will checkerboard the audio onto multiple tracks.
How to fix:
- No need to fix this as it is a necessity going from trackless FCPX to tracked ProTools.
3) ProTools is showing the same audio clip multiple times: 2 instances on two different tracks, even up to 9 instances on 9 different tracks!
How to fix:
- The same separate audio clip got connected twice to the video clip, probably confusing X2Pro, or FCPX XML Export. Select the clip in question, Reveal In Browser (Shift F), Right+Click the Clip to Open in the Timeline. Check the presence of dupe audio, delete the extra audio. Now go back to your Timeline and for each instance of the clip, Matchframe (Shift F) and replace the clip in the Timeline with the "fixed" synchronized clip from the Browser.
Thursday, April 14, 2016
Wednesday, April 13, 2016
How to fix a problem installing Frameio extension for Premiere Pro CC2015
Update:
There is a new installer from Frameio:
----------
Original post:
I was trying to install the Frame.io Extension for Premiere Pro only to find out that Window/Extensions was greyed out in Premiere.
After running the Frame.io installer a couple of times, no luck. Window/Extensions stayed greyed out:
Obviously something was missing.
So I then went to Window/Browse Add-ons, which started a Safari page with Adobe Add-ons on it --- and... No Frame.io add-on there, but I got the Wipster Review Panel add-on for PP.
That synced fine to my CC and then appeared in PP under Window/Extensions - not greyed out anymore! Cool, great... Except Frame.io still did not show under Window/Extensions.
Somehow it looked like the Installer was not installing, so I searched for Frameio on my HD and under User/Library/Application Support I found a Frameio folder with a PremiereInstaller folder in it, and inside this folder was a install.txt with the following:
2016-04-13 18:08:52.625 Frame.io Premiere Installer[1870:197477] Launched installer
2016-04-13 18:08:55.105 Frame.io Premiere Installer[1870:197477] SUCCESS download json
2016-04-13 18:09:03.201 Frame.io Premiere Installer[1870:197477] SUCCESS download zxp
2016-04-13 18:09:03.201 Frame.io Premiere Installer[1870:197477] FAILED setting permissions for /Library/Application Support/Adobe/CEP
All right, we're getting somewhere, I then looked into /Library/Application Support/Adobe/CEP/extensions and found out that the Wipster "widget" was in there:
I also noticed that permissions for the Adobe folder looked OK, on the other end, the permissions for the CEP and extension folders looked funky:
Notice the "Fetching..." in the extension folder permissions? To straighten this up, I went to the Adobe folder info and "Apply to enclosed items" the same permissions, and this fixed the "Fetching..." oddity, to "system".
I installed the Frameio for Premiere again, and this time it appeared in the extensions folder:
And this ultimately fixed the problem, now Frameio extension shows as it should under Window/Extensions:
There is a new installer from Frameio:
It came to our attention that some Windows users and some Mac OS X users running 10.10.x were having trouble with the installation. We've since fixed the issue so you should be able to download again. Please grab the new installer below.
If you're still having trouble please shoot me a message. Im happy to help!
Best,
Thomas, Frame.io Integrations Engineer----------
Original post:
I was trying to install the Frame.io Extension for Premiere Pro only to find out that Window/Extensions was greyed out in Premiere.
After running the Frame.io installer a couple of times, no luck. Window/Extensions stayed greyed out:
So I then went to Window/Browse Add-ons, which started a Safari page with Adobe Add-ons on it --- and... No Frame.io add-on there, but I got the Wipster Review Panel add-on for PP.
That synced fine to my CC and then appeared in PP under Window/Extensions - not greyed out anymore! Cool, great... Except Frame.io still did not show under Window/Extensions.
Somehow it looked like the Installer was not installing, so I searched for Frameio on my HD and under User/Library/Application Support I found a Frameio folder with a PremiereInstaller folder in it, and inside this folder was a install.txt with the following:
2016-04-13 18:08:52.625 Frame.io Premiere Installer[1870:197477] Launched installer
2016-04-13 18:08:55.105 Frame.io Premiere Installer[1870:197477] SUCCESS download json
2016-04-13 18:09:03.201 Frame.io Premiere Installer[1870:197477] SUCCESS download zxp
2016-04-13 18:09:03.201 Frame.io Premiere Installer[1870:197477] FAILED setting permissions for /Library/Application Support/Adobe/CEP
All right, we're getting somewhere, I then looked into /Library/Application Support/Adobe/CEP/extensions and found out that the Wipster "widget" was in there:
I also noticed that permissions for the Adobe folder looked OK, on the other end, the permissions for the CEP and extension folders looked funky:
Notice the "Fetching..." in the extension folder permissions? To straighten this up, I went to the Adobe folder info and "Apply to enclosed items" the same permissions, and this fixed the "Fetching..." oddity, to "system".
I installed the Frameio for Premiere again, and this time it appeared in the extensions folder:
And this ultimately fixed the problem, now Frameio extension shows as it should under Window/Extensions:
Tuesday, April 12, 2016
FCPX crash
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.
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.
Tuesday, April 5, 2016
Premiere and Nested Sequences
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.
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.
Monday, March 21, 2016
Alleluia! Me Avid MC (8.5.1) is finally working as it should! (For now.)
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!
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!
Wednesday, March 16, 2016
Apple Motion exports an animated flat background illuminated with Spot or Point light + falloff with bad banding
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!
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!
Tuesday, March 8, 2016
Lumetri
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.
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.
Subscribe to:
Posts (Atom)