Steve Connor
2
Apple Final Cut Pro X Coins
2
COW Coins
Forum Replies Created
-
We need an “add fixed storyline” option, I can’t believe this would be difficult to do and it would do two things, it would effectively disable the magnetic timeline as secondary story lines do not default to ripple and it would also give you virtual tracks
You could then assign “roles” to these fixed storylines which would function as output patching.
“My Name is Steve and I’m an FCPX user”
-
Based on that workflow I can say FCPX is certainly not for you!
“My Name is Steve and I’m an FCPX user”
-
[Kevin Patrick] “It appears that this application moves Events and Projects in and out of the FCP X Event/Project folders. As opposed to you doing it yourself at the Finder level. Or am I missing some additional capabilities?
Steve, I was wondering if you tried, or looked at Steve Martin’s suggestion of managing FCP X Events/Projects with Disk Images?
https://www.kenstone.net/fcp_homepage/fcp_x_managing_disk_image_martin.html
Seemed like an interesting idea when I first read about it. But I have yet to try it. Outside of guessing (correctly) how much disk space you will need, I’m not sure what other downsides would be. Mounting and Unmounting seems simply enough. Quicker than copying, if you don’t have media inside your Event folders.
“It does simply give you a quick graphic UI that results in your folders being moved, it’s a bit of functionality that should be in FCPX. You can move manually but IMHO the app makes it easier to keep track of what is where.
Haven’t tried the disk image idea yet.
“My Name is Steve and I’m an FCPX user”
-
David, gap behaviour is perfectly logical and not a bug at all.
Gaps are the last line of defence between clips in the FCPX, if there is no gap then there can be no space between clips.
It would be illogical for FCPX to have behaviour where when you move or edit a gap, another gap is created!
It assumes by default if you are editing gaps then you don’t want that space there and moves everything accordingly. FCP7 does the same, if you delete a gap between clips it ripples by default.
The position tool manipulates clips without rippling, not gaps. You ignore the gaps because they can be overwritten by clips, they are simply the black space between clips as in FCP7, you don’t edit the gaps in FCP7 you move the clips to fill the gaps.
[David Lawrence] “On an open timeline, if I want to delete a clip or a range, I simply select and delete. In FCPX, a simple delete aways ripples by default. If I don’t want to ripple, I must insert a gap.
“Not true, Shift delete deletes the clip and leaves a gap automatically, you do not have to manage the gaps at all, you don’t have to touch them, you don’t have to create them.
“My Name is Steve and I’m an FCPX user”
-
https://assistedediting.intelligentassistance.com/EventManagerX/
This is what I use, it works perfectly.
“My Name is Steve and I’m an FCPX user”
-
[Herb Sevush] “Oliver –
Thanks for all your comments, and especially for the original article that started this thread.
I think the time has come for a thread like this. I think it is important to know what are the limitations and problems faced by editors who like and use FCPx in order to properly evaluate it.
Every NLE has it’s plus and minuses, even to it’s most enthusiastic users, and getting a sense of where the problems lie is important to anyone trying to evaluate it. It’s one thing to hear about pitfalls from those who don’t like it, and that information is valuable, but the criticism from those who do like it and use it is, if anything, more necessary when trying to gauge it. Seeing how Apple addresses those issues in upcoming releases will be a crucial part of that process.”
I’ve been using FCPX on a variety of projects over the last couple of months, long form event documentary, corporate promos, highlights video etc. The biggest issue for me has been stability before the .01 release. But I did expect problems in that area, the .01 release has improved stability considerably.
I can honestly say I haven’t hit any major roadblocks so far in editing terms, creatively it hasn’t stopped me doing anything I wanted to do and in many respects it has helped.
There’s certainly been a lot of “think” time but like any software I’ve needed less of that as time has gone on. To be honest I’ve enjoyed the change and the challenge, however I do understand that some people don’t want to change their workflows to the extent they would have to if they used FCPX.
I’ve been able to do this because my current slate of projects hasn’t required the major features that are lacking, however to continue using it I would need Multicam, external monitor support and export to Resolve at the least.
But as it stands I’ve had a very positive experience with it
“My Name is Steve and I’m an FCPX user”
-
[Herb Sevush] “I believe you posted this in the wrong thread.
“You are correct!
“My Name is Steve and I’m an FCPX user”
-
FCPX obviously has a lot of issues, pretty confident this has been covered, Oliver is mostly correct, I do however disagree with his claim the GUI is slower than FCP7, I haven’t found that to be the case at all.
The slip behaviour is just an example of another one of the annoying issues FCPX has.
Having said that for my workflow FCPX works well, I’ve been using it exclusively for a couple of months on a range of projects and have found that overall, for me, it hasn’t caused any serious issues. On the whole it has improved my speed of working and there is an awful lot I like about it.
I fully understand how it doesn’t and may never work for a large number of people in the industry. The next few months will show how serious Apple are about reaching the higher end of the market, if they are at all.
“My Name is Steve and I’m an FCPX user”
-
25i is the same format as you are recording, 25 interlaced frames = 50 frames, it isn’t losing any frames
“My Name is Steve and I’m an FCPX user”
-
I DO get this on 10.68
“My Name is Steve and I’m an FCPX user”