James Culbertson
Forum Replies Created
-
[Kathlyn Lindeboom] “How about “ALL NLEs: The Great Debate””
Sounds good to me.
-
In certain circumstances I have used DT Videolabs – PlaybackPro on a fast laptop, or dedicated server, with ProRes masters to avoid compression issues. Though in many cases a good H.264 compression is virtually identical (using a difference test). I usually only see more subtle desaturation in highly saturated colors (more in animation than in traditional films).
Blacks and white values, and other such issues appear to be almost entirely theater system issues. Particularly because BluRay playback seems to be an after thought tacked on to their main DCP playback systems in some cases. Our local theater has a little consumer BluRay player as one example.
Even if you are using H.264 files, if you need to stop and start for any reason, this kind of playback is much more reliable than BluRay from the discussion I have had with people who run large corporate presentations regularly.
-
Apples vs Oranges: The great NLE debate
-
James Culbertson
August 23, 2018 at 5:41 am in reply to: FCPX audio levels, fades, keyframes into Resolve 15?Makes sense. Though with the integration of Fairlight I wondered if perhaps that had changed.
-
James Culbertson
August 21, 2018 at 7:02 pm in reply to: AVCHD stutter bug or camera specific issue?[Joe Marler] “To me AVCHD is a hassle because”
It’s low budget at this point, and they decided to go with 1080p AVCHD to match the resolution limits of the C100 mkII. It’s fine for this project, the footage looks good. While I would avoid AVCHD if I could, in practice I have never had any issues importing and working with AVCHD natively. I’ve not needed to transcode for a couple of years up to this point. I’m assuming it is the 59.94 that is causing the dropped frames, in any case, I only need to transcode the DVX200 footage as the rest is playing fine as usual.
For shorter projects (30 minutes or less) with no more than 25-35 hours of source footage, I tend to just import all footage into the library. Never had any issues with such Libraries.
-
Makes sense. There is no budget for a dedicated data wrangler on this shoot. Though I try to enforce, but the shooters are in the field and don’t always remember my texts. I’m a little afraid to muck with the camera archives contents by opening packages so I’ll probably just leave things as is this time around.
-
MEGA – Make Editing Great Again!
[Personally, I keep coming back to this forum for the entertainment. …just when I think threads can’t get any more silly, they do.]
Anyway, back to my serfdom.
-
James Culbertson
May 12, 2018 at 3:53 am in reply to: Premiere CC 2018 H264 uses Quick Sync, faster than FCPX on iMac Pro at H264 encoding[Walter Soyka] “Is it just encodes? If this accelerates decode, too, does it make working with those devilish H.264 formats [link] any smoother?”
I’d like to know this too. One of the many reasons I prefer FCP10 is that I never have to transcode to edit native AVCHD or H.264 MP4 footage.
-
James Culbertson
May 8, 2018 at 7:00 pm in reply to: Premiere CC 2018 H264 uses Quick Sync, faster than FCPX on iMac Pro at H264 encoding[Scott Witthaus] “Wait. Is this supposed to make me switch to Premiere?”
4 seconds difference? No. But it is great that Premiere editors don’t have to suffer with longer encodes anymore.
-
[Bill Davis] “No need to address anything here, except to note that anyone who feels X is “too cheap” to be any good, must therefore find Resolve Basic “worthless?””
Didn’t Resolve used to cost $250,000 or thereabouts? People are probably still mentally depreciating it… 😉