Bret Williams
Forum Replies Created
-
Not sure what he judged it on, but some others I know recently were editng everything uncompressed 8 bit with AJA IO. They did a test. Digibeta via the IO into the system as uncompressed 8 bit, AND the same video via the IO converting it on the fly to DV format. Playback of the two different images via an sdi monitor after capture led to the discovery that nobody could pick out which was the uncompressed capture, and which was the DV conversion. They have now switched their system to DV based everything from dibeta to betacam to DVCam now gets converted to DV via the AJA IO. By doing so, they just multiplied their available drive space 5 times over.
Given they’re not a boutiqe or doing broadcast work. Just corporate. And they don’t rely heavily on any 3D animation or motion grpahics. Some, but not a lot. I think for them it was a good move. The drive space, and the lessened load on the fibrechannel is worth it. And since they weren’t able to find anyone that could tell the difference…
-
The shadow thing is a bug that seems to come and go with different versions. Right now, it’s busted.
-
[lightning ad] “If your system can handle uncompressed, why compromise and lose something in the codecs?”
But you’re losing something by using digibeta. Why do you recompress your uncompressed to digibeta? Essentially the same as DVCPro50. Just a hair less compression. But technically, if you shot on DVCPro50, acquired natively (firewire), and then output to DVCPro50 (firewire) you’d have a much higher quality image.
-
OMG you’ve lost your mind! 🙂
-
I think it was established centuries ago that dark text on a light background is infinitely easier to look at than the opposite. Which is why 99% of what you see reflects that.
But I don’t get the eyestrain issue. What is it you’re reading anyway? Maybe I read a TC here and there, but most of the time I’m looking at large moving images called video.
Didn’t they add a feature to make the text huge with 5.1? Seems like I saw that somewhere. But I keep it small myself.
-
FCP is idiotic with this sort of stuff. It’s actually scaling up your video so that the 640 width fills the 720 space, instead of changing the distort attribute in the motion tab. FCP should consider the vertical attribute to be the key factor since fields are the most important thing to match up. Stretching fields just creates mush.
So go into the motion tab and make sure scale is 100%. Adjust the distort attribute to fill the width.
-
In your user preferences YOU define how many real time audio tracks your machine can play back. If you have it set to 6, that’s all you’ll get.
Even my old 300mhz G4 could get 12 or so. I usually set machines to around 14.
-
[walter biscardi] “itting idle for extended periods of time will sort of put FCP to “sleep” and when you hit the keyboard or do something it “wakes” up by re-checking all the media sources.”
Never seen nor heard of any FCP waking behaviour in 6 years of using the product. Small project or large.
-
With either they’d probably be best off transferring the file to their hard drive. I wouldn’t be sending out demo reels as quicktimes. It should be a DVD as you mentioned earlier. The quality should look great. Just export it from compressor with a high quality setting, then author it in the program of your choice. Most likely DVD SP of you have it and know how to use it.
I’m not sure why you’re worrying about the quality of your motion graphics when transferred to mpeg2 for a DVD. Did Lord of the Rings or Star Wars III not look good enough for you? If anything, standard motion graphics (logos and animation) should be easier to compress than actual video images anyway.
Why is your format such a bizarre size, 864×480 square? DVDs are 720×480 non-square and are either normal 4:3 or anamorphic. Is 864 some anamorphic thing I’m not aware of? I don’t do anamorphic or letterbox stuff.
-
There is no impact italic. What you’re seeing in FCP is simply skewed. FCP and Boris will skew the type to create a fake italic if an actual italic font doesn’t exist. My guess is that LiveType is a little more discriminating (as should be FCP and Boris IMHO) and doesn’t create fake fonts.