everything related to duct tape audio suite (dtas)
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: James Rowe <jnrowe@gmail.com>
Cc: dtas-all@nongnu.org
Subject: Re: Effects that change duration of a track
Date: Mon, 27 Jan 2020 21:18:38 +0000	[thread overview]
Message-ID: <20200127211838.GA32493@dcvr> (raw)
In-Reply-To: <20200122002243.7u5anj3r7zt7cue4@gmail.com>

James Rowe <jnrowe@gmail.com> wrote:
> Hi,
>   So, you’re laying in bed listening to a podcast with an effect
> that modifies playback length, such as sox’s ``tempo -s 1.9``.  How do
> people deal with dtas-console displaying the “wrong” duration¹?  Or, is
> there a correct way to manage effects that modify track times?

It's a known problem.  dtas-player_effects(7) manpage does warn
against effects which modify track times.

dtas would have to know about which sox effects which could
alter track time, and there's also LADSPA plugins, too...
Things get complicated really fast.

Another solution would be similar to what we do for trim/volume
ReplayGain and expose a parameter/effect which dtas itself will
use to inject "tempo" into the effects chain.  It covers the
majority of cases like yours, I think; but doesn't cover effects
like "splice" or "vad"

> Thanks,
> James
> 1. Laying in bed looking at dtas-console in termux on a phone screen is
>    hard enough without having to do mental arithmetic ;)

Heh.  I just never cared about track times too much when just
listening to what I'm listening to.

  reply	other threads:[~2020-01-27 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22  0:22 Effects that change duration of a track James Rowe
2020-01-27 21:18 ` Eric Wong [this message]
2020-01-30 16:49   ` James Rowe

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:

  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=20200127211838.GA32493@dcvr \
    --to=e@80x24.org \
    --cc=dtas-all@nongnu.org \
    --cc=jnrowe@gmail.com \


* 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


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).