this is a solution in theory... but how??
Code:
I think I know why this happens. The HTTP streams from livestream.com sends a Content-Length header with the value 2GB, and the server is probably closing the connection after that amount of data has been read. You can try using the HLS streams (use --stream-types hls to filter out the other ones) instead.