Todd Beabout
Forum Replies Created
-
I agree. I’ve been back on Avid for several years after moving from commercial into television and the newer Avid leases remind me of the old days when FCP was truly innovating.
I’m going to hold out on judging until I see more from Apple about all this. There was no mention of improved media management, titling, grouping (or multiple-clip), not to mention true dynamic trimming, etc… Hopefully they don’t completely abandon the actual pro user base out there.
FWIW Avid is already making it a bit easier to move over:
https://www.tuaw.com/2011/04/12/avid-offers-995-crossgrade-to-media-composer-for-final-cut-user/
But again, too early to really judge from what use seen of this supermeet.
My $.02
Todd
-
In your timeline, select all the clips and drag them into a new bin. Now just use Batch Export to kick them out individually.
It will use the in/out points from the clips as they are in the bin.
Todd Beabout
Freelance Director/Editor
Los Angeles -
It seems to playback in QuickTime for me even though I haven’t purchased the MPEG QuickTime thing.
You might check out Perian. It’s a free open-source self described “Swiss Army Knife for QuickTime” and gives you a bunch of QuickTime components (including DivX, Xvid, etc…) and hasn’t caused any problems with Final Cut for me. I would disclaim that you should install anything QuickTime-related at your own risk, but Perian does provide an unistall option if something were to go wrong.
Don’t know if that will give you the MPEG-2 playback, but it’s still pretty cool.
-Todd Beabout
Vazda Studios -
Sounds to me like something is corrupt in the sequence you are trying to render.
The way I deal with that here is to start rendering sections of your sequence at a time until you find the area that is causing the problem. Then narrow down which element in that section that causes the error by deleting a layer, render, if it works put that layer back, delete another layer, render, etc…
If it is a still element, try opening it in Photoshop and re-saving. If it is a QuickTime movie, you could try exporting it out of QuickTime Pro (or Final Cut), then re-importing it.
As for processor usage, I don’t believe there is any way to tweak that. You can set memory usage in “System Settings” but I believe that defaults to 100% anyways.
-Todd Beabout
Vazda Studios -
I would suggest picking the format that you want your final product to be, then render everything into that format and cut away. Personally, I would suggest Apple ProRes at around 720P.
You can run all your source footage through Compressor to get all rendering out of the way at the start, but that might be prohibitive based on how much source footage you are dealing with and how much disc space you have available.
The other option would be to pick selects of the footage and just render the shots you plan to use. You could do this either via Compressor or in your Final Cut timeline.
Hope this helps.
-Todd Beabout
Vazda Studios -
You probably need reference going to the deck through SDI. If you don’t have house sync at your facility, you can have the Kona generate sync for you.
Under the AJA control Panel, click the “Control” tab and set your genlock to “Freerun”.
FYI, if you do have house sync, then you should see 525i29.97 (or whatever your standard format is) next to the “Ref In” button in green.
Hope this helps!
-Todd Beabout
Vazda Studios -
Be sure to go to “Displays” under System Preferences and setup that display to the 640×480 setting. It is probably trying to send a larger signal to that display via the DVI out. You might also try clicking the “Detect Displays” button. Can’t say for sure what that will do, but I think it worked when I setup my HDTV to my Mac Mini at home.
Hope this helps.
-Todd Beabout
Vazda Studios -
Hey Walter,
Where is that BluRay setting located in Compressor?
I could be misunderstanding, but is it the same as the “HD-DVD” settings?
Sorry… I’m a BluRay noob.
-Todd
-
FWIW, lack of FireWire on the MB is a Deal-Breaker for me. The end.
I’m sticking with my last-gen white MB. It handles FCP just fine BTW, even though is isn’t technically compatible. I do not use Motion or Color on it though…
-Todd Beabout
Vazda Studios -
We had a similar problem last week after a complete reinstall of everything on a system. We updated everything to the current version, but then had problems with Batch Capture.
After a call to AJA support, they recommended that we downgrade the Kona drivers to version 4. They said that there are a few known bugs in the version 6 drivers and an update is coming very soon, but until then version 4 seems to be rock-solid. After downgrading to 4 our problems went away.
One note… This system is running Tiger. If you are on Leopard you might try version 5.
-Todd Beabout
Vazda Studios