Mitch Ives
Forum Replies Created
-
[walter biscardi] “Ed, it’s obvious you don’t want any further help from us. We’ve fully explained that FCP, and in fact all NLE’s, do not alter the original media files for no apparent reason. The operator (either you or someone else along the way) has done something to cause the files to change OR you’re looking at the wrong files. “
Ed has a number of issues. If he was as experienced as he claims, it would have already donned on him that the simple solution is to take one of the other reels that he has confirmed are not letter-boxed, copy it and walk it through FCP. When the problem doesn’t occur, then he will know that the one reel he had trouble with was in fact different in some way. If the problem does occur, then he can document in detail exactly what he did… post some footage for Apple and the rest of us to test. Of course that would actually accomplish something…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
If you go to 6.0.3 and QT 7.5, I think you will find that it works again. It appears to have been QT 7.4.5 that broke it. We first saw that when 6.0.3/7.4.5 were installed. It affected more than LiveType… all the chroma keyers stopped working as well…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[walter biscardi] “Yay! What did they break this time? Anyone want to go first?”
Doesn’t appear to have anything meaningful, unless you have FCP server. Of course, they may not be telling us everything?
I’m going to pass. I just recovered from the severe “bitch-slapping” they gave us in the 6.0.3/7.4.5 updates. I really don’t need anymore drama right now, since each update seems to break plugins…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[walter biscardi] “4GB of RAM is a major problem as I have noted in my blog and in other posts here on the Cow. Our Mac Pro Quad had all sorts of issues with 4GB RAM that went away when we dropped down to 2GB. Now it’s running 8GB RAM with zero issues. The new Octo Core is running 10GB with no issues. “
I’m glad Walter addressed this. 8Gb should be the minimum.
FWIW, our new 8-core crashed regularly with 10GB (two fours, two ones) of ram. At 8GB (two fours) it doesn’t crash at all. If you read Apple’s tech note, they pretty much tell you that with FCP you need even matching modules on both risers, which means from 8GB you will probably want to go to 16GB next.
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[Jeremy Garchow] “[Warren Eig] “They know of no known issues with 10.5.3 or QT 7.5. ”
If running a KOna card and a Mac Pro, it’s actually recommended to update to 10.5.3 (not sure of QT 7.5, I’d stay away from that). “
I wouldn’t avoid it. That combo works. 10.5.3 and QT 7.4.5 is a nightmare. It was QT 7.5 that fixed it…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
So you’re saying that working in an unfulfilling position that you may hate is somehow okay just because you’re making a lot of money? Jeez, you sound like me many years ago, before I became enlightened and changed things in my life…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
I think you are reading too much into this. Yes, the OS will continue, and as always, any new development in the OS will not have anything to do with FCS. FCS always lags behind and lately, has been held hostage by the barrage of QT updates, most of which introduced problems for FCS… all to benefit of the iToys line. FCP is the single most out-of-date program Apple has… in terms of code, speed and interface. It’s nostalgic at this point.
As for speed, the only thing that will speed up FCS is a complete re-write to be all native 64 bit. We’ve been wondering in what decade that will arrive… if ever. Apple continues to beat up the developers and tell them that they need to be writing in the native 64 bit… the developers keep pointing to FCS and saying “why… you don’t”.
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[john ladle] “everything will always do what it did if you don’t update it. its just that chase for one more new feature that keeps it exciting… “
I disagree. Things have become far more inter-dependent, forcing you to upgrade to fix one problem, only to create another. The days of saying “I just won’t be an early adopter” are over. Many of us had to go to 10.5.3 to fix some glaring problems whether we wanted to or not.
[john ladle] the iphone has nothing to do with it, it only helps apple to be a stronger company.
i really cant remember too many times in FCP’s history–or avid’s for that matter that dont have some degree of excitement. FCP had a very small crew and there was no pro applications division. now they have quite a suite of products and programmers who were never there before. (fcp 1.2.5 with QT 4.1.2 was finally stable…but it bloated the installer larger than 20 MB!) all of the uproar with 10.5 is nothing compared 10.3.x, 7.5.x, as well as vista and all previous service packs for windows… “
The iPhone has been acknowledged as the reason for pulling so many OS X programmers away from OS X. The latest round of 10.5.3, FCP 6.0.3 and QT 7.4.5 have caused more problems than we’ve every experienced in the past.
I’m not sure where you’re getting your info, but the morale in the Pro Apps division seems to be at an all time low. Many of us have been told that there are less programmers there now, than before, so your comments are interesting. The complete “head in the sand” over Blue-Ray support only punctuates this…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
This isn’t easy to answer. According to Apple, if you’re using a Kona, you should be on OS X 10.5.3 and as a result, FCP 6.0.3. However, if you have an Io HD, it looks like you should not be on 10.5.3, so you can stay on 10.5.2 and FCP 6.0.2.
Following so far? Of course, 10.5.3 has fixes for the 8800 nVidia card, which fixes the issues under 10.5.2 that made it on occasion slower than the ATI 2600. So if you have an 8800, you probably want 10.5.3.
But wait, there’s more. In addition, many of us are having issues with keying and LiveType under 6.0.3, but mostly on the new Intel Mac Pro’s. So, maybe staying at FCP 6.0.2, QT 7.4.1 and OS X 10.5.2 is the way to go… unless of course, you have a new 8-core, a Kona or an 8800 (sarcasm intentional).
So, it’s a weird time out there right now for FCP users. Hopefully Apple will finish the 3G iPhone and get back to fixing OS X and FCP…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
As I said earlier, all was good up through FCP 6.0.2 & QT 7.4.1. All the keyers worked then…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com