Michel Gutierrez

closing

with the current vdhcoapp/ffmpeg, the command line below does the job inside one thread, at very low speed (0.0663x) ``` ~/git/vdhcoapp/dist/linux/x86_64/ffmpeg "-y" "-i" "/tmp/vdh--3163143-h28yZKXDuJeV-.tmp" "-i" "/tmp/vdh--3163143-l9Qz7TItvz8o-.tmp" "-c:v" "av1" "-strict" "experimental"...

The same command without the `-strict experimental" produces an ffmpeg error: ``` [libaom-av1 @ 0x5597c5ef9700] The encoder 'libaom-av1' is experimental but experimental codecs are not enabled, add '-strict -2' if...

We (VDH team) are not working on this. The project being open-source, others might be working on this port but we haven't heard of such an initiative.

I took the details from [there](https://github.com/MicrosoftDocs/edge-developer/blob/master/microsoft-edge/extensions-chromium/developer-guide/native-messaging.md) where it specifies `/Library/Microsoft/Edge/NativeMessagingHosts/com.my_company.my_app.json` for system installs and `~/Library/Application Support/Microsoft Edge {Channel_Name}/NativeMessagingHosts/com.my_company.my_app.json` for user setup but i agree it's not logical. As soon as...

Sorry but would be a no-install version ? Note that for the coapp to be callable from the extension (i.e the browser), it takes creating manifest files at specific locations...

Can you open the finder, go to the downloads directory where the `.pkg` file is and open it from there ?

You are absolutely right. I have only discovered that this was possible a few days ago and planned to implement it in the next roll of vdhcoapp (which i don't...

Just deleted a comment from Kunal Naithani that included binary files to affect the registry. Since the files cannot be verified, it is way too dangerous to keep them in...

Each release of the vdh coapp comes with several flavours of glibc versions ([https://github.com/mi-g/vdhcoapp/releases/tag/v1.6.3](https://github.com/mi-g/vdhcoapp/releases/tag/v1.6.3)) to accommodate various linux distros. Did you try other `.tar.gz` packages ?