Tangier Clarke
Forum Replies Created
-
You’re correct and I am fully aware that I can do that. I could also put the browser in list view and just look for the 13 then go back to icon view. However my typical workflow has been to quickly search for what I need inside a synced smart playlist using the scene. I don’t recall having this much trouble. Perhaps there’s something unique about the media/project I am working on.
-
You can select the clips in the timeline (even as a group by searching for them) and select “fill” in the spacial conform parameter of the inspector (the video inspector). It’s usually near the bottom.
-
It’s the simultaneous in the same library workflow that is sought.
-
Oliver I agree. I have been using Resolve to get more familiar with it. If I had to choose another NLE of choice of the ones available it’d be Resolve. However Resolve has always been that app that is feature rich, but does’t perform as fluidly nor as intuitively as FCP X. There’s really a stark difference between FCP X and other NLEs in my opinion. Often to get similar performance on other NLEs, I’d have to have a more robust computer than FCP X requires. I am sure others may have different results based on the media they’re working with and their workflows. I’ve also often felt that I wish Resolve and FCP X would just have a baby already and get it done. In my heart of hearts what I mean by that is I wish FCP X would incorporate many of Resolve’s features, not the other way around. I don’t know how many ways I can say it though. I loathe [now] a track-based NLE even though I still use it in Premiere Pro and Resolve. As great and as many features PPro and Resolve have, they just don’t get out of my way the way FCP X does. I even wonder sometimes how I got along with FCP legacy for so many years, but that’s just a matter of perspective of course; hindsight now.
I wish Apple was a little more transparent about the FCP X direction and if they’re just comfortable where they are. With every feature added to PPro and Resolve at their price points respectively (subscription included) i just can’t help but feel like the FCP X is getting strangled slowly. Yet, with all of the added features and capabilities of other NLEs that FCP X either doesn’t have or relies on 3rd party tools to achieve, I find that those capabilities have yet to be deal breakers for me to jump ship. At the end of the day FCP X just lets me work so fluidly that to date I haven’t gotten that experience on another NLE. I fully recognize though my perspective is correlated to the type of work I am doing or anyone is doing for that matter. My latest is an indie feature called Jezebel just released on Netflix (shameless plug). If I were working in teams more regularly and had to do more color work more often then of course I’d likely be in PPro (reluctantly) or Resolve because let’s face it – where are you going to find a studio running FCP X with PostLab and Color Finale 2 and a Jellyfish (at least)?
-
Very good and thought provoking points Oliver. Thank thank you.
-
Oliver I was going to post a thread called “Does this disturb you?” or something to that effect until I saw your post. The announcement of Adobe Productions does give me sincere concern. As much as I love FCP X, that Apple still hasn’t built in a robust multi-user workflow seems to be giving Adobe even more room to get further entrenched in the workplace. Granted I udders understand that technology over the years has gotten to the point where you don’t always need more than one editor and one person can do many things. Could it be that Adobe is going directly after AVID with this update and in one way or another ignoring FCP X and it’s potential. It still seems to be built around co-located teams with a NAS as Joe mentioned. This his is yet another thorn to deal with for us FCP X advocates. I don’t mind using Premiere Pro, but I don’t prefer it. We still have yet to see how it works in real practice, but that it’s available at all is great news for those who prefer PPro even with the persistent bugs it may have.
I read that announcement and for a brief moment saw the light dimming on FCP X, but it still lets me work more fluidly and faster than PPro and DaVinci for now. Apple has make great strides, but these incremental improvements aren’t enough to quell my angst about it’s survival at times.
I prefer not to go back to tracks…forcibly.
-
My understanding was that using the “Send to Compressor” feature within FCP X will offload more of the work in Compressor to the GPU giving you improved performance.
-
As an added bonus, you may really enjoy this automator tool. I have found it very useful. The link below will show you how to get SMS messages to your phone (and maybe your Apple Watch if you have one) when Compressor jobs are complete. You can walk away and be alerted!
-
Here’s some initial tests I ran after the 10.4.7 update just to see what would happen. I had hoped for better. Perhaps with Catalina I’ll see better numbers.
– Majority Picture Media: Multicam Sony FS7 4K (3840×2160) @ 23.98 AVC Intra, Linear PCM, Sony S-Log3/S-Gamut3.Cine (2-2-1) applied automatically by FCP X, Color Profile (2-2-2)
– Other Picture Media: GoPro Media, Canon C-100 MKII Media, created animated graphics at above frame rate/size
– FCP X Storyline Settings: 3840×2160 @ 23.98 FPS, Stereo 48 Khz sample
– Storyline duration: 37 minutes, 56 seconds
– Export Settings: Apple ProRes 422, Multitrack Audio Roles (how I usually make them for D, M, & E)Computer 1: 2016 MacBook Pro 2.7 GHz Intel Core i7 / 16 GB of RAM / Radeon Pro 455 2 GB & Intel HD Graphics 530
– Mac OS: 10.14.6 Mojave
– Media Source Drive: Western Digital USB 3 desktop hard drive
– Media Source connection to computer: USB-3 thorugh USB-C connected hub
– Destination drive: G-Tech SSD Slim USB 3.1 drive
– Destination drive connection to Computer: USB-C
– Export Time: FCP X 10.4.6 – 53 minutes
– Export Time: FCP X 10.4.7 – 1 hour 1 minuteComputer 2: 2013 Mac Pro / 3.5 GHz 6-Core Intel Xeon E5 / 64 GB Ram / Dual AMD FirePro D500 3 GB Cards
– Mac OS: 10.14.6 Mojave
– Media Source Drive: Western Digital USB 3 desktop hard drive
– Media Source connection to computer: USB 3 (Type A) to USB 3 Micro B
– Destinatino drive: G-Tech SSD Slim USB 3.1 drive
– Destination drive connection to computer: USB-C to USB 3 (Type A)
– Export Time: FCP X 10.4.6 – 29 minutes
– Export Time: FCP X 10.4.7 – 28 minutes -
If I could get a built-in planar tracker and more options for setting up parameters (and separating them), for publishing to FCP X I’d be very happy about that.