Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

I hate gamma!

Steve Sherrick said:
Timecode window has been addressed in FCP7.

I understand your point though.
Click to expand...

Steve... do you know if FCP 7 and/or color 1.5 supports full debayer in L&T Native or Color 4K/2K DPX render out?
 
Steve Sherrick said:
I have heard from reputable sources that Apple is aware of the issues and they are working towards a more stable Quicktime. My only concern is how much crossover is there with consumer apps and devices?

Hopefully the new architecture for Quicktime offers professionals a feature rich and stable environment and doesn't get bogged down with features/bugs that are a result of making it an all-in one solution. I'd rather have two versions if it means keeping it stable.
Click to expand...

I think every pro agrees with this and I WOULD PAY FOR IT!
 
Steve Sherrick said:
Looks great Martin! Now if we can just get rid of tearing and banding life would be splendid. :-)
Click to expand...

Are you using an NVIDIA display card? I was having horrible tearing on NVIDIA cards, but as soon as I switched to a (slower) ATI card, everything was silky smooth. Bad NVIDIA drivers if you ask me, I'm always surprised more folks don't complain about this. It's sort of like rainbows on DLP projectors, I can't stand to see either one, but most people don't seem to see or care.
 
Yeah, I do see it on my MBP which has the NVIDIA 8600M. Seems to have improved over the past year, maybe they improved the drivers. As for the banding in Martin's video, well that's just compression working it's magic. Perhaps it's bit depth conversion.
 
Steve Sherrick said:
Timecode window has been addressed in FCP7.

I understand your point though.
Click to expand...

I hardly call an additional window for timecode a fix more a bandaid. I could go on forever, I really think apple has drop the ball on FCP big time!! Think I might drag out my old punch and crunch. Might not be as fast but at least marking an outpoint lands in the right spot and not one frame later........

Cheers, Chris
 
Chris, I agree with you that Final Cut has its shortcomings. So does Avid, so does Premiere, and so does Vegas. But as much as Final Cut may be flawed in some of its implementation, it's not stopping top editors like Walter Murch from using it.

If there's a complaint I have about it, it's the disconnect they have from the community that uses it. Even Walter and his team had a hard time at first with Cold Mountain. Apple wasn't exactly jumping through hoops to help them. I suppose being a large company, with a wide variety of products that need support probably makes this a whole lot different than the RED community. There's no way to really post something on a forum and have the head of the company see it and respond to it like we are able to do here. When the message is clear about something not working, RED is able to respond, fix the issue, and move on. I think it takes a lot longer for those messages to arrive at Apple and when they do it takes a while to implement them.

All of the NLEs can do better in my opinion. But they are still great, all things considered. For $999 FCP Studio does a heck of a lot.
 
You must log in or register to reply here.
Back
Top