Forum Replies Created

Page 7 of 38
  • James Culbertson

    July 13, 2017 at 11:52 pm in reply to: Informal NLE poll

    [Andrew Kimery] “Something I see come up often is how much a tool costs… but what doesn’t seem to get brought up along side that is how much a tool earns. Is generating revenue so unimportant?”

    Where is this place that pays you differently based on what editing tool you use? I keep hearing rumors of it, but where I come from (Seattle) editors (at least of my generation) get paid for their editing experience and sensibility. Some clients want me to use Premiere and some want me to use FCP10, but they all pay me my standard rate. I’m sure I would be paid the same if I were asked to use AVID.

  • James Culbertson

    July 12, 2017 at 6:17 am in reply to: Informal NLE poll

    I can only speak to certain corporate and educational facilities in the Seattle/Bellevue/Redmond area which I have found to be a mix of Premiere and FCP10. It’s not monolithic in any particular corporation either as some groups (at a large Redmond corporation as one example) use Premiere and other groups use FCPX10 exclusively. Not much AVID, no FCP7, and no Resolve.

  • James Culbertson

    July 6, 2017 at 5:31 pm in reply to: FCP minus the X

    [Michael Gissing] “but I have to constantly ask, hence why I see zero advantage in trimming the identifier off the name.”

    My overall point being that more and more people are trimming the identifier off the name, so how to deal with that going forward. In Seattle I have not had to use FCP7 is probably over 3 years, so when someone refers to FCP I pretty much know they are talking about FCPX.

    By the way, on the Apple App store FCPX is listed as “Final Cut Pro” in most places (except for the main title when you search for it) as it is in the applications folder (only on the splash screen does it say FCPX). Seems like Apple is starting to transition it to FCP too.

    Anyway, I am going to start calling it FCP10. YMMV.

  • James Culbertson

    July 5, 2017 at 11:51 pm in reply to: FCP minus the X

    [Shane Ross] “I’ll be calling it FCX for the rest of my days…”

    Not a few AVID editors I interacted with back in the early 2000s said the same of the original FCP. One editor friend called it FCT (Final Cut Toy) for many years.

    Same as it ever was…

  • James Culbertson

    July 5, 2017 at 11:48 pm in reply to: FCP minus the X

    [Michael Gissing] “Language is best when it doesn’t cloud meaning. When someone says FCP it automatically requires clarification between two very distinct software packages.”

    To provide more context… I’m getting more requests from producers and other potential clients to use the newer FCP and they just ask if I know FCP, or “the Final Cut” as one example.

    Also, for younger generations, particularly teens and 20-somethings, who have never used FCP Legacy, and seem to prefer FCPx more than many in my generation, they often just call it FCP, or even more they shorten it to “Final Cut.”

    After posting this, I realized I always called FCP legacy by tacking on its current version number: FCP7 for example. So, perhaps the best balance is to call the new FCP: FCP10

  • [Steve Connor] “Well the Trashcan’s do run very hot….”

    Mine is barely lukewarm at the top,

  • James Culbertson

    March 18, 2017 at 5:19 am in reply to: Revisionist History…

    [Oliver Peters] “the app was largely rewritten after Randy’s version 4 and then modified a couple of times again.”

    The original version Premiere 4 (actually 4.2.1) was pretty stable (at least with a Truevision Targa card). I was trying to use v5 and got so frustrated I ran out and bought the original FCP 1.0 two weeks after it was released. Never looked back. Premiere 5 was so bad they eventually borrowed one of the original After Effects developers to try to salvage it. Might be why I wasn’t as bothered by the FCPX roll out. People understandably mistrusted Apple, but it doesn’t hold a candle to the decade long Premiere debacle. Adobe is just lucky few people remember all that.

  • James Culbertson

    March 12, 2017 at 6:47 am in reply to: FCPX Crashed today

    I tend to forget that FCPX can crash these days. I used to have occasional problems with iZotope audio plugins in FCPX a year or two ago; but that went away a long time ago.

    Same with Compressor, Photoshop, After Effects, and Cinema 4D.

    Good times.

  • James Culbertson

    January 29, 2017 at 8:53 pm in reply to: Night Shift mode

    [Robin S. Kurz] “So essentially what you’re/he’s saying, is that the color of light you are exposed to whilst asleep can make a difference in your sleep pattern (which I’m sure it does, no matter the color), but has nothing to do with the type of light you are exposed to prior to going to sleep, right?”

    If your eyes are open you are being affected by this phenomena (asleep or awake); since most of us sleep with our eyes closed I would assume that there would be less effect at that time.

    Whether one is asleep or awake does not change sensory receptor function to my knowledge. That happens at higher levels of the brain, though there is no reason that your sensory neo-cortex isn’t still receiving sensory information even though your consciousness has receded in sleep.

  • James Culbertson

    January 29, 2017 at 7:20 am in reply to: Night Shift mode

    This is pretty interesting (prior to getting into video production I studied Biology and specifically Neuroscience in college and then did Neurophysiological research studying the visual and auditory pathways to the brain looking for neuroplasticity and neuroregeneration in CNS neurons):

    “There’s a third kind of sensor in our eyes, officially discovered in 2002. Called intrinsically photosensitive retinal ganglion cells, or ipRGCs, these relatively crude sensors are unable to pick up on low levels of light — from a dim night light, for example — but sluggishly signal light changes.

    They are the body’s way of sending ambient light information to the master circadian clock, a huddle of nerve cells in the brain. This clock makes the pineal gland start and stop the secretion of melatonin. The ipRGCs are most sensitive to blue light — that’s why blue light is bad for your sleep.

    To counteract the effects of tablets’ blue light, Figueiro and Lockley recommend a free app, F.lux, that automatically warms up the colors on your various screens — more reds and yellows — at sunset and returns them to normal at sunrise.

    “The amount of light you need [in order] to see is lower than the amount of light you need to affect your melatonin,” Figueiro said, which means that light-emitting screens can be used at night without disrupting sleep cycles if you put some distance between your eyes and the device….”

    https://www.washingtonpost.com/national/health-science/blue-light-from-electronics-disturbs-sleep-especially-for-teenagers/2014/08/29/3edd2726-27a7-11e4-958c-268a320a60ce_story.html?utm_term=.f5e955e1996f

Page 7 of 38

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy