Blackmagic Camera App - General discussion and Releases

I know everyone is ecstatic that we can record in true 24.00 and true 30.00 FPS, but I'm trying to match with Sony cameras that record at NTSC frame rates (29.97 specifically). Has anyone found a way to do that in the BMD Camera app yet?

Here you can see where Apple Log sits in the histogram. Because it's measuring the flat image which appears to not reach full black or white none of the exposure tools are usable for the log. I checked and the false color and zebras respond the same way. I assume at some point they'll fix it, hopefully soon.

https://www.dropbox.com/scl/fo/katg07dil6hpkyhj2qhkv/h?rlkey=df1zb4i4tyc57cnu87wa160qc&dl=0

I know everyone is ecstatic that we can record in true 24.00 and true 30.00 FPS, but I'm trying to match with Sony cameras that record at NTSC frame rates (29.97 specifically). Has anyone found a way to do that in the BMD Camera app yet?

Good question.

Why log only on 15 and 15 pro? And also HEVC HDR. How Filmic pro shot log and DV HDR, but BMD Camera app can't on older iPhones?

Why log only on 15 and 15 pro? And also HEVC HDR. How Filmic pro shot log and DV HDR, but BMD Camera app can't on older iPhones?

From what I understand FilmicPro is using their own version of Log. Apple is opening up Log capabilities from the sensor with the 15 Pro and 15 Pro Max.

I think the issue of the BMC App making the Log footage look “overexposed” in the viewfinder is related to the phone trying to go into HDR mode. It’s getting tone mapped unnecessarily.

You can see the display doing the tone mapping when you set the colorspace to 2020 too. Change the settings to 2020 then go to the camera view. You’ll see it initially load as SDR and then the view will brighten to the HDR mode.
The Log color space is ALSO trying to do this, but it’s wrong, probably because the log colorspace is 2020 too and it’s kicking in. I don’t know if this is Apple’s fault for taking over the display, or BM needs to tell the app to not let this happen.

I’ve looked through the iPhone settings and I can’t see a way to disable this at a system level. There is an option in the settings for the Photos app to disable “View in HDR” but it has no effect elsewhere

Thought I had read this correct in another thread but wanted to confirm it with others.
Is everyone experiencing this problem with the app currently and monitoring the image? When recording through the app, the image is completely blown out, but by way of histogram, image looks fine. Once the image is recorded and viewed in the media tab, image looks normal and how the actual histogram is reading out.
Image attached for reference. Top is while in the app, bottom is the a screenshot from the Media section and actually recorded footage.

Hope this isn't just me and they fix this.
Or I guess in the meantime, is there a LUT anyone has made to balance out this look?

Thought I had read this correct in another thread but wanted to confirm it with others.
Is everyone experiencing this problem with the app currently and monitoring the image? When recording through the app, the image is completely blown out, but by way of histogram, image looks fine. Once the image is recorded and viewed in the media tab, image looks normal and how the actual histogram is reading out.
Image attached for reference. Top is while in the app, bottom is the a screenshot from the Media section and actually recorded footage.

Hope this isn't just me and they fix this.
Or I guess in the meantime, is there a LUT anyone has made to balance out this look?

This is correct. You can see my previous posts about this and the inaccuracy of the exposure tools as well. I generated a LUT from the color space transform node in resolve to view a rec 709 display while shooting log, but it’s still blown out. I hope an update to fix all of this isn’t far off.

Thought I had read this correct in another thread but wanted to confirm it with others.
Is everyone experiencing this problem with the app currently and monitoring the image? When recording through the app, the image is completely blown out, but by way of histogram, image looks fine. Once the image is recorded and viewed in the media tab, image looks normal and how the actual histogram is reading out.
Image attached for reference. Top is while in the app, bottom is the a screenshot from the Media section and actually recorded footage.

Hope this isn't just me and they fix this.
Or I guess in the meantime, is there a LUT anyone has made to balance out this look?

This is correct. You can see my previous posts about this and the inaccuracy of the exposure tools as well. I generated a LUT from the color space transform node in resolve to view a rec 709 display while shooting log, but it’s still blown out. I hope an update to fix all of this isn’t far off.

Ah yeah, not sure how I missed that. Bummer that it's happening and hoping it's just a quick fix to their app. Although usable still for sure just definitely trips my brain out and makes me want to under expose everything ].

