Muxing is the process of combining captured audio and video media streams it to a container format (ts, mpg, mp4, mkv etc) that can be played back.
It can take a long time depending on the file size and codecs used by those streams. It can be CPU and disk intensive. Disk intensive if it is reading and writing very large files. CPU intensive if it is having to convert codecs from one format to another, to meet the container requirement. Having multiple muxing happening at the same time will cause even more spikes in CPU and disk activity obviously.
The type of muxing performed, is based on the protocol that the site streams in. You can see the protocol being used in the captures progress log. Select the entry and then Menu > Properties > Progress log.
Muxing settings can be changed for some protocols via Settings > Internet Downloads > Advanced and selecting the appropriate protocols tab.
I distribute the excellent open source ffmepg with JMR and in most cases this is what is used to perform muxing.
To speed things up, you can try.
1. Capturing smaller streams. You can do this using the split functionality in the monitor, or changing the requested resolution.
2. Identify the protocol being used by the site being captured (look in the progress logs) and see if there are settings that you can adjust in the advanced settings. For HLS streams for example, muxing to ts format (RAW using HLSD) or switching of mpg format when using ffmpeg will be much quicker than muxing to MPG, MP4 or MKV. Settings > Internet Downloads > Advanced > HLS tab.
3. If using ffmpeg to mux, then you could try different versions of ffmpeg from https://ffmpeg.org/download.html#build-windows. Note that ffmpeg changes constantly as it is a developer driven project. Ie that dont really have official releases.
4. If monitoring a large number distribute them over several machines. Ie you have two machines and want to monitor 20, monitor 10 on one and 10 on the other.
From CRS @ 24 Mar 2021 08:03