-
Notifications
You must be signed in to change notification settings - Fork 15
Known Issues
- Virus False Positive
- Recording volume is too low
- Error on graph
- Automatic control stops randomly
- Failure of Audio device
SOME ANTI-VIRUSES MARKS WALE(later than 0.3.4) AS FALSE POSITIVE. The app is COMFIRMED AS VIRUS FREE via full analysis by F-Secure and BitDefender. Jan 25, 2019. I always test the app on virustotal and get confirmation it's clean from some AV providers before release.
This is occurred because Wale controls recorder's recording volume too. I'm planned to add the feature about user controllable exclude list. Before than, please let me know the name of process you are using to record.
- Open Wale and get the name of the app which you use.
- Open new issue on Issues page to let me know. I'll add them to internal exclude list.
- Open file
%localappdata%\WALE\wale.exe_~\{recent version}\user.config
- Add
<string>{process name you want to exclude without curly brackets}</string>
into following block
<setting name="ExcList" ~>
<value>
<ArrayOfString ~>
<string>{process name}</string>
</ArrayOfString>
</value>
</setting>
"OxyPlot exception: XAxis not defined." error occurs when advanced view is re-activated in config page after the plot is drawed once.
- open another page and then come back to config page.
- move plot by right-click drag
This is commonly occurs when the audio device's state, setting or something else is changed. WALE tries to restart automatically when controller stops detected but sometimes this action might also be failed. I'm still finding what exact change is triggering this.
- Restart WALE. You can restart the app quickly via context menu button.
Not reported currently on windows version 1709(16299.192) or later
- Right click to start menu.
- Click run
- Type
services.msc
and click OK - Find and double click 'Windows Audio' service.
- Go to Recovery tab.
- Select 'Restart the Service' on Subsequent failures and check 'Enable actions for stops with error.' check box.
- Click OK