-
Point Me In the Direction of A………..
-
[Craig Seeman]It’s fact that it exists there in resources. It’s fact that it wasn’t implemented.
The only fact is that there is a string reference to it in the binary. No more, no less. It may have been nothing more than placeholder from a coder who thought it was a surefire thing to be implemented, only to never actually have tried at all.
To read any more into that is, in my opinion, extremely wishful thinking.
-
[Gary Huff] “The only fact is that there is a string reference to it in the binary. No more, no less. It may have been nothing more than placeholder from a coder who thought it was a surefire thing to be implemented, only to never actually have tried at all.
To read any more into that is, in my opinion, extremely wishful thinking.”
I seriously doubt that coders at Apple can include code based on wishful thinking and not from instructions higher up. To say the coders have free reign doesn’t jive with anything I’ve heard described about Apple’s campus.
-
compressor isnt 32 bit
front end GUI is 32 bit
render engine 64 bit
get facts correct before whining
-
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.“How anyone call it a professional tool in August of 2011 is beyond me.”
Not anyone but everyone calls FCP7 a professional tool, it’s FCPX that doesn’t currently meet all the criteria. But yes, FCP7 is very dated, which is why the huge disappointment in the lack of a suitable upgrade. Because we got X instead of 8 most of the “whiners” here will be migrating to Avid and Adobe during the next year. At which point X still won’t be capable of many complex workflows. Skimmer and all.
Herb Sevush
Zebra Productions -
[alban egger] “How anyone call it a professional tool in August of 2011 is beyond me.”
The allure is more popular after death, than in life.
Fcp7 has some huge, gaping, glaring holes that are all of sudden forgotten. You really have to hold FCP7s hand so it doesn’t freak out in large projects, media managing, mixed format support, frame rates, nesting, media reconnection, clumsy text tools, archaic audio controls, database management, “rt extreme”, edit to tape, project sharing, field order, alpha channel type and linking to other apps in the “suite”. It was time for a big change.
Still pissed about the loss of Color though. That one hurt.
-
Jeremy –
Most of us are not pining for FCP7. Its the loss of FCP8 that we mourn.
Herb Sevush
Zebra Productions -
I find it truly amazing how many Apple apologists there are on this forum.
I think it is OK for people to knock or praise a product that they have used and know. On the other hand I think it is bad for people to spread rumors either for or against something when they have no actual knowledge of it. When people speak for Apple (as if they worked for them) saying that Apple will or will not be adding features in the future it really does not help anyone since this is pure speculation on their part. Apple needs to be telling the consumers what their plans for the future are, and they should be the only people doing this.
Never in my life have I seen so many people step up to the plate and pretend to be mouthpieces for a company or product. It is very cult-like behavior and I do applaud Apple for creating possibly the most brand loyal consumers in history.
i am going to repost this as a new thread.
-
[Herb Sevush] “Most of us are not pining for FCP7. Its the loss of FCP8 that we mourn.”
I hear you.
I hate to do this as I feel it’s “name dropping”, but its important. I know someone who used to work in Cupertino on the ProApps team. When new features were requested the constant answer was no, because the code was that old. Basically, it was a road to nowhere developmentally speaking.
It is not Apple’s style to patch and rewrite while keeping things looking the same. They start over, and when they do they start small and then build. You can follow their history and watch when it’s happened. Tim Wilson wrote about it somewhere around here.
I am not aplogozing for Apple, or really happy about the way they do things sometimes, nor do I agree with their methods, but I am also not surprised.
I will say, I like their products, and I like what they have allowed me to achieve. Call me a fanboy or whatever, I don’t really care. I have a career in part to do with Apple and their products (even before FCP). Am I wrong for wanting to give them a chance?
We recently got a Windows server in the office. Man, what a huge difference. Talk about learning a new language.
-
[MIke Guidotti] “When people speak for Apple (as if they worked for them) saying that Apple will or will not be adding features in the future it really does not help anyone since this is pure speculation on their part.”
Apple spoke
https://www.apple.com/finalcutpro/faq/
https://alex4d.wordpress.com/2011/07/06/notes-from-apples-london-pro-briefing-on-final-cut-pro-x/ -
Craig, you don’t seem to understand what I’m saying. I said “placeholder” not actual code in and of itself.
Do you know what a string reference in a binary is? They didn’t reverse-engineer the executable, they simply did a dump and saw a string value with that info. That’s all. Doesn’t mean there’s any actual code (or attempt at a code) whatsoever.
Reply to this Discussion! Login or Sign Up