everything related to duct tape audio suite (dtas)
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Rene Maurer <rmnet@mailc.net>
Cc: dtas-all@nongnu.org
Subject: Re: Adding fade effect
Date: Mon, 12 Jan 2015 22:01:16 +0000	[thread overview]
Message-ID: <20150112220116.GA5148@dcvr.yhbt.net> (raw)
In-Reply-To: <20150112122353.2004b8bc@loco5>

Rene Maurer <rmnet@mailc.net> wrote:
> Hello
> 
> I have two questions concerning sinks:
> 
> 1.
> What is the recommended way to add a fade effect like
> 
> # play song.flac fade 0 15 5"
>
> to a sink?

Sinks have no concept of which song is playing, however you can
edit the source instead using "dtas-sourceedit sox".  Change
(or add) the following line starting with "command:"

command: exec sox "$INFILE" $SOXFMT - $TRIMFX fade 0 =0 5

I think the above fade example requires sox 14.4.x and later,
if you're using an older version you'll probably need to calculate
the "=0" offset based on the length of the track itself, but
also need to take into account the offset set by the $TRIMFX
variable (if you're seeking)

> 2.
> When I change for example the default sink with "dtas-sinkedit default"
> and I then store the edited sink. Is the changed sink directly applied
> or is a dtas-player restart required?

It should be applied immediately upon exiting your editor.  You'll
probably hear an audible gap if you're using ALSA directly as your
device gets restarted.

Again, I recommend editing the source instead of the sink as it won't
restart the device and for most effects, there won't be an audible gap.

I think dtas-sourceedit will get inotify support in the next release.
It'll allow you to hear changes with every save of the $EDITOR and not
have to restart dtas-sourcedit on every change (similar to how the
splitfx YAML file editing works in dtas.git)


  reply	other threads:[~2015-01-12 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 11:23 Adding fade effect Rene Maurer
2015-01-12 22:01 ` Eric Wong [this message]
2015-01-14  4:56   ` Rene Maurer
2015-01-14  9:06     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://80x24.org/dtas/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150112220116.GA5148@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=dtas-all@nongnu.org \
    --cc=rmnet@mailc.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/dtas.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).