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 :)

Notes on the New Final Cut Studio -- It's not FCS3!

Matt, be a little nuanced, will you? :-) There is a big difference between making it a bit more Apple-like than giving it an itunes interface. Come on...

Like I said, I think the most comparable re-design is when they took over Logic and have slowly brought it closer to the way Apple likes their interface design.

I also think you should be worried about other things if you're worried about these app's just "looking" more consumerish. When it all comes down to it, I really don't care as much how they look as much as if they ARE pro app's...which mean getting the stuff pro's do...right.
 
color speed

color speed

any idea on how the color speed could possibly be enhanced by RED Rocket™?
the playback speed was the biggest issue for me using color. i couldn't get realtime playback even by lowering all parameters on my mac 8 core with disk array...
i believe RED Rocket™ can take care of debayering, then color can manage grading pretty easily, with RGB files, but then? will color send back the stream to RED Rocket™ for playout or will it send it to the graphic board?

by the way, any idea on the best available graphics board for color? the fx5600 that i have on my mac doesn't seem to push color any faster...
available at the moment are a bunch of geforce, an Ati and recently the fx4800...
 
alex trettenero said:
any idea on how the color speed could possibly be enhanced by RED Rocket™™?
the playback speed was the biggest issue for me using color. i couldn't get realtime playback even by lowering all parameters on my mac 8 core with disk array...
i believe RED Rocket™™ can take care of debayering, then color can manage grading pretty easily, with RGB files, but then? will color send back the stream to RED Rocket™™ for playout or will it send it to the graphic board?

by the way, any idea on the best available graphics board for color? the fx5600 that i have on my mac doesn't seem to push color any faster...
available at the moment are a bunch of geforce, an Ati and recently the fx4800...
Click to expand...

there have already been reports of redrocket producing realtime 1080p 25p out of the Color timeline. pretty cool stuff
 
It would make sense for Apple to bring up the big release within the next 6 months or so. Because Adobe is now clearly attacking the FCP users by offering them sweet sweet candy like importing FCP projects in Premiere (s. clip) or by offering better RED integration :thumbup:

Honestly I'm thinking of going Adobe if Apple doesnt show up with something better soon.

http://tv.adobe.com/#vi+f1510v1003
 
The best thing about new Final Cut Studio released today is Color 1.5 with much integrated support for 4k DPX and Red Raw native support (No Resizing).

Hope FCS3 will be native 64-bit support with Snow Leopard!
 
Actually, what would be real progress would be that Color could access more than just a couple of cores whenever we have to do any renders. At the moment, Color is sloooow as molasses for 2K output (I can't imagine what 4K render times would be), and barely uses 2 cores for renders. Maybe this has been addressed, or will be once Snow Leopard is released...
 
Patrick Scheller said:
It would make sense for Apple to bring up the big release within the next 6 months or so. Because Adobe is now clearly attacking the FCP users by offering them sweet sweet candy like importing FCP projects in Premiere (s. clip) or by offering better RED integration :thumbup:

Honestly I'm thinking of going Adobe if Apple doesnt show up with something better soon.

http://tv.adobe.com/#vi+f1510v1003
Click to expand...

I have used FCP forever and just received my copy of CS4 yesterday. It is SO much freaking better than FCP when using r3d.
 
I think people are confusing UI changes/New Features with the application re write. it has been rewritten from the ground up in cocoa. that doesn't mean the UI was going to change drastically. just that everything was going to be faster and more solid under the hood and 64bit once snow leopard drops.
 
I don´t think its been rewritten to Cocoa yet. None of the OSX features of Cocoa is in there. It still have the worse text generator, the soundmixing features are a joke. And talk about native formats, it only does QuickTime and its wrappers. Did anyone for shure get info about 64bit? This version is still the middle version before the rewrite. Log and transfer and some other new windows are cocoa but not the rest of FCP. I still think Apple is working on a real Cocoa OSX FCP. Using modern technology from Motion and Soundtrack. If you look at iMovie 09 it got some really nice workflow enhancements. Though it is not a Pro app. I do think the more modern way of editing will go over to FCP. It takes time to write, bugfix and trim a modern app like FCP for Cocoa and SnowLeopard.

Like I said this is just one step closer. Just want a Cocoa, modern FCP!!!
 
Bing Bailey said:
I think people are confusing UI changes/New Features with the application re write. it has been rewritten from the ground up in cocoa. that doesn't mean the UI was going to change drastically. just that everything was going to be faster and more solid under the hood and 64bit once snow leopard drops.
Click to expand...

The UI is just too close a match. Given that FCP predates OS X, there's presumably QuickDraw code lurking in there somewhere to draw all those custom UI elements in Final Cut. If they rewrote that as Quartz code for a Cocoa app, it's unlikely they'd bother to keep things pixel-for-pixel identical. Why would they? It's not as if FCP couldn't do with some updated UI as well, and a rewrite provides a great opportunity for that.

Plus, if FCP were 64-bit now, Apple would be telling us. They'd probably even explicitly tell us if it had been rewritten, actually.

Now, mind you the Carbon/Cocoa dichotomy isn't always as clear as some people think. Objective-C (the language used for Cocoa apps) is a strict superset of C, and Carbon is a C API. A lot of data types in Core Foundation are also "toll-free bridged" with Cocoa objects, which means an app can internally pass data back and forth between Cocoa and Carbon code with little trouble. The upshot is that Carbon and Cocoa can be mixed within a single app without too much trouble. I'd be stunned if some of the new features, like the shiny new export interface, weren't mostly Cocoa code.
 
Actually, when I think about it, it's pretty clear why this version of FCP isn't a Cocoa app: QuickTime. QuickTime was, for quite a while after OS X shipped, only available through Carbon. Apple started adding Cocoa APIs to access QuickTime functionality a couple of versions back, but QuickTime itself was, as far as I'm aware, still just a big, complicated chunk of Carbon code.

QuickTime X, due with Snow Leopard, and derived from the iPhone version of QuickTime (the iPhone doesn't have Carbon) puts and end to that. But QuickTime is huge and complicated, and re-implementing all that functionality is no small task. I would guess that QuickTime X's feature set isn't robust enough to support an app as demanding as Final Cut Pro. So this version of FCP has to still rely on the old Carbon QuickTime.
 
You must log in or register to reply here.
Back
Top