10.1 Preview Final Cut Pro X "New Feature" Exclusive

[Birkkromann]

You're an idiot

[ChiTownSweetness34]

What a completely unfunny video. The funniest part is how much time you spent putting it together.

Tell me - did FCP 7 stop working when X was released? no you say...?

[GregBurke7759]

@ChiTownSweetness34 FCP 7 will be Dead Software in next 1 year with support from apple. No Post House Will use it. Final Cut Studio was destroyed for a 64 bit iMovie that can go on the ipad.

[ChiTownSweetness34]

@GregBurke7759 Yeah, I work in post and that's not going to happen. FCP7 has been at 7.0.3 for how long now? Two years? Does it break in a year? No-it's basically been unsupported since 7.0.3 came out. Have you had issues with it? Well, neither have I. Do you think 3rd Party Developers will stop creating new plugins as new codecs come along? No.

And in a year and a half, you'll want to use FCPX. I've been to many seminars at this point, and although frustrating the potency is clear.

[KyleSiopiolosz]

@GregBurke7759 You're a fool. A lot of Post Houses are still on Leopard instead of Snow Leopard due to stability issues despite not having "support from apple." In addition, Post Houses will stick with what works, regardless of its age or support availability, which can easily be seen when I still see these Post Houses using Shake vs. Combustion or other nodal based compositing software. They, as well as myself, stick with what works, not with what is current or supported.

[GregBurke7759]

@KyleSiopiolosz ya, but for how long? FCPX, Premiere take any native codec, FCP7 does not...everything has to be transcoded to Proress witch is extremely annoying, having to render, extremely annoying, these are things that final cut 7 has no answer for them and never will, meanwhile, Avid and Adobe will continue to make there programs better without alienating a entire user base...

[KyleSiopiolosz]

@GregBurke7759 FCP7 does not require footage to be converted to ProRes, in fact FCP7 accepts codecs within the MOV, MP4 (M4V), and AVI container. FCP7 requires that, for a realtime workflow without rendering times during editing, only for exporting, you should use ProRes. FCPX also does that, but instead of making you manually encode the imported clips, the software itself does it itself and caches the results in temporary files. You still have to render when exporting in FCPX regardless.

[GregBurke7759]

@KyleSiopiolosz your right, but editing in h.264, mp4, or avi causes nothing but problems in a FCP7 even after you render. I own X Final Cut Pro and there're things in there that would have been amazing in FCP7 but instead of doing that.Apple decided to slapped every creative in the face with FCPX, Randy Ubillos is a idiot, and should never be allowed to touch software design again...I mean this is the same guy who thought a TIMELINE wasn't necessary in a editing program...what a joke.

[GregBurke7759]

@KyleSiopiolosz your right, but editing in h.264, mp4, or avi causes nothing but problems in a FCP7 even after you render. I own X Final Cut Pro and there're things in there that would have been amazing in FCP7 but instead of doing that.Apple decided to slapped every creative in the face with FCPX, Randy Ubillos is a idiot, and should never be allowed to touch software design again...I mean this is the same guy who thought a TIMELINE wasn't necessary in a editing program...what a joke.

[KyleSiopiolosz]

@GregBurke7759 I agree, there are some problems when editing with H.264 MPEG-4/Quicktime Videos and AVI within FCP7, however these problems do exist in FCPX as well, except as I said before, FCPX rectifies these issues by encoding them in the background in a new format. I myself only experience problems when rendering these formats, and that they seem to toggle between two different gamma values when playing / not playing. In addition, FCPX is missing tons of useful features from the predecssor.

[DaJokerx]

maaaaaan this misses me off...

[micksproduce]

funny