Hello Emmanuel

After a new test, The tool work.

The synchro come after one or two minuts.

73's

Very good Idea Emmanuel !

I've tried on your phantom.

Synchro issues

73's

We did that, you rejected everything.
Ignored all we asked you to improve.

Why? Manolis has improved your code so much, I don't use it, but others do. He does listen.

So again, why? You never listened before.

I do not get this.

We have been posting so much information, so much code and changes.

Why would it be different this time?

For me the ship has sailed, I moved over to the dark side of Uber

A Receive Diversity tool is testing now. You can work with it in  http://phantomsdr.no-ip.org:8900

The goal is to pair the receiver with a second one somewhere else and listen to whichever site currently has the better signal, so a fade at one is covered by the other. The second receiver can be another PhantomSDR-Plus, a KiwiSDR, an UberSDR or a WebSDR — the first three need nothing at all beyond the listener's browser, and only a WebSDR needs a small relay on your own server. Alignment takes about twenty seconds.

What it does, and what it does not

Diversity here means **selection**: at any moment you are listening to one site or the other, with a short crossfade when it switches. It is not a phased array and it does not add the two signals together.

That is a deliberate choice, and the reason is physics rather than software. Two receivers hundreds of kilometres apart hear the same transmission over different ionospheric paths. The two audio waveforms arrive with unrelated phase and slightly different Doppler, so adding them sounds hollow and comb-filtered — the classic "phasey" artefact. True coherent combining needs two receivers on a **common clock**, sample-aligned; two independent receivers connected over the internet can never provide that.

So what you gain is continuity, not raw signal strength:

- On a stable path where one receiver is simply better, you will hear that receiver and gain nothing. This is normal.
- On a fluttery path with deep QSB, fades at two distant sites are largely uncorrelated. Site A drops out for three seconds, site B does not, and the audio carries on. Expect "I stopped losing words", not "S3 became S7".
- The second win is often local noise and QRM. Two sites have different neighbours, different power lines and different broadcast splatter. On a noisy band this can matter more than the fading.

There is a cost: you listen one to three seconds behind real time, because the earlier stream has to be delayed to match the later one. That is irrelevant for listening and decoding, and unhelpful if you are trying to work a station.

After the tests, the tool will be released in the next version.

Hi all,
please implement this minor update to your instance. Some minor fixes to admin panel and kiwi bridge.
Then  recompile backend and restart your server and admin panel.

I will post a link here then

Yes, this will come soon

v.3.9.0 to work with Audio needs these in the used .toml file:

[kiwi_emulation]
enabled      = true
audio_gain    = 60.0    # dB, Kiwi clients only. 0 = untouched.
wf_cal        = 0.0  # dB, display taste. 0 = agrees with the S-meter.
wf_fps_max    = 23      # frames/s. 23 is the protocol maximum.
# smeter_offset = 5.0  # dB. Defaults to input.analog_smeter_offset.
everybody else using these settings (in v.3.9.0) HAS Audio!
It is written in the instructions and in the demo .toml files in the repo....

My live phantom is on "stock" 3.9.0.

I will correct tonight at Home