Close Menu
geekfence.comgeekfence.com
    What's Hot

    Amazon launches an AI shopping assistant for the search bar, powered by Alexa+ 

    May 13, 2026

    Choosing the Right Agentic Design Pattern: A Decision-Tree Approach

    May 13, 2026

    The Rise of Sports Intelligence: How the Lakehouse Turns Tracking Data into Competitive Advantage

    May 13, 2026
    Facebook X (Twitter) Instagram
    • About Us
    • Contact Us
    Facebook Instagram
    geekfence.comgeekfence.com
    • Home
    • UK Tech News
    • AI
    • Big Data
    • Cyber Security
      • Cloud Computing
      • iOS Development
    • IoT
    • Mobile
    • Software
      • Software Development
      • Software Engineering
    • Technology
      • Green Technology
      • Nanotechnology
    • Telecom
    geekfence.comgeekfence.com
    Home»iOS Development»ios – AVCaptureDevice.exposurePointOfInterest readback does not match set value on iPad Pro M4 / M3(UltraWide)and Gen2,3,4(TrueDepth) using resizeAspectFill
    iOS Development

    ios – AVCaptureDevice.exposurePointOfInterest readback does not match set value on iPad Pro M4 / M3(UltraWide)and Gen2,3,4(TrueDepth) using resizeAspectFill

    AdminBy AdminApril 24, 2026No Comments2 Mins Read3 Views
    Facebook Twitter Pinterest LinkedIn Telegram Tumblr Email
    ios – AVCaptureDevice.exposurePointOfInterest readback does not match set value on iPad Pro M4 / M3(UltraWide)and Gen2,3,4(TrueDepth) using resizeAspectFill
    Share
    Facebook Twitter LinkedIn Pinterest Email


    Closed. This question needs to be more focused. It is not currently accepting answers.


    Want to improve this question? Guide the asker to update the question so it focuses on a single, specific problem. Narrowing the question will help others answer the question concisely. You may edit the question if you feel you can improve it yourself. If edited, the question will be reviewed and might be reopened.

    Environment:

    • Devices: iPad Pro 11″ M4, iPad Air 11″ M3, iPad Pro 11″ Gen2/3/4

    • Language: Swift

    • Framework: AVFoundation

    • Front camera: UltraWide (M4/M3), TrueDepth (Gen2–4)

    • Video gravity: .resizeAspectFill


    Background

    I am setting an exposure point of interest using coordinates defined in captured image pixel space.

    • Input point: (1170, 1370)

    Image sizes:

    • Gen2/3/4: 2316 × 3088

    • M3/M4: 3024 × 4032

    Preview sizes:

    • Gen2/3/4: 834 × 1194

    • M4: 834 × 1210

    • M3: 820 × 1180


    What I do

    First, I convert image pixel coordinates to preview layer coordinates, then use captureDevicePointConverted(fromLayerPoint:).

    let devicePoint = previewLayer.captureDevicePointConverted(fromLayerPoint: layerPoint)
    

    Reading back exposure point

    After capture, I convert back:

    let layerPoint = previewLayer.layerPointConverted(fromCaptureDevicePoint: exposurePoint)
    

    This results in:


    Observation

    It seems that captureDevicePointConverted(fromLayerPoint:) does not perform a linear mapping when using .resizeAspectFill.

    My understanding is that:


    Questions

    1. Does captureDevicePointConverted(fromLayerPoint:) account for .resizeAspectFill cropping, making it unsuitable for direct pixel mapping?

    2. Is it correct to compute exposure points directly using normalized coordinates (pixel / image size) instead of using preview layer conversion?

    3. Is exposurePointOfInterest always expressed in full sensor normalized coordinates (0–1), independent of preview settings?

    4. Does this behavior differ between UltraWide (M3/M4) and TrueDepth cameras?

    5. Is there official documentation describing correct coordinate mapping for this scenario?




    Source link

    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email

    Related Posts

    My Outer Loop | Cocoanetics

    May 13, 2026

    Conventions for Xcode – The.Swift.Dev.

    May 12, 2026

    ios – How to add shadow to border?

    May 11, 2026

    Introducing SwiftPorts | Cocoanetics

    May 7, 2026

    Awesome native Xcode extensions – The.Swift.Dev.

    May 6, 2026

    ios – Flutter UI not matching design: top-right badge not properly attached to card border

    May 5, 2026
    Top Posts

    Understanding U-Net Architecture in Deep Learning

    November 25, 202539 Views

    Hard-braking events as indicators of road segment crash risk

    January 14, 202627 Views

    Redefining AI efficiency with extreme compression

    March 25, 202626 Views
    Don't Miss

    Amazon launches an AI shopping assistant for the search bar, powered by Alexa+ 

    May 13, 2026

    Whether you like it or not, Amazon continues to put AI at the center of…

    Choosing the Right Agentic Design Pattern: A Decision-Tree Approach

    May 13, 2026

    The Rise of Sports Intelligence: How the Lakehouse Turns Tracking Data into Competitive Advantage

    May 13, 2026

    AWS expands Anthropic partnership with Claude Platform launch

    May 13, 2026
    Stay In Touch
    • Facebook
    • Instagram
    About Us

    At GeekFence, we are a team of tech-enthusiasts, industry watchers and content creators who believe that technology isn’t just about gadgets—it’s about how innovation transforms our lives, work and society. We’ve come together to build a place where readers, thinkers and industry insiders can converge to explore what’s next in tech.

    Our Picks

    Amazon launches an AI shopping assistant for the search bar, powered by Alexa+ 

    May 13, 2026

    Choosing the Right Agentic Design Pattern: A Decision-Tree Approach

    May 13, 2026

    Subscribe to Updates

    Please enable JavaScript in your browser to complete this form.
    Loading
    • About Us
    • Contact Us
    • Disclaimer
    • Privacy Policy
    • Terms and Conditions
    © 2026 Geekfence.All Rigt Reserved.

    Type above and press Enter to search. Press Esc to cancel.