Tangier Clarke
Forum Replies Created
-
Brandon, consider WaveAgent to address the sampling header to the audio file. To be honest, I have had the best result with syncing using FCP X more than any other NLE. With third party apps, PluralEyes I only use if I have to and usually only for one feature – the sync drift. It’s not a product I am fond of for various reasons which I’ve gone into in detail on other threads/forums.
I wrote this (https://forums.creativecow.net/thread/344/49664) some time ago. There may be some nuggets in there that are helpful.
-
While we’re on the subject of broadening base, looking forward, “borrowing” ideas from other apps…I just need Apple to implement something like Project FastMask in the next version of Motion (or FCP X but I know that’s not likely)…
and get on with it with batch exporting out of FCP X or to Compressor for that matter. I loathe the idea that one day that alone is going to be the new “killer feature”.
-
I think the first question is a bit confusing, but I’ll try to help. When you duplicate a new project (aka a storyline/timeline) and you have a multicam clip or clips on that storyline, you should be able to edit that without it affecting the multicam clip in the browser. The multicam clip in the browser and the one edited in the project are separate instances of the same clip.
I have not experience any difference with audio in NLEs between Resolve, FCP X, and Premiere Pro. Not saying what you’re experiencing isn’t real, but I haven’t had that experience between three NLEs.
Your third situation is a mystery. Confirm that what you’re experiencing in FCP X’s browser is the same as the import window. Try checking with EditReady (or KYNO – but I’ve had artifacting issues with KYNO with AVCHD footage) as well to see how it combines clips and the timing of them. I use that a lot to preprocess my clips.
-
There really is no right answer, but I’ll second that we store our masters as ProRes 422. However we’re mostly shooting with Canon C100s, Sony A7s and Panasonic GH series cameras. So I suppose it really depends on what your shooting format is. I will say though that when we’re licensing our content we’re being asked to deliver ProRes 422 HQ so either way we have to transcode our masters.
-
This is a very meaningful and insightful discussion and it brings me to one very uncomfortable thought: I lament the notion of having to work in a track-based system, non-magnetic timeline system. Granted I realize that AVID, Resolve, PPro are simply tools, but the notion of how theses RAW formats are/could be tethered to NLEs and cameras heightens my awareness of just how much I enjoy using FCP X. Resolve would be my second choice and it is insanely feature-rich and an app that I jump to for specific features. However from a stability, performance, and workflow standpoint FCP X just stays out of my way and let’s me work (mostly). I am sure I would adjust as needed should any of these RAW formats really affect the NLE usage landscape, but boy it makes FCP X feel more like an island…one that I want to stay on, but at some point may not make logistic sense to.
-
Yep. I sent the full list. Had to retype though and send multiple feedback submissions since the field space limits how much one can send.
-
I haven’t installed the trial yet, but my thoughts were the same as mentioned above in that at first glance it seemed a lot like Magic Bullet Looks. I like the tools built into FCP X and will have to do my homework to get the most out of Resolve.
-
LOL – this will take up an entire power strip or PSU.
-
I forgot one long-standing thing that I wish were resolved. With it’s database backbone, I wish FCP X had some way of restricting the creation of duplicate or sometimes multiples of the same clips in a library. Too often I cam cleaning my events and libraries to isolate the original imports that have been created and their keywords.; clips that are in use and not. This takes up too much time. Merging same clips and their information (metadata, ins and outs, etc.) could be a welcome option.
I find that duplicates and multiples of clips seems to be just par for the course working in FCP X and especially when moving XMLs back and forth between editors. The organizational and search capabilities of FCP X are great, but this is one item I wish Apple would address…and Reveal in Browser working better in identifying the clip. I tend to have to Shift+F several times before I can see the clip.
-
I’d be happy with just the ability to batch export from FCP X or batch send to Compressor, better relinking tools and reporting, batch syncing, and for FCP X to be able to read the chapters in a Quicktime that it created…just for starters.
Some additional nice treats would be:
- To have the crop and retime buttons/menus, all other buttons, and timecode display available above the timeline when using viewers on a second display.
- Being able to rename clips in the app which would also change in the finder the way FCP 7 did. This feature alone would allow me not to have to use EditReady.
- To have the exported role names in a multitrack Quicktime come back into FCP X as those same names.
- To be able to shift-select all channels at once (rather than manually selecting each one) in a polyphonic audio file.
- Have the forward/backward selection (using T) from FCP 7 back.
- Speed ramping curves more akin to FCP 7
- Expand a compound clip in place, rather then in a storyline.
- IG Story preset for Compressor – yep it’s a part of my workflow now – vertical and 30p. I can only do this in FCP X at the moment.
- Have content scaled inside a mask do actually that.
- Some smart Apple-esque features like auto detect the best audio channel and disable the others for dialogue. Not perfect, but just a starting point to save time from enabling/disabling channels. Another unique feature would be auto marking where the clapper hits…for those times when you have to manually sync content. These two are far fetched but they would be tantamount to the magnetic timeline for me in reducing clicks and time.
- The ability to save a Compressor batch session. Couldn’t we do that a while ago or am I imagining that?