Difference between revisions of "Ghpsdr3 Bugs"
From HPSDRwiki
(added 3 known problems) |
(+ Category:Ghpsdr3) |
||
| Line 8: | Line 8: | ||
* If dspserver for Rx 1 is started before dspserver for Rx 0, the Rx 1 client will receive spectrum and audio data for Rx 0, and changes in Rx 1 frequency will not result in changes to spectrum or audio data. Once dspserver for Rx 0 has also been started, everything is correct. | * If dspserver for Rx 1 is started before dspserver for Rx 0, the Rx 1 client will receive spectrum and audio data for Rx 0, and changes in Rx 1 frequency will not result in changes to spectrum or audio data. Once dspserver for Rx 0 has also been started, everything is correct. | ||
* When a client disconnects or is terminated, it or a newly running client is not able to connect to the server unless the server is terminated and restarted. This applies to both dspserver-server pairs, and to monitor-server pairs. | * When a client disconnects or is terminated, it or a newly running client is not able to connect to the server unless the server is terminated and restarted. This applies to both dspserver-server pairs, and to monitor-server pairs. | ||
| + | |||
| + | [[Category:Ghpsdr3]] | ||
Latest revision as of 11:06, 11 April 2011
Features not currently implemented in this version
- Transmit has not been implemented but the structure and functions are in the code.
- Bandscope has not been implemented.
Known problems
- Server & dspserver must both be running on Windows, or Linux, not a mix.
- If dspserver for Rx 1 is started before dspserver for Rx 0, the Rx 1 client will receive spectrum and audio data for Rx 0, and changes in Rx 1 frequency will not result in changes to spectrum or audio data. Once dspserver for Rx 0 has also been started, everything is correct.
- When a client disconnects or is terminated, it or a newly running client is not able to connect to the server unless the server is terminated and restarted. This applies to both dspserver-server pairs, and to monitor-server pairs.
