Takes more upstream bandwidth when restreaming single source

[barlowd55]

I am using your code for restreaming sources to clients.

I just noticed a bug in the app. When I am restreaming a single source to more than 1 client, the app consumes the same upstream bandwidth for each client.

For example:

1 source, 1 client: 1 upstream bandwidth, 1 downstream bandwidth
1 source, 2 client: 2 upstream bandwidth, 2 downstream bandwidth

while, the downstream bandwidth is understandable, the upstream bandwidth should only be consumed once for restreaming a single source, that is, 1 channel restream > to n users.

The weird part is that the source only shows a single connection from the restreaming app, while the nload shows that every client is consuming the same upstream and downstream bandwidth.

Let me know if you can fix this issue. Happy to donate.

[shaunschembri]

Thanks for opening the issue.

This was tested using a single client stream a single service and currently its not possible to re-utlize the same stream to multiple clients if the same stream is requested more then once. Definitaly and improvment that can me made but might require some redesign as the code was always inteaded to support a single client.

[barlowd55]

Thanks for the reply and I appreciate your application. I understood the reason behind the current implementation, but I cannot seem to figure out how the source only detects as a single connection even though it is using multiple connections for each clients.
Maybe it is possible to download the source first to the local hard disk before restreaming.