Replies: 2 comments 2 replies
-
|
Not sure what heppens: if you have 2 receiving devices: the coordinator is determined from the first returned confirmation. The confirmations from the other device will be ignored. If you are planning to have multiple receivers, you might cosider to switch the confirmations off and just throttle the sending speed, as proposed in one of my anwers above. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Never thought about the impacts. At least you would need to implement some mixing logic on the receiver side if you want to receive audio from multiple sources at the same time.. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Yesterday i tried, to have 2 devices sending audio to a 3th device. To see what would happen.
And i found something other then i expected.
The first device started nicely to send as expected. The second on locked down which i did not expected.
That the device locked with this version (1.2.1) i understand. I need to test it with the latest (dev) version to see if it now not stay blocked.
My hypothese is that device 1 does not give room for other device to send there packages currently.
ATM. there is a solution to wait when the package could be send, but there is no delay when it go's well, or is there something that i have overlooked?
Beta Was this translation helpful? Give feedback.
All reactions