Daniel Frome
1
COW Coin
Forum Replies Created
-
Haha. But at least it does XML now :p
-
I am envious of your system specs.
-
That’s because you have your project setup up as RGB instead of YCbCr in the format settings. Change that you’ll get the rest of the codecs back.
-
WIth photos, I think Adobe always had a much more popular and better offering (lightroom). If they dumbed down Aperture I don’t think it will cause nearly the stink that FCPX did.
-
Nah, they don’t snap like they do on FCP, except if they are really close together sometimes they nudge into place. It’s something that really annoyed me when first using MC, but once you create a setup that you like (and take the time to place every window pixel perfect) it ceases to become an issue.
-
Hi Jim, thanks for bringing attention to this. I have plenty of memories of exporting h264 quicktime files out to the network for rough cut approval, only to have them blast the “dull colors” (we were working in animation, so color shifts were 100x more noticeable than on live action).
If I might ask a further question: If a computer without FCPX watches your h264 outputs, is the color still properly calibrated for them? I ask this because I found that many quicktime movies actually did contain the proper color information — it was quicktime that seemingly didn’t interpret it properly.
For example, we could watch a 1080p quicktime movie in VLC player and get a more accurate view than if we viewed it in Quicktime 7. This indicated to me that the problem wasn’t necessary the exported file, but the “player.”
My question is ‘how did they fix it’ I suppose: since it seems like the weak link is equally the quicktime playback engine… which would still inherit these issues on the client machine? Hopefully I’m asking this clearly enough…
-
Good post Andreas. Your FCP tools have saved my ass on more than a few occasions. It’s interesting to hear about these shortcomings as it proves that Apple didn’t really think this new database setup through. Looking forward to your future work.
-
[Pat DeFilippo] “if there are major advantages in operating these three pieces of software with the 2010 “Westmere” Mac Pro over the 2008 “Nehelam” Mac Pro? “
In my opinion, there are no ‘major’ advantages, no. Some performance, but nothing substantial.[Pat DeFilippo] “Would 8gb of RAM be adequate as well? “
You will probably want 12GB or 16GB.[Pat DeFilippo] “What AJA card is best for a BetaSP deck “
Talk to AJA directly about this. -
I switched from FCS3 to Avid MC5.5 (and now 6) about 6 months ago. The first month was a terrible swear-fest. It got better gradually. Our next TV show was one of those reality TV shows where footage was being shot up the wazoo … so, despite the annoying quirks with Avid I learned to appreciate the media management and have been generally happy.
I still dislike how Avid handles graphics, and especially its layering system (filler… filler is black? lets stop pretending we’re cutting film already…). For anything graphics-heavy I would choose Premiere Pro. For narrative film I would definitely use Avid.
-
[Bill Davis] “I must say that if you look over my writing here overall, I’m more often part of the minority than the majority. So in that sense, I believe my views help present a bit of “check and balance” to some running trends and that may contribute to a broader picture for the lurkers”
Huh? It’s the opposite. Your view is very extreme towards FCPX. The majority – aka, the greater number of people who edit video in a professional setting, give YOUR agressive forum proselytizing a more balanced picture. “Running trends” ? Oh c’mon, stop trying to win some kind of imaginary information war here. The majority of us are going to use whatever gets the job done in order to make a living. If we don’t use it… well, there’s probably a very good reason why – not because we’re involved in some kind of secretive pact to make Apple lose the NLE market. We really don’t care what logo flashes for 5 seconds before the program loads up.