DVBserver + dvb-t bandwidth bug.

[gibman]

Quite easily reproduced.

 

Start an instance of DVBserver on PC1 sharing a DVB-t device. In myst case this is the Yakumo USB2 stick (with latest BDA drivers 1.0.0.42 and 5.9.19.0).

 

Here in denmark we currently have 4 (std. def.) channels in one mux.

 

Now on the client, use a clean install of either 3.2.6 or one of the latest beta's - it doesn't really matter, since the bug is present no matter what client version you use.

 

Ok, now are ready to rock and roll. Configure the client to use a dvb-t unicast connection.

Finally start up the client. Tune to a dvb-t channel. Now here comes the fun part. Check the network bandwidth by using the builtin task manager in windows.

(On my 54mbit wireless laptop it's around 10% for a 2.3 mbit broadcast) - This is fine and expected.

Now change to another channel on the same mux. Observe the bandwidth on the client - it has now doubled itself. Change to a third channel also in the same mux, now the bandwidth has been multiplied by 3. My wireless client is now coughing up blood, it simply can't keep up with the bandwidth requirements no more.

 

It seems like when changing channels the previous channels are still preserved within the stream sent by the dvbserver.

 

When the bandwidth has become too much I tried To remedy the problem by:

 

1) Change to a dvb-s channel and back to dvb-t again. No good, same deal.

2) Rebuild graph, same deal.

3) Close and re-open client, same deal

4) Hitting stop-start on the dvbserver + re-opening the client, this works!!!!

 

Maybe the problem lies with dvbserver ? Since toggling start stop does the trick.

I hope you fix this, as this is really bothersome.

Or maybe it lies within the client, not releasing channels, so the server thinks the client still needs them, like when you use mosaicview.

 

My only fix is currently ; use a 100mbit cable, since this can hold all 3 channels.

 

Regards Elo, your devoted dvbserver tester

[gibman]

I tried the new beta 3.4.9.136 and the problem has since then disappeared.

 

/Elo