Try Rec.2020 for recording as it made the zebras go away for me shooting outdoors. In post you have the flexibility to define your output so Rec.2020 can make sense until this is fixed by an update to BMCAMAP.

This is where I think the bug is happening in the app. The iPhone display is trying to render the log footage with tone mapping, as if it was a regular Rec2020 hdr clip. If this flag is enabled/disabled by the developers when turning on Log mode, maybe it will fix the issue.

https://developer.apple.com/documentati ... 1-wantshdr

Completely uninstalling and reinstalling the app gave me the log option. I think it had stored info about what phone it was on from my old phone and transferred that over when setting up the new one.

With iPhone 15 Pro and BMD Camera app v.1.01, I do not have log video as an option, and uninstalling and reinstalling today did not fix this. Am I looking in the wrong place? Apple Log should be a choice under Codec, right?

OK, got it. Reboot, reinstall, Apple Log under Color Space

An update for anyone with the “overexposing” display issue:

I’ve figured out the way to fix this, at least on my phone, is to turn off stabilisation.
It’s as simple as that.

With stabilisation set to off, the Log image displays perfectly. I think the bug I mentioned in my other post is only kicking in when the camera is processing the stable image.

An update for anyone with the “overexposing” display issue:

I’ve figured out the way to fix this, at least on my phone, is to turn off stabilisation.
It’s as simple as that.

With stabilisation set to off, the Log image displays perfectly. I think the bug I mentioned in my other post is only kicking in when the camera is processing the stable image.

Ah good find! Can confirm that this works. Just tested.
Weird it is trying to process the stabilized image different though.

When I try to apply a display LUT to look though it actually reverts back to the bug, even if stabilization is off though.

Actually noticed if you turn on any of the features it does it as well.
So if you turn off stabilization, it returns it to normal and make it look like it should.

If you turn on LUTS, Zebra or false color (while stabilization is off) it also bugs out and overexposes the image on.

I know everyone is ecstatic that we can record in true 24.00 and true 30.00 FPS, but I'm trying to match with Sony cameras that record at NTSC frame rates (29.97 specifically). Has anyone found a way to do that in the BMD Camera app yet?

Can we? On my iPhone13 I only get variable frame rates.

Same here, tested on an iPad Pro M2 and an iPhone SE II.
Always variable, even if low-light adaptation is off.

An update for anyone with the “overexposing” display issue:

I’ve figured out the way to fix this, at least on my phone, is to turn off stabilisation.
It’s as simple as that.

With stabilisation set to off, the Log image displays perfectly. I think the bug I mentioned in my other post is only kicking in when the camera is processing the stable image.

Ah good find! Can confirm that this works. Just tested.
Weird it is trying to process the stabilized image different though.

When I try to apply a display LUT to look though it actually reverts back to the bug, even if stabilization is off though.

Ah yeah, I hadn't actually tried the LUTs or other overlays yet and you're right, having any of them turned on breaks Log monitoring.

It's a shame as the app is so close to being usable but I really can't right now. After looking at footage I filmed with stabilsing turned off, wow, my hands are shakier than I thought
It's really doing a lot to take out micro jitters and I don't feel like wanting to post-stablisie everything.

Same here, I use Cinematic setting for motion Stabilization. The BMCAMAP is very close to perfection which I would define as also including the ability to capture stills.

Actually noticed if you turn on any of the features it does it as well.
So if you turn off stabilization, it returns it to normal and make it look like it should.

If you turn on LUTS, Zebra or false color (while stabilization is off) it also bugs out and overexposes the image on.

Nice find! I’m sure this will be an easy fix in the next update.

I wanted to share a forum post I made trying to get Apple to add constant frame rate as a setting to their camera API, this way the Blackmagic app could take advantage of it. If enough of us raise this concern, they might actually do something about it.

We can also send feedback through the feedback app on MacOS suggesting this feature. There really is no excuse for Apple to be limiting ProRes to VFR. For normal phone videos, it somewhat makes sense but if you're recording in massive ProRes files... absolutely not.

https://discussions.apple.com/thread/255162902

I wanted to share a forum post I made trying to get Apple to add constant frame rate as a setting to their camera API, this way the Blackmagic app could take advantage of it. If enough of us raise this concern, they might actually do something about it.

We can also send feedback through the feedback app on MacOS suggesting this feature. There really is no excuse for Apple to be limiting ProRes to VFR. For normal phone videos, it somewhat makes sense but if you're recording in massive ProRes files... absolutely not.

https://discussions.apple.com/thread/255162902

I can't see this happening since at least the 15 pro does have constant frame rate. Even if they can do it in older phones, they probably just don't care if it encourages people to get newer phones.

I wanted to share a forum post I made trying to get Apple to add constant frame rate as a setting to their camera API, this way the Blackmagic app could take advantage of it. If enough of us raise this concern, they might actually do something about it.

We can also send feedback through the feedback app on MacOS suggesting this feature. There really is no excuse for Apple to be limiting ProRes to VFR. For normal phone videos, it somewhat makes sense but if you're recording in massive ProRes files... absolutely not.

https://discussions.apple.com/thread/255162902

I can't see this happening since at least the 15 pro does have constant frame rate. Even if they can do it in older phones, they probably just don't care if it encourages people to get newer phones.

But it doesn't, my testing is with a 15 Pro Max and my videos are coming out as VFR. Every once in a while I'll get one in CFR but about 95% are variable.

Mr. Tim Cook is all about managing the slow incremental release of annual editions of phones to increasingly drive new sales. He’s not beyond claiming new features that we already have as if they were just invented for the new phone such as shooting 48MP photos in the new phone whereas that was already added to the previous year (never giving an unsuspecting buyer the complete context. He’s never about adding value to older products although occasionally something slips in anyway.

Fortunately the products are decent and useful although seldom cutting edge as they used to be under his predecessor.

But it doesn't, my testing is with a 15 Pro Max and my videos are coming out as VFR. Every once in a while I'll get one in CFR but about 95% are variable.

Wait are you talking about h.265? I was just referring to ProRes. I'm only using ProRes if I care at all about the quality.

But it doesn't, my testing is with a 15 Pro Max and my videos are coming out as VFR. Every once in a while I'll get one in CFR but about 95% are variable.

Wait are you talking about h.265? I was just referring to ProRes. I'm only using ProRes if I care at all about the quality.

I’m talking about ProRes log as that’s all I care about using with video on the iPhone 15 Pro.

I can't see this happening since at least the 15 pro does have constant frame rate.

Nope. It doesn't. It's an APPLE issue.

JB

I can't see this happening since at least the 15 pro does have constant frame rate.

Nope. It doesn't. It's an APPLE issue.

JB

Strange. None of my files are showing variable frame rates.

Strange. None of my files are showing variable frame rates.

They can work fine and then there will be one clip. No one can explain why Apple do this.

JB

Strange. None of my files are showing variable frame rates.

They can work fine and then there will be one clip. No one can explain why Apple do this.

JB

Yeah, I'll be on the lookout for it now.

I can't see this happening since at least the 15 pro does have constant frame rate.

Nope. It doesn't. It's an APPLE issue.

JB

Strange. None of my files are showing variable frame rates.

Can you screenshot your settings in the iOS settings app for video? Maybe one of those is disabling it somehow although I’ve already tried most of them.

Strange. None of my files are showing variable frame rates.

They can work fine and then there will be one clip. No one can explain why Apple do this.

JB

That’s why my suggestion is to bombard Apple via the Feedback app with suggestions / bug reports on the issue. In the past they have fixed things I’ve brought up so it’s worth a shot.

I've opened a dedicated topic for this: viewtopic.php?f=2&t=189291

Does anyone know why I am unable to record externally to ssd on an iPhone 13 Pro? I have a dongle that’s lightning to usb. I can only record about 15 seconds in ProRes LT in 1080p to a ssd. The limitation of lightning is 480 mbs and ProRes LT 1080 is at approximately 100 mbs. Is there some other limitation I’m missing? The app just flashes an explanation mark and freezes up. I understand why I wouldn’t be able to record in 4K but not sure what the limitation here is.

But it doesn't, my testing is with a 15 Pro Max and my videos are coming out as VFR. Every once in a while I'll get one in CFR but about 95% are variable.

This is exactly what I get from my Standard 13. The first clip I shot had CFR and I was excited, even wrote this in a post here. The next ones all had VFR but this VFR is constant across all clips (min 30 max 31.59).
To me it looks like the app tries its best to get CFR and from time to time it hits the nail.
Don't know if this depends on the codec being used, I only tried PR422 so far.

Interesting. My 11 Pro Max will only do H264 and H265, but does produce rock steady 24 FPS HD video. At least Resolve has not complained yet! Not tried 4K yet as I need a new computer.

Steve.

I discovered you can record to external drive in the BM camera app. 4k prores HQ at 60p on a Samsung T5. iphone 15 pro .The app is glorious.

Just popping back to say that you can record directly to an external SSD using this app. In Settings > Media you can navigate to an external SSD and save files there; the downside is that it won't fall back to internal storage if you disconnect the SSD, but will instead refuse to record.

Looking forward to the next update, but this is already a very useful app.

- Is it possible to synchronize time codes between several iPhones for multi-camera?
- How to activate the Flash
It would be an interesting feature.

thank you

anyone have problem with the app that it displays black screen?
worked first day , next day this:

- black screen switching to any camera. with any parameters.
- can select options and press record.
- record can not be stopped, not responding to touch or physical buttons
- fully uninstalled app and reinstalled - same issue

Just popping back to say that you can record directly to an external SSD using this app. In Settings > Media you can navigate to an external SSD and save files there; the downside is that it won't fall back to internal storage if you disconnect the SSD, but will instead refuse to record.

Looking forward to the next update, but this is already a very useful app.

With external ssd connected if you go to 'save clips to' you can browse and choose the ssd from the files menu in your phone. Just scroll through to find the drive. When you unplug the ssd it will automatically fall back to internal storage.

The great thing is I can use all my cfast 2.0 cards I got for my Blackmagic pocket camera and my angel bird card reader/writer as a external drive.

Is anyone else having issues with a frozen video cleanfeed via AirPlay screen mirroring after about 2 seconds? After switching lenses it works for a moment but then freezes again. It only affects the Blackmagic Camera app, otherwise everything runs smoothly when I use the Apple camera app, for example.
I have already tried it with different Apple TVs (some connected via Ethernet) and Macs but all show the same problem. I use an iPhone 13 Pro with iOS 16.6.1 and app version 1.0.10003.

We don't have a hold on an iPhone 15 yet but was scrolling through the app tech specs page.
Anyone know what this means?

2023-10-05 12_46_02-Blackmagic Camera – Tech Specs _ Blackmagic Design.png (2.25 KiB) Viewed 4073 times

ACES -> Surely has to be a mistake right?

shebbe,
Ha, maybe is like Apple Log space. But then what does Apple know of color, or of photos or video. But not to worry, as 'they' will fix it in AI.

Hey Jeffrey, not sure if I get what you're saying, sorry about that.

It's clearly BMD listing ACES as a Color Space meaning they suggest it's a recording option? I would hope this doesn't mean ACEScct/cc as this is not at all meant to be a camera encoding. And any linear encoding wouldn't work in ProRes obviously. Or is ACES an actual option on the iPhone 15? That would be very weird.

Regardless, it feels like a mistake in just the tech specs page and there is no such option actually available.

In the event Apple made a big deal about ACES and external recording ... as a way for
on set matching of clips from a cinema camera and the phone ....

Matching a phone to a cinema camera is obviously optimistic to say the least. But Apple Log recording is very welcome to allow proper post workflows including ACES. But that doesn't mean that the phone records in ACES of course. Just the word ACES doesn't even mean a color space.

...
Regardless, it feels like a mistake in just the tech specs page and there is no such option actually available.

Resolve 18.6 has an ACES IDT for Apple Log. You can use it in an ACES color managed workflow or using the ACES Transform effect on a color node.

Matching a phone to a cinema camera is obviously optimistic to say the least. But Apple Log recording is very welcome to allow proper post workflows including ACES. But that doesn't mean that the phone records in ACES of course. Just the word ACES doesn't even mean a color space.

You might be surprised

Resolve 18.6 has an ACES IDT for Apple Log. You can use it in an ACES color managed workflow or using the ACES Transform effect on a color node.

That is not my point. I'm very well acquainted with ACES workflows. The point is that in the description of the BMD Camera App on BMD's website they list the color spaces the app supposedly can shoot in. One of those is ACES. This is plain wrong. It is not a color space, and even the ones that are one (ACEScct/cc, ACEScg, ACES2065-1) are not for camera to file encoding.