VLC m3u8 stream recording stops at timestamp rollover
So just to start off, I have created 2 posts about this bug on the forums, but as I was pointed to this site, I had to realize, I had been wasting my time on the other forum for an entire month, just to be redirected here. So thank you for keeping 2 forums up videolan, one of which you guys don't even read, I will waste your time too as much as I can, just so you can feel the care.
I will link the forum post that I have discussed this bug with a kind soul on the forum, there I have the bug described properly. LINK TO VLC FORUM #1
I have uploaded the VLC log file with descrpitiveness of 2 to WeTransfer (LINK), because pastebin and this website doesn't allow files larger than 10MB for some goddamn unknown reason. (Link will expire in 6 days tho), and my VLCRC file HERE
But, because I'm hungarian, and to see how generous we are, I will also type out again the tldr of the bug.
I wanted to record an m3u8 stream, and record it to MP4 with ctrl+S, I set up the output file, I checkmarked display locally, I selected convert to a custom profile (the profile is MP4, but I checkmarked original video and audio feed in that settings), and I checkmarked display all stream feed, and clicked the stream button. Every other setting is kept at default. Then, stream is set up in a way that even though both the stream and I am in Hungary, but stream is receiving a timestamp of 2 hours ahead of my time. So, 22:00 real time, is for the stream 00:00. And when 00:00 hits, the recording stops, it repeats the last packet it received 3 times, then continues to only play the stream, and not record it. In the error log, when 00:00 hits, this error message pops up.
main error: cannot add a new stream (unsupported while muxing to this format). You can try increasing sout-mux-caching value duplicate debug: - failed for output 0
However I would advise you to read the surrounding bit of the log in order to grasp the true story, because it's just a snippet of the event that occured at 00:00, and also, the original forum post, because all the detail is there, and not here.
So I am looking forward to your answers and fixes, devs.