>>> I download from only one site in FLV, and that is starrranch.org/blog. That is because it is the only site that still uses Flash. The downloads finalise instantly, and sometimes I've forgotten to stop them at ~20 hours long but they're ready instantly. I do not choose to use FLV, it chooses itself.
RTMP or direct FLV streams normally stream audio and video together and so dont need to be combined and their video and audio codecs will be compatible so no muxing is required. You can switch on through the settings to automatically fix live streams and add a duration. This will result in Muxing as a status in the UI. Again this can take sometime depending on the size of the captured file, but does not involved codec conversion.
>>> That's how YouTube streams come down, I don't use any setting to specify a format. YouTube streams on Monitor automatically stop themselves at 6 hours - I have set the Check Interval @ 15 seconds so as not to miss activity between the 6-hour sessions, but the Monitor does not pick up the stream until Jaksta has finished with the stopped stream, which, these days, can easily take 15 minutes. That can be a disaster (in the world we're talking about!).
Youtube stops the stream after 6 hours, not JMR. JMR is intended for personal use for a bit of fun and is not designed or intended to be used for commercial or mission critical tasks.
As I have said a 6 hour recording will be quite large and muxing can take a while. The length of time you are reporting is not unheard of depending on the codecs being muxed together and their size.
>>> A short while ago I manually stopped a YouTube stream @ 4h37m and watched and timed it. It was Cancelling for 14 minutes - it then changed to Tagging/Complete in very quick succession. It did not Mux at all. The completed file is as it should be.
If you cancel - it just displays cancelling in the UI but it will be muxing if the audio and video streams require muxing so that a usable file is provided. You can see this in the Progress Log.
>>> Almost at the same time I noticed another YouTube stream stop itself and it was reporting "muxing ... %" - why some have to mux and some not is another mystery... Well, the one I manually stopped that spent ages cancelling was 720p and the muxing one was 1080p, if that makes any difference. Both had video with sound.
If a stream has finished then it displays muxing in the UI.
>>> Therefore, in the bold sentence, I'm asking that the Monitor will re-pick-up a stream after it has been stopped without waiting for the stopped stream to be finalised, by which I mean "Complete".
I can have a look at that for you. Not sure if it will be doable or when it might be implemented if it is.
>>> There is no time "suitable" for split times to be set. I need to monitor 24/7 and that used to be achievable with minimal gaps between the 6-hour "sessions".
JMR is intended for personal use for a bit of fun and is not designed or intended to be used for commercial or mission critical tasks. If you split every hour or less you will be muxing much less data and therefore it will take much less time and any perceived breaks will most likely be smaller.
>>> I wondered if my disk could be too full but it has 340GB free of 730GB (it's the data partition of a 1TB SSD), I've been using the same hardware for over 2 years and was using less powerful hardware previously with no problems - except when I reported "muxing ad infinitum" in 2017.
Muxing is CPU intensive for the most part.
From CRS @ 12 Aug 2020 13:08