Forum Replies Created

Page 113 of 282
  • [Mark Raudonis] “[Rafael Amador] “The main difference between FCP and FCPX, is that Apple developed FCP with the editors in mind and has developed FCPX with Apple in mind. ”

    Quote of the day!

    “

    Indeed!

  • Brett, I generally agree with you. But I think if you are cutting something highly supported like ProResHQ, and in a highly structured environment, you’re not really feeling the problems you are talking about. If you are going from HDcamSR to HQ and then back, the kind of rendering and transcoding you are talking about never really enters the picture.

  • Chris Harlan

    November 29, 2012 at 3:04 am in reply to: New MacPro closer to reality?

    [Marcus Moore] “The other is collaborative workflow, which was more FinalCutServer, but it’s an area I think many still hold as a limitation vs legacy FCP. Tighter Motion integration needs to return as well. Those are the major areas, I think.”

    Stupid me. Yes, of course. I agree with both of those. Good point.

  • Chris Harlan

    November 29, 2012 at 2:13 am in reply to: 2005-fcp 5, 2012-fcpX

    [Aindreas Gallagher] “And you might need to visually interrogate the waveform – not least because some significant stuff isn’t seen in even the 7 waveform – I personally really need to get comfortable with exactly what the waveform is, if only because some of the significant beats that are buried in parts of it? “

    Yeah. I’m guessing I could get used to it, because others say I can, but I also find it disconcerting.

  • [Shane Ross] ” Even LEVERAGE has switched away from it.”

    Oh No! FCP X, the little lever that could lift the world, has just snapped? What did they replace it with?

  • Chris Harlan

    November 28, 2012 at 10:29 pm in reply to: Transcode bug?

    [Michael Phillips] ” was told by engineering that the only way to keep ProRes as ProRes but got from a QT wrapper to MXF was to an import with the proper import settings and codec set.”

    Cool! Can’t argue. It worked flawlessly for me last night. Thanks.

  • Chris Harlan

    November 28, 2012 at 10:25 pm in reply to: New MacPro closer to reality?

    [Steve Connor] “Chris Harlan] “One thing I have to say in defense of the 7″ iPad is that I thought it was a stupid idea until I held one in my hand. I probably won’t get one, but it really is interesting that you can hold it in one hand and sort of thumb through it. At least I can, but I’ve got very big hands.”

    I got one a couple of weeks ago and after using it a lot it has now replaced my retina iPad3, I also have big hands!
    “

    I think it probably would for me, too. I probably would have chosen it over my retina iPad if it had been out at the time. Its funny, though, that I didn’t think I’d have any use for it until I put it in my hand. I literally changed my mind about it in an instant.

  • Chris Harlan

    November 28, 2012 at 10:15 pm in reply to: The NLE that keeps moving forward?

    [Jeremy Garchow] “[tony west] “Maybe Apple looked and said nobody is using this patch panel for almost 10 years accept Tony West so lets get rid of it : )”

    I have it on good authority, this is exactly what happened.
    “

    NDA violation, man. Right there.

  • Chris Harlan

    November 28, 2012 at 10:12 pm in reply to: New MacPro closer to reality?

    Excellant post! I’d quote it bit by bit but I’d be agreeing with most everything.

    [Craig Seeman] “Some of the interesting design things are:
    7″ iPad remember Jobs position on that but it wasn’t outside his tendency to reverse his own public positions.
    New 21″ iMac no user upgradable RAM like MBPr
    New 27” iMac has user upgradable RAM
    iPhone 5 and iPad 4 change in dock connector especially the change in the iPad within its product life cycle.
    Which were Jobs and which were Cook’s decisions?
    “

    This I have to chew on. Interesting observations.

    One thing I have to say in defense of the 7″ iPad is that I thought it was a stupid idea until I held one in my hand. I probably won’t get one, but it really is interesting that you can hold it in one hand and sort of thumb through it. At least I can, but I’ve got very big hands.

  • Chris Harlan

    November 28, 2012 at 10:07 pm in reply to: Transcode bug?

    [Michael Phillips] “The secret for native MXF wrapped ProRes in Media Composer is to import, and not AMA. With AMA, it will do through a decode, re-encode process even if you select the same codec/data rate.

    The process is to import, which will be a fast import.

    Michael
    “

    Thanks, Michael. I’m getting conflicting reports about AMA not doing Fast Import with ProRes. According to the Avid website it does, but you and a few others have told me it doesn’t. Its also been suggested by several people as the best way to avoid the notorious Gamma shift, which it does seem to do.

    On the other hand I did two direct Fast Imports last night (because of the disk space counter bug) without any Gamma issues, so maybe there isn’t a problem at all. Maybe its just that I hadn’t been using the Media Creation settings properly in the past. Its the little things that take a while to drip in.

Page 113 of 282

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