Issues when stream or connection are not stable

[roberto-sartori-gl]

So, sometimes the stream, the internet connection, tiktok itself or the streamer internet connection are not stable. In this situation, the recorded file is very small as the recording ends at the first connectivity issue - or if automatic recording is used, a lot of small files are generated.

I think this is the case even when the streamer 'pauses' the live (but I couldn't confirm this).

Various recording tools (even fork of this one!) 'solved' the problem concatenating all the files after the live actually ends. Is there any plan to include something like this?

There are also various ffmpeg options that could be used (reconnect_streamed, reconnect_delay_max) which may be useful.

[Michele0303]

Hi Roberto, to solve the problem, I was thinking of exploring some options in ffmpeg, like reconnect_streamed, etc.

[Michele0303]

Fixed in: https://github.com/Michele0303/tiktok-live-recorder/releases/tag/5.5

[roberto-sartori-gl]

@Michele0303 Thanks, I'll try it!

[roberto-sartori-gl]

@Michele0303 I don't know if it is related to this, but the issue appeared after this change so. I was recording a ~2hours live, and it was working pretty well: I was recording the same live with the previous release and with the new one, and the previous one was creating multiple files while the new one was not.

At a certain point though, the new release failed with the error:
[!] ('Connection broken: IncompleteRead(0 bytes read, 2 more expected)', IncompleteRead(0 bytes read, 2 more expected))

After this, the file was damaged: it can probably be repaired because the video can be played but it does not have a lenght (VLC, media player classic), so I cannot go back and forward in the video. This is not a big issue for now, I wanted to report the above error though.

[Michele0303]

Are you using version 5.7?

[roberto-sartori-gl]

Are you using version 5.7?

I was using 5.5 because 5.7 was not out when I tried that :)
I'm trying now 5.7, I'll let you know if the issue happens again!

[roberto-sartori-gl]

@Michele0303 with 5.7, I saw some of these errors:
[!] 2024-12-28 18:55:35 - [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:2578)

I have a damaged file for each of these lines with that same 'modified date' as the log (e.g. 18:55:35) (like yesterday, the file is there, playable, but it does not report a lenght so I can't move forward-backward with any player).

Looking at journalctl, I never had this line before today so versions < 5.4 probably were cutting the file at this point. I was using the options 'ffmpeg' and 'auto-covert' (or whatever it was) so maybe I did not saw the files damaged because they were converted on the fly. These options do not exist anymore so the resulting file is damaged.

To add a note, manually running 'ffmpeg -i damaged_file.flv -c copy restored_file.mp4' generates a working file.

edit: I'm going to try 5.8 that may fix the problem, as it catches more exceptions now.

[Michele0303]

If that ffmpeg command solves the problem, then version 5.8 will work correctly