Tom Brooks
Forum Replies Created
-
I’m not finding FCX to be a time-saver in these situations. It seems to be slow on any kind of export–like it always re-renders in 32 bit float. But for this workflow, I’d probably use the suggested Send to Compressor and then apply two presets there. Or just Export Media under the Share menu and take the resulting self-contained QT into Compressor or another compression program.
-
Solved! Well done, sir.
Final Cut Pro 7, FCX, Mac OS-X 10.6.8, Quicktime 7.6.6, Adobe Prod Prem CS5.5, Kona-LHe, 6TB RAID-5
-
Not entirely true. You don’t get the nice window full of thumbnails that are scrubbable. But, you can use the tools built into OSX to preview clips. Basically, you are looking at a Finder view of your files. So, you can use Finder viewing tools, such as Quicklook. For example, you can highlight a certain .mov file and hit the spacebar to do a Quicklook at that file. Because it’s a movie, the Quicklook plays the movie for you. When you hit spacebar again, the Quicklook goes away. Or, you can view the files as thumbnails or even use the Coverflow view. You’re using the power of OSX to aid in the previewing of material for import to FCX.
-
FCX doesn’t support the file structure of Canon 7D as a camera archive. You have to import the .mov files directly, not from camera archive.
-
I had to do workaround on a similar issue. Multiple cameras with audio. One six-channel WAV audio file for the master audio iso’s. Trouble is, you can’t break apart the clip items from a multi cam audio track. My choice was to create a project from the multi cam clip and then connect the six channel audio to it. I manually synced the audio track. Now, I can break that track into its six parts and manipulate them individually.
-
Limited experience so far, but I have had no problem simply importing the mov files without optimizing. Of course the clips have no time code, so they all start at 0.
-
I am trying it out right now on a 720p DVCProHD project. Mac Pro 12 core, 96GB RAM, ATI Radeon HD 5770, AJA IoExpress. Number one, the responsiveness is very bad. JKL double-speed and reverse are horrible. Audio is quite often not there at all–literally, it’s hit or miss for the audio to play with the video. Part of that is probably drive access and throughput (this project is on a substandard OWC RAID drive), but I found myself wishing to be back in FCX, or better yet, FC7.
As far as real-time without transcoding…not seeing it perform as advertised on this system. Files from Canon 5D and even AVCCAM files are not playing very well in the source monitor–slow, skippy, and hesitant. If this is the experience I’m to expect, this product better improve a lot in CS6. Maybe it all works like a charm in a PC with nVidia Cuda, but not on this Mac Pro. Final Cut X is far, far speedier and much more responsive.
-
https://www.adobe.com/devnet/flash/apps/flv_bitrate_calculator.html
Final Cut Pro 7, FCX, Mac OS-X 10.6.8, Quicktime 7.6.6, Adobe Prod Prem CS5.5, Kona-LHe, 6TB RAID-5
-
Jon, I often use a tool put out by Adobe that helps with the proper sizes and data rates. It’s here: https://www.adobe.com/devnet/flash/apps/flv_bitrate_calculator.html
-
Both RAM and video card are probably important. I just got a 12-core machine. Could not wait any longer for new machines. It has the 5770 card and 64GB RAM. So far the machine loafs with fairly minimal use of RAM and processors, as far as I’ve seen. It will take some time to figure out what makes it work harder and just what is OpenCL and what aspects of FCX and Motion 5 it affects. I might need to upgrade the card in the future.