Forum Replies Created
-
Check out this:
https://www.kenstone.net/fcp_homepage/burn_br_mac_superdrive_stone.html
Not exactly the best solution, but it does get you an AVCHD encoded file on a red laser (non BluRay) DVD that most BluRay players can play.
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.comHear me pontificate: Speaking Schedule .
-
I believe you get the DISPLAY overlay on the HDMI output while recording, which would make the output unusable, unless it’s only for screening / dailies.
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.comHear me pontificate: https://michaelkammes.com/post-production/speaking-schedule/
-
Michael Kammes
January 25, 2011 at 7:07 am in reply to: From Canon 5D to Film out . Apple Pro Res 422 or Pro Res 422HQHQ will give you more latitude when color grading. It will really shine if you have some gradients; banding can sometimes appear less frequently with HQ than 422. Also, if you plan on doing motion effects, the less compression you use, the better.
This does come at a price: It takes up more space on your drive, and the renders are longer.
What about doing it the old fashion way: Cut at a low res, then online? Transcode the 5D to an edit friendly codec like ProRes Proxy or LT. This is easier for the CPU to handle and takes up less space. Then online/conform at an uber high Res – Cineform, ProRes 4:4:4:4, Uncompressed, etc. If you can afford a film out, you should be able to afford an online & conform session 🙂
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.comHear me pontificate: https://michaelkammes.com/post-production/speaking-schedule/
-
Michael Kammes
January 25, 2011 at 6:59 am in reply to: Creating, using multi-track sequences and exporting sequences to create EDL’sKevin…anxiously awaiting as I want to shout it from the roof tops 😉
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com -
Well, for starters, 10.6.6 is not supported.
See System requirements here: https://www.avid.com/US/products/Media-Composer-Software/system-requirements
As Shane pointed out, OMF and MXF are just fine. Basic troubleshooting:
Quit Avid, kill all databases on each drive.
Relaunch Avid, let databases rebuild. This may take some time depending ont he amount of files you have. See if problem persists.
Create a new project and import Bins. See if problem persists.
Create a new user and a new project, and import bins. See if Problem persists.
Try copying media locally, and turning off external storage. See if problem persists.
As you can see, we’re systemically eliminating constants; all of which can become corrupted; in hopes of finding the culprit.
10.6.6 worries me the most, however.
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com -
I thought this too…however…
If you buy v5, your are entitled to older versions – in fact, if you pay to have a dongle for v5, it will run older versions.
Best bet is to contact Avid directly (or a reseller), they do have older versions available, but only for paying customers.
All that being said, it’s been a very long while since 1GB of RAM was enough to run Media Composer, and a MacBook hasn’t ever been qualified for MC – only the MacBook Pros. Not enough horsepower or as you are encountering…memory.
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com -
5D and 7D is h.264. Highly compressed.
400GB? That’s a ton right there. I would think that amount of files PLUS the h.264 decode…..time is about right. How many hours? Data rates vary with the 5D and 7D so it’s hard to ballpark the time length of the files.
In the future, I would recommend:
NOT using MC for transcoding (i.e. importing). Use a 3rd party encoder which works better and faster AND doesn’t tie up Media Composer…that way you can begin editing while the 3rd party app is chugging away in the background transcoding. I recommend Telestream Episode, which can be distributed amongst many computers easily. Yo would wantt o do an encode so Avid can do a Fast Import, which is roughly 80% faster than a straight Import. ( https://michaelkammes.com/encoding/avid-is-self-aware-fast-import/ )
Have you tried using Menu Meters? Free application which allows you to see how your machine is using the processors…I use it to see how efficient the Codec and/or editing/transcoding application is hitting the processors.
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com -
Close your project.
Use an Easy Setup or create a custom sequence that uses Pro Res as the timeline codec. I’d try ProRes HQ, then ProRes 422 HQ, the maybe 4:4:4:4 if you are in FCP 7.x
Start a new Project.
Import the graphic. See if the image looks sharper.
Essentially, attempt to load the graphic into a sequence that uses a more robust codec as the render codec.
If that does not work, try using After Effects to generate the video file FOR FCP.
Try to also stay away form serif fonts and small font sizes. The fine lines and flourish don’t always translate well to video.
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com -
Correct. However, the original poster did say HD.
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com -
DNxHD, which is Avid’s HD codec.
In a perfect world, the DNxHD codec would be in an MXF wrapper, however, few programs can do both a DNxHD encode AND place it into an MXF wrapper. Thus, best practice is to create a DNxHD Quicktime file into a format, that Avid can FAST IMPORT.
Shameless Self Promotion: I penned an article on it, which outlines how to do it and why: https://michaelkammes.com/encoding/avid-is-self-aware-fast-import/
This allows Avid to import a file into an MXF wrapper, which performs better than the Avid 5.0+ AMA via Quicktime workflow.
~Michael
.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com