Thnaks. I'm still trying to sort the connectivity out.
So, FMP-VC routes signal to VC bat. Got that.
Let me see if I have this correct. To do voice following I need to run two instances of DSD+, FMP-CC, FMP-VC, VC.bat, and CC.bat. That's assuming I don't want to use SDR# for control channel decoding.
I guess you already know how to connect a SDR to DSD+; something like:
a) Airspy > SDR# > VB Cable > DSD+
or
b) DVB-T > SDR# > VB Cable > DSD+
or
c) DVB-T > FMP > VB Cable > DSD+
For trunking, you just need two of them.
CC side can be a), b), or c) [or even d) - a scanner with discriminator tap]
VC side has to be c)
FMP-CC.bat and CC.bat are preconfigured for:
DVB-T#1 > FMP > WaveDevice#2 > DSD+ (-rc / CC role)
FMP-VC.bat and VC.bat are preconfigured for:
DVB-T#2 > FMP > WaveDevice#3 > DSD+ (-rv / VC role)
The assumption is that your Wave devices are:
#1: onboard sound
#2: first VB Cable.
#3: second VB Cable.
If you are using Airspy as CC source, you don't need/use FMP-CC.bat; just run Airspy > SDR# > VB Cable
The -i<num> parameter in CC.bat has to point to that VB Cable
The parameters in FMP-VC.bat and VC.bat just have to point to a different VB Cable
It's the same as if you wanted to run two independent dongle --> DSD+ setups - they have to use different VB Cables
One more dumb question. Which parameter tells FMP-CC to look for Airspy and which tells FMP-VC to look for the dongle?
There is no Airspy support in the batch files. You just run SDR# > VB Cable; no FMP-CC.bat