Claude Lyneis
Forum Replies Created
-
Uncheck create optimized media, then it won’t create the large proves files. If you need them to edit, you can create them and use them for editing, then delete them when you are done.
-
If when you imported it converted your H.264 into Apple Pro Res then it can expand by a factor of 10. In finder go to a library, control click on it and choose show package contents. Then you can see if you have a big optimized file, or large render file etc.
-
I agree. The 52 W is probably an average power and relates to an average current. When they are first turned or or maybe actively seeking date, the surge current could be much higher. That is what will trip your breaker. So there may not be a simple answer.
-
I have a mid 11 27 inch iMac with I5 processor and edit AVCHD from a Canon XA10. I generally just edit straight from the AVCHD which is H.264. A couple of difference my I5 is 3.2 GHz and I have up the RAM to 24 GBs. If you can afford it, I would increase your RAM to at least 16 GB. I now use an XA20 at a record bit rate of 35 MB/s and 1080 p at 60 fps in Canons MP4 format with is 60 p and it works well. The trouble with going to Apple Pro Res it generates much bigger files. One more difference I use a LaCie 2Big 6 GB in Raid 0, which seems to help.
A typical project for me is about 80 minutes of clips, which I cut down to about 5 minutes. -
Claude Lyneis
July 30, 2015 at 9:43 pm in reply to: looking for a video that was posted here – maybe by Bill Davis.The shadow indeed looks like a stabilizer, but not a steadicam or a Movi. As the camera guy runs over the rise of the hill, it is though the camera flies off into the sky like a crane shot. Anyway amazing work.
-
Maybe this relates to teaching track editors to use FCPX.
https://youtu.be/MFzDaBzBlL0Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Comments not connected to BAVC. The suggestion to buy a Mac for field work was for those trying to get into paying gigs on smaller shoots around the Bay Area. A fully loaded MacBook Pro is a major investment for these students.
Anyway, I am enjoying the passion this subject generates on the COW. -
In my Bay Area film class this week, the teacher who works professionally as an AC and or data rangler said get a Mac if you want to work here because it is the de facto standard. This was focused on field work and not necessarily for desk top editing in post.
Good luck to Dell, they had enormous quality problems in the past and their reliability was terrible. -
Claude Lyneis
July 23, 2015 at 12:27 am in reply to: I tested the 2014 VS 2015 Macbook Pro using both FCPX & Ppro and results show FINAL CUT X ROCKS!!!I need Light Room to take over for Aperture. I was all set to get their cloud version as my 1 month trial is ending. Maybe I should just buy LR 5 instead. I don’t really need the Photo Shop that comes bundled with LR CC. Hmmmn.
-
Claude Lyneis
July 22, 2015 at 6:17 pm in reply to: 2014 VS 2015 Macbook Pro Comparison for Final Cut – Nvidia VS AMD graphics results.I found this very interesting, although more for the speed differences between X and Premiere. If this was posted in the FCPX debate forum instead of techniques, it would launch a huge discussion on X vs PP. Anyway, happy to see FCPX has a great engine underneath.