Bret Williams
Forum Replies Created
-
Just open the clip in Quicktime, make an in and out and copy and paste that to a new QT movie, then make an in and an out and paste second half to a qT movie.
No exporting, rendering or any of all that. Don’t even have to open FCP.
-
In the bin/browser, double click on your sequnce to open it. Or possibly you’ve closed the whole project, in which case, you’ll need to open the project.
-
FCP doesn’t edit in 15fps. Only standard video frame rate formats sadly.
-
You can do this in FCP by slicing the clip up and making each chunk a different speed. The speed and pitch will change. I don’t hear any artifacts. Once the clips are all sliced up you should be able to do roll edits to tweak the amount of time between each pitch change. Obviously the more the better. Most likely if you do it in 5 or 10% increments and do it on a drum beat it’ll sound smoother.
Execution of the whole process is about 45 seconds. Slice, speed change, next. Works great.
-
But with Firewire the TC will slip a good bit. But it should be close. Usually 3 or 4 frames off.
For anal retentives: If you really need something accurrate for the client, put it on tape with the assemble to tape method mentioned above, then adjust the sequence to match. For example, if on tape it slips and starts at 01.00.00.03 instead of 00, just adjust the timeline start point to 03.
-
At least by June when the Production Studio comes out. And some of Adobe’s new software is intel only. You can bet in a year or so the same will start with other manufacturers. Even Apple. Think of Universal as a bridge. The next versions of software may be universal, but the versions after that will most likely be Intel only.
Go for the MacPro otherwise you’re just staying behind the curve and you’ll be in the same boat again later.
-
11Mb for 5 minutes is extremely small.
In FCP use compressor and output h.264 for the best output. I keep the keyframes on auto, and the frame rate usually in half, 15fps, which looks fine and lowers the file size by half. Set the video to be about 300-500kb/sec data rate.
You can lower the audio to mono and 60-80kb for great quality. Just keep it 16bit and no lower than 22khz.
What matters in the end is whether people have to wait or not. Somewhere around 500kb/sec people are going to have to wait before the qt starts playing. Below that, even DSL should be able to play immediately and keep up.
You tube video looks like utter trash. Why are you worried about their file sizes?
-
[Jeff Carpenter] “You’ll get slighty better results starting with a high resolution and converting down to the final size. This is nearly always true which is why TV shows are often shot on film even though the resolution is much higher than any HDTV. It’s because the higher level you start out at the better off it will look in the end.”
Shooting on film is not because it’s a higher resolution but because the exposure latitude is much better. Over and under exposure are less of a worry as well. Not enough room here ot explain exposure latitude, but it has much more to do with the look of film than frame rate.
For this very reason you’d actually have better looking results by shooting on film and converting to video via scanning unless you’ve got a nice slr. (but probably too much trouble)
Not sure if HD cameras have finally reaced film’s exposure latitude or not. I’ve seen a lot of things showing off thier ability to shoot in candle light, etc. but that’s not the same thing.
-
Add some minor noise in ps or don’t use the DV codec. You can try adding a little blur.
-
[FooKai] “All the animation exported as Quicktime files at the Animation Codec.