Best Input stream type

[Stevan90]

Hello, I using Cesbo Astra for streaming, Flussonic for GPU transcoding, and XC UI portal.

I install trial Midnight Streamer last night because I want to use it instead Flussonic and XC UI if work same or better. I work at night when users sleep: Turn off Flussonic, put new SSD for system and HDD for TV Archive, install MS, migrage DB from XC UI. The last step is manual update source streams because is Flussonic offline and need to use streams from Cesbo Astra. I try to update two channels with http streams but lines won't start. Then I try to update two channels with hls streams but linest won't start. I test http and hls streams in VLC, and streams is good. I don't know how to troubleshoot streaming problem? I returned old SSD on transcoding hardware and start Flussonic. I plan to try again to set up MS tonight.

What si best input stream type for MS? I can create any tupe of stream (including multicast).

Sorry for bad English.

[midnightstreamer]

Hello

MS opens literally every type of stream since it's ffmpeg based.

If you set your streams as Proxy, the source MUST be MPEG-TS. HLS doesn't work with Proxy.

For troubleshooting stream issues your best best is to check the stream log. Log icon on the top-right of the stream info-box.

There you can check for forbidden or 404 not found errors.

 

[Stevan90]

I found log in /streams directory. I missed some packages need for ffmpeg start. I resolve problem.

Ok i understand it opens every type of stream, but what is best practice? Let's say if a problem occurs with input stream, and input stream go back online. Whether a mw faster handle this problem with some type of input stream?

[midnightstreamer]

There is no need to check for log error files in /streams. You can directly click the log icon inside the stream settings in the panel.

All type of input streams are handled the same way.

MS has an anti-drop function. If your source fails it will try to recover it.

Try to manually kill your ffmpeg instances:

killall -9 ffmpeg

and immediately after check whenever they are started again:

ps -A | grep ffmpeg

you will see ffmpeg is started immediately after an ffmpeg exit, usually caused by the source stream not being available for whatever reason, poor network, source down etc.

 

If the source is down for more than 30s and you set just one stream source (no backups) you have 3 scenarios.

If you set "Show Monoscope / Blank Screen on Stream Interruption" to Monoscope, a monoscope will be shown until the source comes back online.

If you set it to Blank, a black screen will be shown until the source comes back online.

If you set it to Don't Show, the last good stream segment will be repeated until the source comes back online.

So clients will not be disconnected if source goes down even for prolonged periods.

 

The monoscope and blank videos are h264, aac encoded and you can find them in:

/home/midnightstreamer/iptv_midnight_streamer/data

 

If you do set stream backups you can choose if they are pulled simultaneously or only if the previous stream fails.

If they are pulled simultaneously the stream will quickly switch to the working one since it's already active so there are zero possibilities of downtime.

 

If they are not pulled simultaneously, the backups will be probed sequentially until a working backup is found.

If you set "Use Priority in Backup Sources" to Yes, the system will always check if the main stream is online again and it will switch to it if it is.

 

[midnightstreamer]

All the previous is valid for normal, no Proxy streams.