Jim Giberti
Forum Replies Created
-
[Franz Bieberkopf] “There was an article I read recently about a theory that language itself is based on metaphor at a fundamental level;”
Absolutely.
That reminds me very much of something I remember from Carl Sagan a while ago, discussing the origins of language.
Specifically the expression “shhhhh” as a pre-language warning representing the sound and potential threat of a snake. -
[Franz Bieberkopf] ”
Who said there’s anything inherently wrong with analogies? Chris Harlan’s title is “limits, uses, and failings”. You seem to think that the intention is “problems with analogies”, when it’s clearly larger than that.”No, I just chose to counter with the potential limits and failing of analogies with the potential and success of analogies.
I don’t think either is larger or smaller in context.
I was just having a little fun by ending my post with an analogy.
-
[Chris Harlan] “He’s just so Baroque.
Plus, I love that he actually gets across what that “feeling” is when you push to magnets together.”
He’s amazing.
From a writing, storytelling standpoint I have great respect for well crafted analogies, and from a technical standpoint too.
But I agree, nothing’s more frustrating than weak and arbitrary analogies (and any analogy that includes the word nazi.)
In a real sense, American culture is fueled by bad analogies.
And that sucks.
-
I’m familiar with this piece and don’t see it as a “problem with analogies” exposition.
Analogies are a fundamental and essential part of human understanding.
In fact Mr Feynman actually uses the term “analogous” when referring to the magnetic and electrical forces. In this case it was obvious that analogy would have no value to the interviewer. If he were talking to a physics student it would have helped push understanding forward.
Analogies are invaluable short hand for people with a shared base of knowledge.
Analogies are invaluable in communicating abstract concepts to people with no shared base of knowledge – parables for instance.
Analogies fuel music, poetry and literature in general.
The value of any analogy is based on the quality of the comparison being struck and the ability to grasp the cultural/experiential background of the people you’re communicating with.
Saying that there’s something inherently wrong with analogies is like saying there’s something inherently wrong with Italian food or Impressionism.
-
They’ve definitely got my attention.
Adobe’s had about 8 months to listen to the FCP professional community and capitalize on a once in a program opportunity to move an entire market segment over night.
If they hit it out of the park, and I hope they do, I’ll be an immediate adopter. We already have a few Creative suites and I’d immediately upgrade to the broader suites.
Real audio mixing, real tracks, 64 bit, .h264 playable…show me more.
My question to Shane is, how do you know it’s lacking in some of the FCP7 features when it hasn’t been released yet?.
-
[Jeremy Garchow] “FCPX saves everytime a “change is detected” or every 15 minutes, which ever comes first. So, having a 56 GB file and having FCPX “detect a change” is going to cause major performance slow downs. I mean imagine trying to save a legacy project after every click, edit, move, whatever, and that should point to what X is trying to do. “
That’s another great point Jeremy.
It’s actually the third crazy way that they don’t manage memory, and they all create different levels of disfunction. -
[Jeremy Garchow] “Just curious, Jim. Did you ever get this solved?:
https://forums.creativecow.net/readpost/344/8643
Bad ram can cause things to go down in a hurry. Did you try reloading the system at any point?
10.0.3 has certainly brought some bad performance and there’s no excuse to release something that hasn’t been vetted, but if files in the Finder are corrupt, it could point to other more systemic issues.”
Hey Jeremy,
RAM is fine, all systems are fine and optimized and were at the times of the corruptions.
I had a chance to play a little catch up today and started with a long talk with AppleThere’s no question that FCPX can be “sensitive” with content.
In essence this is what I’m sure of:The simple graphic (in this instance was correctly formatted and a simple, flattened jpg out of PS) didn’t corrupt the FCPX project, FCPX corrupted the file, which then apparently corrupted the project as well.
2nd time in two weeks both times using simple graphic files.
Here’s what I think overall after spending several hours exploring all potential options/solution – FCPX is very high maintenance if you’re doing work beyond simple edits and small projects. At least higher than other similar programs.
It’s very sensitive to project size and I wouldn’t be surprised if it’s inane practice of bloating itself until it chokes is the fundamental cause of many of the problems people are having.
Here’s an example of what I found. There was one project, a scratch pad that was used to try out some ideas and filters etc. I didn’t even think of it till I decided to go through the program piece by piece.
it was 2 minutes long and had a few transitions. It was 54 GBs. When I deleted the unused render files it reduced the project to 2 GB.
My guess is there’s a point at which any project becomes more susceptible to hanging, crashing and possibly corruption – based on it’s relative project bloat.
Until Apple provides for the simple, logical, automatic deletion of any previous render files, they should make continuous file deletion a primary instruction for users in order to protect projects and media.
Why a project would accumulate every overwritten action in a project defies all logic, but if they fix this and provide a “Clear RAM” command, FCPX would have a functional memory approach.
Apple created a project that both gobbles RAM by the minute with no way to release it and simultaneously grows every project every moment it renders.
I’m not sure how they assess their priorities with updates, but I’m thinking these are first tier considerations.
-
[Steve Connor] ”
As I’ve said in a couple of previous posts, FCPX is in effect beta software and I have a regular back up strategy in place for all the projects I work on with it.”Hey Steve,
Me too…back up strategy that is. The same we’ve always had that’s always been effective.
But this is something else entirely…like a virus.
For instance it took a long time to isolate corrupted media trying to rescue this last project.
I’m talking about files so bad that FInder wouldn’t allow me to mouse over them in the browser.
Something I’ve never even heard of let alone experienced in decades of Macs.One problem is if you don’t know there’s a corruption and you put tons of work into something the best you can do is lose all that work.
But associated things also get corrupted with the corrupt media.
I’m glad you’re not seeing this on a lot of boards but three people in this thread have had similar experiences, which is more than enough evidence that Apple isn’t doing there job.
I can deal with new software that requires a little massaging, but I can’t fathom software that destroys it’s own efforts.
This is all since 1.0.3.
As I said, at this point the software is probably corrupt so I guess I have to lose more of my life talking to Apple and downloading another 1-1/2 TB and reinstalling.I’ve got 4 or 5 other projects all in FCPX now.
Yikes, thanks Apple.
-
[David Lawrence] “I think calling this beta software is overly generous. The data corruption described by Jim and others is simply unforgivable in professional commercial software. Imagine if Oracle launched a new version that randomly nuked the client’s DB. No question it would be recalled immediately. These are alpha level bugs at best. It really seems like 10.0.3 is unfit for release.
“Exactly David.
We’ve had two important projects virtually ruined by 1.0.3, something I never imagined happening by simply running a software program in the 21st century.The fact that it’s not only an Apple program, but the supposed replacement for the actual Final Cut Pro is just mind numbing at this point. That these things happen during the simplest of tasks shows how desperately unrefined this software is.
I don’t know what they did trying to rush out the beta monitoring and multicam but they broke FCPX.
WTFX
-
[Don Walker] “(I am also waiting with baited breath to see what Premiere 6 looks like!)
“At this point they have my undivided attention.
And from a production standpoint, it couldn’t possibly interface with Motion worse than fcpx, so nothing lost there.