If you include "pids=all" in the URI then all the time the streaming is good, but if you use instead some "pids=" with a list of low biterate tables then you show some discontinuities and/or stops in the streaming. Installed as a native windows service, the Media Server is capable to start the computer from standby or hibernate. It takes care of the recordings, as well as for streaming jobs and offers a modern and comfortable web interface. It can start the machine from Hibernate/Standby for recordings without needing DVB Task. The DVBViewer Media Server is a chargeable enhancement for the DVBViewer Pro. The DVBViewer Recording Service is a native Windows service. Addition means it belongs to the DVBViewer software family and is meant to be used only be customers of the DVBViewer Pro. In this case the client don't receive correct packets.įor testing I recommend this setup: Download TSReader Lite and use the HTTP interface (don't forget to check "Don't check for HTML5 streams") to receive the TS using the HTTP API of the minisatip. DVBViewer Recording Service is an addition for the DVBViewer Pro. If you put filters for only receive some tables (PAT, PMT, etc.) then the result is an irregular streaming. The troubles seems to be with output streams with low bitrates. I explain more about this issue: The current code seems to use some type of timers for sending the TS (I don't really check this, It's an assumption). The main problem is a problem with LOW BITRATE STREAMS. However, the scanning process has several problems using minisatip. For example, if you do the scanning process with another device (BDA device) and then enable only the minisatip as input, then you can receive the channels.
Related to the problem with DVBViewer Pro.
0 kommentar(er)
