| Age | Commit message (Collapse) | Author |
|---|
|
The functionality of the preliminary 'i2s_dump' PD is now available
in the proper 'i2s' PD, via the OUTPUT_BINARY mechanism that frontends
can use to dump decoded data (in various formats) to a file, or pipe it
into other applications, and so on.
Old sigrok-cli example usage:
$ sigrok-cli -i 2ch-16bit-16khz.sr \
-P i2s:sck=0:ws=1:sd=2,i2s_dump:filename=foo.wav
$ aplay foo.wav
New sigrok-cli example usage:
$ sigrok-cli -i 2ch-16bit-16khz.sr \
-P i2s:sck=0:ws=1:sd=2 -B i2s=wav > foo.wav
$ aplay foo.wav
New sigrok-cli example usage (piping into other applications):
$ sigrok-cli -i 2ch-16bit-16khz.sr \
-P i2s:sck=0:ws=1:sd=2 -B i2s=wav | aplay -
|
|
|
|
This automatically figures out the files to install for each protocol
decoder, without involving autotools.
All python files (filenames ending in .py) are always installed. If a
protocol decoder requires installation of a non-python file, a small
file called 'config' can be created in that protocol decoder's
directory, with the following content:
# comments are ok
extra-install vendorlist.txt commands.txt
|
|
|
|
|
|
|
|
This stacks of top of the 'i2s' decoder and outputs the audio data to
file (or stdout) in various formats. Currently only WAV is supported.
This is work in progress, it has various hard-coded assumptions.
|
