Skip to content

Syncer now produces frameset - always - #8573

Merged
maloel merged 2 commits into
realsenseai:developmentfrom
aangerma:playback_bug
Mar 14, 2021
Merged

Syncer now produces frameset - always#8573
maloel merged 2 commits into
realsenseai:developmentfrom
aangerma:playback_bug

Conversation

@aangerma

@aangerma aangerma commented Mar 14, 2021

Copy link
Copy Markdown
Contributor

Solves the playback with syncer bug added on #8378 and pipeline with single stream bug:
The old code expected syncer output to always be a frameset.

Comment thread src/proc/syncer-processing-block.cpp Outdated
_matcher = dev->create_matcher(frame);
frame_holder f;
{
std::lock_guard< std::mutex > lock(_callback_mutex);

@maloel maloel Mar 14, 2021

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happened to:

            // Another thread has the lock, meaning will get into the following loop and dequeue all
            // the frames. So there's nothing for us to do...
            std::unique_lock< std::mutex > lock(_callback_mutex, std::try_to_lock);
            if (!lock.owns_lock())
                return;

@maloel maloel changed the title Syncer will always create composite frames even if the frame is single Syncer now produces frameset - always Mar 14, 2021
@maloel
maloel merged commit 6e01478 into realsenseai:development Mar 14, 2021
maloel added a commit that referenced this pull request Mar 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants