Sidebar
Wren troubleshooting
- When you have stuttering audio see the section about Stuttering_audio.
- When there is no sound at all see No_sound.
- When the sound quality is bad, see Bad+sound.
When Wren will not start up make sure that it was installed properly, that is:
- it must not be located in a Windows owned folder (such as Downloads, or Program Files), also see the section about Installation.
When an ASIO device is being used things may not work when the ASIO sample rate differs from the Wren sample rate. Check the Settings Screen F3 for this.
Had a user report that the program would not run in Windows 7. Turned out his antivirus was blocking it as an unsigned program that was downloaded from the web … with a message saying:
- 'Windows cannot access the specified device, path or file you may not have the appropriate permission'. Please fix such issues in your AV software.
Had another user report repeatedly popped up access violations. It seems that this can be caused by the PortAudio DLL (or Wren's interaction with it most likely). You can read more about this on an electro-music.com forum thread.
When the startup screen appears and disappears again and Wren does not start try to temporarily rename the espeak_sapi.dll to _espeak_sapi.dll, when that helps I'd like to know about it, please send me the Wren.log file then (it is in the Wren.exe folder created in the Installation process).
On some computers it was reported that when an audio input was selected PortAudio refused to work (reporting an error on opening the input stream). For Wren releases after 2020.6.24.0 it is possible to explicitely select '~nothing~' for the device, this may help.
From time to time users are discovering exciting new bugs, please let me know about any failures. For this please go to the Wren Debug Screen F5, Wren logs some information there. When you right click on it you can highlight the text, and then with another right click copy it. At times I will ask for the information present there to help troubleshoot issues. By default this information is written to a log file in the Wren application directory as well, look for wren.log.
Also see General_troubleshooting.