Bj Ahlen
Forum Replies Created
-
…and finally, even when the new version comes out, you don’t want to buy it.
Not until the bleeding edge early adopters have stopped bleeding and their dried corpses have been swept off the streets.
This goes for any sufficiently complex product, not just FCS (which is definitely up there in complexity).
-
“Devanagari” is technically just the name of the alphabet, there are many font implementations of it.
My favorite font supplier for non-Roman languages is Linguist Software (I have no connection with them other than as a satisfied customer for many years).
-
See this old but still good Lighting Infinite White Tutorial Video.
Savage offers vinyl background rolls, more expensive than paper but easier to light and they last longer.
-
Yes, particularly with a filmout, it would make sense to use a Teranex for this.
For normal scenes.
Sometimes there may be fuzzy extreme motion scenes where you could do the conversion by pointing a lens-scratched Barbiecam at the FCP preview window [“Holgavision”], and no one would know…. :O)
-
If the end result is to be viewed on a typical computer LCD, that’s what you need to use.
Note that the gamma difference between OS X and Windows has been a problem in the past. Snow Leopard finally standardized on 2.2 screen gamma (same as Windows), but you can of course set that in earlier versions of OS X.
It’s like mixing pop hits to be listened to in the car; you gotta check the mix in an actual car, not on your $10K studio monitors in a treated room.
-
I don’t understand what Cinema Tools could do here?
In the opposite direction, from 24p to 60i (aka “29.97i” or just “29.97”), yes. Just add the pulldown (please don’t do this and edit afterwards!).
If the footage was actually shot at 29.97i (aka 60i) or 30P or 29.97p, then I don’t see how Cinema Tools could do anything meaningful.
Compressor can do a decent conversion (with the proper settings) from 29.97i to “24p” (23.976p). Not Teranex output, but it can be very decent depending on the content, and there are numerous other tools to do that conversion.
If the B cam was shooting 30P, then you have a bigger problem. That is naaasty. Use Compressor with Frame Controls on and be prepared to wait a long time, and after that prepare to be disappointed most likely.
-
You are rendering to interlaced footage for display on a progressive computer screen, This can lead to many surprises.
Try the “YouTube HQ 16:9” setting in Compressor, that may just fix the problem.
-
48k -8% = 44.1k
Do any of these numbers look familiar?
:O)
-
-
[Ben Holmes] “I feel certain that Apple will be looking to add this functionality to FCP, otherwise a lot of people like me will be looking a lot more closely at the copy of Premiere Pro I have in CS4 (and CS5 soon). “
Do that and weep.
Ever wonder why it’s so hard to find professional PP users anywhere?
Many former PP users gave up after encountering incurable problems that repeatedly stopped their work.
Actually saving time or revolutionizing your workflow can’t happen until they completely rewrite the PP software.
BTW, Apple is pushing OpenCL, an open standard. Doesn’t that make more sense than a proprietary Nvidia-only interface?