James Culbertson
Forum Replies Created
-
What are you using to calibrate your computer monitors?
-
Turns out it was a combination of titles and iZotope RX4 dialogue denoiser both applied to a clip. Either by itself worked fine, but both together froze renders at 0%.
I upgraded to RX5 and things are fine now… though RX5 dialogue denoiser appears to be a bit unstable when applying to a clip.
-
[Craig Alan] “What do you think of FXP for FCP X?”
How about dropping the X and just calling FCPX FCP. That way we can piss off a few editors even more, and elongate the “debate” for another couple of years. Plus, there is the added benefit of completely confusing everyone as well.
Though to be honest, I’ve already started dropping the X among colleagues that are using FCPX anyway.
-
[Steve Connor] ” An interesting thread and some great points, the only thing I can add is that I don’t care what Apple chose to call them, it could have Hilda, Dennis and Gertrude, as far as I’m concerned. It took me about 10 mins to get used to the new names and that was that”
Agreed.
I’ve been thinking about using BBedit to replace every instance of “event” in the FCPX package with “bin” and see if that actually changes things, and if FCPX still works afterwards. Easy enough to reinstall. (…only half joking.)
If Apple gave editors the ability to modify interface names like it does key commands, a lot of folks might be happier with using FCPX. …OK, maybe not.
-
[Tony West] “A bin is a name for a folder that holds footage from an event you covered. Apple just short cut it and called it the “event” itself.
I don’t really get the problem,…”
There is no problem. There are people who have problems. And they only have problems because of an attachment to names they have used in the past. For new editors, event makes a lot more sense than bin. I like bin better than event because of my history (first few edits were on a flatbed), but I also know that times change and you have to adapt or be left behind. I’m not going to let a word get in the way of my using a better tool.
-
[Craig Seeman] “Of course none of the above are exactly the same. It’s not only new language but new features. But one should be able to use old familiar language to learn the new language.”
True. In many cases, it is fairly intuitive to find equivalencies. But I’ve found that a quick Google search provides the answer for exceptions. Not optimal in some cases, but worth it for the value of using FCPX.
-
[Craig Seeman] “[Oliver Peters] “I just wonder what others think about this and FCPX’s positioning versus “establish” concepts, terms, analogies, and metaphors.”
The biggest challenge is the lack of translation in the User Guide. Imagine an editor coming from any other NLE trying to search for “Match Frame.” It just isn’t there and they have absolutely no easy way to know what the equivalent feature is in FCPX. Such editor might leave in frustration with the mistaken believe that such function doesn’t exist.”
I remember trying to find Match Frame in FCPX. I was lucky in that I used Google instead of the User Guide. Took about 10 seconds. I can see how FCPX would be annoying to some who are attached to the older terminology. But in practice, the naming is secondary to the functionality (particularly when collaborating). If you don’t let the language get in your way the adaptation process is very fast and smooth. In my case it probably helped that I had always jumped back and forth between programs like FCP Legacy and After Effects which had different terminology, so dealing with FCPX wasn’t all that big a deal.
-
It’s for Beats; in Santa Monica. I would assume they have an existing installation that came with the purchase?
I’m sure they will want to switch to FCPX as soon as they can. 🙂
-
[Walter Soyka] “If you really need top-line system speed, I don’t see how the nMP is a consideration. Is this the architecture you would want to build a high-end finishing system on?
[Tim Wilson] “…but really, can you imagine Apple saying that they make the most powerful computer? “”
I’ll just take a moment’s break from happily editing on my “lower-powered” nMP to observe that Macs and PCs have been leap-frogging each other for as long as I have been buying computers. If a nMP is not high enough powered to do the “high-end finishing” you need for your niche than buy something else. Next year perhaps a n(ewer)MP will be the high-end system you need to buy because it leap-frogs PCs. Same as it ever was. Fortunately, most of us can do high-end finishing with our existing systems because even an iMac or moderately powered MacBookPro is more than fast enough for most of the finishing done today.
If only we could all be paid somehow for our time complaining.
-
[Gary Goldblum] “As someone who has used Pro Tools for 15 plus years I can see where I need to make an edit before I hear it. I am at a loss to why they use rectified waveforms now as I think the audio is as important as the video.”
I’ve only done audio editing from within the context of video editing and video editing apps, but I’ve never had a problem seeing an edit (using only audio) before I hear it, using a rectified waveform. I’m not sure what a full waveform would add to the experience, or to my speed of editing music or dialogue.