-
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 not working on Windows 11 / 2.50 #10258
Comments
I have confirmed that the hardware timestamps are working on Windows 11, so that can't be it. |
Hi @roelofvandijk If you suspect that the problem that you are experiencing began with SDK 2.43.0 then a logical starting point in investigating this case would be to install the 2.42.0 version of the full RealSense SDK for Windows to see whether your program works currently under that SDK version. https://github.com/IntelRealSense/librealsense/releases/tag/v2.42.0 The syncer changes that were introduced in 2,43.0 are quoted below in an extract from the 2.43.0 release notes. |
Hi @roelofvandijk Do you require further assistance with this case, please? Thanks! |
The current syncer behaviour seems like a regression that makes a common use-case (software-sync for frames from separate cameras) impossible. The syncer currently alternates between framesets of a single D415 unit, while the previous (and desired) behaviour was receiving single synchronized framesets that contained all frames from both D415 units. It would be great if Intel could reproduce this regression and - if confirmed - solve this in a next release. If I am doing something wrong, it would be great to know how to achieve software-based sync for two different D415 devices using the current version of the SDK (2.50). |
If you only need to capture a single frame from all attached D415 cameras simultaneously and export the frames as a PNG image then there is a C++ script shared by a RealSense user at #2219 (comment) that can do this and does not make use of syncer. Conceivably if you needed to capture multiple frames then you could just loop the script round continuously until it is stopped. |
Hi @roelofvandijk Do you require further assistance with this case, please? Thanks! |
Hello @MartyG-RealSense, it would be great if this is either confirmed as a regression with a forthcoming fix, or if you can confirm that this is the intended behavior for the syncer now (no support for multiple devices anymore). |
A number of changes have been made to syncer inbetween SDKs 2.48.0 and 2.50.0. 2.48.0 2.49.0 2.50 It is unlikely that multiple device support in syncer would deliberately be removed. If other RealSense users can identify a potential bug when using syncer with multiple cameras and resolve it, I would encourage them to submit the fix as a Pull Request so that it can be considered for merging into the SDK. https://github.com/IntelRealSense/librealsense/pulls |
Hi @roelofvandijk Do you require further assistance with this case, please? Thanks! |
Case closed due to no further comments received. |
Issue Description
After upgrading from 2.38 on Windows 10 to 2.50 on Windows 11, using a rs2::syncer to sync frames from 2 D415 cameras does not work anymore.
This comment contains a minimal example that seems to be broken now: #4158 (comment)
The syncer now returns a frameset only containing half of the expected frames.
This issue points towards a potential change that causes this: #9030
Is there any way to make this work using the current release, or should I revert to an older one?
The situation before: rs2::syncer yielded one frameset with 6 frames
The current situation: rs2::syncer yields framesets with 3 frames, one per device, interleaved.
The text was updated successfully, but these errors were encountered: