Bret Williams
Forum Replies Created
-
When you say broadcast what do you mean? Are you talking Satellite, Digital Cable, Regular Cable, or Rabbit Ears? Many people don’t realize that the latter is by far the best quality. In fact, right now, I’m watching rabbit ears hooked up to a vcr, run into a PVM-204U! When you’ve got the ears just right, it blows away anything on cable or satellite.
-
Sorta. You should always use field rendering IMHO. I only use motion blur if I have the time or I’m mixing non field rendered stuff (like film footage) with CG stuff.
Using AE can make different speeds look ok, but it’s no replacement for the Adam Wilt method. Adding motion blur may help the interlacing problems, but it’ll make the text blurry.
-
[Dave LaRonde] “I see that you’re trying to use the DV codec for graphics. Don’t. DV is horrible for graphics. If your graphics aren’t animated, you can give your client a still.”
That’s kind of old school information. I use DV for graphics all the time. It’s come quite a long way in the last 6 or 7 years when this was actually a problem. And back then, it was only a problem for FCP’s DV codec, which they fixed. EditDV at the time had an amazing DV codec even back in 1999.
Most likely the problem is a 720×480 quicktime being blown up full screen to 1680×1050 or something huge. If it’s not played back exactly at 100%, then it’s going to have issues.
-
Use photoshop to create a long text layer, and simply animate it in FCP. Make sure you use one of only 2 scrolling speeds that work for video. 120 lines per second if you want the text to be read, 240 if not. This will keep you from getting any flicker whatsoever and ensure perfectly sharp text. So, for example if your first keyframe were at 0,0 then one second later the position of the text would be 0,120 and a second after that 0,240 etc.
You can find the details at https://www.adamwilt.com/Tidbits.html
-
You answered your own question. You may actually lose a little quality by removing it from it’s native bit for bit format and transcoding it to another. However, working in a uncompressed sequence will improve the quality of everything else. Titles, photoshop elements, jpegs, photos, animations, etc. They won’t ever get “better” in quality, but they won’t go down in quality all the way to NTSC DV.
-
Never said it was. Just using that as a reference point.
-
A TB in an hour sounds pretty fast. However 100gig can be done in less than 2 hours over fW400, so 100gig in an hour over sata is kinda slow isn’t it?
-
Hmmm. Well, on P2 clips it seems to work. Allthough a little awkwardly. It puts a white bar across the top with the TC, and a black bar on the right.
I think QT is quite buggy lately actually. For example, in FCP the info will show that clips are 720×480 DV, but in QT those same clips are described as 640×480 across the board.
Here’s a screen shot… https://www.bretwilliams.com/tc.png
-
In QT, press cmd+j or ctrl+j(win) to open the properties. Then click the check box for TC track and it’ll display the timecode.
-
That can be tough if you don’t remember what drives they were on. Does anyone know if there’s a command like in OS9 called “Put Away”? I think it was cmd+y but it doesn’t seem to exist in OSX. You could highlight everything in the trash and press cmd+y and it would place all the files back in their previous locations. It was the kind of function that macs had that windows didn’t. But now where is it?