Not quite as positive things

Seriously -- anyone posting their distress here is distressed because of everything that's in this short film -- we can not use 10 years of work created in FCP in this new product - it's great for a quick stand alone non tape or film based short project - everything else has an enormous question mark. Even Larry Jordan's seen the light with his latest blog post - David Pogue's straight from Apple PR piece came with a follow up - rare for that reporter who loves all things Apple - that "Apple blew it"

This video - while melodramatic - says it all. Anyone in Cupertino listening?

[url=

]FCP Studio's demise Video[/url]

Wow.

Nice rigid body simulations there. I would like to know what they did it with.

I suspect by this time next year nearly every feature issue in that video will be addressed. I believe the first update will be in four months. Of course many can't wait 'till it reaches feature parity with FCP7. They should have kept FCS available until then. It would have allowed for a year long transition.

Many of Noise Industry plugins are already compatible. Nearly FXPlugs from the various companies will be converted to 64bit and made compatible with FXPlug2. Any movement to 64bit will break all 32 bit plugins. I believe the same happened to After Effects.

One Sequence per Project is a bit of an oxymoron. Project is a container for a Storyline (what used to be a sequence).
Think of an Event as what used to be a project and you can have multiple Projects (sequences) for an Event.

Autosave I believe is built in. There's no iterations though. You have to duplicate the project to save that "state."

craig seeman Wrote:
-------------------------------------------------------
> Autosave I believe is built in. There's no
> iterations though. You have to duplicate the
> project to save that "state."

Lion will take care of that.

My software:
Pro Maintenance Tools - Tools to keep Final Cut Studio, Final Cut Pro X, Avid Media Composer and Adobe Premiere Pro running smoothly and fix problems when they arise
Pro Media Tools - Edit QuickTime chapters and metadata, detect gamma shifts, edit markers, watch renders and more
More tools...

Jon Chappell Wrote:
-------------------------------------------------------
> craig seeman Wrote:
> --------------------------------------------------
> -----
> > Autosave I believe is built in. There's no
> > iterations though. You have to duplicate the
> > project to save that "state."
>
> Lion will take care of that.

True, Lion will have the ability to go back iterations built into the OS.

Seriously, and in all due repect...

Really? By next year all the missing functionality will be fixed and we'll have an app that fully replaces an entire suite of apps previously called Final Cut Studio and working as the full post production business solution FCS was originally sold to us as being? And no more dropping new apps like Color with no forewarning, no more pulling stock from resellers with no forewarning, no more making a vast selection of third party apps and gear unuseable with no forewarning, no more blindsiding an entire industry of third party software and hardware providers, no more creating a total PR disaster worthy of the textbooks on the subject for years to come?

And in the meatime I'm supposed to use the old FCS suite untill they get around to fixing things, and trust that everything will be aok while sales and support for FCS are being discontinued, and with it most likely all the third-party development and gear?

I honestly really and truly feel for you guys who are involved with running and moderating FCPX usergroups right now, or have businesses centered upon selling FCP training and related stuff. It's gotta be tough going. Especially so, with such an uncertain future. Obviously, all that you all can do now is try to make the best of a bad situation. Judging by the overwhelming majority of negative opinions here and on every other Pro user forum, the damage has been done. It is going to take a very long time to turn opinion around now. Just try to keep it real.

The roof blew off mainly because Apple released a product that was not ready and dropped sales of a stable system that was. I was just with my ops manager and he is trying to get licenses of FCP 7 as the current version of X does not have the functions required for a collaborative editing environment. A product should be released as a pro release only after the pro features are in it, not before.



www.strypesinpost.com

I was wondering about licenses. Now that FCS is basically Abandonware, what does that mean re the EULA? Have you found out anything yet?

Wow, Raberco is a bit of a drama queen, eh? I can't think of anything more pathetic than joining a circle-jerk of hate called, "FCP Professionals Not Happy With FCP X", even IF I was as upset as he seems to be.

It's funny, among the actual legitimate missing features that pros are complaining about, someone comes along who says, "You know, it doesn't sound like enough to complain about Multicam, EDLs and XMLs, let's add a bunch more crap despite the fact that it has little to do with Apple at all."

Thus the complaint about: plugins not working, import from tape, video monitoring. Even though these are reliant upon the 3rd party manufacturers producing hardware and software to fit the new rewrite. It is a rewrite after all, not an add-on to existing code. All that will be addressed...by the companies that handle that stuff anyway.

If you were able to buy FCS 3 and install it on your computer, you would not be able to import from anything other than firewire without a capture card, nor monitor without one (with the exception to FW monitoring. Not sure if that's gone or not. If so, then it's a legitimate complaint), and your plugins will work when the company that makes the plugin makes them work on the new system.

Then there are the complaints that aren't even true, or are simply different from how it was done previously. Only one sequence per project? Not true. Can't set scratch disk. Not true. Media not handled the way it used to be. Absolutely, and thank goodness. Honestly, I can't believe there are so many people upset that media is being handled differently than before. Especially from pros. A lot of them, those pros, are used to working with Assistant Editors who are tasked with organizing media in projects. When left to it themselves, they are typically horrible with it. Not everyone, I'm particularly AR about handling media, but only because I've learned to be. FCP REQUIRED it. Now, FCP X handles media more like Avid, and aren't pros always complaining that Avid does a much better job handling media than FCP?

Some people just can't get off the hate train long enough to be honest with themselves about this. You don't like the interface? Fine. You can't use it yet to collaborate with others? Fine. But don't go hunting for random little things that weaken the argument, not strengthen it.

