Skip to main content

in reply to Mikołaj Hołysz

@miki Do you use an apple browser? I'm trying to track that issue down but it seems to only happen in apples browsers, so far only on IOS. But it's taking long to fully figure it out because I don't have an apple device myself.
in reply to The Byte Bender

Yes, Safari on Mac.

I suspect this might be related to one of the audio formats being unsupported, I know Apple has some issues with that. Perhaps you should look into what formats are compatible and how to transcode them properly with ffmpeg.

in reply to Mikołaj Hołysz

@miki Most of our audio is lossy. Transcoding lossy to another lossy format will have considerable implications, not to mention the time it takes to transcode the longer audios is massive! Literally all other browsers play every common thing just fine but apple's gotta be apple again. I don't know what to do about that issue for now.
in reply to The Byte Bender

TBH most if not all media platforms (including Mastodon) transcode, it's only the tiny little blindy ones that don't.

There's nothing wrong with having a "download original" option, of course.

in reply to Mikołaj Hołysz

@miki I wouldn't jump so quickly and associate it with blindness. There are valid reasons related to quality in transcoding, especially for a platform which its hole point is audio.
in reply to The Byte Bender

TBH most if not all media platforms (including Mastodon) transcode, it's only the tiny little blindy ones that don't.

There's nothing wrong with having a "download original" option, of course.