-
Point Me In the Direction of A………..
-
Placeholder can indicate a possibility. It means someone was thinking about that whether aborted or for future implementation.
-
Jeremy –
I believe you when you say that Apple had to totally re-write the FCP to move forward, there were so many long standing bugs and quirks that it became obvious the programmers were hamstrung by the existing code.
I was a Discreet edit*or back when their programmers took almost 2 years to totally re-write their code. The results were a better faster more powerful editing ap that was an upgrade in every way (which didn’t stop Discreet from Eol’ing it, or might actually have hastened it’s demise; but thats another story.)
Why Apple chose not to create an upgrade that would have freed them from the limitations of the older code, but rather to create FCPX in it’s place, an ap that is a huge step back in useability for the “high end” of their market (at lest in the short term) is the unanswered question at the heart of every post here. Only a few people at Cupertino know, and they ain’t talking – at least not to me.
Herb Sevush
Zebra Productions -
Which was my point, but you are constantly trying to stretch it into that it was a fact that there was an attempt, when this says nothing at all.
-
Thank you Mike! That was part of my original thoughts. You said it much better! I think I said something like “it is a Mac thing” I will say, my MacPro is the best computer I have ever owned, and I have owned almost every workstation sized system, even a Silicon Graphics back in the day, the Apple hardware is top notch. I just hope they keep producing it. They seem to be leaving it behind. Also, the app store is a big error for pro users. If I can go to say, BH in New York, and they can sell me Avid, or demo Adobe for me and make a buck, they wll be a sales force for those products. The app store is part of Apple’s vision for a medialess future that is not completely here yet. First off, I like back up install disks, every now and then I do a full system clean and need them. It is the mentality that did away with DVDSP. Admittedly, I can make blu-rays and my clients don’t really want them, blu-ray is sort of DOA, they hype it and all, but it is still not so popular. And HD media players are more accessable today. I give clients a lot of HD downloads they can play right on their TVs or via ps3 or WD, etc. But many many clients still want a DVD, everyone has a Player and can watch it. Apple should usher in the future, but you can’t force it on people. If they had introduced the iPod with no way to get the music off of your CDs and on to iPod, nobody would even know what an iPod is…or was.
Rich Kaelin
Kaelin Motion Production Services
https://kaelinmotion.com
New York -
[Rich Kaelin] “my MacPro is the best computer I have ever owned, and I have owned almost every workstation sized system, even a Silicon Graphics back in the day, the Apple hardware is top notch. I just hope they keep producing it. They seem to be leaving it behind.”
I don’t see anything that indicates they’re leaving the MacPro behind. Like most things Apple, there may be a major redesign soon. I suspect Thunderbolt may result in the decline in the number of PCIe slots but as to when that will happen is anybody’s guess.
[Rich Kaelin] ” Also, the app store is a big error for pro users.”
It certainly is a problem on many levels. When I bought FCPX I was able to download it of course but it didn’t acknowledge the purchase. Therefore any attempt to install on another system attempted to force me to purchase again. That’s when I also found the App Store has no phone support when I wanted to fix the purchase issue. I ended up having to call another department with a vigorous complaint so they would transfer my call. In then took them a couple of days to fix the issue. This is absolutely unforgivable for a “pro” application.
I’m not sure how VARs are handling things buy I know locally Tekserve, which offers VAR like support, as well as other VARs, seem to be moving forward with strategies. I have to check out how B&H is handling things.
For a variety of reasons, while I like the App Store as an option, it’s a hinderance as the only means of purchase for a “pro” application.
[Rich Kaelin] “But many many clients still want a DVD, everyone has a Player and can watch it.”
But I think the demand of authored disks is on the decline. Of course people will cite exceptions. We’re at the point were one can play back at 720p HD from tablets and smartphones hooked to an HDTV that will be higher quality than standard def 16×9 from a DVD.
-
[Herb Sevush] “Alban –
Scott listed a series of industry standard features shared by every other professional NLE in existence. Other than 64 bit and background rendering, which are desirable features for any NLE, you counter with a bunch of FCPX specific attributes that many editors would be happy to live without.
no skimming – don’t care
no keyword tagging with smart collections – bins with automation that I don’t want.
no magnetic timeline – thank the lord
no “conform” within the timeline – have no idea what it is.
terrible 3-way color corrector – The combination of 3 way CC and Color beats FCPX hands down.
overcomplicated editing-tool-selections – not overcomplicated for me, but then I’ve been out of school for more than a few months.“
Herb, Scott listed a bunch of features that are indeed missing and needed by SOME editors on SOME projects, including myself on SOME of my projects. But I get around it, because I still have FCP7 and guess what….it still has all the tools it had on June 20th.
I am wondering about your reply to my list, because if you don´t realize how good the skimming feature is then I don´t know what to say. It is saving HOURS of time no matter what you do and how you do it. The 3-way color corrector in FCP is pracitcally unusable professionally now, because it simply doesn´t have a good quality. In FCP7 you need Color, true….and in FCPX we will need another 3rd party tool (or Color again) once the XML works. But the NLE FCPX itself has a much superior colortool. MUCH!
FCP7 is full of workarounds. The editing was by far the worst I experienced on any NLE in its time. In fact FCP7 is FCP6 (what did they bring so valuable since 2007 to call it 7 anyway? Alpha transitions and reflections in Motion?) The software stalled years ago. And it behaves like it. It is clumsy, it crahses when you throw a few thousand waveforms and thumbnails at it. It uses 400% of my 1600% and it uses 4GB when I have 16GB of RAM.
It is made for a workflow from the 90ies and it shows...well, Herb, I am out of school a while and edit for 20 years on all different NLEs from SpeedRazor to Edit* to Liquid, Edius, FCP, Premiere…..I used everything but AVID and Media100. Just because I understand what FCPX does better, doesn´t mean I am 17 and it doesn´t mean I don´t produce broadcast programmes. It only means I make them faster even with the extra loop I need to take to bring the project to FCP7 to output it for the network.
I wish XML, OMF, HD-SDI output and all those features were here already, but they aren´t. But that is no reason to bash the rest of the software. It is a delight to use it if you really school yourself in it.
P.S: FCP7 is overcomplicated and you say you know how to use it. Well I do, but other NLEs (not just FCPX) understand what I tend to do just by reading my mouseposition. No more “R” “RR” “S” “SS” etc to start slode, roll etc, the NLE has to understand that just by seeing I am in the clip or on the end of it. FCP7 doesn´t. That´s what I meant and I am happy to hear your argument why less keyboard-shortcuts are such a professional way of doing things.
-
Companies like Adobe, Avid, Autodesk, and Genarts all figured out a great way. Deliver installer files that come with free trial periods, and have license utilities for moving a license from computer to computer. If you have an issue with the license, you can use it in trial mode until you get it sorted out. I hadn’t really thought about using the implications of the app store. Just one more reason not to bother.
Robert Brown
Editor/VFX/Colorist – FCP, Smoke, Quantel Pablo, After Effects, 3DS MAX, Premiere Prohttps://vimeo.com/user3987510/videos
-
I find it truly amazing how many Apple apologists there are on this forum.
See, that’s ironic because I find it amazing how many Apple complainers have been whining about Apple apologists. The people slamming Apple outnumber “apologists” 2-1 on this forum and yet anyone who maintains an optimistic point of view strains the credulity of the “haters.”
You say that both sides need to stop pretending that they speak for Apple when it comes to speculation on what features will or won’t be added, but you only slam the “cult-like” fanboys. Where’s your derision for the people saying that Apple isn’t planning on adding multicam back in, or any true “professional” features because they are only interested in making gadgets and toys? You know, the vast majority of posters. There is as much truth to any of that as there is to those saying that FCPX will have all the pro features back by the end of the year.
Andy
https://www.timesavertutorials.com
-
“Scott listed a bunch of features that are indeed missing and needed by SOME editors on SOME projects”
No Scott listed some features that are industry standard on every pro NLE available now. Whether you use all, some or none of those features doesn’t change their essential place in “high end” post.
“..well, Herb, I am out of school a while and edit for 20 years on all different NLEs from SpeedRazor to Edit* to Liquid, Edius, FCP, Premiere…..I used everything but AVID and Media100. Just because I understand what FCPX does better, doesn´t mean I am 17 and it doesn´t mean I don´t produce broadcast programmes. It only means I make them faster even with the extra loop I need to take to bring the project to FCP7 to output it for the network.”
Well it’s nice to know we share some of the same pedigree. Of course FCPX would be the only program that required you to use a totally different NLE to output for Broadcast, but I’m sure you see that as a feature, not a bug. Myself I see it as a ridiculous proof as to just how inept X is, at this moment.
“I am wondering about your reply to my list, because if you don´t realize how good the skimming feature is then I don´t know what to say. It is saving HOURS of time no matter what you do and how you do it. “
I’ve been told by experienced editors that is a toy and a waste of time. Different strokes. It’s what I meant by a list of program specific features. An external monitor is required by everyone, skimming is liked by some. There is a difference.
“The 3-way color corrector in FCP is pracitcally unusable professionally now, because it simply doesn´t have a good quality. In FCP7 you need Color, true….and in FCPX we will need another 3rd party tool (or Color again) once the XML works. But the NLE FCPX itself has a much superior colortool. MUCH!”
I’m sure the X color tool is better than FCP7 – but it’s not better than round tripping from Color is it? And because X exists in a vacuum it’s limited in ways that FCP7 isn’t. And how is that possible, how do you spend years developing this sparkly new program, only to have it more limited than the creaky old software you’ve already EOL’d? It’s so screwed up you have to use the old software as part of your kludgy workflow. So I guess FCPX can be thought of as an advanced FCP7 plug-in.
I’ve never said FCP7 wasn’t in need of a total overhall, nor do I doubt that there are many excellent features in X (I love the idea of auditions) I just maintain that with X Apple has announced that they’ve decided to exit the world of “complex-workflow” video post.
Herb Sevush
Zebra Productions -
[Ben Scott] “compressor isnt 32 bit
front end GUI is 32 bit
render engine 64 bit
get facts correct before whining”
Neither Compressor 4 or Motion 5 list 64 bit operation in the specs on Apple’s web site. Only X is advertized as being a 64 bit app. There is zero reference to “64 bit render engine” in Apple’s tech specs for Compressors rendering system. There is a reference to shared render engine with Motion and Compressor in the specs for X and Motion, but on the Apple Compressor specs there is no mention of this process, with no indication that any process in Compressor is 64 bit.
And since this ‘feature’ is reliant on sharing with X, it must not be native to Motion and Compressor, and probably not available if they are installed in a stand alone configuration.Scott Sheriff
Director
https://www.sstdigitalmedia.com“If you think it’s expensive to hire a professional to do the job, wait until you hire an amateur.” —Red Adair
Where were you on 6/21?
Reply to this Discussion! Login or Sign Up