-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rs2::syncer
T265 fails to synchronize fisheye streams (since v2.43.0)
#9030
Comments
Any updates !! |
Found a fix: diff --git a/src/proc/syncer-processing-block.cpp b/src/proc/syncer-processing-block.cpp
index 34ebcb492..020b88eb7 100644
--- a/src/proc/syncer-processing-block.cpp
+++ b/src/proc/syncer-processing-block.cpp
@@ -11,7 +11,7 @@
namespace librealsense
{
syncer_process_unit::syncer_process_unit(std::initializer_list< bool_option::ptr > enable_opts, bool log)
- : processing_block("syncer"), _matcher((new composite_identity_matcher({})))
+ : processing_block("syncer"), _matcher((new timestamp_composite_matcher({})))
, _enable_opts(enable_opts.begin(), enable_opts.end())
{
_matcher->set_callback( [this]( frame_holder f, syncronization_environment env ) { It seems that the matcher type was EDIT: Patch here https://gist.github.com/matlabbe/8d66bbf3c690aa689c73da1a8708306b |
the above solution is working with T265 and L515 ...thanx @matlabbe |
I am also facing a similar problem, a syncer that used to sync all 8 frames from 2 D415s perfectly on 2.38, but does not anymore on 2.50. |
@roelofvandijk did you try |
Issue Description
This issue is related to this issue introlab/rtabmap#716 where
rs2:syncer
API cannot synchronize T265 frames correctly with realsense SDK >=v2.43.0
I tried to make a minimal example to reproduce the problem using the
rs2::syncer
api. Here is a modified version of pose-and-image example:Expected output (v2.42.0)
Note that the 2 frames are synchronized.
Current master version (d5e775b):
The current master version of
rs2::syncer
cannot synchronize T265 images correctly, returning randomly either the image of the first or second camera. The problem seems appeared since this commit: a49d873 (@aangerma)The text was updated successfully, but these errors were encountered: