FreeCalypso > hg > gsm-codec-lib
comparison doc/Binary-file-format @ 302:f469bad44c0e
doc/Binary-file-format: s/gsm_explode/gsmfr_unpack_to_array/
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Mon, 15 Apr 2024 18:45:08 +0000 |
| parents | 7e490a8efe8a |
| children |
comparison
equal
deleted
inserted
replaced
| 301:019eed8b1948 | 302:f469bad44c0e |
|---|---|
| 20 special meaning on Unix systems, but many developers still strongly prefer to | 20 special meaning on Unix systems, but many developers still strongly prefer to |
| 21 have them for psychological comfort. | 21 have them for psychological comfort. |
| 22 | 22 |
| 23 Any gsmx file (FR or EFR) can be dumped in human-readable form with our | 23 Any gsmx file (FR or EFR) can be dumped in human-readable form with our |
| 24 gsmrec-dump utility. This utility turns every read frame from bytes into codec | 24 gsmrec-dump utility. This utility turns every read frame from bytes into codec |
| 25 parameters with gsm_explode() or EFR_frame2params(), and then displays those | 25 parameters with gsmfr_unpack_to_array() or EFR_frame2params(), and then displays |
| 26 parameters in a sensible manner, with a per-frame header line followed by 4 | 26 those parameters in a sensible manner, with a per-frame header line followed by |
| 27 lines of subframe parameters. | 27 4 lines of subframe parameters. |
| 28 | 28 |
| 29 FR and EFR frames are not expected to be mixed in the same stream recording; | 29 FR and EFR frames are not expected to be mixed in the same stream recording; |
| 30 our low-level binary file reading function and gsmrec-dump will grok such mixing | 30 our low-level binary file reading function and gsmrec-dump will grok such mixing |
| 31 just fine, but each higher-level test program (beyond gsmrec-dump) is expected | 31 just fine, but each higher-level test program (beyond gsmrec-dump) is expected |
| 32 to be written for only one codec, either FR or EFR. | 32 to be written for only one codec, either FR or EFR. |
