everything related to duct tape audio suite (dtas)
 help / color / mirror / code / Atom feed
From: James Rowe <jnrowe@gmail.com>
To: dtas-all@nongnu.org
Subject: Re: Unwanted trim after source edit
Date: Sat, 23 May 2020 15:09:29 +0100	[thread overview]
Message-ID: <20200523140929.p7af4yqrvvnqs3k4@gmail.com> (raw)
In-Reply-To: <20200523140525.yprijrqoq6kwilll@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

[Resent to the list, because I’m a fool.  Rene, sorry if you get
a dupe.]

* Rene Maurer (rm@cumparsita.ch) wrote:
> Do I use the source in a completely wrong way (should I use sink instead?) or
> what is the reason for this trim?

  The trim exists because sox is restarted when you edit the source in
order to apply your changes, you can see this by checking the PID of the
running sox command after editing.  In order to take in to account your
current position in the track when you edited the source the trim effect
is added to continue playback from the right place.

  You can see it in action if you:

    dtas-ctl play_pause; dtas-ctl play_pause; dtas-ctl current

  In the large YAML dump it emits you’ll see the TRIMFX setting, and
also current_initial value.

> Do I use the source in a completely wrong way (should I use sink instead?) or
> what is the reason for this trim?

  So — assuming I’ve read your mail correctly — you’ve done nothing
wrong at all and are just noticing an implementation detail.

Thanks,

James

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-05-23 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 11:05 Unwanted trim after source edit Rene Maurer
     [not found] ` <20200523140525.yprijrqoq6kwilll@gmail.com>
2020-05-23 14:09   ` James Rowe [this message]
2020-05-23 15:19     ` Rene Maurer

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=20200523140929.p7af4yqrvvnqs3k4@gmail.com \
    --to=jnrowe@gmail.com \
    --cc=dtas-all@nongnu.org \
    /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).