2.0 was more a bugfix and testing of some new stuff then a very large overhaul.

Many things were tested. 

It will have multiple receiver support, like via Network(IP), via Soapy, Direct RX888 and I/Q-recording.
Recording? Yes, but then I/Q recording so e.g. somebody can 'broadcast' messages to others, like they are on the air.

Not exactly know what Steven means with I/Q recording, but it's not the normal recording, it's like a receiver but recorded.

Also was discussed to make it websdr.org compatible, so it can use PocketRXTX and CatSync or even register at websdr.org, but has not further discussed yet.

But I have seen remote-setup for receivers, like openswebrx has, you can configure loads of stuff without editting files.

Maybe Steven will show some screenshots shortly, as the ones I have are pretty old by now. Probably not where the new project stands now.

Quote from: Bas ON5HB on Sep 01, 2025, 05:50 PMNovaSDR is also opensource and far more advanced

These are good news. To be honest, v.2.0 does not cover my expectations. I think the previous versions were better.
If you have some more information about the "many new options". please share with us.

Phantom V2.0 will be the last of this kind.

Steven is bussy with a totally redesign of the backend and frontend. 
Nothing like what we are using now.

It will also carry a new name: NovaSDR

New domain-names are already registered, and the forum is ready to start.....as soon as Steven has a version ready for release.

As Phantom isn't his own work but just a fork, it's decided to start from scratch and a new name.

I expect (hope) that he has a release ready at the end of the year. Trust me, it will blow you away as it has many options.
I have seen screenshots of it.

This PhantomPlus will not be continued by him. NovaSDR is also opensource and far more advanced.

As I can see, in the v.2.0 there are not some basic functions that were existing in the previous setup.

- Initial frequency for each band is a function named "initFreq" (in waterfall.js)

- Different values for brightness for each band can be setup using min: max: in bands section (in waterfall.js)

For example:
{ name: '40M HAM', min: -30, max: 110, initFreq: '7120', startFreq: 7000000, endFreq: 7200000, color: 'rgba(50, 168, 72, 0.6)',
          modes: [
            { mode: MODES.CW, startFreq: 7000000, endFreq: 7050000 },
            { mode: MODES.LSB, startFreq: 7050000, endFreq: 7200000 }

- Band selection outside the popup window must be rewritten from the beginning, using the rather old app.svelte. Tour v.1.54 has already well formed for this.

In your place, I would try to replace app.svelte and waterfall.js with the older versions. I don't know if recompile will work without errors. If not, we have to work from the beginning.

QuoteDarko, can you please upload your current app.svelte and waterfall.js?

No problem,
I send app.svelte and waterfall.js from my phantom v.1.5.4.

The files are messed up because I'm not a programmer, I made it by trial and error, I used what you posted on the forum as a model.
It was important to me that it does what it needs to, as the code looks like, users of sdr don't see it anyway. 

I sent you the same files for v2.0.0, I added medium wave and cb ssb band.

Best regards,
Darko,9a7aof

Darko, can you please upload your current app.svelte and waterfall.js?
I use the older version modifies for my needs but I have also ever older versions of these files where bands are not on a popup window, there is a center frequency for each band and dedicated waterfall control for each band.

Hello,

I would like to ask the author or someone who understands programming to add a configuration file where the minimum brightness of the waterfall could be manually set for each band.

The problem is that on some bands the antennas are resonant and on others they are not, so in some places the waterfall is too bright, in some places so dark that nothing can be made out and there is a signal.

I know that there is a slider that can be used to adjust the minimum brightness of the waterfall, but if you only watch predefined bands, it is an additional hassle.

Another wish, if it is possible to add a starting frequency for each band to that external configuration file, so that the band remains in the center but so that I can, for example, set my starting frequency to 3675 for 80m, 7123 for 40m, and so on.

Those two options were in that complicated App.svelte before the automatic addition of bands. I really liked the manual adjustment of the minimum brightness of the band and the starting frequency and I had it until I switched to v.2.0.0.

I also ask that the frequency step by moving the mouse wheel be placed somewhere below or above the Fine Tuning option. It's awkward to click on that icon in the top right.

Another thing, I especially liked in version 1.5.4 is that the buttons for selecting bands were available on the desktop in the early version, changing bands with one click. This with the popup window slows down and makes changing bands difficult.

Best regards,
Darko, 9a7aof

These is a BCB filter on that receiver too. I'm amazed you saw a signal.

Here is a screenshot taken while receiving the talk show "Coast to Coast AM" on station WHAS. It seems to be a quiet evening on the NY4Q PhantomSDR site, with very few static crashes from lightning.

The frequency adjustment function of the scroll wheel is no longer working in PhantomSDR+ 2.0.0