Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
The latest SmartSDR Software:
SmartSDR v4.1.5 | SmartSDR v4.1.5 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes
The latest 4O3A Genius Product Software:
The latest 4O3A Genius Product Software and Firmware
SmartSDR v4.1.5 | SmartSDR v4.1.5 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes
The latest 4O3A Genius Product Software:
The latest 4O3A Genius Product Software and Firmware
How to Receive Technical Support::
If you are needing assistance with FlexRadio products, 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.
If you are needing assistance with FlexRadio products, 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.
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
- 388 Community Topics
- 2.2K New Ideas
- 658 The Flea Market
- 8.4K Software
- 156 SmartSDR+
- 6.5K SmartSDR for Windows
- 186 SmartSDR for Maestro and M models
- 439 SmartSDR for Mac
- 275 SmartSDR for iOS
- 265 SmartSDR CAT
- 204 DAX
- 386 SmartSDR API
- 9.4K Radios and Accessories
- 53 Aurora
- 297 FLEX-8000 Signature Series
- 7.2K FLEX-6000 Signature Series
- 970 Maestro
- 58 FlexControl
- 866 FLEX Series (Legacy) Radios
- 944 Genius Products
- 471 Power Genius XL Amplifier
- 347 Tuner Genius XL
- 126 Antenna Genius
- 306 Shack Infrastructure
- 215 Networking
- 468 Remote Operation (SmartLink)
- 142 Contesting
- 811 Peripherals & Station Integration
- 144 Amateur Radio Interests
- 1.1K Third-Party Software
