I updated ASL3 and AllScan 2 days ago and the full-duplex functions stopped working. I'm using an ANF-101 node and have not changed any settings. I'm running duplex = 3. Before the update, I could transmit while receiving and would hear receiving audio if there was someone doubling with me. Now, all I am receiving is a dead carrier no matter what when I am transmitting. I have tried listening on different radios, and the same thing is happening.
Has anyone else experienced this with the update? If so, what is the workaround or how can I submit this to the devs?
Sounds like duplex=3 is doing exactly what it's designed to do.
That sends audio to the network from the receiving input, but not back to the transmitter, unless you are saying that when you transmit now, nothing is heard on the remote node, not just yours. I wasn't clear on that.
To Josh - THANK YOU for finding this issue and reporting it. I have just confirmed that as you stated, that full-duplex with duplex=3 is now COMPLETELY broken in ASL3.
I had actually opened a bug a few days ago (duplex=3 is now COMPLETELY BROKEN. · Issue #703 · AllStarLink/app_rpt · GitHub) because I noticed that a burst of Rx audio is now being echoed to Tx audio after COS drops, which is a definite annoyance - but I had not yet noticed that not only was that broken but that audio from other nodes is now not transmitted at all when keyed up.
One of the devs already identified the changes to ASL3 that have broken all this and hopefully all ASL devs are aware of how serious of an issue this is and will have it fixed soon.
To all ASL devs - if anyone can please advise what release we need to go back to to get this working and what commands need to be run on the command line to make that happen it would be greatly appreciated. Thank you.
