sox-users@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Zsolt Ero <zsolt.ero@gmail.com>
To: sox-users@lists.sourceforge.net
Subject: Re: splice not working correctly
Date: Mon, 23 Dec 2019 23:51:58 +0100	[thread overview]
Message-ID: <CAKw-smA8K4x+P8tQyVWeELdeXvzyVFyTZeODxMvMAa7RS2GO+A@mail.gmail.com> (raw)
In-Reply-To: <CAKw-smB9eNin2mtwsyVvAxXT=ZstaJqqxzjMy44TTcfqHMGU=w@mail.gmail.com>

It's very visible with silence as the second track.

sox -n -r 96000 -c 2 silence.wav trim 0 7
sox in.wav in_trim.wav trim 0 6
sox in_trim.wav silence.wav out.wav splice -q 5,1

There is this echo / duplication starting already at 3-4 seconds.


On Mon, 23 Dec 2019 at 23:43, Zsolt Ero <zsolt.ero@gmail.com> wrote:
>
> Hello,
>
> I'd like to use split to mix two slightly different tracks for AB
> testing purposes. I'd like to have 0..5 second from track A and 5..10
> seconds from track B, etc. 10..15 track A, 15..20 track B.
>
> I'd be very important to make sure that it doesn't change the signal
> in any way, as in if I run it with identical tracks, I'd get back the
> original track.
>
> My problem is that it's not what is happening. For validation I'm
> using a big excess value = 1 sec + -q for equal cross fade.
>
> So far here are my basic CLI arguments:
> sox A.wav tmp/A_0.wav trim 0 6
> sox A.wav tmp/A_5.wav trim 4 7
> sox tmp/A_0.wav tmp/A_5.wav out.wav splice -q 5,1
>
> Can you correct me in how to use splice correctly? The way I'm using
> it I get a bit of an echo / duplication at the end of the first file,
> just before the mixing point.
>
> Zsolt


_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users

  reply	other threads:[~2019-12-23 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 22:43 splice not working correctly Zsolt Ero
2019-12-23 22:51 ` Zsolt Ero [this message]
2019-12-24 14:00 ` Jeremy Nicoll - ml sox users
2020-04-18 11:19 ` Jan Stary

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-list from there: mbox

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

  List information: https://lists.sourceforge.net/lists/listinfo/sox-users

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

  git send-email \
    --in-reply-to=CAKw-smA8K4x+P8tQyVWeELdeXvzyVFyTZeODxMvMAa7RS2GO+A@mail.gmail.com \
    --to=sox-users@lists.sourceforge.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/mirrors/sox.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).