# HG changeset patch
# User František Kučera
+ We are pleased to introduce you the new development version of
+ Note: the only difference between
+ See the
+ Please note that this is still a development release and thus the API (libraries, CLI arguments, formats) might and will change.
+ Any suggestions, ideas and bug reports are welcome in our
+ Several earlier tools have non-standard CLI interface and does not conform with
+ In
+ These options may be set globally or for particular relation using the
+ Remaining tools that will be transformed in the same way:
+ A powerful audio system called JACK allows us to
+ build pipelines consisting of audio interfaces, players, recorders, filters and effects…
+ and route sound streams (both PCM and MIDI) through them.
+ MIDI messages can come from keyboards or other hardware MIDI controllers or from MIDI players and other software.
+
+ In the
+ We can join the JACK graph with
+ Besides capturing and playing the MIDI, we can use the
+ Both commands have also the
+ More details in the examples:
+
+ The
+ The reason behind this rename is that Scheme is a programming language and Guile is one of implementations of this language.
+ And we prefer depending on interfaces rather than on particular implementations.
+ Similar situation is
+ The CLI interface of the
+ We can repeat these parameters and generate several relations (that was not possibel in the older version).
+ One relation may be filled with values from STDIN:
+ The CLI interface of the If we have only data in the CSV file (no headers) and thus want to specify them on CLI, the syntax is different: Bash-completion scripts for all tools are provided.
+ Future versions should allow optionally storing the attribute data types in the CSV header and parsing them back (together with the attribute names).
+
+ Instalation was tested on Debian GNU/Linux 10.2.
+ The process should be similar on other distributions.
+
+ Released versions
+
relpipe-out-gui
.
+
+
+
+ relpipe-in-cli
module has changed CLI interface: see details below
+ relpipe-in-csv
module has changed CLI interface: see details below
+ relpipe-out-csv
module has new CLI interface: see details below
+ relpipe-out-tabular
module has new CLI interface: see details below
+ relpipe-tr-guile
was renamed to relpipe-tr-scheme
: see details below
+ relpipe-out-jack
for generating MIDI through JACK: see details below
+ New CLI interfaces
+
+ relpipe-in-cli
, relpipe-in-csv
tools dropped their old CLI interface
+ and got a new one based on named parameters and long options.
+ The relpipe-out-csv
and relpipe-out-tabular
had no parameters in previous versions and now have standard CLI interface.
+ relpipe-out-tabular
we can now optionally omit several parts:
+ --write-record-count false
,
+ --write-types false
,
+ --write-relation-name false
+ and thus simplify the output if we do not need given information.
+ --relation
option with pattern parameter.
+ Thus we may e.g. print some relations with data types and some without them.
+ relpipe-tr-grep
, relpipe-tr-cut
, relpipe-tr-sed
+ and will get standard CLI interface.
+ JACK (MIDI) output module
+
+ relpipe-in-jack
was introduced.
+ This tools allowed capturing the MIDI events from JACK and sending them to the relational pipeline.
+ Now, in v0.17, we introduce the counterpart tool relpipe-out-jack
that reads relational data
+ and sends SysEx messages, MIDI notes and other events to the JACK pipeline.
+ relpipe-out-jack
command.
+ It does not produce anything on STDOUT, it sends MIDI events to JACK instead, so no other output data are needed.
+ relpipe-in-jack
and relpipe-out-jack
+ to tak a snapshot of the JACK graph (connections between ports) and recreate it later.
+ Or establish any new connections or break existing ones.
+ Either through CLI commands of relpipe-in-jack
or through relational data (list of connection and disconnection commands)
+ sent to relpipe-out-jack
.
+ --required-connections
and --connect-to
parameters,
+ so they can react on reaching particular connection count or automatically connect their port to another one specified on the CLI.
+ The bash-completion suggests available port names.
+ Feature overview
+
+ Data types
+
+
+ Inputs
+
+
+ Transformations
+
+
+ Streamlets
+
+
+ Outputs
+
+
+
+ New examples
+
+
+
+ Backward incompatible changes
+
+ relpipe-tr-guile
has been renamed to relpipe-tr-scheme
, so it is necessary to modify existing scripts.
+ However the CLI interface has not been changed, thus it can be simply updated e.g. by:
+ relpipe-tr-sql
: this module is also named after the language (SQL), not after the default implementation (SQLite)
+ and this module can use relpipe-in-cli
tool has been standardized and made consistent with other tools.
+ Now, it uses named parameters instead of cryptic positional ones.
+ The format of the STDIN stream remains unchanged (values separated by \0
byte).
+ --records-on-stdin true
(replaces the old relpipe-in-cli generate-from-stdin
syntax).
+ And the last relation may be filled with values from remaining CLI arguments: --records "1" "Hello" "true" "2" "World!" "false"
.
+ The demo (relpipe-in-cli demo
) has been removed (sample data can be easily generated by setting the CLI arguments).
+ relpipe-in-csv
tool has also been standardized and made consistent with other tools.
+ If we have attribute names on the first line of the CSV file (which is quite common), the usage is same as in previous versions:
+ Installation
+
+ out-gui.qt
and tr-python
require additional libraries and are not built by default.
+
+ Note: there is also relpipe-out-gui
).
+
relpipe-in-cli
module has changed CLI interface: see details below