Vittorio Palmisano

The not-headless webkit version works setting `--enable-mock-capture-devices=true` option. For the --headless version (using wpe), we need to enable "enable-mock-capture-devices" in the wpe build: https://wpewebkit.org/reference/wpewebkit/2.23.90/WebKitSettings.html#webkit-settings-set-enable-mock-capture-devices

I've prepared a patch for adding a "enable-mock-capture-devices" command line option to the wpe executable. I'm no able to update the browser_patches/webkit/patches/bootstrap.diff, I've tried `./browser_patches/export.sh webkit` but the script stops...

> what about the rest of Consumer types? Simulcast, SVC ? In those cases the implementation should also check if that switch is possible (e.g. checking codec compatibility before switching...

Running with `--force-fieldtrials="WebRTC-Vp9DependencyDescriptor/Enabled/WebRTC-DependencyDescriptorAdvertised/Enabled"` enables the DependencyDescriptor extension also for VP9. Tested with chromium 91.0.4434.0

Current state: 1. I've added the AV1X descriptors in the `supportedRtpCapabilities`; 2. I've added `worker/src/RTC/Codecs/AV1X.hpp` and `worker/src/RTC/Codecs/AV1X.cpp` (https://github.com/versatica/mediasoup/commit/e0ded5e9b702fa65046328089a65cd4363e05a1a) that are basically a copy of VP9 classes with an initial parser...

I'm digging into the code and AFAIK the best place where to collect the DD headers informations is inside the `EncodingContext` class. I'm trying to figure out how this informations...

@agouaillard In the mediasoup case we need to know at least, for each arrived RTP packet, if it belongs to a keyframe or not, and actually this is done inspecting...

> > This is not the only way. > > Correct. There are different ways to achieve it. > > Anyway we are targeting AV1 here. Let's not add SFrame...

Updates: (This is related to chromium code, so maybe we should report this with a specific bug report, I'm reporting this if anyone could help) I've followed what indicated in...

Dependency Descriptor implementation status in chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=1196318 https://bugs.chromium.org/p/webrtc/issues/detail?id=11999