Date | Commit message (Collapse) |
|
Followup-to commit 403ed90e2e7bed3e017938d76e17037b0d5059b6
(replaygain uses the "gain" effect instead of "vol")
The `gain' effect seems superior as it can "see" across the effects
chain to take into account extra/lost headroom.
|
|
While the Ruby Hash class is ordered in 1.9+, the YAML
specifications do not specify hashes as ordered by default.
Thus we must explicitly declare ordering via !omap for
interopability with non-Ruby tools.
This makes the YAML output of dtas-sourcedit and dtas-sinkedit
slightly more verbose
Users of dtas-splitfx are also encouraged to declare !omap
when creating their YAML files for interoperability.
Ordering env is important because any implementation of
built-in variable expansion is dependent on it.
|
|
While we're at it, document the splitfx manpage and
make the example suitable for tests.
|
|
The "-l" and "-r" switches used by the sox ladspa effect
(for latency compensation and replicate, respectively)
are not available until sox v14.4.2, so avoid using it
since it can fail tests on common systems today.
|
|
This should allow users to setup effects in a more standardized
fashion and avoid needing to specify a "command:" field in their
splitfx YAML files in the general case.
|
|
This allows splitfx users to test CUE breakpoints and run
file-specific effects without interrupting their normal flow.
|
|
This seems to be working out nicely. Having a basic integration
test should be enough to get us started for now.
|
|
This is lacking tests and documentation, but it works from
a old trivial sample I had from a recording I previously
split using plain POSIX shell
splitfx is like make(1) for splitting and minor audio
editing. It also allows any number of effects.
|