Closed Psynewaves closed 4 months ago
This was fixed in 1.9.9.1. Can you try that version and confirm?
Any updates?
Hello, Thank you for your reply. I am currently out west for rostered work. I will be returning home on Wednesday and will certainly try the above recommendation. I shall provide an update as soon as possible after testing.
On Sun, 26 May 2024 at 15:45, Mooneer Salem @.***> wrote:
Any updates?
— Reply to this email directly, view it on GitHub https://github.com/drowe67/freedv-gui/issues/722#issuecomment-2132074650, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4IE2W7DYCMCFZLEV4EUHFDZEFZJHAVCNFSM6AAAAABH3WVAV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGA3TINRVGA . You are receiving this because you authored the thread.Message ID: @.***>
I have tested this on 1.9.9.1 and the issue appears to be resolved. The error is no longer present and the modem is functional again :) Thank you for your time, help, assistance and patience with me.
No worries! Feel free to open another issue if you find any other problems :)
Not sure what the cause is, but I am unable to use VB-Audio cable as the input for FreeDV. The issue occurs on both 32 bit and 64 bit windows versions. See attached pictures