Skip to content
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

startStreaming() does not send frames to processFrame() after a call to stopStreaming() #65

Closed
ftc14140 opened this issue Feb 23, 2023 · 2 comments

Comments

@ftc14140
Copy link

After a call to stopStreaming(), a subsequent call to startStreaming() on the same webcam does not result in further frames being sent to the attached pipeline. Logs are attached for the events after the initial call to start, the call to stop, and the subsequent call to (re)start.

start.txt
stop.txt
restart.txt

@Windwoes
Copy link
Member

Wow, how has this bug not been found before now? It's specific to webcams, and usually I just test with the internal camera so I guess that's how I didn't notice it, but surprised nobody else has.

Fixed in 4d050a5

Will turn the release crank for a new point release soon.

@Windwoes
Copy link
Member

Fixed in v1.6.1

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

No branches or pull requests

2 participants