RTSA-Suite PRO File Format (IQ and SPECTRA) Documentation & Sample Files
Quote from AdminTC on 20/06/2024, 21:34Please send us a mission that shows that compression problem since it should be possible to set the compression to "none" in any case.
Please send us a mission that shows that compression problem since it should be possible to set the compression to "none" in any case.
Quote from ChristianEhrlicher on 21/06/2024, 08:42Simply create a new project and add a HTTP Server - no option to specify the compression type there:
Simply create a new project and add a HTTP Server - no option to specify the compression type there:
Quote from fw_dev on 21/06/2024, 12:58It looks like you‘re confuse with the file format and the streming format.
For reference, take a look at https://github.com/AlexandreRouma/SDRPlusPlus/blob/master/source_modules/spectran_http_source/src/spectran_http_client.cppWe‘re using chunked transfers, so the JSON is meta data, the actual payload is not compressed by default.
https://v6-forum.aaronia.de/forum/topic/rtsa-suite-pro-http-streaming/
It looks like you‘re confuse with the file format and the streming format.
For reference, take a look at https://github.com/AlexandreRouma/SDRPlusPlus/blob/master/source_modules/spectran_http_source/src/spectran_http_client.cpp
We‘re using chunked transfers, so the JSON is meta data, the actual payload is not compressed by default.
https://v6-forum.aaronia.de/forum/topic/rtsa-suite-pro-http-streaming/
Quote from ChristianEhrlicher on 24/06/2024, 10:00Quote from fw_dev on 21/06/2024, 12:58It looks like you‘re confuse with the file format and the streming format.
Not really - as I already said I don't think that encoding (on the server side) and decoding (on the client side) a json for every sample is a good idea for high-speed data.
If you call "/stream?format=float" (not float32) you will get the stream as binary stream in the way it's described in the RTSA-File-Format-3.pdf but with enabled compression. After some back and forth I found that "/stream?format=float&compression=0" does the trick - I get the stream in binary and uncompressed. So now I don't have to distinguish between reading from file or from a http stream. Topic solved for me (even it's undocumented).
Quote from fw_dev on 21/06/2024, 12:58It looks like you‘re confuse with the file format and the streming format.
Not really - as I already said I don't think that encoding (on the server side) and decoding (on the client side) a json for every sample is a good idea for high-speed data.
If you call "/stream?format=float" (not float32) you will get the stream as binary stream in the way it's described in the RTSA-File-Format-3.pdf but with enabled compression. After some back and forth I found that "/stream?format=float&compression=0" does the trick - I get the stream in binary and uncompressed. So now I don't have to distinguish between reading from file or from a http stream. Topic solved for me (even it's undocumented).