it happened again.

[youforgetsomething]

2 hours stream , this is the result .
v5.8
command line args used = -mode automatic
, in addition when new connection happens , the user goes offline or whatever reason , the tktok-live-recorder hangs , freezing , like it's writing a record but it do nothing.

[RealityQuizzicality]

2 hours stream , this is the result . v5.8 command line args used = -mode automatic , in addition when new connection happens , the user goes offline or whatever reason , the tktok-live-recorder hangs , freezing , like it's writing a record but it do nothing.

with automatic mode i use -duration 120
that way only some of the clips are broken and not the entire Live

[youforgetsomething]

2 hours stream , this is the result . v5.8 command line args used = -mode automatic , in addition when new connection happens , the user goes offline or whatever reason , the tktok-live-recorder hangs , freezing , like it's writing a record but it do nothing.

with automatic mode i use -duration 120 that way only some of the clips are broken and not the entire Live

this not a solution , this make you lose less parts as possible , but the problem still exists .
it's video issue ( conversion , incode , decode ) idk.

[youforgetsomething]

this what tiktok live i have recorded .

[youforgetsomething]

the only method that prevented destroyed video is just with some old version with use of encoding the recorded file after finish record , but it was take heavy much time (ultra slow like hours) and high cpu use , imagine that with old H.W ...

[youforgetsomething]

using "-duration" trying to save parts and lose not all stream , is 90% of time hangs for some reason , and when splitting the record it just freeze like connection issue , ignoring the live stream once is this happen , the app act like recording but it do nothing.

[youforgetsomething]

another lost live

[roberto-sartori-gl]

another lost live

The issue is there, I have it too, but it's not like reposting it multiple times a day will make it better :)

[yann01240]

We noticed that this issue seems to occur specifically when a match is started on TikTok live. It might be related to the video stream or a conflict with another feature active during these sessions.

[roberto-sartori-gl]

I have the issues even during 'nornal one user streaming', though it seems that certain users are more affected.

My idea is that there are packed drops and ffmpeg (o python requests) cannot fully recover from those for some reason. No idea on how to debug this :)

[yann01240]

For my part, it happens systematically at the start of a match. I tested it with several live streams for the same person, and it works well every time. But as soon as a match starts, the image gets corrupted, and only the sound works.

[yann01240]

the only method that prevented destroyed video is just with some old version with use of encoding the recorded file after finish record , but it was take heavy much time (ultra slow like hours) and high cpu use , imagine that with old H.W ...

What version does it work with?

[NotSooFriendly]

2 hours stream , this is the result . v5.8 command line args used = -mode automatic , in addition when new connection happens , the user goes offline or whatever reason , the tktok-live-recorder hangs , freezing , like it's writing a record but it do nothing.

with automatic mode i use -duration 120 that way only some of the clips are broken and not the entire Live

this not a solution , this make you lose less parts as possible , but the problem still exists .

it's video issue ( conversion , incode , decode ) idk.

This is the solution. Recording in small segments helps prevent data loss and also cuts down on processing when encoding/transcribing, you can make a very simple function to stitch the segments back together.

To say that is not the solution is a bit silly when most people have a 2 hour long video that was compiled into a single file using segments, and you have nothing saved as you have a singular corrupted 2 hour long video recording.

This is a very basic theme across code and digital devices in general. Collect data in small amounts and then ensure there is a backup and the compile a finished product when you know the data is good.

The issue you are having could be when the video is being encoded, if one small part of the file gets corrupted then it will all become corrupted. If you are trying to process a 2 hour long video then you have a significantly larger chance of something going wrong...

[youforgetsomething]

assume it's a filter!
or caused by damn filters.

[manumurcia]

2 hours stream , this is the result . v5.8 command line args used = -mode automatic , in addition when new connection happens , the user goes offline or whatever reason , the tktok-live-recorder hangs , freezing , like it's writing a record but it do nothing.

with automatic mode i use -duration 120 that way only some of the clips are broken and not the entire Live

this not a solution , this make you lose less parts as possible , but the problem still exists .
it's video issue ( conversion , incode , decode ) idk.

This is the solution. Recording in small segments helps prevent data loss and also cuts down on processing when encoding/transcribing, you can make a very simple function to stitch the segments back together.

To say that is not the solution is a bit silly when most people have a 2 hour long video that was compiled into a single file using segments, and you have nothing saved as you have a singular corrupted 2 hour long video recording.

This is a very basic theme across code and digital devices in general. Collect data in small amounts and then ensure there is a backup and the compile a finished product when you know the data is good.

