Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
Need the latest SmartSDR, Power Genius, Tuner Genius and Antenna Genius Software?
SmartSDR v3.9.18 and the SmartSDR v3.9.18 Release Notes
SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
Power Genius XL Utility v3.8.9 and the Power Genius XL Release Notes v3.8.9
Tuner Genius XL Utility v1.2.11 and the Tuner Genius XL Release Notes v1.2.11
Antenna Genius Utility v4.1.8
SmartSDR v3.9.18 and the SmartSDR v3.9.18 Release Notes
SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
Power Genius XL Utility v3.8.9 and the Power Genius XL Release Notes v3.8.9
Tuner Genius XL Utility v1.2.11 and the Tuner Genius XL Release Notes v1.2.11
Antenna Genius Utility v4.1.8
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
speech processor setting (FRS dev only pse)

Walt - KZ1F
Member ✭✭
Somewhere I recall reading the speech processor settings (in SmartSDR) being Normal, DX and DX+, equate to 0,1,2 internally. And, in fact, transmitter status shows this
"speech_processor_enable=1 speech_processor_level=2"
There are places in SmartSDR where tristate controls (those controls having 3 possible states) are explicitly checked in Flexlib for only those valid values, presumably 0, 1, 2, in this case.
However, this is not the case and the valid values for speech processor settings are 0-100 and, if negative set to zero and if > 100 set to 100.
My question is this:
Should the logic in anyone's bridge logic between a UI and the radio check solely for values, 0-2 OR do values greater than 2 have significant value? In other words, is there a use case for a value of 3 or 50 or 100?
"speech_processor_enable=1 speech_processor_level=2"
There are places in SmartSDR where tristate controls (those controls having 3 possible states) are explicitly checked in Flexlib for only those valid values, presumably 0, 1, 2, in this case.
However, this is not the case and the valid values for speech processor settings are 0-100 and, if negative set to zero and if > 100 set to 100.
My question is this:
Should the logic in anyone's bridge logic between a UI and the radio check solely for values, 0-2 OR do values greater than 2 have significant value? In other words, is there a use case for a value of 3 or 50 or 100?
0
Answers
-
I think the fact that you can set it to higher values is a holdover from the speech processor iteration before the current one. It probably should be checked in our code. I don't know what would happen if you set it higher, but needless to say it is undefined.0
-
Thanks Eric,. I'll make that change in xpslib.0
-
Tim/Eric, you guys can mark this answered. Thanks.1
Leave a Comment
Categories
- All Categories
- 322 Community Topics
- 2.1K New Ideas
- 587 The Flea Market
- 7.8K Software
- 6.2K SmartSDR for Windows
- 164 SmartSDR for Maestro and M models
- 390 SmartSDR for Mac
- 255 SmartSDR for iOS
- 245 SmartSDR CAT
- 177 DAX
- 368 SmartSDR API
- 9K Radios and Accessories
- 11 Aurora
- 144 FLEX-8000 Signature Series
- 7.1K FLEX-6000 Signature Series
- 902 Maestro
- 50 FlexControl
- 854 FLEX Series (Legacy) Radios
- 860 Genius Products
- 443 Power Genius XL Amplifier
- 303 Tuner Genius XL
- 114 Antenna Genius
- 272 Shack Infrastructure
- 192 Networking
- 435 Remote Operation (SmartLink)
- 135 Contesting
- 709 Peripherals & Station Integration
- 131 Amateur Radio Interests
- 935 Third-Party Software