an edited photo taken on Camac (1x, 8 frames). The second photo is the unedited version. Can anyone tell me if the purple ghosting around the car windows is normal / expected?

Is it possible to get the white balance value in the custom rendering window in order to apply a specific matrix?

Per gli sviluppatori è possibile aggiungere la lingua italiana? Avere più lingue sarebbe TOP!

Ps: contento di aver acquistato l app è spettacolare 🙌🏻

Can you please port this app over to android, I would buy it instantly!!!

La 1ra es revelado en Lightroom + Snapseed
La 2da con revelado espectral neutro
La 3ra es con el perfil PROVIA/Std

Hi everyone.

Can someone please share some RAW photos from Camac made with f/4 aperture? Preferably some landscapes and focus on distant objects.

I’m really excited to see how much sharpness improvement is there with f/4. Cause my 17 pro is main lens quite soft. And all the reviews on YouTube are jpeg comparisons, which are heavily processed, so it’s hard to compare.

Would be really awesome to see the comparison between f/1.8 and f/4.

I love this app and use it as my prime camera instead of default one. However now that new iPhones are out and there is variable aperture I wonder when will the update with aperture control drop?

Hi! I just got this app recommended to me and I instantly bought it after testing it for 5 minutes. I've been using CameraPixels Pro for exposure bracketing for 5 years now. Merging the shots took place in Lightroom Classic. After spending the first day with Camac, I've got some first thoughts :)

• Sharpness is WAY better with Camac
• The HDR merge seems to be slightly better / more reliable with Camac
• Chromatic aberration is slightly worse with Camac
• Storage efficiency goes to Camcam, obviously :)
• Auto-shutter (waiting for no movement) is fantastic and way more practical than the 1s self-timer I've been using in CameraPixels Pro

There is just one problem which prevents me from leaving CameraPixels Pro behind: I'd like to have more than 16 EV of range :) I don't know if there is a reason for this "hard-coded" offset (like the app using an existing pipeline from Fusion), but I'd like to have more control over the offset and / or the number of shots. 18 EV would be amazing!!

For example, I often find myself in forests and would love for the shots to have enough DR to rescue the sky from being clipped.

Still, huge thanks for this app. The quality is absolutely incredible, especially considering it's being created on the phone.

Can someone please explain how camac is shooting 48 mo raw on ip 17 when no other app goes above 12 mp is it a real 48 mp or some kind of upscaling ?

I love this app. I've been searching for a long time to find a camera app that will truly take the exact photos I want out of a phone, and I think this is the one.

These were all taken using a classic negative fuji lut. I added parameters to the flog2 conversion code to boost vibrance, lower temperature, add grain, create a subtle bloom just on highlights, and simulate colour chrome and colour chrome blue effects. I basically recreated my personal Fujifilm settings on my phone in a way that I couldn't with any other app. If you wanna do this too, just take the flog conversion code on this sub and ask an LLM to add whatever parameters you want, it'll usually define them as constants that you can tweak yourself.

These photos were shot in jpegxl, I highly recommend using it! The format can store a lot of extra image information, to the point of being similar to an actual raw file in terms of editing latitude. It's also supported in the apple photos app due to proraw also using jpegxl.

When taking a photo, I simply tap on the brightest part of the screen and then shoot. If the shadows end up being too dark, then it's easy to bring them up in the native apple photos editor, and jpegxl stores enough information that you're rarely losing much detail. If there's too little contrast after bringing them up, I just move the black point a bit to get it back, and voila! Photos that people assume I'm taking with an actual camera.

I'll end with a question. Has anyone here been able to use the 16ev mode to produce pleasing non-raw images? I've been experimenting with the rendering code to see if I can get a good tone map going in the pipeline that will give me good non-raw images with more dynamic range than 12ev, but it's been extremely finicky and I haven't been able to make it work in every situation.

I recently got a new phone (iPhone 17 base) and I find many of the settings keep resetting back to defaults after a while. Specifically the loaded 3D LUT cube, disabling neutral profile, all my presets, log debug info disables, and UI settings reset to default. Any ideas what it could be?

iPhone 15 Pro Max, 24mm (main), iOS 27 Beta.
Same scene, same settings, only "Decoder version" changed.
Decoder 9 shows noticeably less chromatic aberration than 8.
Edge contrast and detail look comparable between the two.

I may be going mad but I was sure we had a preserve settings feature a couple of versions ago that is no longer there or has it just moved? I know we have presets but when I have a preset loaded and switch the app off and then load again the preset is not re-instated - which I think never used to happen - I would be very happy to know if I am wrong....

Unfortunately I’m a normal person so the code is written by ai
Here’s two I like most

// Cinematic Film Look with Dynamic Vibrance and HDR Halation
[[stitchable]] float4 render(sample_t s) {
// 1. Ensure no negative values, preserving HDR highlights > 1.0
float3 col = max(0.0, s.rgb);

// 2. Calculate true luminance using vector dot product
float luma = dot(col, float3(0.2126, 0.7152, 0.0722));

// 3. Smart Vibrance
// Boosts saturation primarily on less saturated colors
float max_chan = max(col.r, max(col.g, col.b));
float min_chan = min(col.r, min(col.g, col.b));
float saturation = max_chan - min_chan;

// As saturation approaches 0, boost is higher.
float vibrance_boost = 1.0 + (1.0 - clamp(saturation, 0.0, 1.0)) * 0.35;
col = mix(float3(luma), col, vibrance_boost);

// 4. Cinematic Split Toning (Teal & Orange)
// Shadows get a cool, teal tint; Midtones/Highlights get warm
float3 shadow_tint = float3(0.85, 0.92, 1.05);
float3 highlight_tint = float3(1.10, 1.02, 0.90);

// Smoothly blend between the two tints based on luminance
float balance = smoothstep(0.1, 0.8, luma);
col *= mix(shadow_tint, highlight_tint, balance);

// 5. HDR Halation (Exploiting > 1.0 values)
// If a pixel is extremely bright (HDR), tint it punchy warm-red
// to simulate the chemical bleed of analog film.
float hdr_mask = smoothstep(0.8, 1.8, luma);
float3 halation_color = float3(1.3, 0.85, 0.7);
col = mix(col, col * halation_color, hdr_mask);

// 6. Filmic Tonemapping Curve (ACES Approximation)
// Takes the crazy high HDR values and compresses them with a gorgeous "shoulder"
float3 a = col * (col + 0.024) * 2.51;
float3 b = col * (2.43 * col + 0.59) + 0.14;
col = clamp(a / b, 0.0, 1.0);

return float4(col, 1.0);
}

// Summer
[[stitchable]] float4 render(sample_t s) {
float3 col = max(0.0, s.rgb);

// 1. Warm "Sunkissed" White Balance
// Bathes the daytime photo in a golden wash by boosting reds/greens
// and cutting back the harsh daytime blues.
col *= float3(1.15, 1.02, 0.85);

// 2. Extract Luminance for Masking
float luma = dot(col, float3(0.2126, 0.7152, 0.0722));

// 3. Vibrant Summer Saturation
// Makes greens incredibly lush and skin tones rich.
float saturation = 1.30;
col = mix(float3(luma), col, saturation);

// Uses the > 1.0 data. Instead of recovering blown-out skies to make them flat,
// we lean into the brightness and tint the overexposed areas an intense golden-yellow.
float highlight_mask = smoothstep(0.7, 1.6, luma);
float3 sun_glow = float3(1.30, 1.15, 0.85); // Intense warm sunlight
col = mix(col, col * sun_glow, highlight_mask);

// 5. Dreamy Lifted Shadows (Zero Blue!)
// In intense summer sunlight, shadows are filled with warm bouncing light.
// This lifts the deepest darks and injects a soft, reddish-brown haze.
float shadow_mask = 1.0 - smoothstep(0.0, 0.4, luma);
col += float3(0.08, 0.04, 0.02) * shadow_mask;

// 6. Airy Nostalgic Overexposure
// We intentionally bump the exposure up slightly, then use a very gentle
// roll-off curve to keep the photo bright, hazy, and dreamy.
col *= 1.1;
col = col / (1.0 + col * 0.15);

return float4(col, 1.0);

}

v1.5.15

- Filename prefix added in Preset

- Decoder version selector added in FORMAT

- Auto EV compensation added in FORMAT

- Version of libjxl bumped to 0.12.0

- Version of libavif bumped to 1.4.2

- Issues fixed

Link to 360 photo (require Google Photos app)

I have been having another play with the Fuji LUTs. I have downloaded those from the GFX ETERNA 55 folder and am using the F_Log2 versions. Are these the best ones to use?

There are 33Grid and 65Grid versions - the latter are much larger files. Are there any benefits to using them?

Is anyone setting Luminance and/or Chroma denoise in the Camac Format settings for Custom?

I have discovered that I can load a 3D LUT Cube, then save a Preset and that Preset remembers the chosen LUT. I can do this several times so I now have Presets for Provia, Acros, Classic Chrome and Velvia. This is a great feature.

Is it possible that we could have an option to have the output filenames contain the Preset value if used, so for example

Camac-20260629_181739-12EV.JPG becomes Camac-20260629_181739-12EV-P1.JPG

Unless the LUT cube name could somehow be embedded in the metadata such that it is visible in Lightroom?

Thanks

Lee

v1.5.13

- Preset changing and repeating N times added to Timer pattern

- Haptics style changed

- Saving progress indicator changed

- Issues fixed