shanepeters@bellsouth.net wrote:@chrishocking.....The "cinema camera" argument no longer holds water. BM decided to take this camera beyond cinema camera specs when they promised professional audio inputs and recording, and a video mode with a pre-colored look (although still not correctly colored). Those features were designed and advertised to attract people who had planned to use the camera as a dslr replacement with better sound capability, and better image capability. A camera they could use as effectively for small jobs that required embedded audio and pre-colored footage. That was false advertising. If it never is resolved, it should be grounds for a class-action suit.
Don't get me wrong, I would absolutely LOVE BMD to update the firmware to fix the audio issues.
But... the cinema cameras are still cinema cameras. The market doesn't dictate that - the manufacture does. Canon market's their DSLR's as high end stills cameras... oh, and by the way, it also offers "Live View movies recorded in Full HD".
BMD have made it clear when talking about the camera, that it's not a DSLR replacement. It's designed for high end, serious work. And... people are actually using this camera for this kind of work.
It's such a strange beast though, because being so cheap goes against everything we've previously known as professional. As always you get what you pay for - so this camera will always have major compromises - but at the same time they're aiming at the pro market. Very bizarre.
shanepeters@bellsouth.net wrote:Strongly considered a c300, but was convinced by BM that their camera would deliver far better images WITH embedded audio than the canon product.
This is why BMD have been so disruptive and made the whole market so confused.
BMD has spent a huge amount of time and energy on the sensor. They have managed to create a sensor and colour science of similar look to the Alexa for really, really cheap. This is ground breaking. But, then they through it in a new and innovative, yet not very practical, high-tech case.
The BMCC & Pocket have fantastic image quality (albeit still with a few quirks!) - but you get what you pay for.
The C300 costs significantly more than a BMCC - and as a result, the build quality is better, it has much more functionality, and it just works.
If I was doing doco or run-and-gun work, I'd pick a C100/300/500 over the BMCC any day of the week.
thomas bruegger wrote:Is there such bad audio hardware on the market? this is standard stuff being around for years now its not rocket science. 5DMII from 2009 does record better audio than the BMCC did Canon use better parts for their Foto first Camera than BM for their Movie-Camera? Sounds strange. Anyway its just dissapointing.
I'm not an engineer, so I actually have no idea. But... the headphone output on all of the camera's sound horrible - and I would imagine this would have to be a hardware limitation. Whether the audio circuit's are better or worse than than of a 5D I don't know... but my guess is that even if the audio circuits are the same, the way they are implemented might be at fault. Maybe by trying to jam so much tech into a tiny box that needs to be able to function correctly over a wide range of temperatures, means they cut some corners, and there's some earth leakage problems, or some of the wiring is not as well shielded as it should be. I have no idea - but one day I'll open up our camera, take some photos and send it along to some professionals to give their thoughts!
g14matthew wrote:And I disagree that the audio on the camera is horrible. By itself, maybe, but as I noted in my post, when paired with the JuicedLink Riggy Assist RA333, I've been very pleased with the results that we've achieved on a number of projects.
As I said, you can make it work if you do some work in post. What gets recorded is no where nearly as bad as what you have to monitor from the headphone jack. And THIS is my major complaint. Because the headphone jack is so horrible - you have no idea what you're actually recording, until you listen to the final result. You can't actually monitor what the camera is recording, as you'll get a massive headache - so you end up just listening to what you're mixer's sending, and you just have to trust that nothing goes wrong between the mixer and the camera.
This is a big problem if you're using the 1.2 firmware - because if the "mic level protection" kicks in, you can loose audio, without even knowing it, and the only way to fix it is a camera restart. Fun! Fun!
g14matthew wrote:What was communicated to me by Blackmagic technical support when I called them and discussed this issue (as I had scanned the forums and thought the same thing that you did) was that the line level protection still existed. Whether or not it has been adjusted for higher input before overload, or I simply misunderstood the person I was talking to, I can't say with certainty.
What firmware are you running?
That's really interesting if they've brought back the functionality in newer firmware, as it was DEFINITELY gone in one of the previous releases. Let me know what firmware you're running and I'll do some tests.
g14matthew wrote:Also, for the event, I was receiving a signal that only came in via the Mic setting from the camera. I assume that this is because the Riggy is sending a Mic Out Level, as is labeled on the front of the device, but again, I'm not as technically savvy as some folks. In any case, we weren't able to get any kind of sound into the camera via Line level setting, so we went with what has worked for us in our repeated testing of the camera.
Yes, the RA333 is designed for DSLRs, and only offers an amplified mic level output. So regardless of what you're feeding the RA333 - the settings on the camera must be set to Mic Level.
This is the problem with the juicedLink products when using with BMCC. If you're using a firmware version with the Overload protection, the whole system is unreliable, as if you feed it a "hot" signal, the camera will switch from Mic to Line, or worse, just switch off the whole audio functionality without notice, requiring a restart to fix. I was under the impression that this was fixed in 1.3 and above... but if you're running 1.3 or above and it's happening to you, then maybe not!
Personally, I would always run a Line Level signal to the camera - so I've never run into this overload protection issue in the past. But if you're using the RA333, you have no choice.
g14matthew wrote:No, what I said was correct, I am almost one hundred percent positive as I was actually on the phone with the Blackmagic support person and had the conversation with him. I did not talk with Kristian, so perhaps there's a disconnect in communication at Blackmagic - which I'm not insinuating there is - but that may be why you're reading one thing on the forum and I'm hearing a different thing in person. I'm assuming it will get sorted one way or the other and I do hope that, as I mentioned earlier, they at least add an audio peaking indicator in the camera via a firmware update.
Back in June Kristian Lam commented:
We are always trying to improve things with each software release. In 1.3, there was a change to fix DC offsets in the audio which I'm sure you've noticed but as a result, it affected the frequency response of the audio. But rest assured we're looking into it.
They've had 6 months to fix the frequency response issue. They've fixed it in the Pocket. It didn't exist in 1.2, so it's obviously a mistake in the code. They fixed the DNxHD crashing bug VERY quickly - so we know they can release firmware updates quickly. Why haven't they fixed this audio issue then... no one knows...