You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everything is represented under the hood as complex float 32, but it's not a super quick addition because there's some code involved in fetching bytes from a file that may need *2 removed for real-valued signals.
Also every datatype needs a "c" or "r" so have the parser spit out an error if it finds a recording without either, and remove ones like i8 and u8 from list
So, for example, the string "cf32_le" specifies "complex 32-bit floating-point samples stored in little-endian", the string "ru16_be" specifies "real unsigned 16-bit samples stored in big-endian", and the string "cu8" specifies "complex unsigned byte".
The text was updated successfully, but these errors were encountered:
777arc
changed the title
Feature Request
Feature Request - support for real valued recordings
Sep 18, 2023
Everything is represented under the hood as complex float 32, but it's not a super quick addition because there's some code involved in fetching bytes from a file that may need *2 removed for real-valued signals.
Also every datatype needs a "c" or "r" so have the parser spit out an error if it finds a recording without either, and remove ones like i8 and u8 from list
From SigMF:
So, for example, the string "cf32_le" specifies "complex 32-bit floating-point samples stored in little-endian", the string "ru16_be" specifies "real unsigned 16-bit samples stored in big-endian", and the string "cu8" specifies "complex unsigned byte".
The text was updated successfully, but these errors were encountered: