1 · Run self-test
- Settings → "Software & License" → "Audio self-test" → "Start test" button
- The test walks you through five steps: "Step 1 · Do you hear the test tone?", "Step 2 · Does your microphone respond?", "Step 3 · Does the music dim when you speak?", "Step 4 · Online sessions (Zoom / Teams / Meet)", "Step 5 · License active?"
- At each step, click "Works" or "Does not work" yourself
- At the end, "Result" shows for each step whether it worked
2 · Export diagnostic report
- Settings → "Software & License" → "Generate diagnostic report" → "Build report" button
- Optional: brief description of your problem
- Preview shows what will be in the report
- "Save report" → file picker → saves as
.txt - Email the file to support@deutsche-hypnose-online.de
3 · What's in the report
- App version
- Electron and Chromium versions
- OS (Windows 11 build, etc.) + architecture
- Self-test results per step — only as an event, and only if the self-test ran since the app was started
- The latest app events since the app was started, at most 250 (phase changes, trigger plays, errors) — they can contain track file names, device names and the save location of a recording; keys and passwords are cut down to at most 4 characters
- Settings snapshot (crossfade-sec, QuantizeMinLead etc.)
- Track count + analysis status
- Names of all detected audio devices (inputs and outputs)
- Browser language
- Audio state (sample rate, latency, IDs of the selected outputs) and whether VB-Cable or VoiceMeeter was detected
- Microphone and ducking settings
- Number of presets, name and BPM range of the active preset
- License status (activated, devices in use, expiry date, test mode, last check)
- Number of saved sessions and storage used
- Your description from "What happened?"
4 · What's NOT in the report
- ❌ Audio data or track contents
- ❌ Full license code (only first 4 and last 4 chars for ID)
- ❌ Email address, IP, client data
You can open the file in any text editor before sending — it's plain text.
5 · Console logs for live diagnosis
- In the app: Ctrl+Shift+I opens DevTools
- Console tab
- Reproduce the bug
- Copy lines starting with
engine.or[Hypnotika] - Paste into support email with description of expected vs. actual behavior
Related: Troubleshooting · Contact support