Since I haven't gotten a response from the GitHub post I'll just drop this here

Both Roman and Vasily have Said over and over said over and over we have duplex working on tests programmer is working on it. one of them is here- at around 22 minutes into this video

There are several videos where they have openly said this over a year ago.

My gut tells me that really isn't the case and many were/ have been led on including myself.

Also, because of that and another question regarding how you are going to perform something like Pure Signal, in which that response was we have to use Fullduplex and get it working in order to obtain pure signal or the like of it.

So just how and or when, - Prefer the reply on the GitHub topic regarding this so not to drag this into a full-blown shit fest on the forum esp. since I don't want to use the forms, but over a month since I asked that and no response.
github.com/ExpertSDR3/ExpertSDR3-SUGGESTIONS/issues/123

silent or lack of reply makes one think things are not so!

Even if we never see full-duplex and APD (adaptive pre-distortion) they are still very fine transceivers however it’s not very nice to deceive your customers and it also changes their value position in the market as the competitors have 2 ADC’s and ADP with similar pricing.
I hope they prove us wrong and give us Full-Duplex and ADP soon.

Hello everyone.
First of all, Rick, if you have a question for me, you could ask me directly, as you always did, or ask it via email, I would miss this branch entirely if I wasn't tipped. I do not read everything what is posted on the Forum and do not read GitHub until I'm asked to read something certain. GitHub is for programmer, but he doesn't answer anything there, he's busy programming.

At this point, I've read many speculations/demands/threats here and there about Duplex/Predistortion and that is why I want to address this. Anyone could use the following information as a reference to what is going on in this area at the moment and what are our plans for it.
1. First of all, in the referenced video I clearly state that any of these functions will be considered ONLY after we implement all basic functionality, thus the release of ESDR3 1.0.0 final. I've mentioned the same thing many times in Telegram and other Forum posts. Here is the snippet of information I shared with Rick in early June:
"...Our main goal is to make ESDR3 identical to ESDR2 in terms of functionality, it's already way more stable and easy to develop and it's a great advantage in the future. The next step will be duplex and predistortion.
SunSDR2 QRP firmware has duplex, it was the latest firmware developed from scratch, so this indeed was prepared some time ago, but again we'll implement it in MB1, DX and PRO after the ESDR3 is ready. This time we want to move forward step by step, gradually, with ESDR2 we jumped from one feature to another, which greatly complicated the development on later stages."

So any discussion about these features until the release of ESDR3 1.0 could be purely speculatory, or so I thought...

2. As you all know, recently we've implemented two major changes in the ESDR3 and TRX's firmware:
1. New data exchange protocol between a transceiver and PC
2. New CW-core
Both features are absolutely awesome, but require a lot of processing power and current FW/HW combination hit its limits. In the following months, we've tested different combinations of potential Duplex implementation, which led us to a similar idea we came up with 2 years ago in relation to ESDR2 - we need a completely new firmware. To be able to implement Duplex, ALC, Predistortion, and many other cool features (DHCP, ADC overload indicator, unified sample rate as in NANO/QRP, TX frequency correction, SWR log, TX time limit for DX, etc.), we require a unified firmware based on the new architecture, similar to what we have now in ESDR3.

3. We implement and work on many many different things at the same time, some may have higher priority than others at some point, it doesn't mean we forget about them. For example, I know that some users are happy with the current ESDR3 functionality and all they need is remote operation. They don't care about Duplex, Predistortion, ALC, VLC plugins, ESSB audio and other stuff, what they need is proper/reliable remote control and that's it. ERS is one of our main goals for the 2023, it means that while we work on ERS we won't be working on many other things and vice versa, I want to emphasize this.

Thanks to everyone who shares suggestions/opinions and questions with us, we do appreciate it

github.com/ExpertSDR3/ExpertSDR3-SUGGESTIONS/issues/134
Please offer your suggestions for how should Duplex GUI should look like and operate.

You're beating around the question:

in the video Vasily at time frame 26:09 state We already know Full Duplex works. period his own words Rome, his own words- play the video!

That almost a year ago- Yes you said in V3 version one- no argument there

I asked for an update were does this stand? how is it coming along he mentioned then firmware- you again mention firmware

Again, that was A YEAR AGO- I asked were is it at in the curent time frame (as in where this currently stand as of now)

Now you're asking how should this work and look like, what the heck? in the post above?

It should work like Full Duplex and how ever it needs to operate to fulfill your statement we need FULL DUPLEX in order to make our version of pre distortion work! that's how it should work!!!!!

I can see where this is going and its pretty damn clear!


It's like pulling teeth now- why I don't understand what the hell has happened I use to believe in you guys I told you that many times I want to see you guys succeed in emails and couple voice chats we have had over the past few years. I no longer get that impression at all, I think you have led many of us down a wishful road and fantasy, that's my gut feeling and that is usually pretty much spot on!

Also, Rome, you mentioned I don't check here when you started your reply- But you posted the following on the GiitHub request I made- rvolchkov commented 10 hours ago
It's not a suggestion, discussions are for the Forum. github.com/ExpertSDR3/ExpertSDR3-SUGGESTIONS/issues/123

So, which is it- here or there? no emails they aren't public, no voice chats they aren't public either- so Here or there Roman its out in the public which is it?

I've already explained our plans for the future of ESDR3, I don't see a reason to continue this discussion any further here or there (GitHub).
I deleted your comment from - github.com/ExpertSDR3/ExpertSDR3-SUGGESTIONS/issues/134 because we've asked for suggestions regarding the implementation of the Duplex in GUI and this is not a suggestion:
It should work like Full Duplex and however it needs to operate to fulfill your statement, we need FULL DUPLEX in order to make our version of pre distortion work! That's how it should work!!!!!

I feel like I'm repeating myself, but it seems necessary, what I said was: "...SunSDR2 QRP firmware has duplex..." and it's true, but it has no implementation in the software - ExpertSDR2 earlier or ExpertSDR3 now, since QRP has only one antenna input. So what we need now is a better understanding of what it should look like in practice, should we display TX signal when you still receive with the other software receiver, etc. We want users opinions about these topics, so when we begin implementation, we have a clear view of the final version and don't have to redo this in time.

All I can say is I own both the MB1 and a 2DX and I am very happy with them. If Roman says Full Duplex and Pre-Disrortion are coming soon then I will take him at his word.
We all have things that we want to see added to ESDR3 and seeing how fast EE is developing ESDR3 I’m sure some of those things will come to light.

Here is my basic list of items for ESDR3
1.Bring back All Mode Squelch
2.Fix CTCSS RX distortion in FM
3.Fix auto-start startup issue where sync issue causes esdr3 to auto-start with sample rate mismatch error.
4.Fix persistence issue when restarting esdr3 does not remember RX filter setting and Mode selection
5.Fix all metering for audio input to show correct and calibrated accurate display
6.Add ALC indicator so user knows when they are over driving the PA causing power fold back

Anyway that’s my basic wish list and suggestions for esdr3.
Thanks

OK we can take #1 off the list (All Mode Squelch). Added to Beta 1.0.2 Thank You.
Will there be a change log soon, what other changes are there in the latest Beta.