Unfortunately it doesn’t read streamlink configuration files
It's not hard to add. In principle, I thought to make the main styreamlink settings (session options) in the form of a GUI accessible from the plugins menu ... But the parameters for specific add-on plugins can be passed element-wise to url.fragment and this does not require streamlink configuration files
Example for https://streamlink.github.io/plugins.html#bbciplayer add-on
Codehttp://localhost:port/https://www.bbc.co.uk/iplayer/episodes/p0frq6zd/champion?seriesId=p0frq798#bbciplayer-username=xxxx&bbciplayer-password=xxxxx&bbciplayer-hd=1
parameters passed to url.fragment are simply parsed and can be passed in proxy "HandleRequest" to the streamlink add-on plugin used to get a link to the video ... It's not difficult at all...
It is not about GUI and anything related to that. You missing the crucial info. Streamlink by design supports cli commands and configuration files and that is described in documentation. I will direct you to documentation as well https://streamlink.github.io/cli/config.html, but to the page where is described what I’m talking about. You don't need to pass parameters separately to each stream individual, that’s why streamlink supports configuration file for each plugin individual , or globally for all.
An example
In case of example e2 when you have root user boxes path looks like this
/home/root/.config/streamlink/config.bbciplayer
This path is home directory, and that why is included in settings backup in basically every image.
That just works with streamlinksrv since many years with accordance to documentation. I actually created my configuration files five years ago and they still works, because this format didn’t changed. Adding login, password and for example proxy to each link is unnecessary, when you can do that collectivity in a file.
Passing parameters also works with streamlinsrv and that can be used when specific streams need individual parameters becouse cli command can be handled by http HTTPServer. So those two methods were implemented. Don't see iprovment here as streamlinkproxy only one of those cases, but both are equqly important.
Practical Example.
You have 5 boxes, and want to use on them the same channel list prepared on PC editor. But due to device/streams limitations on service provider side you have to use separate account in each box. Then with passing parameters with url, you have to prepare 5 separate lists on PC editor, or create a script that will replace credentials each time the channel list is updated. With configuration files, no extra steps are necessary, you just sending list to those 5 boxes in the same time, and everything works because box have credentials stored seperatly.
QuoteI checked on OpenPli dev it works without problems .. it’s not at all clear why it wouldn’t work ...
I also don’t know, only if I had more detailed log, but
QuoteThe server code is so simple that I can't even imagine what to log there =)
Maybe you see now the problem.
QuoteThe difference is in more concise code =) and more or less correct implementation of chunked HTTP streaming -
Less correct, more correct, the jury is always on. Debate never ends, ultimately whats matter is if it works or if it doesn’t work. Anyway could you post any practical example when improvements can be observed ?