My uploads to Frameio sometimes get stuck to some 88%-94% never to reach 100%, nothing moves.
When this happens, I noticed that if I click the Pause (||) and then the Play (>) buttons situated on the left of the video placeholder when you hover over with the mouse, it seems to trigger something and the upload resumes and finishes - it backtracks to 80%-90% usually and then goes to 100% from there.
Not sure why this happens in the first place, in any case this beats having to start again a complete upload from the beginning. Do not click the Stop button (X) on the right of the video, else game over...
Monday, April 18, 2016
The World's Longest Invoice
Freelancers waiting to be paid for their services... This is slowing down the economy as a whole.
https://www.worldslongestinvoice.com
https://blog.freelancersunion.org/2016/03/28/add-your-ious-worlds-longest-invoice/
https://blog.freelancersunion.org/2016/03/29/he-went-undercover-get-scoop-serial-deadbeat-client/
https://www.worldslongestinvoice.com
https://blog.freelancersunion.org/2016/03/28/add-your-ious-worlds-longest-invoice/
https://blog.freelancersunion.org/2016/03/29/he-went-undercover-get-scoop-serial-deadbeat-client/
How to sync mixed audio into FCPX
After the cut is locked, I export a fcpxml of the project, then run X2Pro to create a ProTools Session. (See: http://humanuser.blogspot.com/2016/04/fcpx-to-protools-via-x2pro-ironing-out.html)
Mixing is done into ProTools, and a 4 tracks mix (Stereo Dialog stem/ Stereo Music stem) is Bounced out of ProTools to sync back into FCPX.
In the Timeline, select the original Music and click (V) to mute it. Select all the video clips, and then "Expand Audio Components" (Control+S), then select the audio portion only of the clips and click (V) to mute the audio only.
Now all your audio is muted. Collapse Audio/Video (Control S.)
Import your mixed stems, make sure to select the proper Pan Mode - stereo in this case, and sync them to the In-point. Done, now your final image plays with your final mix, ready for Share / Export.
Mixing is done into ProTools, and a 4 tracks mix (Stereo Dialog stem/ Stereo Music stem) is Bounced out of ProTools to sync back into FCPX.
In the Timeline, select the original Music and click (V) to mute it. Select all the video clips, and then "Expand Audio Components" (Control+S), then select the audio portion only of the clips and click (V) to mute the audio only.
Now all your audio is muted. Collapse Audio/Video (Control S.)
Import your mixed stems, make sure to select the proper Pan Mode - stereo in this case, and sync them to the In-point. Done, now your final image plays with your final mix, ready for Share / Export.
Thursday, April 14, 2016
FCPX to ProTools via X2Pro - ironing out the hiccups
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.
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.
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.
Subscribe to:
Posts (Atom)