NLE Needed

[Gavin Greenwalt]

Or Both...

Something else to consider is:

1) You need Photoshop. $700+
2) You should probably have AE. $999+

vs.

Production Suite (Photoshop, AE and Premiere). $1699

 

[Trevor Meeks]

Got production suite last year for 50% off during Adobe's SWITCH promo. Really glad I moved over to premiere, although I still don't know it as well as FCP... it'll be essential to my RED workflow.

 

[Jarek Zabczynski]

From a die hard FCP user, I admit FCP is dead in the water, Apple killed it. I will still use it as long as I can for the formats it supports, but for my RED projects and onward, I'm diving into Premiere.

 

[Trevor Meeks]

From a die hard FCP user, I admit FCP is dead in the water, Apple killed it. I will still use it as long as I can for the formats it supports, but for my RED projects and onward, I'm diving into Premiere.

Agreed. I really enjoy(ed) FCP7, and will use it for some non-red projects... but it's sickening what Apple did with FCPX, and it really did push me to buy Premiere in order to move forward.

 

[Robert L. Mickles]

Agreed. I really enjoy(ed) FCP7, and will use it for some non-red projects... but it's sickening what Apple did with FCPX, and it really did push me to buy Premiere in order to move forward.

Not to beat a dead horse, and no disrespect but how is it sickening what they did with FCPX. If you look at it, its actually very revolutionary. FCPX may not have a place in everyone's workflow right now, but I can defiantly see it going in the right direction. Like I said, if you have a project that you can use the trail of FCPX for do it. You may just end up seeing all of the advantages instead of the few negatives.

 

[Jarek Zabczynski]

Not to beat a dead horse, and no disrespect but how is it sickening what they did with FCPX. If you look at it, its actually very revolutionary. FCPX may not have a place in everyone's workflow right now, but I can defiantly see it going in the right direction. Like I said, if you have a project that you can use the trail of FCPX for do it. You may just end up seeing all of the advantages instead of the few negatives.

What's sickening is that what they really did was discontinue Final Cut Pro and release a completely new product without telling anyone. Everything that people saw demoed prior to the release was just assumed to be "additions" to the software, not scrapped and replaced altogether. Calling this new NLE "Final Cut Pro" is false advertising. It's not the same product in any way, can't even open old projects. It's a big FU to every professional editor and post house that has invested years and considerable amounts of money into a system that took off so well and so fast that it caught up to Avid in many markets. Personally, I feel hurt and betrayed by this move. You may call me silly for feeling this way, but I am one of many that do. It's may have benefits and do some things differently and arguably "better," but the issue is that it's not Final Cut Pro.

 

[Trevor Meeks]

What's sickening is that what they really did was discontinue Final Cut Pro and release a completely new product without telling anyone. Everything that people saw demoed prior to the release was just assumed to be "additions" to the software, not scrapped and replaced altogether. Calling this new NLE "Final Cut Pro" is false advertising. It's not the same product in any way, can't even open old projects. It's a big FU to every professional editor and post house that has invested years and considerable amounts of money into a system that took of so well and so fast that it caught up to Avid in many markets. Personally, I feel hurt and betrayed by this move. You may call me silly for feeling this way, but I am one of many that do. It's may have benefits and do some things differently and arguably "better," but the issue is that it's not Final Cut Pro.

Couldn't really say it better myself. I think that about sums it up...

 

[Mike Garrick]

It's amazing even after all this time since FCP X was launched, this topic still generates so much anger , passion, heat !

FCP X may one day be right for prime time, but in the mean time don't ask me to support a system that can't even remember its own file paths and external HD configurations from project to project & thats one big fat stonking negative.

 

[Sergei Franklin]

We have been using FCP since version 1 and are considering Lightworks www.lightworksbeta.com as our next edit system.
I'm waiting for the MAC version. PC version is available now.

 

[Christopher Adams]

I also say premiere both for the non-transcoding and the Mercury playback engine. This uses CUDA which i have a Quadro 4000 Nvidia card. This card also accelerates Davinci Resolve. So best of both worlds for me. Also both will gladly use a Red Rocket card. Also nice to just drop a clip into AE and stabilize it then keep going without leaving Premiere.
CJ Adams
my 0.02

 

[Brian Self]

Im with Robert on this, fcpx is actually a great NLE for small projects like podcasts, wedding videos and short cuts. Def premier for red raw and films, but fcpx has it's place and as a wedding cinematographer I use it a lot.

 

[Ryan Emanuel]

I also say premiere both for the non-transcoding and the Mercury playback engine. This uses CUDA which i have a Quadro 4000 Nvidia card. This card also accelerates Davinci Resolve. So best of both worlds for me. Also both will gladly use a Red Rocket card. Also nice to just drop a clip into AE and stabilize it then keep going without leaving Premiere.
CJ Adams
my 0.02

Quick question Christopher, can you put a CUDA card in a thunderbolt expansion chassis for an imac?

 

[Matt Johnston]

Quick question Christopher, can you put a CUDA card in a thunderbolt expansion chassis for an imac?