The issue you are having could be when the video is being encoded, if one small part of the file gets corrupted then it will all become corrupted. If you are trying to process a 2 hour long video then you have a significantly larger chance of something going wrong...

Is not a solution if you say that but dont help or explain how to do it :/.

Can you tell us that "very simple function" to stick fragments together? thx

Anyway, i tried to do fragments of 1min, 5min and 10min, not all the fragments are corrupted but when it happens its not corrupted the entire fragment, its just like 30 seconds to 50 seconds corrupted.

And no is not match event related, because i watch the Live with another account and never did a match event when had the corruption.

[NotSooFriendly]

2 hours stream , this is the result . v5.8 command line args used = -mode automatic , in addition when new connection happens , the user goes offline or whatever reason , the tktok-live-recorder hangs , freezing , like it's writing a record but it do nothing.

with automatic mode i use -duration 120 that way only some of the clips are broken and not the entire Live

this not a solution , this make you lose less parts as possible , but the problem still exists .
it's video issue ( conversion , incode , decode ) idk.

This is the solution. Recording in small segments helps prevent data loss and also cuts down on processing when encoding/transcribing, you can make a very simple function to stitch the segments back together.

To say that is not the solution is a bit silly when most people have a 2 hour long video that was compiled into a single file using segments, and you have nothing saved as you have a singular corrupted 2 hour long video recording.

This is a very basic theme across code and digital devices in general. Collect data in small amounts and then ensure there is a backup and the compile a finished product when you know the data is good.

The issue you are having could be when the video is being encoded, if one small part of the file gets corrupted then it will all become corrupted. If you are trying to process a 2 hour long video then you have a significantly larger chance of something going wrong...

Is not a solution if you say that but dont help or explain how to do it :/.

Can you tell us that "very simple function" to stick fragments together? thx

Anyway, i tried to do fragments of 1min, 5min and 10min, not all the fragments are corrupted but when it happens its not corrupted the entire fragment, its just like 30 seconds to 50 seconds corrupted.

And no is not match event related, because i watch the Live with another account and never did a match event when had the corruption.

I mean you may have to think outside of the box and add custom scripts, some logic and god forbid a little independent research, I really love to help people but this reply of "its not a solution unless you explain how to do it" eeks me.

It really is a simple solution if you're not just used to cloning people's repos and typing run.

I could share my project with you as I offered to do with another dude on a different thread.

It records multiple live streams simultaneously whilst connected to web-sockets, saving, logging, stitching video segments, transcribing live audio, uploading it to endpoints with further backend processing the list of functions go on.

The point I'm getting at here is this repo is a very awesome tool, to be integrated into a bigger project. It's not a final product you just clone and then type in a username and expect it to not have bugs, it's still in development itself.

Please in the future don't just assume someone should tell you how to do something, I like to encourage people to grow their knowledge and me telling you doesn't do that. ✌🏻

[manumurcia]

2 hours stream , this is the result . v5.8 command line args used = -mode automatic , in addition when new connection happens , the user goes offline or whatever reason , the tktok-live-recorder hangs , freezing , like it's writing a record but it do nothing.

with automatic mode i use -duration 120 that way only some of the clips are broken and not the entire Live

this not a solution , this make you lose less parts as possible , but the problem still exists .
it's video issue ( conversion , incode , decode ) idk.

This is the solution. Recording in small segments helps prevent data loss and also cuts down on processing when encoding/transcribing, you can make a very simple function to stitch the segments back together.
To say that is not the solution is a bit silly when most people have a 2 hour long video that was compiled into a single file using segments, and you have nothing saved as you have a singular corrupted 2 hour long video recording.
This is a very basic theme across code and digital devices in general. Collect data in small amounts and then ensure there is a backup and the compile a finished product when you know the data is good.
The issue you are having could be when the video is being encoded, if one small part of the file gets corrupted then it will all become corrupted. If you are trying to process a 2 hour long video then you have a significantly larger chance of something going wrong...

Is not a solution if you say that but dont help or explain how to do it :/.
Can you tell us that "very simple function" to stick fragments together? thx
Anyway, i tried to do fragments of 1min, 5min and 10min, not all the fragments are corrupted but when it happens its not corrupted the entire fragment, its just like 30 seconds to 50 seconds corrupted.
And no is not match event related, because i watch the Live with another account and never did a match event when had the corruption.

I mean you may have to think outside of the box and add custom scripts, some logic and god forbid a little independent research, I really love to help people but this reply of "its not a solution unless you explain how to do it" eeks me.

It really is a simple solution if you're not just used to cloning people's repos and typing run.

I could share my project with you as I offered to do with another dude on a different thread.

