So, that's it for me so far with FCP X.... Got to either stick with FCS3, or head to Adobe...

Today I was working on my first FCP project. I did about 3hrs work this afternoon, and then quit for a while. Everything was fine...

Then I launched it again, and did around 3hrs more work. Of course, there's no 'save', so I'm just assuming everything is 'saving' along fine. I noticed that the 'skimming' feature didn't seem to be working anymore, so I quit FCP X, and then re-launched it (no error messages, or anything).

All of a sudden, my project is back to where I FIRST quit 3 hours ago! 3 hours of work just disappeared in 20 seconds!

Can anyone suggest why this may have happened? If I can't trust this software to do something as basic as just SAVE my files, what good is it at all?

Frustratingly yours....

Ben

I would suggest that you limit your work on FCPX to training yourself with it until the OSX system update shows up. I had some interesting issues that were solved by quiting and restarting and one crash when I tried to delete some media while the program was still analyzing the files. The program is very promising but it's needs real world feedback to Apple before the kinks are ironed out.

So we truly are just 'beta testers' :(

Some of us are, depending on our system configurations. Hardware is not identical across Apple models and sometimes programmers can not foresee what one system will do inconsistently. I say as an official beta tester for several programs over the years. Also FCPX might interact with other programs and third party system enhancements in unexpected ways, this is a fact of computer software everywhere.

As some people recommend, and I adventurously ignored in this situation, never go for version 1 of any program or hardware, always wait for the first set of updates.

William

"never go for version 1 of any program or hardware, always wait for the first set of updates."

The last word on the subject. There seem to be lots of guinea pigs (lemmings) trying out this app for Apple. Nothing wrong with that, but using it for "proper" jobs is a tad foolish at this stage IMO.

What's the sound of a lemming? Let me make it. And the water down from the cliff sure looks brisk!

Seriously, I do not regret the purchase as I am sure that the upgrades will be coming. In the meantime I can use the time to learn and be ready to use it when stability is achieved.

What's the sound of a lemming? Let me make it. And the water down from the cliff sure looks brisk!

Seriously, I do not regret the purchase as I am sure that the upgrades will be coming. In the meantime I can use the time to learn and be ready to use it when stability is achieved.

Why wouldn't you spend the money AND time to learn Premiere Pro CS5 (or 5.5) which is better than FCPX in every way and has been ready for work since its release 18 months ago. Heck, it even allows easy XML importing from FCP 7, something 'X' cannot do. Plus, CS5.5 allows you to set the shortcuts to replicate FCP 7.

Steve: from what it looks like, Apple is taking a new approach how we deal with media and our edit workflow. It is not ready for production use but can be used to play around and see if you can come to like the "new way". I am disappointed and also skeptical where this all goes. I have downloaded the app, and played with it on a non-production machine, I managed to crash it as well.
However the longer I play the more I can see what could be a new approach to editing.
And would we not all sometimes wish for a reset button to go back to square one and look at a problem fresh? It looks like this is what apple has done. - A very bold move, I think. Courageous. but at the same time they did some really stupid things like removing FCS from the Apple Store... This opens a barndoor for Adobe and Avid. Anyone who needs to set up an edit suite now, has to either buy FCS off Ebay, find a leftover copy at a dealer or, go with Premiere or Avid. The latter however requires a downgrade of your OS to 10.6.6 otherwise it will not work and screw up your system (i.e. Bluetooth)

I would not sell my Apple stock just yet. The "second coming" as some people refer to it might still be happening although in installments...

Hi Oliver,

I am sorry to say, but there is absolutely zero evidence that Apple intended FCPX to be a 'Pro' app competing in the 'Pro' arena against Avid and Adobe. However, the evidence does exist that Apple wants 'X' to be an easy to use, consumer-ish NLE. I suggest you listen to the podcast over at the cow of Biscardi and Harrington. After about 30 minutes, they present enough evidence which shows Apple really intended it to be iMovie Pro.

To keep using the 'version 1.0' excuse is not looking at all the facts. Just last year, Adobe released 4 64bit re-written programs for BOTH OSX and Windows, and they were ALL useable from Day 1. Plus, the year prior, Adobe released a completely re-written 64bit Photoshop which worked from Day 1.

I wonder how many people have both AE and Photoshop. I bet it is a significant number, which should mean that they probably have one of Adobe's Production suites as it is cheaper than buying AE & PS separately. Thus, many FCP users should already have Premiere Pro. All they probably need is a supported nvidia card for GPU acceleration and they will wonder why they waited so long.

Premiere Pro CS5 (or 5.5) which is better than FCPX in every way

Steve. Premiere Pro is a wonderful product.

Better in every way?

Here is why I ask:

So far so good. FCP X exists with FCP 7. I am editing a DSLR project right now. Lots of new stuff to get used to, but the performance is FASTER than my CS5 in terms of trimming, adding effects (what there are) and color correcting...
-GReg

(That post was taken from this thread: http://www.dvinfo.net/forum/final-cut-suite/497443-fcp-x-now-available-buy-download-app-store-3.html#post1660292 )

So there are three things per that quote which don't quite jell with your statement.

Here's another one. FCP X is better at leveraging THE EXISTING GRAPHICS CARD in a Mac. It is optimized for that. PPro is currently only optimized for Nvidia. So on a MacBook Pro, for example ...

Here are a few other things I was wondering about PPro performance. There are some FCP X features which I will be carefully testing this weekend:
1/ The removal of background noise upon ingest (always been a massive time-waster for me doing it manually in Soundtrack Pro). Does PPro have this feature?

2/ Automatic color balancing between all of the clips (potentially another big time-saver). Does PPro have this?

So there might be another two which can potentially be added to the list.

My immediate impression of FCP X is that it seems a bit like a new Formula One racing car by Adrian Newey (the top designer in F1). It's got an engine and a chassis that seem to be a generation ahead of the current F1 cars. Capable of doing 400 mph down the straight.

But it's as though he's also put an old packing crate to use for a seat and an old rope attached to each wheel with which to steer. Totally unacceptable for an F1 car. Be that as it may, I'm still going to take it for a test drive around the track this weekend. Then I'll make my short and medium term plans.

The crux of it all is how quickly they respond and come out with 10.1, 10.2, etc. Larry Jordan has indicated that there is a team willing to do just that. One DV Info member has posted in another thread that we should not listen to Larry. Well ... gosh.

I'm going to look for myself, think for myself, take it for a test drive for the next 3 days and then decide whether to integrate it into my business or leave it in the garage until a more meaningful revision is issued.

I will only add that CS5.5 had its interface retooled, and the lag present in CS5 is lessened, at least this is my impression of the trial version, and opinion of a few Colorista users.

But it still does not beat the responsiveness of Premiere on PC, which is instantaneous, and I'm certain on par with FCPX on Mac.

Why wouldn't you spend the money AND time to learn Premiere Pro CS5 (or 5.5) which is better than FCPX in every way and has been ready for work since its release 18 months ago. Heck, it even allows easy XML importing from FCP 7, something 'X' cannot do. Plus, CS5.5 allows you to set the shortcuts to replicate FCP 7.

Why? Because it is not better than FCPX in every way. I have tried it and couldn't do half of what I could do with FCPX in 15 minutes. With FCPX I could replicate several short FCP 7 projects in a few minutes down to the point of being ready to export. That was not possible with me and Premier. Could you do it? Possibly but for me, repeated attempts to use Premier through Adobe's generous 30 day trial offer have not worked out. In short, I don't like it but to balance this out, I don't like Apple's Motion and use Adobe After Effects instead. Anyway $300 is a bargain for an editing program with the level of power FCPX has and worth the money.

Work with Premier, have fun with Premier, in the end the viewer will not know or care where it came from. Let's stick with the thread topic. Anybody else having crashes or odd saving issues with X?

Like it or not, real BEST PRACTICES is to be able to utilize various workflows on various systems to suit what the client wants (some WILL insist that you use FCPX)

If video editing is really your bread and butter, then you should apready have options. FCPX, Adobe and Avid are cheap enough that you can have all of them.

So, that's it for me so far with FCP X.... Got to either stick with FCS3, or head to Adobe...

Today I was working on my first FCP project. I did about 3hrs work this afternoon, and then quit for a while. Everything was fine...

Then I launched it again, and did around 3hrs more work. Of course, there's no 'save', so I'm just assuming everything is 'saving' along fine. I noticed that the 'skimming' feature didn't seem to be working anymore, so I quit FCP X, and then re-launched it (no error messages, or anything).

All of a sudden, my project is back to where I FIRST quit 3 hours ago! 3 hours of work just disappeared in 20 seconds!

Can anyone suggest why this may have happened? If I can't trust this software to do something as basic as just SAVE my files, what good is it at all?

Frustratingly yours....

Ben

Ben - is FCP-X co-existing on the same boot drive/partition as FCP7? If so, did you carefully follow Apple's guidance on installing them? Finally, have you updted your OS to 10.6.8?

Terry

"Ben - is FCP-X co-existing on the same boot drive/partition as FCP7? If so, did you carefully follow Apple's guidance on installing them? Finally, have you updted your OS to 10.6.8?"

Yes.. I did everything the installer told me to do. 10.6.8 didn't exist at the time.

B.

Ben - If you are talking about just downloading and installing from the App Store, unfortunately, through no fault of your own, that may have led to some of your problems. Here is the detailed instructions for getting FCPX up and running on your machine if you also have FC Studio installed...

Final Cut Pro X, Motion 5, Compressor 4: Installation best practices (http://support.apple.com/kb/HT4722)

I did it this way and , so far, no problems.

Best of luck.

Hi, Terry...

Neither that document nor the update was available when I had this issue. Of course, things may be better now, but that doesn't help. It's like saying 'driving is the leading cause of car accidents'. Using the softwareis the leading cause of crashes... :)

I did what I was told at the time. Why doesn't this document pop up when you run the installer? That's crazy!

Things broke. I'm not saying that things won't be better, just that the software is currently 'untrustable'.

Best,

Ben

Ben - I know, I was surprised by it, too. I was just luck enough not to have done much more than start FCPX and quit before I found out about it. If you don't have any luck sort of backing out and starting over, maybe Apple support can get you where you need to be.

Good luck.

I've been using Premiere for many years now, recently switched to running PPro on Mac. It's smooth as silk. I have no complaints. It's all that and a bag of chips. Red Giant's Magic Bullet Looks + Adobe Media Encoder has made workflow efficient and look good, too. My company just ordered 6 new work stations to run FCP X, so I'm gonna have to learn FCP X and make it work with my demanding workload and deadlines. Can anyone tell me their experiences and whether or not these are real issues with FCP X:

* Unable to import / work with certain file types like MPEG2 (HDV)
* Limited video capture, Firewire only capture / ingest
* Can't reconnect to "Offline Media"
* Users can't assign audio tracks, must have utility called "Automatic Duck Pro Export" to do so. - This is especially important to me since almost everything I do involves split tracks, foreign language tracks, narration, and multiple levels of background sound.
* No P2 support, or there is some kind of "trick" to capturing / ingesting P2 files.
* Third party software required to export to tape. I still get occasional requests for that and would like to have that as an option.
* Can’t connect an external video monitor.
* Issues with saving / autosaving project
* FCP isn't really the choice for pros, but merely an advanced iMovie application.

A lot of questions are answered (adressed) here:
Professional Video Editors Weigh In on Final Cut Pro X - NYTimes.com (http://pogue.blogs.nytimes.com/2011/06/23/professional-video-editors-weigh-in-on-final-cut-pro-x/)

Some of the issues you list are indeed issues right now, but most assume those to be fixed fairly soon. EDL being about the only thing it seems Apple will not provide at all (but this may also be provided by 3rd party providers as I understand, same with OMF etc.?).

I gather FCP 7 has been withdrawn from the market, which seems a strange act by Apple when the replacement seems to be a beta rather than a fully functioning program.

If you're going to introduce a new version of professional software that replaces an established product, you need to make sure it performs all the functions of the old one. Also, at the very least, it should convert the old projects into new versions that the new software can handle.

It sounds like Apple put out this underdeveloped version out to show they're actaully doing something to prevent people moving over to the other NLE systems, which now seem to have been listening to editors who use the programs.

* Unable to import / work with certain file types like MPEG2 (HDV)
* Limited video capture, Firewire only capture / ingest
* Can't reconnect to "Offline Media"
* Users can't assign audio tracks, must have utility called "Automatic Duck Pro Export" to do so. - This is especially important to me since almost everything I do involves split tracks, foreign language tracks, narration, and multiple levels of background sound.
* No P2 support, or there is some kind of "trick" to capturing / ingesting P2 files.
* Third party software required to export to tape. I still get occasional requests for that and would like to have that as an option.
* Can’t connect an external video monitor.
* Issues with saving / autosaving project
* FCP isn't really the choice for pros, but merely an advanced iMovie application.

I'll answer what I can from juggling work and experimenting with X.

- X can import QuickTime HDV files made with Clipwrap. Raw m2t is not recognized.

- I have only captured HDV thru FireWire with deck control. That works fine. I frequently capture wild sources thru a Canopus A to D converter, that's my next experiment.

- Offline media is re-connectable if you follow Apple's new media protocol. Otherwise the re-connection options you are used to in 7 apparently is not there.

- You have multiple layers of audio available but there seems to be no formal track numbering on the timeline. This is a problem for my complex projects but for the simple ones it works fine.

- P2 is captured thru "import from camera" regardless of where the files are stored before import. Something to do with the P2 file structure or just a weird oversight.

- Removing export to tape is one of those "Apple skips ahead" things that they do from time to time that drives people nuts. Here's the work around: Export the project as a QuickTime file and open it in FCP7. Export to tape is back. I have been doing for a few years anyway as I frequently use an older computer to print to tape so I can get back to work on the main one.

- No external monitor option yet unless you have a DVI to video device that works outside of FCP. Someone else with experience with these devices will have chime in here. I have a second computer monitor that is color corrected with a Spyder Elite device but it's not 100% accurate, maybe 95%. It works fine for me and I frequently output to 35mm film.

- I have not had saving problems since the first crash.

- That iMoviePro tag is not a fair comparison. While it is based on iMovie's 64bit architecture, there so much that this version can do beyond iMovie that I think it's in class by itself. BUT.... it certainly needs work and several FCP7 features brought back. There are so many color filters and other effects included that it could be worth it just as a 64bit effects program. People should think about that as well.

Add to that list: you cannot purchase more than ONE copy per iTunes account so your boss will have fun trying to buy 6 copies. You will also have to sit and wait for each computer to download from the app store.

You also cannot export audio only or edit multicam.

The writing is on the wall and it is clear as day: Apple intended this app to be a consumer-ish, watered down NLE.

Add to that list: you cannot purchase more than ONE copy per iTunes account so your boss will have fun trying to buy 6 copies. You will also have to sit and wait for each computer to download from the app store.
.


I have downloaded multiple copies with my itunes account. Was allowed to do it on all my systems and even run them at the same time.

According to the podcast with Biscardi and Harrington, if you have multiple users on multiple computers, you need the multi-user license BUT this license is not for sale anywhere. According to them, what you did is not legal according to Apple's licensing terms.

According to them, what you did is not legal according to Apple's licensing terms.

Louis, what you did IS legal. They are all under your own Apple ID for your own computers and I quoted the relevant part of the Apple license agreement in another thread. Walter B. was talking about a different scenario.

Please Steve, this FCP X release has been disappointing and painful enough without adding false data into the mix. I am glad that both Adobe and Avid have such great solutions waiting in the wings. If Adobe were really smart, they'd keep that "Upgrade to 5.5" special open for another 6 weeks rather than having it expire in 4 days. By then, the updates, or lack of them, to FCP X on super-critical features like repairing the connections to your media (the topic of this thread) and importing FCP projects from earlier FCP versions will tell most FCP editors which way the future winds are blowing.

Thanks for the info, William. It's really helpful. I'm cautious about investing time into learning a program that can't recognize M2T file which come from my camera. I've never clipwrapped anything and don't feel good about not being able to edit with native files in the timeline. Well, we are going to have six of these brand new FCP X stations and I don't think FCP X can deliver what we need. It's gonna have to meet our deadlines, complex, multi-language demands while at the same time offer compatibility with other formats and platforms. Can plug-ins such as Magic Bullet Looks, Colorista, etc, be used on FCP X or are users limited to color correction / effects contained in FDC X? Thanks again, William

I've been using Premiere for many years now, recently switched to running PPro on Mac. It's smooth as silk. I have no complaints. It's all that and a bag of chips. Red Giant's Magic Bullet Looks + Adobe Media Encoder has made workflow efficient and look good, too. My company just ordered 6 new work stations to run FCP X, so I'm gonna have to learn FCP X and make it work with my demanding workload and deadlines. Can anyone tell me their experiences and whether or not these are real issues with FCP X:

* Unable to import / work with certain file types like MPEG2 (HDV)
* Limited video capture, Firewire only capture / ingest
* Can't reconnect to "Offline Media"
* Users can't assign audio tracks, must have utility called "Automatic Duck Pro Export" to do so. - This is especially important to me since almost everything I do involves split tracks, foreign language tracks, narration, and multiple levels of background sound.
* No P2 support, or there is some kind of "trick" to capturing / ingesting P2 files.
* Third party software required to export to tape. I still get occasional requests for that and would like to have that as an option.
* Can’t connect an external video monitor.
* Issues with saving / autosaving project
* FCP isn't really the choice for pros, but merely an advanced iMovie application.

Your company did WHAT!? I can't believe that, it may be the most irresponsible thing I've ever heard in a professional industry. Regardless of how you feel about FCPX, it IS a 1.0 completely re-tooled program. Even if it had 90% of these things all the pro's are complaining it doesn't, it's would still be hard to understand any company doing that. I wish you all the best in that place between a rock and a hard place.

Thanks for the info, William. It's really helpful. I'm cautious about investing time into learning a program that can't recognize M2T file which come from my camera. I've never clipwrapped anything and don't feel good about not being able to edit with native files in the timeline. Well, we are going to have six of these brand new FCP X stations and I don't think FCP X can deliver what we need. It's gonna have to meet our deadlines, complex, multi-language demands while at the same time offer compatibility with other formats and platforms. Can plug-ins such as Magic Bullet Looks, Colorista, etc, be used on FCP X or are users limited to color correction / effects contained in FDC X? Thanks again, William

First of all, editing a raw m2t file is no fun and will bog down the fastest computers. It always better and faster in the long run to convert m2t or AVCHD into a frame based codec such as ProRes. Especially if there are filters being used.

And if you haven't tried ClipWrap and you are working with a lot of m2t files, you have been suffering needlessly. For $50 it solves a lot of problems.

No third party filter works with X yet but X comes with an array of color filter presets that should be very useful if not actually replacing some of the presets in the effect packages you mention. And they are 64bit filters so your rendering time is reduced if not eliminated. I have not experimented with them yet but they are there.

The program works but is wonky in places and Apple needs feedback from actual users who have taken the time to work the program and understand the methods used. If after a week it turns out you can't edit a multi language program with it, then you are correct but I can think of one method right now but I would need to test it before passing it along. And I think your bosses should have bought one program to experiment with not six.

Eric, “the most irresponsible thing I've ever heard in a professional industry” is a bit harsh. The decision was made long before the stuff hit the fan with FCP X. There are many involved in this decision, most of whom have been relying on Final Cut for a long time and know the program well.
William, thanks for your feedback! As I mentioned, I’ve been editing with Premiere for a long time. And cutting m2t with premiere on a Mac has been smooth as silk, better than raw from XDCAM EX. I’m actually going into FCP as a relative newbie. Up untill FCP X came out, I was looking forward to mastering the program. Now, I dunno….

Stick with Premier but play with X is my unasked for advice.

M2t is usually a lower bit rate than XDCam, I think almost half the rate, which is why you have a good time with it but XDCam is stiff. ClipWrap turns the m2t files into QuickTime HDV which does not change the data in file. It's still m2t but with frame markers for editing built into the file now which reduces some of the load on the computer.

If this program is not supposed to be used yet for projects, then why has it been released? And if it's not supposed to be used for professional editing projects, then why does it bear the name of the product that is aimed at professional editing?

All these problems and complaints could be solved by simply starting a new product line.. call it "iCut" instead of "Final Cut" and people will go in with the right expectations. Keeping the same name, EOLing the previous version, and purposely turning off backwards compatibility is simply bizarre and insulting to users.

William, your advice is welcome. Thank you! Yes, I plan to stick with Premiere. Being the odd-man-out still using Premiere / Red Giant Magic Bullet Looks while others using 32bit FCP is awkward but very effective.

So major functionality can disappear from a program and we're supposed to accept that this as an upgrade? I'm sorry the Apple Koolaid is beginning wear off and I'm starting to feel the hangover.

The absence of multicam editing makes this program just an inept little toy, like iMovie.

If this program is not supposed to be used yet for projects, then why has it been released? And if it's not supposed to be used for professional editing projects, then why does it bear the name of the product that is aimed at professional editing?

All these problems and complaints could be solved by simply starting a new product line.. call it "iCut" instead of "Final Cut" and people will go in with the right expectations. Keeping the same name, EOLing the previous version, and purposely turning off backwards compatibility is simply bizarre and insulting to users.

As an Apple share holder, I vote for Jad Meouchy as new head of Apple Product Development. I'm serious. Now, someone needs to be fired.

Stick with Premier but play with X is my unasked for advice.

M2t is usually a lower bit rate than XDCam, I think almost half the rate, which is why you have a good time with it but XDCam is stiff. ClipWrap turns the m2t files into QuickTime HDV which does not change the data in file. It's still m2t but with frame markers for editing built into the file now which reduces some of the load on the computer.

That's what I'm going to do too.

I use Premiere CS5 on a optimized Windows machine which I use only for my editing work, but although editing is fast, sometimes (especially using Magic Bullet) it still crashes every now and then. As all of you know, nothing more frustrating than finishing and fine-tuning a sequence and then the suite crashes...

Although I'm used to the Premiere interface, I really like the After Effects integration, last summer I did a project on Final Cut (Express allright...) and it felt very good. Can't quite describe what's exactly different or better, but it just feels better than Premiere. Also, quite an annoying bug in Premiere is that I have to wait a few seconds when I leave the Premier window and go back.

With my 'main' computer being a MBP, I decided to wait for the new iMac and FCP X, rather than buy and learn FCP. So the mixed, mainly negative reception of X, I'm a little bit disappointed. But... Steve Martin's review @kenstone.net is rather helpful, and he's happy to explain the useful improvents of X, rather than dismissing the software after just one quick look and the missing things...

So quite a long story, but in essence what I'm going to do is: keep editing on Premiere CS 5 for now (although I'm tempted to upgrade to CS5.5, really like the new Warp Stabilization in After Effects, and because I work at a university, I can use the Student&Teacher editions), but I still feel FCP X will become a great program once embraced by the community, so I'm going iMac en keep playing with X and see it getting better and better. If it doesn't, there will be always CS5.5 or 6 for Mac...

I hear older versions of FCP were met with mixed reviews in the beginning, and only later grew out to be one of the best NLE's out there...

Also, quite an annoying bug in Premiere is that I have to wait a few seconds when I leave the Premier window and go back.

During this time Premiere checks if all your media files in your project are still present. It takes more time if you have a lot of footage or you're working from a slow hard drive or network. It's not necessarily a bug, although I would hesitate to call it a feature either :)

EDIT: It also checks the render files, so if you do a lot of rendering, and then lose the files by changing stuff, it might be prudent to delete render files from time to time to get better performance.

Okay... I didn't realize that, at least I understand now why Premiere is doing that! Thanks!

Also, quite an annoying bug in Premiere is that I have to wait a few seconds when I leave the Premier window and go back.

Disable your antivirus program.

Michiel, I've been using Premiere with Windows since way back when. It crashed often, froze up, etc. Got PPro 5 for Mac with 8GB RAM and couldn't be happier. It crashes but not nearly as much as it did on Windows. We did a test on the Mac with both OS (Windows and Mac) through parallels. My conclusion is that PPro on Mac OS ran extremely well. The scrubbing was incredibly smooth. Running PPro through Windows on same machine, well, not so much if you know what I mean. I'm sure there's some explanation for this phenomenon, but I'm sticking with PPro for 64-bit Mac. It's the best solution for me right now especially with all the controversy over FCP X.

It's really not a valid test at all to compare any application running native on the Mac with a Windows version of that same software running in a virtual machine. In fact I am rather surprised that CS5 running within Parallels worked properly at all. Many programs work great under a VM but heavy duty NLEs that do a lot of graphics will never work well. I actually managed to get Edius 6 installed in a VMware Fusion VM but could never use it for editing which at least was an improvement on Edius 5 that wouldn't even install.

It's really not a valid test at all to compare any application running native on the Mac with a Windows version of that same software running in a virtual machine. In fact I am rather surprised that CS5 running within Parallels worked properly at all. Many programs work great under a VM but heavy duty NLEs that do a lot of graphics will never work well. I actually managed to get Edius 6 installed in a VMware Fusion VM but could never use it for editing which at least was an improvement on Edius 5 that wouldn't even install.

Thanks Nigel for pointing out exactly what I was going to say.

As far as editing on a PC goes, your experience GREATLY depends on what additional software is installed. My personal editing bay in my studio, I have an HP Z800 (12-core, 24GB, Quadro FX3800, Areca 1680ix, 6 2TB Seagate Constellation ES in R5....) with Win 7 x64 Pro on an Intel X25 80GB SSD with only a handful of necessary programs installed in addition to Master Collection CS5 (C4D 11.5, NukeX 6, FileZilla, TeamViewer, Vimeo Uploader, Office). Aside from a couple of bad Macally external cases causing BSODs, I can count the number of crashes on one hand since I got this computer and CS5 last spring. You can't get a more stable system then this and I got 25% off the Z800 without even asking. Oh yeah, I only use Firefox with add-ons and NO anti-virus.

I have another small drive with Win 7 installed (since its OEM, I can install it as many times as I like on this computer to as many drives as I want). I use this drive for testing and have CS5 installed in addition to many other programs, and the stability is not nearly as good as my 'work' drive because some of these programs are not well written.

I have done IT work on the side for the last several years, and I can say that there are only 2 reasons for PC problems (aside from hardware malfunction) - people installing viruses or installing crap software. For one of my clients, an entire office was infected because of idiots from the federal gov't (HUD) performing an audit and downloading personal 'stuff' while they were supposedly working.

Thanks all, I'm thinking it also could be the combination with the firewall/virusscanner that makes Premiere crash... I've quite a dedicated (win-only, not parallels) system but not as dedicated as Steve's, hence my experience with the occasional crash.

But since I'm planning to go Mac-only, I just as well upgrade to CS5.5 for Mac.

I'm late coming to this thread, but I'm glad that everyone is judging the software based on their use with it, not what a bunch of bloggers and podcasters are saying. I love Rich and Walter, but if I did everything they suggested, I'd be broke! I'm not a big production house, I'm just an individual editor.

A lot of the false info and opinions based on opinions, based on what others have experienced, reminds me of what I was hearing in 1999 when FCP 1.0 first came out. (If fact, Bill Davis has a great thread/discussion (http://www.dvinfo.net/forum/final-cut-pro-x/497907-fcp-x-looking-forward-while-looking-back.html) going on an article he wrote.)

When I get FCP X, I will judge it then; but for now, I'm going to do research with cold hard facts and read real reviews, good or bad, not "I downloaded it, opened it, cried, uninstalled it and asked for a refund," or what not.

heath

Originally Posted by Jad Meouchy
If this program is not supposed to be used yet for projects...
well put

As for Premiere, I've used it only on the PC and have had similar experience in regards to it crashing. FCP is rock solid in this regard. It could very well be Windows or applications that run in the background such as anti-virus. Mac OS underneath is cleaner and better written with a lot less hardware variables to deal with.

well put

As for Premiere, I've used it only on the PC and have had similar experience in regards to it crashing. FCP is rock solid in this regard. It could very well be Windows or applications that run in the background such as anti-virus. Mac OS underneath is cleaner and better written with a lot less hardware variables to deal with.

You really must try Premiere CS5 or newer to see how rock-solid it is. In addition, using Premiere on a Mac Pro from the last few years will amaze you at how much faster your workflow can be when compared to any version of FCP. You just can't beat the simplicity of creating a simple 1080 sequence, importing ANY video format/size and BEGIN editing. Throw on some effects and hit play...rarely is rendering required. Create some motion graphics in AE and easily import without having to render first. Change those AE comps and instantly see the updated version in Premiere.

I think someone else mentioned this, but FCPX cannot import PSD files as layers anymore. With Premiere (and AE), you can alter something in Photoshop and have Premiere show the updated version.

And the rendering speed of CS5 with hardware acceleration is amazing. I tested a 2min AVCHD sequence with 3 layers and 6 effects on each layer. In CS4, it took 51mins to render and only 9mins in CS5 on a stock speed i7 at 2.66GHz & 12GB of ram.

Also, with Premiere and AE, the more ram you have, the faster they render. For example, a 6-core CPU with 24GB of ram is roughly 80% faster than with only 12GB of ram for MPEG2 exporting and about 25% faster for H264 exporting.

I think Premiere Pro is a great app, and some people may switch to it or Avid, but I've always been a FCP kind of guy. I was talking to my friend and former colleague Douglas Spotted Eagle about FCP X and a new paradigm in editing. We discussed something similar in 2005, as Vegas Pro starting to build a loyal following by introducing a new -- and faster -- way to edit.

I'm looking to the future and hope FCP X can meet my needs.

heath

3 Weeks ago, I never would have thought that I'd download a free trial of Premier, 10 days after the release of FCP X. For the last 2 years I have been one of those people that have said, Apple wouldn't do that, give them some time & they will come out with a great new FCP and put some of the $ back into the pros that built their company. But no more.

I see FCP X going to an iPad version, where you can edit and then just hit, send to facebook.

Adobe had a faster way to edit, what a year and a half ago.
You can bring in FCP projects into premier.
Premier even has keyboard shortcuts for FCP7.
I downloaded it last night & felt very comfortable & was editing fairly well in about an hour.
It's very fast.
I could use a PS upgrade & I've always wanted AE and Illustrator anyway.
I believe it will take over FCP's place as the most common pro editing suite, so I want to be familiar wit it.
$799 for the entire suite for me (own PS) till Monday, I believe I'll do that.

For 12 years I've been using photoshop, and throughout that time period, Adobe has always worked to improve it for professionals. I've never felt like they would cripple their product to make more money, where I feel that that has been a major component of Apples marketing strategy.

I'm not bashing Apple really, more just acknowledging Adobes commitment to pros.

For the people that like it, good for them, I wish I had some of it's features, but I don't think you'll be seeing ads on craigslist saying, "looking for a FCP X editor".

3 Weeks ago, I never would have thought that I'd download a free trial of Premier, 10 days after the release of FCP X. For the last 2 years I have been one of those people that have said, Apple wouldn't do that, give them some time & they will come out with a great new FCP and put some of the $ back into the pros that built their company. But no more.

I see FCP X going to an iPad version, where you can edit and then just hit, send to facebook.

Adobe had a faster way to edit, what a year and a half ago.
You can bring in FCP projects into premier.
Premier even has keyboard shortcuts for FCP7.
I downloaded it last night & felt very comfortable & was editing fairly well in about an hour.
It's very fast.
I could use a PS upgrade & I've always wanted AE and Illustrator anyway.
I believe it will take over FCP's place as the most common pro editing suite, so I want to be familiar wit it.
$799 for the entire suite for me (own PS) till Monday, I believe I'll do that.

For 12 years I've been using photoshop, and throughout that time period, Adobe has always worked to improve it for professionals. I've never felt like they would cripple their product to make more money, where I feel that that has been a major component of Apples marketing strategy.

I'm not bashing Apple really, more just acknowledging Adobes commitment to pros.

For the people that like it, good for them, I wish I had some of it's features, but I don't think you'll be seeing ads on craigslist saying, "looking for a FCP X editor".

Hi Chris,

Good to hear that you like what Premiere has to offer.

I think your last comment sums up everything PERFECTLY!

If you have questions how to perform certain tasks, would you like a dedicated thread for people like you who have switched to Adobe from FCP where you can ask fellow Premiere users? I emailed Chris to see if creating a sticky thread would be possible. I was helping someone else the other day and ended up learning a few things myself about Premiere; so, I see this as a good thing for everyone.

Steve,

Do you work for Adobe? I'm just curious.

Heath