Media Server Web interface feature request

[Bart Zorn]

Hello,

 

Currently, the Status windows in the DMS web server only shows what a tuner is doing while DMS is recording something. When it is serving a channel to a client, you only can see that it is doing something, but not what it is doing.

 

Would it be possible to show what a tuner is doing and to which client it is serving?

 

TIA,

 

Bart

 

[Griga]

vor 19 Stunden schrieb Bart Zorn:

Would it be possible to show what a tuner is doing and to which client it is serving?

 

It would make sense to show which tuner is used for which client. But it's not that easy. It would require a re-design of the status page of the desktop and mobile web interface, because both are supplied by the same code.

 

There is already a client list on the status page, as you might have noticed, but without showing which one is associated with which tuner. It also covers clients that are not using a tuner, but are reading a file. Where to put them after live stream clients have been moved to the tuner table?

 

Additionally it has to be considered that the DMS as Sat>IP server cannot display the channel, because it doesn't know it (it just delivers some data requested by the client without a channel name as label). So only the frequency could be displayed in this case.

 

ATM I can see no simple and consistent solution for what you want.

 

[Bart Zorn]

OK, thanks.

 

Please keep it on the list for (non urgent) future improvements!

 

Bart

 

[Griga]

There is another obstacle: The Web Server does not know which tuner is associated with clients that get a transcoded stream.

 

The original request is transformed into a FFmpeg command line, inluding an URL allowing FFmpeg to get appropriate input from the Live Stream Server. After being launched, FFmpeg creates a  Live Stream request, which finally leads to tuner allocation. But there is no trackable link between the original and the follow-up request. It would be necessary to add a kind of ID to the URL used by FFmpeg for getting input, in order to find out which Live Stream request belongs to which original request.