Philipp

One thing that is taking a lot of cpu usage is the animated bar at the top when being in a voice call. You can add this as Custom CSS...

What's so bad about FFMPEG? Does it not support colored pixels?

I think it could be worth trying to either change the source code of FFMPEG and recompile it, so that it is accessible with a JNI class and so that...

The issue is not reproducible on my machine and I have also checked the patterns and offsets and everything is still correct. You might have incorrectly installed the injector or...

Normally you don't have to choose any path, because the installer GUI automatically finds the Edge installation?

Was this the problem? Alternatively, you have to make sure to select the msedge.dll in the application version folder and the msedge.exe in the parent folder (e. g. `C:\Users\kien\AppData\Local\Microsoft\Edge\Application`)

I'm sure you chose the wrong file. This should not be happening: `Wrote patch file to C:\Users\kien\AppData\Local\Microsoft\Edge\Application\93.0.961.38 `, instead it should be: `Wrote patch file to C:\Users\kien\AppData\Local\Microsoft\Edge\Application `

If you choose the files correctly as stated in this comment (https://github.com/Ceiridge/Chrome-Developer-Mode-Extension-Warning-Patcher/issues/69#issuecomment-914302873), it should work. I will add it to the automatic installation finder in the future (https://github.com/Ceiridge/Chrome-Developer-Mode-Extension-Warning-Patcher/issues/70).

You can try looking up the actual executable path of msedge.exe by performing a right click on the Edge process (you might have to expand the group of Edge processes...

The DLL was only injected once. Is that how often you started Edge in the last hour? I would recommend updating the patcher and then reinstall it and maybe install...