Mac OSX does not support graphics cards in Thunderbolt chassis'

Details here: http://www.magma.com/thunderbolt.asp

There is an interoperability issue with MacOS using graphics (GPU) cards externally through Thunderbolt. Unfortunately, external graphics solutions for MacOS X do not work and we do not expect a resolution from Apple in the short term. We realize that external graphics support is a feature that many users want so we’ll let you know if this changes. For the time being our recommendation may be to run Windows using Boot Camp, but this is not yet confirmed as a working solution.

 

[Les C.]

What's sickening is that what they really did was discontinue Final Cut Pro and release a completely new product without telling anyone. Everything that people saw demoed prior to the release was just assumed to be "additions" to the software, not scrapped and replaced altogether. Calling this new NLE "Final Cut Pro" is false advertising. It's not the same product in any way, can't even open old projects. It's a big FU to every professional editor and post house that has invested years and considerable amounts of money into a system that took off so well and so fast that it caught up to Avid in many markets. Personally, I feel hurt and betrayed by this move. You may call me silly for feeling this way, but I am one of many that do. It's may have benefits and do some things differently and arguably "better," but the issue is that it's not Final Cut Pro.

Absolutely agree!

I'll add one other thought. I own FCP7 on a Mac Pro and have enjoyed it very much (although, some have been very unhappy about some bugs they allow to remain in FCP7 for a very long time).

However, getting the latest video cards was an issue (only a few are supported).

The cost was also much higher than on Win7 for the hardware, video cards, etc.

When FCP X came out, I got so annoyed I voted with my pocket book and bought Production Premium for the PC instead of OS X. Win7!!!!

I've been very happy.

You can buy a motherboard with 7 PCIe slots for Windows. The only way that will happen on the Mac is with a PCIe expansion chassis - which will result in slowdown (this may/will change with Thunderbolt), but will definitely add another $2.3K to the cost and one more thing to go wrong.

You can buy any video card you want and it will be cheaper.

Apple is in the business to sell IOS hardware now, not Macintosh computers. It's where the money is and that's their focus.

The 'Pro' market doesn't seem to interest them, and I'll also be very sad when Logic Pro X comes out, probably dumbed down like FCP X. Apple (according to fxGuide), had a 64 bit version of the real FCP7 ready for release, but chose to go in the 'express' direction, as that's the product they released as 'Pro'.

I can see the writing on the wall as far as Apple goes, and I've moved on.

FCPX: What Pros Find Missing in Final Cut Pro X
by Walter Biscardi
http://magazine.creativecow.net/article/final-cut-pro-x-whats-missing-for-some-pros

Why We Can't Use Final Cut Pro X at Our Companies
Podcast Hosted by
Walter Biscardi and Richard Harrington
http://podcasts.creativecow.net/fin...-we-cant-use-final-cut-pro-x-at-our-companies

 

[Robert L. Mickles]

Computers wise, It'll take a lot more than just coming out with a revolutionary, different editing program thats missing a few features to switch to Windows. I think I'd rather not use a computer than switch from a Mac. People are severely misinformed when it comes to Apple's take on the future of Mac and the Pro market. Of course iOS is a huge thing for them, but they still have not lost much focus on the Mac lineup, not the Pro market. FCPX is a powerful professional program. Like I said before I will probably be using Premiere for most stuff to to its native codec capabilities, but after using FCPX I really do like it. It may not be ready to edit a feature, but It will be. I know there's rumors floating that they are killing the Mac Pro line, well there are just as many rumors that say they are updating it soon. A lot signs point more towards the fact that they aren't going to kill it. If you like FCP7 and it still works for you, continue to use it. Everyone is acting like when FCPX was released there was a switch that Apple flipped to disable all copies of FCP7. Technology changes, people need to deal with that. Instead everyones acting like Apple just killed their grandmother in front of them, instead of actually looking into FCPX and seeing what advantages it may or may not have in your workflow. If it's not for you right now, then fine stick with FCP7 or switch to something that works better. Again there is no perfect tool for every job. What is needed and standard technology today, may change tomorrow. I continue to use FCP7, I like using FCPX when I can, I can use Avid when needed, and I am buying Premiere. You have to at lest have a basic knowledge of all these things unless you now for a fact that you are going to be making 100% of these choices in your career. But what if you got hired tomorrow for a huge job that you're going to make tons of money off of, but the client and/or employer say that you have to edit on FCPX? do what you can to keep up with whats out there and try to look at the benefits of knowing all of the different flavors of NLEs out there. At the end of the day if you're a good enough story teller, you're going to get the same result out of any of these programs. Hell, you'll even get the same result cutting on film or tape.

 

[Mike Garrick]

The trouble is no one is going to hire you to do a big job on FCPX.......yet!!!

I take your point about "staying current" we all practise it day in out. FCP X is bit like early versions of Premier ( below 5) not yet ready. It may be one day, but ain't there yet. The Mac Pro question will be resolved sometime this year after that we will all know what direction the wind is blowing for apple and professional users. But it isn't looking encouraging.