#54 will handle stream/clear messages internally, but the library currently has no mechanism to clear the library user's buffers, so stale audio will still play. Since these buffers are out of our control, this is a harder mechanism to implement.
My current thought process is to have a stream/clear signal get sent via the listener interface. Clients are then responsible for calling a "I've cleared the buffers, proceed" method so sendspin-cpp knows it should start sending audio again.
#54 will handle
stream/clearmessages internally, but the library currently has no mechanism to clear the library user's buffers, so stale audio will still play. Since these buffers are out of our control, this is a harder mechanism to implement.My current thought process is to have a
stream/clearsignal get sent via the listener interface. Clients are then responsible for calling a "I've cleared the buffers, proceed" method so sendspin-cpp knows it should start sending audio again.