Just installed OpenEar 1.7 yesterday - and have a couple of issues.
1. Running on a Surface Pro - with a high resolution screen - user interface is seriously distorted. I managed to fix it mostly with a compatibility setting. I am running at 200% enlargement - required to read anything on this screen.
2. No sound so far - but then having VBCable installed -and having fiddled around a lot with all the confusing Windows 10 sound settings - that may be my fault. SDR# outputs sound to the speakers no problem though.
Also had issues making my cheap RTL-SDR dongle work properly - piping from SDR# and using AirSpy at least gave me visible signals in OpenEar - but so far no decoded sound.
POCSAG did decode text - so input should be OK.
I am very excited about this application - appears so much easier to use and more promising than DSD+ Fastlane - which I really struggle with.
high resolution issue: yes there is some bad placement and some coding need to solve this (try to do in free time )
No sound so far: in v1.6.0 software uses default output device as voice output then user dose not have chance to change the output but it was good for first click to sound, but on v1.7.0 user can change the output path, and default is not windows default and it is first indexed on windows settings and user must set the desired output to get voice, but for easier procedure maybe it is better that i set windows default at first selected output option on software (on next release)
Also had issues making my cheap RTL-SDR dongle work properly - piping from SDR# and using AirSpy at least gave me visible signals in OpenEar - but so far no decoded sound. i can't understand the issue, sorry, please describe more
POCSAG did decode text - so input should be OK. :
i tested POCSAG on v1.7.0 but maybe needs more test! do you have this issue on v 1.6.0?