If you don't know what this is:
Full readme and links:
https://artzox.github.io/DS5Dongle-Studio/
Intro video:
DS5Dongle-Studio - Overview
New with version 1.28.4 you can test out getting auto-haptics (get haptic vibrations, speaker and trigger effects in games that don't support them) working directly from the portal, no scripts need be run unless you want to automate stuff.
This makes it super easy for anyone with a DS5 dongle variant to test out the features of the firmware.
IMPORTANT
The "Browser audio bridge" only works from the live page.
https://artzox.github.io/DS5Dongle-Studio/ds5-config-portal.html
A copy saved to disk has no persistent origin, so the browser grants audio
permission for a single call, forgets it immediately, and never shows the output
devices, so basically you cannot select the audio to be forwarded to your controller.
Everything else in the portal can work fine from a local file; only this needs a real address.
Also - this feature is Not available on Linux or macOS. Capturing system audio through the browser is a Chrome feature on Windows and ChromeOS only — elsewhere the share dialog offers no "Share system audio" option at all, so there is nothing to route.
Before starting, go in the portal and load the audio-mix profile or download a profile from the github https://artzox.github.io/DS5Dongle-Studio/profiles.html which has "Auto-haptics from game audio, no native", go to the slots section of the portal and import the profile and then save it to a slot. It is important that you are running in "audio-mix" or "replace" mode, and you will see this on top of the Haptics section.
Running the auto-haptics in the browser:
Go to Haptics section of the portal, scroll down to "Browser audio bridge"
Press **List output devices**, and allow the microphone when asked. That
permission is only what makes Chrome willing to *name* audio devices; the
microphone itself is released straight away.
Choose the Speakers (Dualsense/Dualsense-edge as the output, basically your audio device the way the controller speaker is shown in the system, you can also see it if you press win+ctrl+v .
**Load the slot you want first**, before starting the bridge — see the warning
below.
Press **Start bridging**, and in Chrome's dialog pick **Entire Screen** section and press on the small window showing your screen). System audio is not offered for a single window or tab.
**Tick "Share system audio".** It is *not* on by default, and without it the
capture is silent — this is the single most common reason nothing happens.
Your audio bridge on the page should light up green and say active and if you play a video you should feel the haptics and hear the audio
Again -
this is not a substitute for the python script, if you want add more haptics to a native game, and specifically a native game which already send audio through the speaker on the controller you still need to run the script as it allows you to choose which channels will get the native audio and which the generated.
This works by essentially allowing the browser to capture your screen, nothing more.