Jeffrey Carter
Forum Replies Created
-
Hey Ned – this is Jeff Carter in Tampa – I have a C100 and have been using it with FCPX for several months. Basically you must use the media import command to ingest the footage. It will re-wrap the footage and will be viewable by anything on the Mac. If you choose another folder to copy media to (instead of the library) you can see this in the finder. (You can also view the library by right-clicking and selecting ‘view contents’)
No need to use another utility, X does this for you.
Give me a shout (ateamvideo@mac.com) to let me know how you like the C100 and see how things are going.
-
I have a C100 and love it. It will not be ‘better’ than a C300, no matter what – but Paul Joy (https://www.pauljoy.com) has both cameras and essentially said they are the same when recorded to a Ninja.
I believe the choice comes down to A) do you need an internal broadcast approved codec B) viewfinder issues C) cost.
Doing productions on your own, their is not a big difference between the cameras. I shot for Australia’s “The Feed” once and they had no problem going from their C300 to my C100 (Tampa, FL shots: https://www.youtube.com/watch?v=8juZPOv-8_I )
If you can afford the price difference, I’d probably go with the C300 – you can now upgrade to dual pixel autofocus. Otherwise the C100 is a great camera.
Some 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.
-
I’ve trashed preferences before and it does not help this situation at all.
-
I have the same set up and have always had problems with getting FCPX to get the right focus. Sometimes you have to cycle between cmd-1, cmd-2 and cmd-3 several times before it works. It is something that I constantly have to fight with.
It behaves much better if you have the two viewer layout (ctrl-cmd-3). But I’d like to see Apple fix this bug which has been with 10.0.0.
-
Thanks! That did it. Must be some shared database or registration or something – even the photo browser now shows Aperture and iPhoto!
-
The C100 has way better dynamic range and is sharper than the 5D mkIII. Now that they dropped the price to $4,999 it’s a better deal (although more costly than a 5D). The great thing about this camera over DSLR’s is that it is a video camera. Time code, quick white balance (no taking a still and setting that in the menus), waveform, focusing magnification during shooting, XLR audio in with audio meters, etc.
And the form factor is great. I love shooting this camera over my DSLRs. Of course if you need to do stills as well, then the 5D would be a better choice. I have no regrets buying the C100…
-
Thanks!
Everything I do is for web or broadcast anyways. I’m surprised they have a ‘true 24’ setting – I guess that was their push for cinema – although if going that route a C500 at 2K or 4K seems better suited then 1080…
What is confusing on the C100 is the 24p and 24pf setting. With either 24pf or 30pf I’ve found interlaced jaggies when you blow up the footage – FCPX seems to still consider it interlaced. With 24p it reads it as true progressive and no jaggies when blow up.
The C100 doesn’t have much frame options, but for the sake of quality it only has one real shooting option – 24p.
-
Yes, these were old (10.0.9) projects. I also had some graphics (PSD) and mLogo titles totally disappear and had to be re-created! If you use mLogo watch out. I will have to try a native 10.1 project. However, I started to notice slow renders in 10.0.9 when I upgraded to Mavericks. It seemed to be a Mavericks ‘thing’. Maybe it’s putting more emphasis on GPU instead of CPU? I have a mid 2011 iMac – so not the best graphics card out there…
I also tried to update some 10.0.8 projects and it hung up requiring me to force quit. So I’m wondering if there’s an issue updating older (pre 10.0.9) projects straight to 10.1 or just an issue with that file.
-
No…
-
I thought it used both CPU and GPU. The activity monitor would go full tilt on the cores when rendering before – but not anymore…