Closed debugrr closed 3 years ago
I've actually realized I've introduced a very very stupid logic back in February, that made AFSK look like it's working while it was not. I fixed it in 52a8c56c12b58bfd5f05421509b4ee340d4d161d now and released 1.6.1a, so maybe that was the real culprit?
Thank you, I'll give it a go and report back.
Yes, that fixes the AFSK issue. I'll close my pull request.
I believe some devices have odd permissions (especially new devices. Specifically using VOICE_CALL, though in the code below, we have "if using bt, then use 1 or 1" essentially.
I think switching to the DEFAULT recording device should alleviate recording issues for at least the Samsung Galaxy line.
Another option could be UNPROCESSED -- 9.
I'd be willing to test a compile, but currently I don't have a compile env.
Example would be Issue #205
Alternatively A selector could be added to to select the audio in device, the same way The output device is selectable.