Forum Replies Created
-
[Oliver Peters] “First, I’m not totally sure what you mean by intranet.”
Consider a geographically distributed corporate environment, where camera files and editors could be in different states. GigE network speeds at best, with fiber, switches, etc, between.
[Oliver Peters] “For me, I see a big advantage in that there’s a more direct correlation between folder/subfolder/media location on your drives/NAS and the Premiere browser bins than there is with FCPX.”
This used to bug me when I switched to X, but these days I’m pretty happily divorced from most physical camera asset organization and very much liking the metadata+keyword approach. Relinking… I certainly had issues a while ago with X some time back when I used proxies more often than I do now. Relinking & proxies as pertains to a “remote edit” workflow could be a crux matter.
[Oliver Peters] “Beyond that, it gets down to the UI itself. “
Yeah, I prefer PPro’s tear-off panels to X’s semi-customizable UI, and I agree the UI animations & thumbnails in X need to hit the trash, but in whole I find editing is X is much faster than a track environment (YMMV of course!), so I just deal with those nuisances.
How robust would a large broll library in PPro (Bridge?) be? Say 5TB, 20,000 clips. The one I’m using in X is about 1.5TB, 6,000 clips, and it’s fast as I could want. Cut from it into other projects, file management no worries. Multiple keyword, metadata, etc, coverage.
-
Oliver, you post so frequently in here, perhaps you could help the OP’s question with a related one of my own – what is better currently about PPro over FCPX? I may find myself in the opposite case; a group I work with is considering a mandated use of PPro (currently editor’s decision). I’m in the minority on X, and would like some counter arguments. Though without some strategic advantage in X, I expect to lose the argument due to simple numerical weight.
Cost is not an issue, CS is on all desktops, graphics are split between AE & Motion, no collab editing though project “tag-teaming” is a possibility while currently infrequent, work is corporate short to long form, audio is relatively simple, color correction is also basic (ie; Resolve unlikely).
On strategic advantages; I could see proxy editing over an intranet as being a big asset. Another potential asset would be a curated broll library, probably 5TB minimum to start, with associated need of useful metadata. Graphics that would flow “top down”, preferably with “automatic” updates would be useful. Again, all this with an intranet in mind.
\”Constituo, ergo sum\”
Bob Woodhead / Atlanta
CMX-Quantel-Avid-Premiere-FCPX-AFX-Crayola
\”What a long strange trip it\’s been….\” -
Bob Woodhead
April 8, 2017 at 12:27 pm in reply to: Newbie Learning File Structure (Libraries, Projects, Events – Oh My!)A huge “What he said”!
The only training I’ve actually sat down & watched a series of was when switching from 7 to X. Too many basic concepts handled a different way in X. And some years in now, must say for the better.
Don’t create pain for yourself, do some tutorials!
\”Constituo, ergo sum\”
Bob Woodhead / Atlanta
CMX-Quantel-Avid-Premiere-FCPX-AFX-Crayola
\”What a long strange trip it\’s been….\” -
But it uses tracks. I though we were past those.
😀
-
Bob Woodhead
April 4, 2017 at 2:01 pm in reply to: best practices in setting graphics timings in bin?I should’ve said – the above can be done without the plugin aspect, of course. The basic idea of using a “slide reference cam” to visually edit stills to a presentation timeline is the key. The plugin just makes the rest of it as easy as the basic edit.
-
Bob Woodhead
April 4, 2017 at 1:54 pm in reply to: best practices in setting graphics timings in bin?Dunno if you’ve already shot the lectures, but if you haven’t – we do a fair bit of this, and have settled on this approach.
What you end up with is an “almost automated” way to have a presenter PiP with the slides. The “2 box” PiP is a plugin to fly the “2 box” on & off screen. End result:

Shoot the presenter in MS to MWS (MS if locked to a podium, MWS if walking). Shoot the presentation screen with any old camera. Audience, etc, cams as desired. Multicam the shots. In edit, scrub through the multicam, with the presentation screen angle showing. Connect edit the slide stills, easily aligning stills with presentation cam (which shows the slide changes by the presenter). When done (it’s fast, as it’s a totally visual process, no listening) grab the stills and drag them below the multicam. Cut your multicam, don’t worry about the slide cam. If it’s just the single cam of the presenter, even easier.
Now blade the multicam at the points the connected slides change. Drop the Motion-created “2 box” effect plugin onto the portions of the multicam you need slides. I made this in an hour or so, and it’s a huge time saver.
It’s got fly in/out options, a pop-up to select backgrounds, and some other controls. I just labelled it enough so I’d remember what it does. ???? Top drop zone is for the slide, uses the connected clip slides from below the timeline – just click & apply, done. Bottom drop zone is in case you want to use an image (or video) as BG to the rest. In the above sample I use the gradated BG.
When I want the slide full screen, copy & paste the connected slide from below the timeline to above, and use a dissolve. The build option pushes the presenter video down & to the side while the BG and slide push on.
Anyway, it may sound a bit convoluted, but in practice it’s wicked fast.
PS – some may prefer drop shadows, boxes with perspective, etc, but in practice we find this sort of video is all about the content. So we want to present the slides as large as possible, and try to break up the visual boredom by having the presenter in a smallish box. For complex slides we dissolve to full screen slide.
PPS – one of these days I’ll mod this plug so I can move the presenter video in the box. Right now that would screw up the fly on/off keyframes. If I’m really bored, maybe a TrackX integration so the presenter is Mocha-tracked in the box. 🙂
\”Constituo, ergo sum\”
Bob Woodhead / Atlanta
CMX-Quantel-Avid-Premiere-FCPX-AFX-Crayola
\”What a long strange trip it\’s been….\” -
Bob Woodhead
February 23, 2017 at 2:35 pm in reply to: Twitter Compressor settings? (or, is Compressor’s AAC low complexity?)Appreciate the info Craig!
\”Constituo, ergo sum\”
Bob Woodhead / Atlanta
CMX-Quantel-Avid-Premiere-FCPX-AFX-Crayola
\”What a long strange trip it\’s been….\” -
And if you find your Event is getting cluttered with “utility” keywords, just create a folder in the Event, and dump the clutter in there, never to see the light of day again.
It wold be awesome if Apple would publish specific FCPX hooks into Automator so we could go really crazy with personalized solutions.
-
Perhaps not elegant, but you could use a “preliminary” keyword first, like “meta_add”. Add this keyword to your clip selection, then use a smart folder that shows only clips with keyword “meta_add” (as they’ve disappeared from your “not keyworded” smart folder). Now you’re viewing just your new set of clips. Add more keywords. When you’re done, select all the clips in “meta_add” smart folder, and delete the temp keyword “meta_add”. This empties the “meta_add” smart folder and frees it up for your next set of clips.
-
AT THIS POINT, it is a fail. (mostly? like I said above, I didn’t think to see how it interacts with the Inspector – mea culpa).
Macbook PRO. Final Cut PRO. And the TouchBar is not customizable for a PRO. When working in the main X interface, all you get are a few shortcuts to the tools that we use most. We all know those shortcuts. (Yes, you also get the nifty timeline scrub tool.)
I would fully expect AT SOME POINT that X will get the same “customize TouchBar” menu option that Safari has. But as of now, it doesn’t, so I’m gonna call fail.
When X was 10.0.0 is was a FAIL. When it was 10.0.6 it was workable. Now it’s starting to shine brightly.
Don’t apologize & accept something that’s wrong. Insist that it be better. And perhaps it will.
