Riccardo

Should be fixed, works for me now, @buzzdeee .

At the moment, no... both are unmaintained software and there is a lot of burden. I don't know how functional Camera.app is and where the maintainer did go, dependencies, etc...

I do compile on RaspberryPI, but it has SIMD. you can disable WebRTC as a test and if you don't need it with `--disable-webrtc` I don't think you need do...

To be honest, I don't know if there is an option not enabled or still some code path missing. Do you know what component should provide h264 decoding? ffmpeg?

Are you able to use h264 for wha tyou need on latest firefox? I am on linux with latest and testing https://canonical.github.io/inbrowser-encode-test/ only works for vp8, but that is encoding

https://tools.woolyss.com/html5-audio-video-tester/ this confirms that SeaMonkey and Firefox can play 264, but ArcticFox does not. At least we have an easy test.

Very good. So essentially, without WebRTC fine. Why do you need to foce CFLAGS then? On Intel and PPC I can set arch CFLAGS, so it must be something ARM...

> Yeah I believe the h264 support should be provided through ffmpeg. hmm.. Just by chance do you know if FF52 ESR has h264 support? and FF 45ESR? that way...

Then it will be quite a bit more work and won't get mad over it right now. First goal is to match FF 52 as best as possible. If you...

Hmm.. more complicated. Read here: https://askubuntu.com/questions/389437/how-do-i-get-html5-h-264-video-working-on-firefox and I now test on Linux firefox 125 and it has an addon installed for H264. Seamoneky has not! Wonder... I guess ArcticFox doesn't...