Axel wrote: Then there is the aforementioned difference in general approach. As a wedding videographer, I have a story, a pattern, a typical "template" (that's only adjusted to fit the individual wishes of the clients) beforehand, I shoot with my 6-7 plot points in mind, the rest is B-roll. I import the footage with that existing concept and the fresh memories ready, and I favorite and tag accordingly. That's what I meant with "executing". Nobody can tell me that he is faster elsewhere then.
arc wrote: Perhaps you could do a simple tutorial of your workflow. I would watch it.
I literally have a template. I created an empty Library with an all-for-one library-wide smart collection that searches for framerates and standard set of keywords (like Intro, bride, groom, make up, church, photo shoot, dance, marryoke, B-roll). I don't use "close up" and "wide shot" or the like because these things are obvious in clip view anyway. I exported this Library as an XML. Right in the night after I return, I open this Library, rename it to "Jane & Joe" and import everything by copying it into the Library - with "create proxies" checked. Had I to worry about disk space (which I don't), I would instead only copy clip selections (FCPX's way to 'smart render'). It's a bad habit that I don't do that, in theory. In practice, it makes no difference.
Then I open the "Organize" workspace (actually I open "Axels Organize workspace", where the viewer is 100% UHD) and let the video play continuously. Without stopping with "k" very often, I hit backspace to reject whole clips (of which I already know they're useless because the shoot began that same morning), i,o and f for favorites (basically subclipping). When I saw enough of the current clip, I jump to the next with down arrow. I typically have about 300 video clips (and 15-20 audio clips , I let the recordings run, because I have no sound guy, but that's another story) that add up to short of 2 hours. Length of the finished video is usually between 5 and 8 minutes.
The first run does not take an hour. Everything is imported by then, proxies are long created. Then I go to bed.
On another day, I filter for favorites, play them back continuously and add the keywords from the said collection that was saved in Template.fcpxml by hitting ctrl 1-9 . Half an hour.
Sometimes I don't need to tag everything. The very purpose of filtering is to have a manageable amount of clips in the browser. It's absolutely essential that during editing (standard workspace, viewer set to "proxy") there never are more than 80 clips shown at once, be it list view or clip view. But 80 are still way too many. Once I realize that I'd get below 20, I stop multiple tagging. For instance, the whole ceremony in the church will always be cut down to around 30 seconds, and the content is always the same (some crying relatives in CU as B-roll, those'd be connected). So there need to be rejected, favorites (done before) "church" and "B-roll"- 30 at the most - easy to identify in clip view.
Time check: I spent 90 minutes so far. I could exclude "B-roll" from any of the stages, "select all" and hit "e". This would take another 5 minutes to have a rough cut. Trimming and adding B-roll? Depends, but doesn't take long. Audio clean-up is a little more time-consuming, because I don't use the "Audio-Only" - Transition (because it translates to a video transition in Resolve).
In reality, of course, the couple chose music, and I have to edit to it's rhythm and emotion. The "story" is not straight and chronological. There's a lot of finetuning involved, the timing must fit, and that means retiming on a regular basis. I always assign different video roles for different frame rates, so that I immediately see what can be done through the different colors.
A challenge is the marryoke-part, which replaced the old-fashioned congratulations with talking heads. The wedding guests only sing a line from the song, and all those snippets have to be aligned to the whole song (sometimes manually) and the voices must be mixed with the music (half"live", half "playback").
So it was a lie if I said, I'm done in 5 hours (that's when I call it a day) . But never more than two days.
Thank you for the response. Having said that I would like to see a tutorial so I could see how you are navigating the FCPX GUI. Having said that if I were to make a quick video demonstrating how I have the GUI of Premiere Pro laid out would you watch it? I think after watching my video you might be incline to want the FCPX GUI to be revamped. I am not saying FCPX doesn't work. I am saying it could be better.
arc wrote: Thank you for the response. Having said that I would like to see a tutorial so I could see how you are navigating the FCPX GUI. Having said that if I were to make a quick video demonstrating how I have the GUI of Premiere Pro laid out would you watch it? I think after watching my video you might be incline to want the FCPX GUI to be revamped. I am not saying FCPX doesn't work. I am saying it could be better.
As my workflow description proves, I'm not the most efficient editor. I am an amateur who films weddings as exercises, and I ask for a peace of equipment as a compensation. If I had to do this for a living, I probably starved to death. So I'm not the right person to teach others how to edit.
One who is is Thomas Grove Carter (joema linked to him on the previous page). Here is my incentive to become a less sluggish editor:
I recommend that you watch this intently. Yes, it is rehearsed, but it's inspiring, at least for me.
Now, speed isn't everything (comforting myself).
Go ahead and make a Premiere demo. I bingewatch tutorials for pleasure, as others watch GOT. Right now I'm watching Fairlight tutorials to get an idea of what could be missing audio-wise. And I remember that I had been watching a very similar thing many years ago when I had purchased Larry Jordans Soundtrack training. Didn't ever make use of it in FC Studio back then, because I finished my audio clip-wise in the timeline, as I do now.
just to put in my tuppence worth, I have tried to use Resolve twice on a mac with 16gb ram and running off fixed 1tb hard disc and it kept crashing. I think it needs a very robust and powerful computer behind it in order to run efficiently, certainly out of my range so I went back to fcp, which has much lower computer requirements.
Nodes in Resolve isn't only the beautiful icons, or comfortable presentation of effects, but also and a work of effects in any configuration.
A parallel connect of effects from source, layers, keys. This is very impoertant.
You can't make it in fcp x. There're only a sequentually performance. The performance from 90/00x years. Excuse me.
No, I mean... it really was) A good example, why you can't always use sequentually one be showed on the example when you select a reds in picture, that gave a certainly saturation and lightness and after it you want to select a yellow colors with! other saturation and lightness for color correction. with a hsl paradigm you can't make it. Only with two effects, or with 3dlut creator (3d hsl mask) But in 3d hsl you can it more harder, than with two nodes.