Ein Script schaltet im Hintergrund mit wget über den streamdev-server die Kanäle durch ...
Nun ruckelt mein LiveTV . Das Alles läuft auf einem NUC10i3. Es sollte also keine Frage der Rechenleistung sein ...
Für einen Ruckeltest reicht einfach wget -T3 localhost:3000/TS/1
Im Plugin Readme habe ich Folgendes gelesen:
ZitatCodeAlles anzeigen* Priorities: ------------- (Affected: 0.5.x and older) The server-side setting "Suspend behaviour" has been dropped in 0.6.0 in favour of priority based precedence. A priority of 0 and above means that clients have precedence. A negative priority gives precedence to local live TV on the server. So if "Suspend behaviour" was previously set to "Client may suspend" or "Never suspended", you will have to configure a negative priority. If the "Suspend behaviour" was set to "Always suspended", the default values should do. Configure the desired priorities for HTTP and IGMP Multicast streaming in the settings of streamdev-server. If you haven't updated all your streamdev-clients to at least 0.5.2, configure "Legacy Client Priority", too. In streamdev-client, you should set "Minimum Priority" to -99. Adjust "Live TV Priority" if necessary. .... Precedence between multiple clients and between client and server is controlled with priorities. For HTTP and IGMP Multicast, the priority is configured in streamdev-server's setup menu. A negative priority gives precedence to local live TV on the server. Zero and positive values give precedence to the client. The priority for VDR clients watching live TV is configured in the plugin setup of streamdev-client. For other client tasks (e.g. recording a client side timer) the same priority as on the client is used. With the parameter "Legacy client Priority" in streamdev-server's setup menu you can configure the priority for clients which cannot be configured to use negative priorities. It is used when an old client is detected an it requests priority "0". On the server, the main menu entry "Streamdev Connections" gives you a list of currently connected clients. Use the "red" key to terminate a connection. Note that depending on connection type and client, the client might re-connect sooner or later. The "blue" key in the server's main menu will suspend live TV on server. An image is displayed instead. This would allow a low priority client to switch to a different transponder. Enable "Client may suspend" in the server setup to allow VDR clients to suspend live TV remotely. In the server's setup there's also an option to suspend live TV when starting the server. The "auto" option will suspend live TV if there's no device with an MPEG decoder available which is typically the case on a headless server. NOTE: Precedence is mainly an issue on One-Card-Systems, since with multiple cards there is no need to switch transponders on the primary interface, if one of the other cards is idle (i.e. if it is not blocked by a recording). If all cards are in use (i.e. when something is recorded, or by multiple clients), this applies to Multiple-Card-Systems as well. If your client suffers from buffer underruns while watching live TV, you can configure buffering on the server side. Enter a reasonable value (e.g. 300ms) as "Live TV buffer delay (ms)" in the server setup. .... With "Maximum Priority" and "Minimum Priority" you can keep VDR from considering streamdev in certain cases. If for instance you have a streamdev client with its own DVB card, VDR might use streamdev for recording. If this is not what you want, you could set the maximum priority to 0. As recordings usually have a much higher priority (default 50), streamdev is now no longer used for recordings. The two parameters define the inclusive range of priorities for which streamdev will accept to tune. Setting the minimum priority to a higher value than the maximum, you will get two ranges: "up to maximum" and "minimum and above".
Trotz folgender Einstellungen in der setup.conf stoppt das LiveTV für einige Sekunden und ruckelt alle paar Sek. vor sich hin ...
liveTV beim Start pausieren: NEIN, LiveTV Puffer=1500, Server Priorities= -99
Lt. syslog läuft der Server mit "prio=high" Mar 30 18:15:29 BM2LTS-N64native-MCLI vdr: [3627] streamdev server thread started (pid=3596, tid=3627, prio=high)
streamdev-server.AllowSuspend = 1
streamdev-server.HideMenuEntry = 1
streamdev-server.HTTPBindIP = 10.75.25.22
streamdev-server.HTTPPriority = -99
streamdev-server.HTTPServerPort = 3000
streamdev-server.HTTPStreamType = 0
streamdev-server.IGMPBindIP = 10.75.25.22
streamdev-server.IGMPClientPort = 1234
streamdev-server.IGMPPriority = -99
streamdev-server.IGMPStreamType = 0
streamdev-server.LiveBufferMs = 1500
streamdev-server.LoopPrevention = 0
streamdev-server.MaxClients = 5
streamdev-server.ServerPort = 2004
streamdev-server.StartHTTPServer = 1
streamdev-server.StartIGMPServer = 0
streamdev-server.StartServer = 0
streamdev-server.StartSuspended = 0
streamdev-server.VTPBindIP = 10.75.25.22
streamdev-server.VTPPriority = -99
Alles anzeigen
Tja was soll ich sagen ... "mit Latein am Ende" ... ... oder "selber schuld"