Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

NEW FCP is 4k and only $299

I like it, but what about R3D support? is it possible to work straight with your R3D Files on timline ?
 
Explain. You seem to have an insight into FCPX that no one else has.

I have no access to special information. If I seem to have more insight ... it may be my background as a computer scientist at work.

In this case however I am talking about an essentially human problem.

A lot of what we do when we sit down to edit in Premiere, Media Composer or Final Cut 6/7 is not editorial at all, but rather timeline management and organization, subclipping, creating sequences and nested sequences - keeping mental track of that. Its doing technical things as opposed to art things.

That stuff is pretty hard, and its also difficult to be disciplined and consistent when doing that type of work.

Now, for a lot of editors, fixing that sort of disaster is how they earn their money.

That in fact has been how I've gotten some clients- fixing disastrous projects some other editor screwed up completely to the point where further progress was difficult.

I keep clients however by showing great judgement and taste. I know that a lot of the editing "technicians" don't do this at all. They just solve the problems.

Well FCP X is going to solve a lot of problems before they ever become problems, and that should make the technical editors nervous.

Well ... not really. There are new ways to organize in FCP X. Some are available in Avid or other NLE's, some are new. I think I can state with confidence there will be more inventive ways to screw up a timeline. You know the aphorism ...

"Make it "idiot proof" and someone will just invent a better idiot."

Now to be fair I was also thinking of all the other things we are called on to do, like our own IT support. Just making FCP 64 bit and cleaning up and modernizing its interfaces with the system will obviate a lot of the IT support we spend time doing so we can edit- but there are enough big issues that I don't think anyone who specializes in solving IT problems for post has to worry. FCP X won't solve those problems, but it should let you focus better on genuine IT issues rather than antiquated software limitations.
 
If ColorSync is anything like Adobe's ICC handling then it'll just add one more blackbox layer of horror to a color pipeline. I finally and thankfully learned how to disable color profiles in photoshop and have been all the happier ever since.

He he he, same here, I only believe in real numbers.
 
If ColorSync is anything like Adobe's ICC handling then it'll just add one more blackbox layer of horror to a color pipeline. I finally and thankfully learned how to disable color profiles in photoshop and have been all the happier ever since.

ColorSync is nothing more than a system for applying a calibrated output LUT for each different output device. How is that a bad thing?
 
ColorSync is nothing more than a system for applying a calibrated output LUT for each different output device. How is that a bad thing?

I guess it can cause problems when you're relying on a colour profile for gamma correction and the output device doesn't support it. For example, I took a bunch of photos to be printed using the AdobeRGB colour space, and they came out all dull. I had to convert them to sRGB so they would work...
 
ColorSync is nothing more than a system for applying a calibrated output LUT for each different output device. How is that a bad thing?

Implementation. Photoshop seems to think that it needs to desaturate all of my images to almost grayscale and pump up the red for 'srgb'. As a result instead of it being consistent in every program and every computer it's seemingly randomly changed from app to app and computer to computer. If I output a linear EXR I know it'll be opened correctly in every linear EXR compatible application--exactly the same.
 
Back
Top