I can't imagine there not being some sort of catch at this price/spec ratio, but the design alone is really, really impressive. I love how everything is logically located and there's not a lot of fluff that need not clutter things up. Hell, I'd love to buy this camera if it was 1080p. It's just a gorgeous design and I hope it works out well. Would seriously consider getting one down the line if it's a solid performer.
Like I said earlier, I will use this for my personal projects that are very controlled. The ergonomics of this camera do not appear to favor a run and gun shooting style, or that require quick changes on the fly. It appears the mark3 will still be my preferred choice for faster stuff.
It's so simplified.
I'm not sold yet, but this camera is very intriguing.
I guess that's a downside to working in Hollywood is that we are stuck in some surreal world where up is down, left is right and the 5DMIII isn't in the same class of gear as, say, a C500.The film, tv, and event video industries consider it professional, but no XLR. Sure... I get it. ::chuckle::
There are a number of catches, smaller censor size compared to the DSLRs it gets compared to, 30p cap on the frame rate, 1/4" audio jacks instead of XLR, not TC I/O or sync lock, internal battery, lens mount that limits lens selections, limited focus assets, etc., but every camera under $10k has a number of trade-offs. I know BM is still finalizing some details on the software/firmware side so things could change a little before launch. Until this camera gets into the wild, or production models get to reviewers early, we won't really know how well the camera actually performs. Honestly, as long as this camera keeps the rolling shutter artifacts under control I think BM has a winner.I can't imagine there not being some sort of catch at this price/spec ratio, but the design alone is really, really impressive.
I guess that's a downside to working in Hollywood is that we are stuck in some surreal world where up is down, left is right and the 5DMIII isn't in the same class of gear as, say, a C500.
But like I keep saying, there's no reason to get hung up on your gear. Just go out there and make great things. Gear is just gear, it's not a reflection of you. Regardless of what others may think one isn't more pro for using tool X or less pro for using tool Y. Pro is attitude, results & making a living, IMO.
Lethal
Now that that's over we can get back to our regularly scheduled programming.Now that I can agree on.![]()
The 7D gets a little murkier, but only because it doesn't have a full frame sensor. that's really the only drawback. However, people who have used the camera will generally tell you that this is only a hinderance to non-professionals, since professionals can easily get professional results from it.
Oh dear. Makes the great EF 70-200mm f/2.8 L IS II USM more or less useless for everyday stuff EF lens choice is going to be a tough one on this camera !
I agree. I'd love to see a version with more of a DSLR body, one with a grip, that's ready for the run-and-gun of event video and documentary. This is great for studio work or filmmaking, but it doesn't look like it's built that tough. I also don't see the possibility for add-on attachments like the Red has.
RED was supposed to be the company that had only one camera that was forever upgradeable but then the RED One didn't quite live up to that so then introduced a whole line of potential cameras (fixed lens, not fixed lens, s35, FF, etc.,) that thankfully boiled down to Epic and Scarlet. Of course now RED has two camera tiers so, whether they like it or not, they have to decide what goes to both tiers and what gets saved for the top tier.
RED definitely swung for the fences right out of the gate and I don't fault them for that. Jannard did admit that they made some mistakes w/the Red One and that's why Epic and Scarlet were born. I think they've done a great job of trying to stick by their 'obsolescence is obsolete' mantra though the seemingly endless versions of beta software/firmware and constant announcements can be wearing (which is why I gave up on following Red development a couple of years ago even though I'd been intrigued by them since they were just a rumor).It's the problem that people always want more. I think one thing that RED has stuck by is the modularity of their products. The ability to upgrade the RED One to the MX sensor and the ability later this year to upgrade both the Scarlet and Epic to the Dragon sensor and further down the line a 28k sensor is in the works!
The scarlet is also AFAIK made from parts that don't quite make the spec for the EPIC so they are essentially just recycling by creating the scarlet.
My new Cinematographer […] is very excited about this Blackmagic Cinema Camera and will be picking one up as soon as it's available.
[…]
But in my opinion, any way you look at it, it is a very exciting time for the independent filmmaker!
I know this NAB was supposed to be Canon's big splash with 1DC and CS500 but I feel like they totally got lost in all the BMCC talk.
"I'm sure the Blackmagic camera shoots beautiful stuff, and I'm sure we'll see a job from it soon. They always make it enticing for directors and prodcos to demo them. But I guess if you sense any annoyance from me it's that they shoot, ignore our specs, and then drop these drives off to us and we have to figure out workflows.
With 5D, Alexa, and Red it's all pretty straight forward at this point, albeit time consuming. With Phantom, and some of the newer cameras, it totally sucks and adds time to our ingest. I'm sure the Blackmagic will be no different, and at the end of the day, it won't matter what we want at all!
Damn Genshi you went from shooting on iPhones to buying CP.2 primes? Holy crap!
You must have had one successful film.
Wow as a student who just bought a DSLR, I can say that if all goes well with the launch and its delivers, I will sell all my DSLR stuff. 12 bit 1080p in prores ftw.
Well, I guess we'll see if that happens. It's got lot of bang for the buck, despite its shortcomings.
I suppose the biggest drawback for me is the 2.5x crop factor on the sensor. The widest EF prime Canon makes is a 14mm f/2.8 (L-Series), and that lens is north of $2k. After crop adjustment, it becomes a 35mm. They do also have a normal (and cheaper) 10-22mm zoom (f/3.5 at 10mm) to squeeze out 25mm but that's about the widest you're going get out of the BMCC with the stock lens mount.
A lot of people are already complaining about the internal battery, but I imagine someone (like Anton Bauer) is going to think up an external battery that feeds into the DC power jack. No XLR and timecode sync are things I think I can live with (we already deal with it on DSLRs), as long as the camera can run a reference mic (looks possible). PluralEyes does a pretty amazing job of syncing to external audio quickly.
Another really cool thing about this camera is that it records to industry-standard SSD drives. That's huge! Large storage capacity (less media swapping during production) and you can plug it right into a SATA dock (like OWC's $65 quad-interface model) for fast ingest.
With that sensor size I'm wondering why they didn't go M4/3, which is pretty close to Open Source (at least the original 4/3 was planned as such)
I cant see why not but will it preview full raster is another question.Will the new Retina Macbook Pro be able to run Davinci Resolve 9?
Run, I would assume so. Usable? That's a totally different question.Will the new Retina Macbook Pro be able to run Davinci Resolve 9?
Im out of the loop with this new Mac release.Run, I would assume so. Usable? That's a totally different question.
It's not necessarily any issue w/the new MBP itself, but the weak GFX cards in laptops in general. Blackmagic's documentation, which is from this spring, lists MBPs as suitable for SD footage and SD/HD grade previews. Their 'bare minium' Mac Pro config has two CUDA GPUs (one for the GUI and one to render). Their recommended setup suggests using an PCI expansion chasis so you can use up to four cards (one in the Mac Pro for the GUI and three in the chasis for rendering).Im out of the loop with this new Mac release.
What exactly is the issue with this?
Sorry for hijacking the thread![]()