+- phyphox Forums (https://phyphox.org/forums)
+-- Forum: App-Feedback (https://phyphox.org/forums/forumdisplay.php?fid=6)
+--- Forum: Experiment editor (new Blockly-based version) (https://phyphox.org/forums/forumdisplay.php?fid=15)
+--- Thread: Camera GUI not allowing full exposure controls (/showthread.php?tid=2238)
Camera GUI not allowing full exposure controls - wuppel - 02-11-2026
After editing the experiment Camera -> Brightness (Luminance) the camera-GUI in the app only shows the simple controls no matter what value is defined in the parameter "exposureAdjustmentLevel".
When using the original experiment in the same app the full controls are shown.
Example:
Code:
<camera-gui label="Vorschau" exposureAdjustmentLevel="3" grayscale="true" markOverexposure="ff0000" markUnderexposure="0000ff"/>Also the parameter "showControls" seems to have no effect when used.
This is true both for an iPhone11 (app version 1.2.0) and for a phone with android 16 (app version 1.2.0).
What could be the problem with my code (which was generated by the new editor)?
RE: Camera GUI not allowing full exposure controls - Sebastian Staacks - 02-17-2026
Thanks for reporting. Looks like a mistake from our documentation made it into the editor. It should be exposure_adjustment_level instead of exposureAdjustmentLevel. Should be an easy fix for the next update of the editor.
RE: Camera GUI not allowing full exposure controls - wuppel - 02-18-2026
Hello Sebastian,
thanks a lot! After editing the parameter name, the controls work fine now.
A little off topic, but maybe another aspect where you might want to doublecheck the documentation:
I had the impression that the "locked"-parameter for the camera input had no effect in my experiment (on iPhone and Android):
<camera aeStrategy="prioritiseFramerate" locked="iso=200 , shutter_speed=1/125">
best regards
RE: Camera GUI not allowing full exposure controls - Sebastian Staacks - 02-23-2026
The problem is that the auto exposure setting defaults to "true", so the ISO and shutter speed are set, but auto exposure modifies them immediately. So, you should also specify auto_exposure="false" and I should probably modify the various auto exposure "strategies", so they take into account which settings are locked as that probably makes more sense for most use cases.
Embarrassingly, while testing, this also brought up a few more errors in the editor:
prioritiseFramerate should be prioritizeFramerate (iOS ignores this while Andorid throws an error) and autoExposure should be auto_exposure (perfecting the confusing mix of camel and snake case).
I am a bit surprised that our new automated testing for the editor did not catch that...