FCP X is missing the following:

Multicam
XML/EDL import/export
Log and Capture (and monitoring?) for FW devices

There's probably one or two more legitimate complaints in there that I can't think of, but of those three, I expect all of them to be addressed by Apple. The others will be addressed by Aja, Blackmagic, FX Factory, Boris...etc.

Andy

Inability to open any previous projects created in any version of Final Cut.

Seriously unstable, but maybe we've been spoiled. Couple of crashes a day, and occasional complete loss of data.

No reconnect function at all. Only reimport, and no reconnect to existing project.

It is only one sequence per project. However you can have as many projects as you want, but each project is in a unique folder.

Scratch disk can only be set to a local drive and only to the top level of the drive. No shared storage, no custom folder structure for scratch disk assignment. All media is open to all projects, sounds like a good thing, unless you have clients in your room, who you might not want to show competitor's media. There are ways around this, mounting and unmounting multiple drives.

There is no save function or any backup from any project file, unless it's done manually, or a mirrored RAID system is used.

Serious audio mixing and sync issues in the magnetic timeline interface. Not a question of like or not like, more like not working. Clips go out of sync with cross fades, mixing is horrendous, and often simply not possible.

That's all that comes to the top of my head, I'm sure there's more.

All the best,

Tom

> Now that FCS is basically Abandonware, what does that mean re the EULA? Have
>you found out anything yet?

Problem is that I was looking at a bunch of machines hooked up through a SAN. Other than firewalling the software (not sure if you can do that on a SAN), you basically need licenses which authorized dealers are not supposed to sell. I don't mind waiting a bit, but when projects need to be cut today, you can't wait for feature roll outs on a software that is not even at beta level.



www.strypesinpost.com

Tom Wolsky Wrote:
-------------------------------------------------------

> It is only one sequence per project. However you
> can have as many projects as you want, but each
> project is in a unique folder.

An Event in a project.
A Project holds a Timeline which is the Primary and Secondary (if used) Storylines.

There are separate Event and Project Libraries.
You can create as many Projects (sequences) as you like and use them in any and all events. I've tested this.
It's like a relational database. To create a new version of a Timeline, just duplicate the Project.
You can have Rough Cut, Second Cut, Final or whatever you like. Just duplicate and start the next version.
Keep in mind though that the Project is NOT tied to an event.

For example:
I create Book Publishers Marketing Video Final as a Project. I can open that in my Corporate Safety Training Event.

Projects (Timelines) are independent of Events (what is now a project more or less). They are two separate Libraries and any Project can be opened in any Event.

Key is understanding that an FCPX Project is not tied to an Event and you can do versioning as you have always done.

Won't it make sense to rename "project" and call it "scenes", and rename "events" to "projects". In this way you can have a short project like an ad with one scene, and that would be in one timeline. Instead of having a feature film with lots of projects.



www.strypesinpost.com

strypes Wrote:
-------------------------------------------------------
> Won't it make sense to rename "project" and call
> it "scenes", and rename "events" to "projects". In
> this way you can have a short project like an ad
> with one scene, and that would be in one timeline.
> Instead of having a feature film with lots of
> projects.

Apple's use of the term Project in FCPX is certainly confusing. Also adding to the confusion is the ability to
Duplicate Project
Duplicate Project and Referenced Events
Duplicate Project plus Used Clips Only

So in that sense it's still like a Project in relation to Media Management.
Option 2 would be if you were to continue to edit on another system. Keep in mind that the Project can use clips from different Events.
Option 3 would be if you were to archive the project using only the media in the Timeline.

This is part of the relational database kind of thing. I do think it would have made sense for Apple to use a word other than "Project."

Duplicate Project is just like a save as. No media is moved or changed and if you send that project to someone else everything will be offline.

Duplicate Project and Referenced Events keeps the all the media associated with the project with the ..erm, project. It's a bit like a consolidate.

Duplicate Project plus Used Clips Only is a media manage of yore, and you can make a new 'event' to go with the cut-down version during the dupe.

Quote
Tom Wolsky
Inability to open any previous projects created in any version of Final Cut.

This is an off-shoot of the XML import/export support. I don't think it realistic to expect FCP X as a completely different program to be able to seemlessly open FCP 7 projects. Once XML support is restored, then this will return.

Quote

Seriously unstable, but maybe we've been spoiled.

Again, new software. You can beta test for months and it's pretty much guaranteed that someone will break it the first day.

Quote

Scratch disk can only be set to a local drive and only to the top level of the drive.

I have mine set to an external drive, but maybe that's not what you're talking about? I don't have a NAS or SAN, so I don't know about shared storage. Does FCP X not see a mounted SAN?

Andy

>Lion will take care of that.

Not necessarily, not unless FCPX suddenly becomes document based.

Andy Neil Wrote:
I don't
> have a NAS or SAN, so I don't know about shared
> storage. Does FCP X not see a mounted SAN?
>
> Andy


I have OSX Server running on my Mac Mini, and I can tell you FCP X cannot recognize shares from the server. I'll keep experimenting and let you know if anything changes.

However, Xsan is built into Lion (both client in Lion and Xsan in Lion Server), so I would imagine that Apple's assuming some kind of Xsan in the future.

Steve Kanter
Avid Certified Trainer and Editor
Final Cut Studio Master Trainer and Editor
Certified Xsan Administrator and Workflow Specialist
(323) 823-6952
steve@editdog.net
www.editdog.net