-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chat out of sync - issue with Twitch itself? #1285
Comments
I noticed this behavior when viewing a clip on the Twitch website a bit ago. I'm not sure if theres much we can do. |
This is a bug on Twitch's side, and we can't do anything about it. You can try reporting it to them. |
Yes, appears to be something with Twitch. As a temporary workaround, what I found seems to work, is instead of downloading the clip chat, to get clip info through the API, and download the chat for the VOD with the Seems to me that the |
> a temporary workaround The problem is that the VOD will eventually be deleted due to expiration, while the clip will exist forever. In this case, it will not be possible to obtain the chat history from the VOD. Is there a need to add a new temporary feature that will no longer be needed sooner or later specifically for the Twitch bug? I feel like he should be pretty busy these days... |
@egormelyakin This is what I get with the Twitch API about the clip:
Yes, but the problem is that it affects all VODS Some people complain that Highlights don't save the chat, but for some clearly there is: About the chat history for the Highlight, I don't know if Twitch keeps the entire chat of the VOD and only shows the corresponding part in the highlight, or trims the chat the same duration of the highlight. Then it would be a problem if does not match exactly... |
The starting point of the highlight in the VOD is not accurate either, for example https://www.twitch.tv/xqc/clip/MotionlessBenevolentVampireGOWSkull-6PyPUdoKvIZS2jlK links to VOD 1:28:32 where says "Watch Full Video" But in the VOD the highlight starts at 1:28:08 so it's 24 seconds more. The highlight duration is 28 seconds:
But don't know if that has something to do. |
the chat of the VOD can't be downloaded once the VOD expires, I've checked and get the error
|
I think the best practice at the moment is for users to use the enqueue function of VOD Download to fetch data for a specified range of clips and chats at the same time before the VOD corresponding to the clip expires. Then they can deal with it on their own. As for the case where the VOD has already expired, there is nothing we can do about it. It's not like we can just add in the clip download module whether the VOD has expired or not, and then handle it differently depending on the situation, is it? |
Clip chats are generated by Twitch servers based on the VOD chat. In other words, when the VOD expires, the clip chat log expires with it. |
Seeing the example from suberbonaci about the clip offset being wrong too, it seems impossible for us to patch around the issue on our end. It needs to be fixed by Twitch. |
Checklist
Edition
Command Line Interface
Describe your issue here
When downloading and rendering chat from a Twitch clip, it is about 30-40 seconds in front of the clip itself, meaning the clip is delayed behind the chat replay. When opening the clip page in a browser, the chat replay there matches with the rendered chat exactly, being also in front of the clip, but chat replay on the VOD page is in sync with the video.
Add any related files or extra information here
For example, in this clip, the word "transaction" is mentioned right at the end of the clip, but in both the rendered chat and the chat replay on the clip page, this word is mentioned in one of the first messages, giving the desync of about 40 seconds.
In the chat replay on the VOD page, this desync is not there, only the clip page, possibly indicating some issue with Twitch clips themselves. I am not sure whether this is an issue or my end, or whether this issue is even new or not
Rendered chat
HonorablePoorWasabiPRChase-GoFX7qTL_BCvznuZ.mp4
The text was updated successfully, but these errors were encountered: