Sean Oneil
Forum Replies Created
-
[Lisa Rolley] “Hmm maybe the producer is just wrong about that…so you are saying on a D5 the only 720 format is 60 fps?”
That’s correct. Now it could have been originally shot on film or 24p video, but the tape will always be 60p. With DVCProHD you can remove the extra frames and bring it back to 24p automatically during capture. But with D5 & HDCam it’s much more complicated to do that.
Sean
-
[Simon Krom] “The current setup has the 2 raid chassis split into the native 2 x 8 drive RAID5 groups per chassis and pumps out around 170-190MB/sec (from 8 drives), so HD 10bit Uncompressed is hit and miss.”
Something is wrong there. It should be getting double that. 16 disks should easily saturate the 4gb bandwidth. Are you sure your switch or one of the controllers isn’t set for 2gb FC?
Sean
-
Sandblaster. Lasers.
Sean
-
[Lisa Rolley] “What if any other things do i need to be aware of in taking on this endeavor.”
You can’t capture 720p 24fps from a D5. There’s no such format. 720p is always 60fps. Now you could have footage that was originally shot at 24, but in order to capture 24 it is very complicated. Better to convert it after capturing.
Sean
-
Apple offers a free ProRes decoder to download. I doubt it will let you import it to FCP 5, but you can at least open it and convert it.
Also, the real ProRes Quicktime components that come with FCP 6 can be moved between systems as there is no copy protection or anything like that. I’m not condoning anything, just stating the facts.
Sean
-
[Jason Diebler] “I know that in FCP, when you move the position of an image (movie, png, etc.) on the y-axis by odd numbers (1, 3, -5, etc.) you get a poorer result in image quality due to shifted field lines. For best results, you should keep y-axis position changes in round, even numbers (0, 2, -4, etc.). But what about scaling an image? Is there a rule of thumb about scaling an image?
I’ve always assumed that with anything digital, it is best to keep things in round numbers, and in factors of 2, 4, or 8 (I assume this because data is binary). But is it the case that when you scale an image in the FCP motion pane, that it is better to use a factor or 4? Would there be a quality difference in an image that is 87.5% (reduced by 1/8) versus 88% or 90%? Or 112.5% (increased by 1/8) versus 112 (increased by 3/25) or 110% (increased by 1/10)? I’m just wondering what happens to the pixels when they’re being displaced by odd-fractions that don’t mesh with binary factors of 4 & 8.
This is a fairly technical question, but I am curious if anyone knows whether these little math differences matter when it comes to quality… and what’s the best rule of thumb?”
I just spent 20 minutes Googling this. It seems nobody knows what scaling algorithm FCP 6 uses. I have one post here on the Cow saying FCP 3 used bicubic while AE back then used bilinear (meaning FCP was better than AE in 2003 at least). But maybe Apple changed it to bilinear make RT Extreme work in FCP 4. Who knows. FCP 6 has three different quality settings for scaling. Is “best” bicubic? I’d love it if someone knew definitively.
I know Compressor uses Lanczos which is supposed to be the absolute best for video. Better than bicubic.
As for all the math and field questions, I think FCP 6 is smarter about that stuff now. But a progressive workflow always eliminates those concerns.
Sean
-
I think you’re crazy for even thinking about this.
Sean
-
That’s weird because I (like most people) run the card at 4x.
Sean
-
From Dec 2007:
https://www.nextlevelhardware.com/storage/battleship/Back then a 16GB SSD of decent speed was $1000. One year later we can get 20x that capacity for half the price. I like where this is headed.
Sean
-
[Chris Borjis] “uh…I could be wrong, but I don’t believe progressive ntsc
can be anything but 23.98.at least thats what a dvd player expects when doing progressive
output.”DVD spec allows 30p, and a lot of cameras can shoot 30p.
Sean