Adam Schmidt
Forum Replies Created
-
First off, Amund, your right. It is hard to keep up with the forum, and it is a testament to FCPs distribution and the so-so manuals. But I argue that if people were to search a little better, and use other forums to talk about their problems, the FCP forum could get down to size, without the need for more dedicated forums. If you have HD questions put them in your capture cards’ forum or the HD forum. If your mac crashed, put that in the Apple forum. And beyond all other suggestions “Search Before You Speak! Please!” The greatest asset that this forum has to me is that I learn just by browsing the pages, and segmenting would only require more work.
It’s all a little frustrating any way you slice it.
Adam -
Head over to the Convergent Design forum and ask them when they will support such a move. They are working on it as we speak, but right now they are a DV only option, i think.
Adam
-
see post in aja io forum.
-
apple jumped on the distributed computing idea for Logic 7 and it works damn well. And remember, many apps like AE, Shake, maya, and even Compressor can utilize “grid” computing, so the investment in a couple cluster nodes is not a bad idea for time critical work environments. Apple’s Xgrid node software even has subdirectories for FCP and Motion, but they have not been taken advantage of yet. And if the rumor gods have it correct, we will be looking at dual core, dual 3.0Ghz G5 macs (that’s 4 G5 3Ghz chips) with 32GB of Ram, and 4 20GB/s PCI-X slots between NAB and MWNY.
Dream Very Big,
Adam -
Although FCP can work and render float type data via a setting in the video setup dialogue box, it will only work as a functional editor with data well suited to video playback. I was shocked when FCP opened and played avi and mpg files, but I can not edit with them in an efficient manor. in out cards can work in 8, 10, and 12 bit resolutions, but the video needs to be in a codec that FCP will function with. On the io, apple and aja support the Apple UC 10bit codec. This is a true 1024 color per channel codec without alpha in a 4:2:2:0 YUV arrangement. The io also supports the black magic codecs in both 8 and 10 bit depths. The kona 2 cards can work with 12 bit video (4096 colors per channel) via there own 12bit codecs. All of this can be rendered and processed in a float setup with most filters and codecs, but FCP will only run well when the quicktime based codec meshes well with the hardware that supports it.
FCP nor QT supports natively “frame stack” data like what you describe. Instead, use a QT codec that supports 10-12bits and turn on float in the settings. Then any work that you do in FCP will be processed in a float environment, but in the codec transition you will loose the “cary over” or “greater than” information in the original file. Float based rendering will greatly slow down FCP’s operation. FCP 5 will have a full “shake 3” like implementation of float FPU based information.
Adam