REKLAMA

DSDPlus1p072.zip

Nie tylko zdjęcia z satelitów czyli inne emisje cyfrowe

Z tego co zauważyłem to wykorzystują ją do odbioru tv sat. Prawdopodobnie uda ci się też odebrać sygnał z satelit meteorologicznych pomiędzy 1600Mhz a 1800Mhz. http://www.w7forums.com/threads/drivers-for-skystar2.2148/ https://www.youtube.com/watch?v=LALMQ6U80ow Co do tych meteorologicznych satelit to nie pamiętam w jakim formacie jest sygnał nadawany chyba QPSK ale wiem ze o szerokości około 4 Mhz to akurat karta dałaby rady. http://www.wmo-sat.info/oscar/satellites/view/341 http://noaasis.noaa.gov/NOAASIS/ml/future.html I następna wersja DSDPlus


Pobierz plik - link do postu
  • DSDPlus1p072.zip
    • DSDPlus.frequencies
    • FMP-Map.cfg
    • msvcr100.dll
    • libusb-1.0.dll
    • FMP-Map.EXE
    • rtlsdr.dll
    • DSDPlus.EXE
    • DSDPlus.radios
    • DSDPlus.sites
    • FMP.txt
    • DSDPlus.groups
    • lame_enc.dll
    • DSDPlus.txt
    • FMP.cfg
    • LRRP.EXE
    • FMP.exe
    • LRRP.cfg
    • DSDPlus.networks


DSDPlus1p072.zip > FMP.txt

FMP
---

FMP is a simple DVB-T dongle tuner / NFM demodulator. It samples at 1 MHz,
so its spectrum display spans 1 MHz of the RF spectrum. FMP is designed for
low power devices like low end netbooks where CPU and screen resources are
limited.

FMP takes four command line parameters:

WaveOut device number

You would set this to your PC speakers if you are just monitoring the
demodulated audio, or to a VAC/VB-C instance if you are feeding a
digital decoder like DSD+

DVB-T device number

Typically, this will be 1 or 2 for the first or second DVB-T device

PPM correction

This is the same value that is used in programs like SDR#

Frequency

This is the initial frequency (in MHz) to tune the dongle to



FMP uses a configuration file (FMP.cfg); its contents are:


line 1: sampling rate; DO NOT CHANGE


line 2: window width; DO NOT CHANGE


line 3: FFT size

8, 16 or 32

lower values use less CPU

higher values produce better spectrum displays, but use more CPU resources


line 4: spectrum update rate

reasonable range is 5 to 20

lower values use less CPU

higher values better catch brief transmissions on the spectrum display


line 5: step size table

in FMP, you can use the left/right cursor keys to retune up or down
by one channel; use this table to specify all of the step sizes
that you will want to be available for your use; add a minus sign
in front of the step size you want FMP to initially use


line 6: primary frequency list
line 7: secondary frequency list

see the frequency lists description at the end of this document


line 8: search units

used with frequency lists
should be miles or kilometers
(protip: FMP just looks for the presence of a 'k' or lack thereof)


line 9: search distance

used with frequency lists
should match about how far you might expect to RX signals from


line 10: search origin

used with frequency lists
this should be your monitoring location; units are decimal degrees


lines 11+:

you can stash extra search origins after line 10; FMP will not see them

if you change monitoring locations (like work, home), cut/paste as required


FMP keys:


Active keys:

0-9 . Enter - set frequency
[/] - select step size
/ - step frequency
Ctrl / - step frequency by 250 Hz

M - toggle spectrum memory overlay
X - reset spectrum memory
Z - toggle spectrum zoom overlay
I - select injection mode
B - select bandpass filter
E - toggle economy mode
F - toggle noise filter
^/v - (cursor up/down) adjust volume level
spacebar - toggle muting

g/G - adjust RF gain
c/C - adjust frequency correction

R - toggle raw I/Q and FM demod recording

S - start scanner mode or exit hold mode

? - list active keys
Esc - exit scanner mode or exit program


help

press ? key

help is displayed in FMP's console window


volume level

use cursor up/down keys

should be left at 100% when feeding a digital decoder like DSD+

spacebar mutes/unmutes demodulated audio


noise filter

press F to toggle

do not enable when feeding a digital decoder


tuning

tuned frequency is displayed in window title

thin white vertical background shows tuning point and
RF bandpass filter width


