You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experiencing issues with the twspace_dl tool while trying to download recordings from Twitter Spaces. Despite ensuring my cookie file is up-to-date and correctly formatted, I am encountering persistent errors.
Error Description:
The tool throws multiple errors during the download process, notably failing to parse the EXTINF value of HLS segments and returning HTTP 400 Bad Request errors. Here's a snippet of the error log:
[hls @ 0xaddress] Cannot get correct #EXTINF value of segment [URL], set to default value to 1ms.
[https @ 0xaddress] HTTP error 400 Bad Request
hls @ 0xaddress] Failed to open segment [index] of playlist 0
Attempts to Resolve:
Checked and verified the cookie file is correct.
Tried using the tool across different network settings to rule out network-related issues.
Questions:
Has there been any change in how Twitter handles HLS streams that I might be unaware of?
Is there an update to the tool or a patch available that addresses these new changes?
Could anyone suggest alternative tools or methods to download Twitter Space recordings?
Any help or guidance on this would be greatly appreciated as this tool is critical for my usage scenario. Thank you!
The text was updated successfully, but these errors were encountered:
Hello,
I'm experiencing issues with the
twspace_dl
tool while trying to download recordings from Twitter Spaces. Despite ensuring my cookie file is up-to-date and correctly formatted, I am encountering persistent errors.Error Description:
The tool throws multiple errors during the download process, notably failing to parse the EXTINF value of HLS segments and returning HTTP 400 Bad Request errors. Here's a snippet of the error log:
Attempts to Resolve:
Questions:
Any help or guidance on this would be greatly appreciated as this tool is critical for my usage scenario. Thank you!
The text was updated successfully, but these errors were encountered: