Use FLOSS formats for video transcoding

[Sp3r4z]

Hello, I've seen Peertube transcode video after upload (really good idea, for security, standardization…) but, here I am: Peertube use MP4 & AAC, the first is under patent encumbed the second is a proprietary format… I think it's not really interesting and satisfying for a FLOSS project promoting proprietary formats.

I think something like: VP9+Opus in a WebM container, is really more appropriate for this project.

Let me know.

PS: I know that x264 and MP4 are more CPU-friendly since low-level CPU instruction sets exist for them ; but for me a FLOSS project should promote free (as speech) formats regardless.

[Serkan-devel]

How can mkv-files be played on the web? It seems to be similar to webm

[Sp3r4z]

@Serkan-devel what do you mean? Is your comment linked to the purpose of the issue?

[Serkan-devel]

mkv is a FLOSS format, that I can only run on VLC but not on the web

[Sp3r4z]

Right, I get that. But why talking about .mkv? I propose WebM container with VP9+Opus inside, because it's readable on Internet browsers (like Firefox), which is free (as speech and as beer).

[rigelk]

@Serkan-devel Matroska is just a container standard, equivalent to WebM but unfit for web diffusion.

The encoding time for VP9 is still 5-fold of H.264, and the upcoming AV1 is gonna be 20-fold (I know it's yet to be optimised but it probably won't be any lower than VP9). So there's that.

We could let administrators choose the encoding they want and leave the actual behaviour as default.

[Sp3r4z]

@rigelk You're right, for the transcoding task but, here is my point: it requires less storage resources and bandwidth. I know, it's a balance between CPU and storage/bandwith, but for videos and streaming, I think it's more important than CPU usage.

As I said on this #479 in mediainfo.txt transcoding seems to pose some problems (30fps but the original was 1fps, worse sound quality… ).
Maybe just improve transcoding parameters, can be something really "in-between".

[Chocobozzz]

We use H264/AAC because we use the videostream package to stream data inside a video element. These codecs are the only ones compatible with all web browsers. It's currently not the case for VP9.

[rigelk]

@Chocobozzz Apple is pushing for H264/AAC, so it's unlikely they will support VP9 anytime soon. It doesn't mean we should abide by their vision. But I have to admit searching for a WebM muxer doesn't yield a lot of results…

[Sp3r4z]

@Chocobozzz You're right, I've thought about that too. My idea was just "open the discussion" and see if it can be a good idea for future. But yeah, Safari (desktop and ios), doesn't want to heard about that :/

@rigelk ffmpeg, doesn't do the job you search? (I'm not a video expert, so maybe I ask for something obvious :s )

[abakkk]

Are there any instances that don't transcode in mp4 ?
I saw old webm video in peertube and it works fine.

[zez3]

In light of the latest browser updates I would also be tempted to have a look at the new AV1 codec
https://en.wikipedia.org/wiki/AV1
ff, chrome already implemented some WebRTC experimental versions.
https://www.phoronix.com/scan.php?page=news_item&px=GStreamer-1.14.0-Released

[Sp3r4z]

@abakkk Some instances don't transcode, mp4 trancsode is an option which can be disable quite simply.

@zez3 it's actually experimental, for sure it'll be, in the future, a good thing to thought about (really, I think that too). Unfortunately, right now it's not really a good idea for mass usage. But we'll see, I guess.