2 commits

Author	SHA1	Message	Date
Henry Gabryjelski	1a7267ca53	Fix .PM3 traces that exceed single-byte range ... This was done programmatically using python. Files with a range that fell outside of [-128,127], but which would fit into that range, were offset by the noted amount to ensure the file woul now fit within range [-128,127]. This allows the trace files to be converted to one-byte-per-sample binary format, for example. offset | filename -----|----- `-14` | `lf_Q5_mod-manchester.pm3` `-14` | `lf_Q5_mod-nrz.pm3` `-10` | `lf_Q5_mod-fsk1.pm3` `-15` | `lf_Q5_mod-biphase.pm3` `-9` | `lf_Q5_mod-fsk2.pm3`	2024-09-16 23:05:15 -07:00
Philippe Teuwen	b4058bc72c	reorg traces	2020-09-29 17:35:48 +02:00

Renamed from traces/modulation-fsk2.pm3 (Browse further)