direct tuning

enter frequency in MHz (nnn.nnnnn) and press Enter

as digits are entered, they are displayed in spectrum window title


mouse tuning

move mouse over spectrum display

targeted frequency is displayed

left click to retune


step tuning

cursor left/right to step up/down one channel

FMP will retune up or down by the current step size amount


step size

the [ and ] keys select the previous/next step size
from the custom step size table that was loaded from FMP.cfg


fine tuning

Ctrl cursor left/right steps up/down by 250 Hz


PPM correction

current PPM adjustment value is displayed in window title

press C or c to adjust PPM up or down (commands are case-sensitive)


show/hide zoomed spectrum

press Z to toggle display on/off

zoomed spectrum shows tuned signal detail and centering in passband

higher FFT sizes show finer detail

lighter background shows RF filter passband and transition bands

tuned signals should be centered in passband

majority of signal should be in passband

signal edges can be in transition bands


show/hide spectrum memory

press M to toggle display on/off

spectrum memory shows previous peak values, which makes it easy to find
exactly what frequency a brief, now gone transmission was on

moving the mouse pointer to a stored peak will show the signal's frequency


clear spectrum memory

press X to clear/reset the spectrum memory display


RF gain

current RF gain level is displayed in window title

press G or g to adjust gain up or down (commands are case-sensitive)

reduce gain for very strong signals

reduce gain if noise floor (background spectrum) is high

in environments with strong signals or a high noise floor,
start with RF gain maximized, then reduce gain while watching
the spectrum display; clipping artifacts (spikes) will diminish
or disappear as optimum gain levels are reached

Also, while the RF gain is too high, as you reduce RF gain,
the noise floor (the lowest parts of the spectrum display) will tend to
drop faster than the levels of valid signals; when everything drops
at the same rate, you have left the overdriven range

select optimal gain level by using DSDPlus -v3 and observing ERRn and e: values


RF bandpass filter selection

press B to cycle through filters

narrower filters reduce co-channel interference

narrower filters reduce noise levels

too-narrow filtering distorts digital waveforms


12.5 kHz

lowest CPU usage

highest noise levels

will not block co-channel signals


9.5 kHz

P25: reduces noise; eliminates most co-channel interference

NXDN9600: should work well


7 kHz

NXDN9600: should work well; low noise

DMR: matched filter


4 kHz

NXDN4800: matched filter; will eliminate most co-channel interference

D-Star: matched filter

DMR: reduces noise, but will distort waveforms (DSD+ can handle it)


economy mode

press E to toggle between normal and eco modes

eco mode uses less CPU

in eco mode, zoomed spectrum is green (duh)

quality of demodulated audio is reduced in eco mode;
effect on DSD+ decoding is minimal

analog signals should sound better in normal mode

at startup, FMP will be in eco mode


scanning

FMP can (slowly) scan frequencies

a frequency list, one frequency per line, should be placed in a file
named FMP.ScanList

the format of each line is:

frequency mode description

example:

450.1250 TIII Acme Radio


frequency is in MHz


mode text controls bandpass filter selection

4 kHz modes:

DSTAR
NX48
NEXEDGE48

7 kHz modes:

DMR
CAP+
CON+
TIII

9.5 kHz modes:

NEXEDGE96
NX96
P25

12.5 kHz modes

any other text string (ProVoice, analog, LTR, ...)


blank lines in the file are ignored

processing of the FMP.ScanList file stops if a line containing
the string & lt; EOF & gt; is found; frequency entries that you don't want
to scan can be stored in the file after the & lt; EOF & gt; line


pressing S starts scanner mode

pressing Esc exits scanner mode

no other scanning commands (Hold, L/O, etc.) are presently implemented


FMP's scanner mode is designed to be used with DSD+. FMP and DSD+
should be running in the same folder. While DSD+ is decoding
digital voice, FMP will auto-hold on the current RF channel.
If DSD+ is not decoding digital voice, FMP will auto-scan to the
next channel in the scanlist. This behaviour will let you monitor
multiple digital channels, including control or rest channels.
FMP will not get hung up on constant carriers that are not broadcasting
digital voice calls.



reducing CPU load

these techniques are generally only required on low end machines

use economy mode (has minimal detrimental effects on DSD+)

use smaller FFT size

use lower spectrum update rate

completely hide or minimize spectrum window (suspends all FFT calculations)

if acceptable, use wider RF bandpass filters



FMP Frequency Lists


Every time FMP is retuned, FMP will search the CSV files specified in FMP.cfg
for matching in-range frequency records. The CSV files can be created from
government data sources or Internet sites.

Each line in the files holds one TX frequency record or a record for
a TX/RX frequency pair. Each line contains eight fields. Text fields must
use enclosing quote characters. Fields must be separated by a comma and
a space.

Example data:

; TXfreq, RXfreq, Licensee, Location, Latitude, Longitude, first emission mode, second emission mode

461.1625, 466.1625, " example licensee " , " example location " , 35.1028, -80.9420, " 16K0F3E " , " "


When in-range matches are found, FMP displays them, sorted by distance,
in FMP's console window. FMP also passes the closest match to FMP-Map.

FMP-Map is a near-clone of the LRRP.exe program. FMP-Map will display
your monitoring location and the database hits that FMP passes to it.

When accurate and comprehensive frequency lists are provided to FMP,
the transmitter locations that FMP-Map displays will usually show you
the correct signal sources.

Like LRRP.exe, FMP-Map uses a configuration file and the ? key brings up
a help overlay.


--


DSDPlus1p072.zip > DSDPlus.txt

DSD+ 1.072 User Guide
---------------------


Installation
------------

This application can create many audio files and log files,
so consider using a dedicated folder to run it from.

The folder can be on your desktop (desktop\DSDPlus) or
off the root folder (C:\DSDPlus), for example.

After copying the zip file contents to the installation folder,
you should probably create a shortcut on your desktop.
The shortcut should run cmd.exe in the installation folder

Shortcut properties:

Target: %windir%\system32\cmd.exe

Start in: & lt; your DSDPlus folder & gt;

Layout / Window size: Width should be about 100 (120 if displaying timestamps)



Usage/Options Summary
---------------------

Usage:
DSDPlus [options] Decode from audio stream
DSDPlus [options] ? file Decode from .wav file
DSDPlus -h Show help

Options ( [...] = default value):

Display/Logging options:
-- Show command line options in window title
& gt; file Create log file
& gt; & gt; file Append to log file
-t Time stamp log file entries
-T Time stamp log file entries and on screen data
-v & lt; num & gt; Frame information verbosity (0-4) [-v2]

-wsl & lt; v & gt; . & lt; h & gt; Source audio waveform window location [10.10]
-wss & lt; h & gt; . & lt; w & gt; Source audio waveform window size (min 50.200; 0 blocks) [200.300]
-wsp & lt; num & gt; Source audio waveform window update period (10-1000) [100]

-wel & lt; v & gt; . & lt; h & gt; Event log window location [50.50]
-wes & lt; h & gt; . & lt; w & gt; Event log window size (min ?) [400.500]
-weh & lt; num & gt; Event log window font height [15]

-wcl & lt; v & gt; . & lt; h & gt; Channel window location [90.90]
-wch & lt; num & gt; Channel window font height [15]

Input/Output options:
-i & lt; spec & gt; Input audio device (1-255) and channel (M/L/R) [-i1M]

-g & lt; num & gt; Output audio gain (0.001-999; 0=auto) [-g0]

-o & lt; spec & gt; Output audio device (1-255; 0=none) and channel (M/L/R) [-o1]
in/out channels are optional; default=in:mono, out:mode based

-Och & lt; file & gt; Output audio file channel count and name/type [-O DSDPlus.wav]
ch: M=mono,S=stereo,blank=auto; file: .wav or .mp3 (NUL=none)

-I & lt; num & gt; Create new wav/mp3 file every & lt; num & gt; minutes (1440=daily) [-I0]

-M & lt; num & gt; MP3 ABR kbps per channel (8-32) [-M15]

Decoder options:
-p Invert signal polarity (may be required for X2-TDMA and dPMR)
-mp optimize for PSK modulation (will not decode non-PSK)

-fa Auto-detect all protocols / frame types except dPMR [-fa]
-fd Decode D-STAR (no audio)
-fn Decode NXDN4800 (Kenwood NEXEDGE and Icom IDAS)
-fN Decode NXDN9600 (Kenwood NEXEDGE)
-fr Decode DMR/MotoTRBO (TDMA inputs + both output slots)
-f1 Decode P25 Phase 1
-fx Decode X2-TDMA
-fp Decode ProVoice
-fm Enable dPMR decoding (no audio)

-1 Synthesize audio for first DMR timeslot
-2 Synthesize audio for second DMR timeslot

-u & lt; num & gt; Unvoiced speech quality (1-64) [-u3]
-e Auto-mute encrypted voice

Advanced decoder options:
-dr & lt; num & gt; Rolloff filter (1-11; 0=auto) [-dr0]
-dh & lt; num & gt; Hotspot size (1-8; 0=auto) [-dh0]
-ds & lt; num & gt; Scaling factor (55-75; not used with D-Star or ProVoice) [-ds64]
-dd & lt; num & gt; Damping level (1-100; not used with D-Star or ProVoice) [-dd10]
-dv & lt; num & gt; Viewport size (1-30; not used with D-Star or ProVoice) [-dv20]

Active keys:
? Display active keys list in event log window
1 Synthesize audio for first DMR timeslot
2 Synthesize audio for second DMR timeslot
3 Synthesize audio for both DMR timeslots
- Toggle command line options display
| Toggle symbol phase display
B Show/hide background events in event log window
E Toggle auto-muting of encrypted voice
F Forget current system information
N Reset/redisplay neighbor list
P Toggle signal polarity
R Start/stop recording of raw source audio to wav file
S Close/reopen source audio waveform display
W Display window locations
Esc End program

Source Audio:
Right click Pause/unpause source audio waveform display



Run Modes
---------

The program can decode live discriminator audio or recorded .wav files.
Recorded audio files must be 48 or 96 kHz 16 bit mono PCM .wav files.



Logging
-------

-v
-v0 generates minimal output.
Use -v3 or -v4 for maximum data logging.
Program output can be sent to a log file ( DSDPlus & gt; logfile )



Input/Output
------------

-i -o
WaveIn/Out devices are listed at program startup.
Select your devices if you don't want to use the defaults.
Use -o0 to disable output audio.

-O
By default, all synthesized audio is written/appended to DSDPlus.wav
Use -O name.ext to write synthesized audio to another .wav or .mp3 file.
Use -O NUL to disable recording of synthesized audio.

-I
Use -I# to start a new synthesized audio recording file every # minutes.



Decoder Options
---------------

-fa
Using -fa (or nothing) will (usually) auto-decode all supported protocols.
Polarity of signals is auto-detected.
Note: -fa does not enable dPMR detection; -fm must be used to enable dPMR

-fd -fn -fN -fr -f1 -fx -fp -fm
When monitoring a single type of traffic, locking the protocol can provide
slightly better decoding results.
Note: more than one protocol can be enabled via the command line.

-u
Lower values (slightly) reduce CPU load.

-e
Use to enable auto-muting of encrypted voice traffic



Advanced Decoder Options
------------------------

Fine tuning the advanced decoder options can greatly increase decoding rates.

Different systems, protocols, receivers and PC sound devices require unique
fine tuning values.

A 15 to 60 second recording of voice traffic on a target system should be made
and used as the input for tuning runs. Use the 'R' key to make recordings.
Recordings of control channels or rest channels are also useable.

To speed up the tuning process, audio synthesis should be disabled
and the protocol should be locked correctly:

DSDPlus ? rawAudio.wav -o0 -O NUL -f1

A decoding score will be displayed.

Pressing the up arrow will redisplay the previous command line,
which you can then edit and re-run.

Adjust a single parameter to determine which value produces the highest score:

DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr1
DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr2
DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr3
DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr4

When the optimal value for a tuning parameter is determined,
use that value (#) and add another parameter and repeat the tuning steps:

DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr# -dh1
DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr# -dh2
DSDPlus ? rawAudio.wav -o0 -O NUL -f1 -dr# -dh3
...

Repeat until all advanced decoding options have been fine tuned.


The recommended order for adjusting tuning parameters is:

1: Rolloff filtering (-dr)
2: Hotspot size (-dh)
3: Scaling factor (-ds)
4: Damping level (-dd)

Viewport tuning is rarely worth bothering with.

Damping settings do not affect D-Star or ProVoice,
so don't bother tweaking them for those protocols.


You do NOT have to try every value for a tuning parameter:

Rolloff: start at 1 and go up by 1 until the score starts trending down

Hotspot: most signals prefer an even hotspot size (usually 2, sometimes 4);
a few signals prefer an odd hotspot size; testing 2, 3 and 4 will
settle the odd/even question; continue until the score trends down

Scaling: test only 55, 60, 65, 70, 75; best is usually in the 60-65 range

Damping: start testing at 5; increment by 5 or 10; watch the trend...


Check your tuning by re-enabling voice synthesis:

DSDPlus ? rawAudio.wav -f1 -dr# -dh# -ds# -dd# -dv#


-or-

Just use the third party program - dsdtune.


When the optimal values for a system + receiver + sound input is determined,
consider creating a batch file to store the settings:

Local-PD.bat:

DSDPlus -f1 -dr1 -dh3 -ds66 -dd40 -dv20 -O PD.mp3

DMR.bat:

DSDPlus -fd -d21 -dh2 -ds58 -dd5 -dv20 -O DMR.mp3

Then to monitor a specific system, run its batch file.

If you prefer, instead of batch files, you can create desktop shortcuts.


If you scan multiple systems and protocols with a single receiver,
you can run multiple copies of DSDPlus in parallel with each one
protocol-locked and fine tuned as required. Each copy of the program
should write synthesized audio to separate files.



Active Keys
-----------

?

'?' generates a list of keyboard commands in the event log window.

1
2
3

When monitoring conventional DMR systems, you may want to block voice
synthesis for one timeslot. Press 1 or 2 to enable only one timeslot.
Press 3 to enable both timeslots.

-
Display of the command line parameters in the console window title
is enabled/disabled by pressing the '-' key.

|
The symbol phase display in the console window title
is enabled/disabled by pressing the '|' key.

B
The display of background events (like LRRP updates) in the event log window
is enabled/disabled by pressing the 'B' key.

E
Use to enable or disable auto-muting of encrypted voice traffic.

F
Use when switching from monitoring a trunking system to a conventional system,
for example from DMR Con+ to DMR conventional.

N
Press 'N' to force DSD+ to regather and display the current trunking site's
neighbor list in the event log window. Useful for when the neighbor list has
scrolled off the window.

P
Press 'P' to toggle the raw signal polarity. You may need to do this when
decoding X2-TDMA or dPMR signals.

R
'R' starts/stops recording of discriminator audio. Use 'R' to make 60
second source recordings of tuning data. Rename the files to identify
what they are.

S
If the source audio window has been closed, this key will reopen it.

W
When the source audio, event log and channel activity windows have been
placed onscreen where you want them, this key will display their current
locations in the event log window. You can copy these locations to
a batch file or shortcut.

Esc
To terminate real time decoding or .wav file processing, press Esc.



Window Title
------------

The window title area shows the command line parameters used (unless -- specified),
symbol tracking/centering, auto-scaling factor, output audio gain,
symbol rate (2400/4800/9600), and protocol.

During raw audio recording, " & lt; REC & gt; " is displayed.



Data files
----------

DSDPlus.networks

You can populate the DSDPlus.networks file with the network IDs and
network names for NEXEDGE, Connect Plus and Tier III trunking systems.
DSD+ will display the network names when those networks are monitored.
You can add or edit network entries in this file while DSD+ is running.

DSDPlus.sites

The names for each site on a network can be stored in this file.
Some non-networked DMR systems also broadcast system IDs,
so entries for them can also be added to this file.
DSD+ will use the contents of this file to display the name of the
currently monitored site as well as the names of sites in neighbor lists.
You can add or edit site entries in this file while DSD+ is running.

DSDPlus.groups

DSD+ will auto-populate this file with every group ID that is seen.
You can edit this file while DSD+ is running and add names/aliases to
group records.

DSDPlus.radios

DSD+ will auto-populate this file with every radio ID that is seen.
You can edit this file while DSD+ is running and add names/aliases to
radio records. This file replaces the DSDPlus.aliases file; if you
already have a large aliases file, you can use a text editor's
search/replace functionality to convert the contents of your aliases file
to match the format used in the radios file.

DSDPlus.frequencies

DSD+ uses this file to display frequency information when DSD+ is monitoring
a rest channel or control channel. The frequency records will also be
used to control channel steering for trunked voice following.

Note:

DSD+ uses two channel numbers for each DMR RF channel:

Channel #1 = first RF channel, timeslot 1
Channel #2 = first RF channel, timeslot 2
Channel #3 = second RF channel, timeslot 1
Channel #4 = second RF channel, timeslot 2
Channel #5 = third RF channel, timeslot 1
Channel #6 = third RF channel, timeslot 2
...

For all DMR systems (DMR, Cap+, Con+, TIII), only one channel record has
to be added to the DSDPlus.frequencies file for each RF channel.
You can use the channel number that corresponds to timeslot 1 or 2 and
DSD+ will use the same frequency information for the other timeslot.


All of the records in these data files have a protocol field;
DSD+ recognizes the following protocol name strings:

D-Star
IDAS
NEXEDGE48
NEXEDGE96
dPMR
DMR
Cap+
Con+
TIII
P25
ProVoice



DMR TIII handling
-----------------

Tier III control channels broadcast a 14 bit identifier that indicates
the network model (tiny/small/large/huge), network ID, service area
and site number for the current site and for neighboring sites.

Many TIII DMR systems are set up using these programming defaults:

large network (uses a 4 bit NID field)

NID = 13

Service area field length: 5 bits

Site number field length: 3 bits

Physical sites are typically assigned unique area numbers (1, 2, 3, ...)
while their site numbers are all set to 1. So odds are good that any network
you find will have sites with area.site values of 1.1, 2.1, 3.1, etc.

When -v3 or higher is used, DSD+ will display a site's 14 bit " SysCode " in binary.

Example:

CSBK Aloha SysCode=10.1100.00010000

The first two bits encode the network model value. Here, 10 = large model.

The next set of digits encodes the network ID. A zero value is used for NID 1,
so here, 1100 = 12 = NID 13.

The last set of digits encodes the area number and the site number.
Since these two fields do not have a fixed length, DSD+ cannot automatically
decode them. The dividing line between the two fields is selected when the
network is created. This is similar to the variability found in Motorola Type I
fleetmaps.

To determine the correct field sizes, gather as many SysCodes as possible
by monitoring system sites and examining their neighbor lists.

Example:

CSBK Bcast SysCode=10.1100.00010000 Neighbor SysCode=10.1100.00000000, CC=600
CSBK Bcast SysCode=10.1100.00010000 Neighbor SysCode=10.1100.00001000, CC=622

From this small sample we have these SysCodes:

10.1100.00000000
10.1100.00001000
10.1100.00010000

It becomes clear that the SysCodes should be decoded as:

10.1100.00000 000 Model=large NID=13 Area=1 Site=1
10.1100.00001 000 Model=large NID=13 Area=2 Site=1
10.1100.00010 000 Model=large NID=13 Area=3 Site=1

So here, the area length is 5 and the site length is 3.

In the DSDPlus.networks file, an area length value can be appended to TIII
network records, so if the following line is added

TIII, 13, " network name goes here " , 5

DSD+ will use the supplied area length value to properly decode this system's
SysCode fields.

These TIII sites can be added to the DSDPlus.sites file as:

TIII, 13, 1.1, " site name goes here "
TIII, 13, 2.1, " site name goes here "
TIII, 13, 3.1, " site name goes here "

The records in the DSDPlus.frequencies file also reference site numbers;
for TIII sites, use the same area.site format:

TIII, 13, 1.1, 600, 462.0, 0.0, 0
TIII, 13, 2.1, 622, 462.3, 0.0, 0



DSD+ Fast Lane
--------------

Early access to features is being offered through the DSD+ Fast Lane program.

Fast Lane updates are expected to be released every 7 to 30 days.

Some Fast Lane updates WILL have issues/bugs. That is the nature of alpha software.

These are a few of the features that are being worked on:

better tablet support

IDAS/NEXEDGE/Cap+/Con+/TIII trunk voice following

per-call audio recordings

other needed DSD+ upgrades

FMP upgrades

squelch

drift tracking

selectable sampling rates

adjustable windows sizes

TCP client/server mode (eliminates VAC / VB-C)

multiple VFOs

Airspy support

Fully tested public releases will continue, but less frequently,
probably every 4 to 6 months.


In light of the extra workload the Fast Lane program will create,
the DSD+ team is asking Fast Laners for:

US$10 for one year of Fast Lane updates

US$25 for unlimited Fast Lane updates

Donations above these amounts are welcomed, but it's up to you.
We're not looking to get rich here. Funds will be used for things like
needed hardware upgrades.

Funds can be sent our Paypal account (dsdplusfastlane@gmail.com)

Please include a comment that specifies the email address that
your Fast Lane updates should be sent to.

--