Change deadband zone message from DEBUG to LOG level to prevent
spam while still showing gain/exposure adjustment messages.
This allows using --gst-debug to see important ramping information
without flooding the output with 'Within deadband zone' messages
every frame.
- Add new brightness-deadband property (default 10.0, range 0.0-50.0)
- Implements deadband/tolerance zone around target brightness
- When brightness is within ±deadband, no adjustments are made
- Prevents oscillation at fast update rates (10-100ms)
- Allows fast corrections when brightness significantly deviates
- Enables fast ramp rates without flicker/oscillation
- Updated README with detailed deadband documentation and usage examples
- Solves exposure fluctuation issue at high frame rates with fast updates
- Updated launch_with_signal.py with PEP 723 metadata for uv compatibility
- Added day/night mode presets with command-line arguments
- Implemented proper rollover-only file saving via Python/PIL callbacks
- Removed multifilesink from pipeline (was saving every frame incorrectly)
- Added funny auto-generated output directory names (e.g., fuzzy-photon)
- Updated rollover_example.py to follow same pattern with uv support
- Updated rollover_example.c to demonstrate signal detection without file saving
- Updated launch_with_capture.ps1 to remove incorrect multifilesink usage
- All scripts now save files ONLY on rollover events, not every frame
- Pipeline simplified: camera -> linescan -> display (files saved in callback)
- New plugin extracts single row/column from frames and builds line scan image
- Supports horizontal mode (extract row, stack vertically)
- Supports vertical mode (extract column, stack horizontally)
- Configurable line index and output size
- Proper caps negotiation with fixate_caps implementation
- Updated build system to include linescan plugin
- Added comprehensive README with usage examples
- Added brightness-smoothing parameter (0-1, default 0.1)
- Implements exponential moving average to filter transient brightness changes
- Samples brightness every frame but smooths before adjusting exposure
- Reduces oscillation from people/cars/birds moving through scene
- Updated DEBUG.md with complete implementation details
Recommended settings for dawn/dusk time-lapse:
ramp-rate=vslow update-interval=1000 brightness-smoothing=0.1
- Added brightness-smoothing parameter (0-1, default 0.1)
- Implements exponential moving average to filter transient brightness changes
- Samples brightness every frame but smooths before adjusting exposure
- Reduces oscillation from people/cars/birds moving through scene
- Updated DEBUG.md with complete implementation details
Recommended settings for dawn/dusk time-lapse:
ramp-rate=vslow update-interval=1000 brightness-smoothing=0.1
- Fixed instant exposure jumps causing visible flickering
- Implemented proper gradual ramping using ramp_step variable
- Added IDS uEye SDK integration for accurate exposure range query
- Added hcam property to idsueyesrc to expose camera handle
- Updated intervalometer to query on first frame when camera is ready
- Added comprehensive debug documentation with tuning guide
For dawn/dusk time-lapse, use:
ramp-rate=vslow update-interval=1000
- Remove hardcoded exposure (0.85/1.24ms) and gain (0/52) limits
- Add automatic querying of camera capabilities on startup
- Query current exposure/gain settings from camera on reset
- Add update-interval property for rate limiting (default 100ms)
- Prevent algorithm from running at full framerate (750fps)
- Expand property ranges to support any camera capabilities
- Algorithm now fully automated and adapts to camera limits
Fixed GLib-GObject-CRITICAL errors caused by incorrect enum type
registration in the intervalometer plugin.
The issue was on line 189 where g_param_spec_enum() was being called
with GST_TYPE_INTERVALOMETER (the class type) instead of a proper
enum GType for the ramp-rate property.
Changes:
- Added gst_intervalometer_ramp_rate_get_type() function to properly
register the GstIntervalometerRampRate enum as a GType
- Defined GST_TYPE_INTERVALOMETER_RAMP_RATE macro
- Updated PROP_RAMP_RATE property installation to use the correct
enum type
This fixes the following errors that appeared during pipeline launch:
- g_param_spec_enum: assertion 'G_TYPE_IS_ENUM (enum_type)' failed
- validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
- g_param_spec_ref_sink: assertion 'G_IS_PARAM_SPEC (pspec)' failed
- g_param_spec_unref: assertion 'G_IS_PARAM_SPEC (pspec)' failed
Implements YASS-inspired automatic exposure control for IDS uEye cameras.
The intervalometer filter analyzes video brightness in real-time and
smoothly ramps camera exposure and gain settings during changing light
conditions - ideal for sunset/sunrise time-lapse photography.
Key features:
- Automatic exposure ramping (0.85-1.24ms configurable range)
- Automatic gain control (0-52 configurable range)
- Real-time brightness analysis (GRAY8, GRAY16, RGB, BGR, BGRA)
- YASS-inspired ramping algorithm (exposure priority, then gain)
- Configurable ramp rates (VSlow/Slow/Medium/Fast/VFast)
- Exposure compensation (±4 stops)
- CSV logging of exposure parameters
- Direct GObject property control (no message bus overhead)
Technical implementation:
- GstBaseTransform filter for in-place processing
- Discovers upstream camera element by name
- Controls camera via g_object_set() for synchronous updates
- Frame-by-frame brightness calculation with format support
Files added:
- gst/intervalometer/gstintervalometer.c: Main implementation (734 lines)
- gst/intervalometer/gstintervalometer.h: Header with structure definitions
- gst/intervalometer/CMakeLists.txt: Build configuration
- gst/intervalometer/README.md: Comprehensive documentation
Files modified:
- gst/CMakeLists.txt: Added intervalometer subdirectory
- build.ps1: Added intervalometer to build and deployment pipeline
Usage example:
gst-launch-1.0 idsueyesrc name=cam ! \\
intervalometer enabled=true camera-element=cam \\
exposure-min=0.85 exposure-max=1.24 \\
gain-min=0 gain-max=52 ramp-rate=medium ! \\
autovideosink
Inspired by YASS (Yet Another Sunset Script) for CHDK cameras by
waterwingz, based on work by Fbonomi and soulf2.
- Deleted all subdirectories from sys/ except idsueye/
- Updated sys/CMakeLists.txt to only include idsueye subdirectory
- Updated main CMakeLists.txt to only search for IDSuEye package
- Removed find_package() calls for: Bitflow, NIIMAQ, NIIMAQdx, FreeImage,
OpenCV, Aptina, EDT, Euresys, GigESim, Imperx, ImperxSDI, IOtechDaqX,
KAYA, Matrox, Phoenix, Pleora, Pylon, QCam, Sapera, and XCLIB
The project now exclusively supports IDS uEye cameras in the sys folder.
This commit introduces third-party work by waterwingz, based on scripts
by Fbonomi and soulf2. YASS is an advanced intervalometer script for
CHDK-enabled Canon cameras that automatically adjusts exposure settings
during sunset, sunrise, or other changing light conditions.
Key features:
- Automatic exposure ramping (shutter speed and ISO)
- Intelligent ND filter control
- Focus lock options (AFL/MF at infinity)
- Configurable shot intervals and exposure compensation
- CSV logging of exposure parameters
- Battery-saving display blanking options
Original work released under GPL license.
Requires CHDK 1.2.0 build 3276 or higher (1.3.0+ recommended).
Files added:
- yass/yass4.lua: Main script (v4.8)
- yass/README.md: Documentation and usage guide
Previously, GET_FRAMERATE and GET_EXPOSURE returned only cached values.
Now they query the actual hardware state using:
- is_SetFrameRate() with IS_GET_FRAMERATE for framerate
- is_Exposure() with IS_EXPOSURE_CMD_GET_EXPOSURE for exposure
This matches the pattern used for auto-exposure, auto-gain, and gain-boost
properties, ensuring UDP control commands return real-time hardware values
instead of stale cached values. Critical when auto-exposure is enabled as
the hardware adjusts exposure dynamically.
- Lower minimum exposure from 1.0ms to 0.015ms in launch-ids.py validation
- Add exposure range validation (0.015-30000ms) to camera_control.py
- Update help text to display exposure range for better user guidance
- Adjust camera config: swap binning/subsampling values in nightcolor preset
- Add comment explaining subsampling vs binning behavior
Enhances exposure control granularity and provides clearer validation
feedback while optimizing camera configuration for low-light scenarios.
- Update camera_control.py to support 'property value' syntax
* camera_control.py gain → gets current gain value
* camera_control.py gain 33 → sets gain to 33
* Add --host, --port, and --timeout parameters
* Remove argcomplete dependency to simplify requirements
* Maintain backward compatibility with existing commands
- Update launch-ids.py to support simplified property setting at startup
* launch-ids.py exposure 16 → launches with 16ms exposure
* launch-ids.py framerate 30 → launches with 30fps framerate
* launch-ids.py gain 50 → launches with gain set to 50
* Preserve traditional flag syntax for full backward compatibility
Both scripts now provide intuitive property-based syntax while
maintaining all existing functionality and command-line options.
- Update camera_control.py to support 'property value' syntax
* camera_control.py gain → gets current gain value
* camera_control.py gain 33 → sets gain to 33
* Add --host, --port, and --timeout parameters
* Maintain backward compatibility with existing commands
- Update launch-ids.py to support simplified property setting at startup
* launch-ids.py exposure 16 → launches with 16ms exposure
* launch-ids.py framerate 30 → launches with 30fps framerate
* launch-ids.py gain 50 → launches with gain set to 50
* Preserve traditional flag syntax for full backward compatibility
Both scripts now provide intuitive property-based syntax while
maintaining all existing functionality and command-line options.
- PROP_AUTO_EXPOSURE now queries hardware using IS_GET_ENABLE_AUTO_SHUTTER
- PROP_AUTO_GAIN now queries hardware using IS_GET_ENABLE_AUTO_GAIN
- PROP_GAIN_BOOST now queries hardware using IS_GET_GAINBOOST
This ensures each camera reports its actual hardware state rather than
a shared cached value when properties are queried via camera_control.py
- Add gain-boost property to gstidsueyesrc (boolean)
- Implement is_SetGainBoost() API call in property setter and framerate/exposure function
- Add UDP control commands SET_GAIN_BOOST and GET_GAIN_BOOST
- Add --gain-boost command-line flag to launch-ids.py
- Update camera_control.py with get-gain-boost and set-gain-boost commands
- Change parameter defaults to None (exposure, framerate, gain) to respect INI file defaults
- Only set properties when explicitly provided by user - INI file is source of truth
- Query camera's actual exposure range before setting exposure time
- Validate and clamp exposure values to supported min/max limits
- Log detailed information about range, requested vs actual values
- Add GET_EXPOSURE_RANGE command to UDP control interface
- Update Python control scripts with exposure range query support
This prevents IS_INVALID_EXPOSURE_TIME errors and ensures values are
always within the camera's capabilities. The exposure range varies by
framerate and sensor configuration.
- Added 'gain' property to gstidsueyesrc element (0-100, 0=auto)
- Implemented hardware gain control using is_SetHardwareGain() API
- Added --gain/-g command-line argument to launch-ids.py
- Added SET_GAIN and GET_GAIN UDP control commands
- Updated STATUS command to include gain value
- Added get-gain and set-gain commands to camera_control.py test client
- Gain can be set at startup or adjusted dynamically during runtime
- Replaced garbled is_GetError() output with human-readable error messages
- Added error code mapping for 25+ common IDS errors from uEye.h
- Enhanced camera initialization with detailed logging and context
- Error messages now include error code, name, description, and troubleshooting hints
- Added information about device/camera ID attempted and available camera count
- Example: Error 3 now shows 'IS_CANT_OPEN_DEVICE (3): Cannot open device - check if camera is connected and not in use. Camera/Device ID used: 99, Available cameras: 2'
Fixes issue where camera initialization failures showed cryptic characters instead of useful error information.
- Added --display option for 1/4 sized preview window using autovideosink
- Added --camera-id and --device-id options for camera selection
- Added UDP control commands: SET_CAMERA_ID, GET_CAMERA_ID, SET_DEVICE_ID, GET_DEVICE_ID
- Updated GStreamer idsueyesrc element to support device-id property
- device-id uses IS_USE_DEVICE_ID flag for system enumeration
- camera-id continues to use user-definable ID (0 for first found)
- Updated STATUS command to include camera_id and device_id
