isl-org / isl-org/Open3D

RealSenseRecorder color frames black/too dark

Open
#6,066 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
C++
Stars
14k
Forks
2.6k
Avg merge
5d 18h
Merged PRs (30d)
6

Description

### Checklist

- [X] I have searched for [similar issues](https://github.com/isl-org/Open3D/issues).
- [X] For Python issues, I have tested with the [latest development wheel](http://www.open3d.org/docs/latest/getting_started.html#development-version-pip).
- [X] I have checked the [release documentation](http://www.open3d.org/docs/release/) and the [latest documentation](http://www.open3d.org/docs/latest/) (for `master` branch).

### Describe the issue

First 10-20 frames recorded by RealSenseRecorder.cpp (examples) are completely/too dark when auto-exposure is enabled. This can be fixed by enabling recording immediately at start and then pausing the recording right after, something like
```
rs_config->enable_record_to_file(filename_);
pipe_->start(*rs_config_);
pipe_->get_active_profile()
.get_device()
.as()
.pause();
```
This probably overwrites any existing file even if nothing is recorded.

I tested this (and the fix) on Windows and RealSense L515.

### Steps to reproduce the bug

```python
Enable auto-exposure on RealSense camera and then run RealSenseRecorder.
```

### Error message

_No response_

### Expected behavior

_No response_

### Open3D, Python and System information

```markdown
- Operating system: Windows 10 64-bit
- Open3D version: v0.17.0
- System architecture: x86
- Is this a remote workstation?: no
- How did you install Open3D?: build from source
- Compiler version (if built from source): msvc17
```

### Additional information

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.