You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm submitting a ...
[ ] bug report
[X] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project
Summary
Would like to see overloaded constructors to allow for passing in an existing stream, as well as a constructor that allows passing in a device ID. Currently, if Chime is using device A and device B is the default, symbl-chime-adapter will listen on device B which Chime is listening on device A. This is also part of the problem with releasing devices -- Chime releases the device it is using, but Symbl does not release its device. If I were to just pass in the stream, Chime killing its device means Symbl wouldn't need to worry about it.
Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
The text was updated successfully, but these errors were encountered:
I'm submitting a ...
[ ] bug report
[X] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project
Summary
Would like to see overloaded constructors to allow for passing in an existing stream, as well as a constructor that allows passing in a device ID. Currently, if Chime is using device A and device B is the default, symbl-chime-adapter will listen on device B which Chime is listening on device A. This is also part of the problem with releasing devices -- Chime releases the device it is using, but Symbl does not release its device. If I were to just pass in the stream, Chime killing its device means Symbl wouldn't need to worry about it.
Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
The text was updated successfully, but these errors were encountered: