DSDPlus DSD+ Event Log Input Setting Keeps Changing

[CanesFan95]

Everytime I open DSD+, the input keeps defaulting to to "Use Direct FMPx Linking". I always have to keep changing it back to "Use FMPx TCP Linking". So how can I make it stay on "Use FMPx TCP Linking"?

And in the Output menu, I want it to always be "Synthesize All Digital Voice", but it keeps going to "No Digital Voice Synthesis" by default.

 

[cg]

Without knowing your batch file or what version you are using I can't say for sure but the options to put in the DSDPlus startup batch file include:

Input/Output options:
-i<spec> Input audio device (1-255) and channel (M/L/R)
-i<linkID> FMPA/FMPP/FMP24 direct link ID (256-65535) [20001]
-iT<[addr:]port> FMPA/FMPP/FMP24 TCP link IPv4 address and port number (256-65535)

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

 

[RaleighGuy]

Everytime I open DSD+, the input keeps defaulting to to "Use Direct FMPx Linking". I always have to keep changing it back to "Use FMPx TCP Linking". So how can I make it stay on "Use FMPx TCP Linking"?

And in the Output menu, I want it to always be "Synthesize All Digital Voice", but it keeps going to "No Digital Voice Synthesis" by default.

Post the batch file (should only be one line) and DSD+ version and we might be able to help you better

 

[CanesFan95]

Using version 2.289. Here's the batch file:

START CMD /c "FMPA -rc -i1 -o20001 >FMPA_CC_Trunking.log -b12.5 -L10 -M10 -V10"

START CMD /c "FMPA -rv -i2 -o20002 >FMPA_VC_Trunking.log -b12.5 -L10 -M10 -V10"

START CMD /c "DSDPlus -rc -i20001 -v2 >CC_Trunking.log -T -E -e -_1"

START CMD /c "DSDPlus -rv -i20002 -v2 >VC_Trunking.log -T -E -e -_15"

 

[slicerwizard]

Well, it's right there in your batch files. You're specifying direct linking in every line. And what's wrong with direct linking?

 

[CanesFan95]

Well, I thought the -o20001 type command were considered TCP? For some reason, DSD+ basically doesn't decode anything until I change the Input setting to Use FMPx TCP Linking. This is the same .bat file I've been using for a while, but this has been a recent problem that suddenly started happening.

 

[CanesFan95]

Other issues I've been having is many times when I run the .bat file, I get this error saying it can't open the device). Then if I close out of DSD+ and re-open it right away, then it works fine.



But I still have to keep changing it back to Use FMPx TCP Linking and sometimes must also select Synthesize All Digital Voice again.

Another more minor thing is, when I er-position the FMPA CC scope window, it doesn't remember where I last put it and it reverts back to the old location next time I open DSD+.

 

[a417]

This is the same .bat file I've been using for a while, but this has been a recent problem that suddenly started happening.

So you're using an older batchfile which was tailored to an older version of the program, and don't know why an updated program behaves differently?

 

[CanesFan95]

So we must change the .bat file with each update? How do we know what changes to make?

 

[RaleighGuy]

So we must change the .bat file with each update? How do we know what changes to make?

Not always required, it depends on the type of updates made to the program. The best way to know what has changed is to read the NOTES.TXT file in the zip file each time (should be in your DSD+ folder now) and watch for update announcements here in the forums.

 

[CanesFan95]

OK, thanks. So what's wrong with my current file?

 

[a417]

Linking". So how can I make it stay on "Use FMPx TCP Linking"?

change your .bat to specify TCP linking now, as were specifically telling it to use direct linking...if that's what works for you. YMMV.

START CMD /c "FMPA -rc -i1 -oT20001 >FMPA_CC_Trunking.log -b12.5 -L10 -M10 -V10"
START CMD /c "FMPA -rv -i2 -oT20002 >FMPA_VC_Trunking.log -b12.5 -L10 -M10 -V10"
START CMD /c "DSDPlus -rc -iT20001 -v2 >CC_Trunking.log -T -E -e -_1"
START CMD /c "DSDPlus -rv -iT20002 -v2 >VC_Trunking.log -T -E -e -_15"

 

[slicerwizard]

Well, I thought the -o20001 type command were considered TCP?

C:\DSDPlus>FMPA -h
FMPA *2.37*

Usage:
FMPA [options] Normal operation
FMPA -h Show help

Options:
-i<num> Airspy / Airspy Mini device number (1-255) [-i1]
-o<num> Output audio device (1-255) [-o1]
-o<linkID> Output audio DSD+ Link ID (256-65535)
-oT<port> Output audio TCP port (256-65535)
...


C:\DSDPlus>dsdplus -h
DSD+ 2.289
Current working directory is "C:\DSDPlus"
...
Input/Output options:
-i<spec> Input audio device (1-255) and channel (M/L/R)
-i<linkID> FMPA/FMPP/FMP24 direct link ID (256-65535) [20001]
-iT<[addr:]port> FMPA/FMPP/FMP24 TCP link IPv4 address and port number (256-65535)
...

For some reason, DSD+ basically doesn't decode anything until I change the Input setting to Use FMPx TCP Linking. This is the same .bat file I've been using for a while, but this has been a recent problem that suddenly started happening.

I'd be willing to bet money that it started when you began using an up to date DSD+ with a not up to date FMPA.

 

[CanesFan95]

So what are these "link IDs" and how do we know what number to use?

 

[CanesFan95]

change your .bat to specify TCP linking now, as were specifically telling it to use direct linking...if that's what works for you. YMMV.

When I run that, it gives an error:

 

[a417]

C:\DSDPlus>FMPA -h
FMPA *2.37*
<snip>
Options:
-i<num> Airspy / Airspy Mini device number (1-255) [-i1]
-o<num> Output audio device (1-255) [-o1]
-o<linkID> Output audio DSD+ Link ID (256-65535)
-oT<port> Output audio TCP port (256-65535)
<snip>

I'd be willing to bet money that it started when you began using an up to date DSD+ with a not up to date FMPA.

...

When I run that, it gives an error:

View attachment 99029

...and it should, it's an older version.

 

[CanesFan95]

My FMPA version is 2.36. So is that the wrong version?

 

[CanesFan95]

Oh, and another question, while I'm at it. The command -_<num> Minimize windows at startup; bitmapped. How do you tell which window is what number? And is there a way to make it remember your last window positions for the next time?

Thanks.

 

[BM82557]

FMPA 2.37

Added direct connection mode; see FMP24 notes above.

Added DLL files integrity checks; see FMP24 notes above

 

[slicerwizard]

My FMPA version is 2.36. So is that the wrong version?

When the rest of us are running 2.37, it's kind of a given.

Oh, and another question, while I'm at it. The command -_<num> Minimize windows at startup; bitmapped. How do you tell which window is what number?

Experiment? Easy enough to try each of -_1 -_2 -_4 -_8 and see what window gets minimized.

And is there a way to make it remember your last window positions for the next time?

It? Is it DSD+? If so, you don't have to do anything for it to remember window positions. Just move them and they'll be there next time.