I don’t want to go full-blown geek on this explanation but the short answer is you can do nothing about it so switching browsers doesn’t help, the problem is server side.

The content is described by the server as one type e.g. audio but is, in fact another, e.g. text. So, your browser is expecting neeps but gets tatties instead.

Why the settings on the server side have been changed, I have no idea, Perhaps a system upgrade with different default settings, or compression has been enabled to ‘improve’ page load performance, but that’s where it has to be fixed.