It records multiple live streams simultaneously whilst connected to web-sockets, saving, logging, stitching video segments, transcribing live audio, uploading it to endpoints with further backend processing the list of functions go on.

The point I'm getting at here is this repo is a very awesome tool, to be integrated into a bigger project. It's not a final product you just clone and then type in a username and expect it to not have bugs, it's still in development itself.

Please in the future don't just assume someone should tell you how to do something, I like to encourage people to grow their knowledge and me telling you doesn't do that. ✌🏻

But a big question, when you reading a text, you know how to read the whole text, or you only read 2 words that you like?

Because i said more than just asking for how to merge that files, even not being the solution because it will merge corrupted fragments anyway.

I will help you to read the whole text, so dont worry.

You posted this:
"This is the solution. Recording in small segments helps prevent data loss and also cuts down on processing when encoding/transcribing, you can make a very simple function to stitch the segments back together."

And i answered you a reply:
"Anyway, i tried to do fragments of 1min, 5min and 10min, not all the fragments are corrupted but when it happens its not corrupted the entire fragment, its just like 30 seconds to 50 seconds corrupted."

So as you can see that you said, is NOT the solution, because the fragments still corrupting even if they last less than 1 minute.

In the past i used other Tiktok tools from github too, to record more than 10 lives simultaneously with no errors but now its not working anymore, so it maybe is just incorrect codec issue or something.

But ok, you can keep writing a bible with your NOT solution.

Thanks lol

[NotSooFriendly]

2 hours stream , this is the result . v5.8 command line args used = -mode automatic , in addition when new connection happens , the user goes offline or whatever reason , the tktok-live-recorder hangs , freezing , like it's writing a record but it do nothing.

with automatic mode i use -duration 120 that way only some of the clips are broken and not the entire Live

this not a solution , this make you lose less parts as possible , but the problem still exists .
it's video issue ( conversion , incode , decode ) idk.

This is the solution. Recording in small segments helps prevent data loss and also cuts down on processing when encoding/transcribing, you can make a very simple function to stitch the segments back together.
To say that is not the solution is a bit silly when most people have a 2 hour long video that was compiled into a single file using segments, and you have nothing saved as you have a singular corrupted 2 hour long video recording.
This is a very basic theme across code and digital devices in general. Collect data in small amounts and then ensure there is a backup and the compile a finished product when you know the data is good.
The issue you are having could be when the video is being encoded, if one small part of the file gets corrupted then it will all become corrupted. If you are trying to process a 2 hour long video then you have a significantly larger chance of something going wrong...

Is not a solution if you say that but dont help or explain how to do it :/.
Can you tell us that "very simple function" to stick fragments together? thx
Anyway, i tried to do fragments of 1min, 5min and 10min, not all the fragments are corrupted but when it happens its not corrupted the entire fragment, its just like 30 seconds to 50 seconds corrupted.
And no is not match event related, because i watch the Live with another account and never did a match event when had the corruption.

I mean you may have to think outside of the box and add custom scripts, some logic and god forbid a little independent research, I really love to help people but this reply of "its not a solution unless you explain how to do it" eeks me.

It really is a simple solution if you're not just used to cloning people's repos and typing run.

I could share my project with you as I offered to do with another dude on a different thread.

It records multiple live streams simultaneously whilst connected to web-sockets, saving, logging, stitching video segments, transcribing live audio, uploading it to endpoints with further backend processing the list of functions go on.

The point I'm getting at here is this repo is a very awesome tool, to be integrated into a bigger project. It's not a final product you just clone and then type in a username and expect it to not have bugs, it's still in development itself.

Please in the future don't just assume someone should tell you how to do something, I like to encourage people to grow their knowledge and me telling you doesn't do that. ✌🏻

But a big question, when you reading a text, you know how to read the whole text, or you only read 2 words that you like?

Because i said more than just asking for how to merge that files, even not being the solution because it will merge corrupted fragments anyway.

I will help you to read the whole text, so dont worry.

You posted this:
"This is the solution. Recording in small segments helps prevent data loss and also cuts down on processing when encoding/transcribing, you can make a very simple function to stitch the segments back together."

And i answered you a reply:
"Anyway, i tried to do fragments of 1min, 5min and 10min, not all the fragments are corrupted but when it happens its not corrupted the entire fragment, its just like 30 seconds to 50 seconds corrupted."

So as you can see that you said, is NOT the solution, because the fragments still corrupting even if they last less than 1 minute.

In the past i used other Tiktok tools from github too, to record more than 10 lives simultaneously with no errors but now its not working anymore, so it maybe is just incorrect codec issue or something.

But ok, you can keep writing a bible with your NOT solution.

Thanks lol

Well in that case it must be a skill issue, because I could produce as much footage as you request with no corruption, encoded, compressed, transcribed, uploaded to a server, served back to you as a static file or stream to be watched on any device.

"Is not a solution if you say that but dont help or explain how to do it :/."

Here's your explanation seeing as you can't do it yourself.

Read through the documentation provided.

ffmpeg is used by the repo to record your request already. So it may be a good place to start.

Make a simple timer function that initiates a command every 29 seconds, set it to record 30 second segments. This provides a slight overlap.

Every 3 x 30 second segments use ffmpeg again to stitch it together into one 1m 30second clip, you of course can alter and play with the formula, but it's then a weigh up between the speed of encoding vs the load on your computer. Encode and compress. You then stitch those together to attain a clean, corruption free clip as long as you wish. Make sure you research multi threading and thread blocking.

There you go pal, as stated quite simple. Now you have your lazy answer you can continue with your project without blaming filters and battles.

If you want I can share my private repo, server passwords, api keys and any other shortcut you want. lol.

Hello world -

[NotSooFriendly]

2 hours stream , this is the result . v5.8 command line args used = -mode automatic , in addition when new connection happens , the user goes offline or whatever reason , the tktok-live-recorder hangs , freezing , like it's writing a record but it do nothing.

with automatic mode i use -duration 120 that way only some of the clips are broken and not the entire Live

this not a solution , this make you lose less parts as possible , but the problem still exists .
it's video issue ( conversion , incode , decode ) idk.

This is the solution. Recording in small segments helps prevent data loss and also cuts down on processing when encoding/transcribing, you can make a very simple function to stitch the segments back together.
To say that is not the solution is a bit silly when most people have a 2 hour long video that was compiled into a single file using segments, and you have nothing saved as you have a singular corrupted 2 hour long video recording.
This is a very basic theme across code and digital devices in general. Collect data in small amounts and then ensure there is a backup and the compile a finished product when you know the data is good.
The issue you are having could be when the video is being encoded, if one small part of the file gets corrupted then it will all become corrupted. If you are trying to process a 2 hour long video then you have a significantly larger chance of something going wrong...

Is not a solution if you say that but dont help or explain how to do it :/.
Can you tell us that "very simple function" to stick fragments together? thx
Anyway, i tried to do fragments of 1min, 5min and 10min, not all the fragments are corrupted but when it happens its not corrupted the entire fragment, its just like 30 seconds to 50 seconds corrupted.
And no is not match event related, because i watch the Live with another account and never did a match event when had the corruption.

I mean you may have to think outside of the box and add custom scripts, some logic and god forbid a little independent research, I really love to help people but this reply of "its not a solution unless you explain how to do it" eeks me.

It really is a simple solution if you're not just used to cloning people's repos and typing run.

I could share my project with you as I offered to do with another dude on a different thread.

It records multiple live streams simultaneously whilst connected to web-sockets, saving, logging, stitching video segments, transcribing live audio, uploading it to endpoints with further backend processing the list of functions go on.

The point I'm getting at here is this repo is a very awesome tool, to be integrated into a bigger project. It's not a final product you just clone and then type in a username and expect it to not have bugs, it's still in development itself.

Please in the future don't just assume someone should tell you how to do something, I like to encourage people to grow their knowledge and me telling you doesn't do that. ✌🏻

But a big question, when you reading a text, you know how to read the whole text, or you only read 2 words that you like?

Because i said more than just asking for how to merge that files, even not being the solution because it will merge corrupted fragments anyway.

I will help you to read the whole text, so dont worry.

You posted this:
"This is the solution. Recording in small segments helps prevent data loss and also cuts down on processing when encoding/transcribing, you can make a very simple function to stitch the segments back together."

And i answered you a reply:
"Anyway, i tried to do fragments of 1min, 5min and 10min, not all the fragments are corrupted but when it happens its not corrupted the entire fragment, its just like 30 seconds to 50 seconds corrupted."

So as you can see that you said, is NOT the solution, because the fragments still corrupting even if they last less than 1 minute.

In the past i used other Tiktok tools from github too, to record more than 10 lives simultaneously with no errors but now its not working anymore, so it maybe is just incorrect codec issue or something.

But ok, you can keep writing a bible with your NOT solution.

Thanks lol

Also just to clarify, this is the reason you struggle with basic tasks and forward logical thinking:

"In the past i used other Tiktok tools from github too, to record more than 10 lives simultaneously with no errors but now its not working anymore, so it maybe is just incorrect codec issue or something."

Because you just clone and rely on other people's work without understanding what's happening, as started you clone and press run.