Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <erikd@zip.com.au>
To: linux-sound@vger.kernel.org
Subject: Re: sound editing tool for split/join/loop
Date: Mon, 15 Mar 1999 08:10:50 +0000	[thread overview]
Message-ID: <marc-linux-sound-92148613900544@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92147901029802@msgid-missing>

Roy-Anders Larsen wrote:
> 
> I have been looking around for good sound tools and found that sox can do
> a whole lot with sound, however there are a few things I'd like to do to
> sound files that sox will not let me:
> I'd like to be able to split a stereo file into two mono files (one for
> left and one for right), then edit those files then join the two mono
> files into a stereo file.
> I'l like to set the loop in a wav file so the sound repeats itself if I
> play it.
> Does anyone know of any good/not so good way of doing this in linux ?

I have just released a C library for reading and writing sound files.
Using this library, writing an application to split a multichannel
files into mono files would be trivial. Unfortunately the library does 
not yet handle looping although I plan on adding this later.

The library is availaible at:

	http://www.zip.com.au/~erikd/libsndfile/

Hope this helps,
Erik
-- 
+-------------------------------------------------+
     Erik de Castro Lopo     erikd@zip.com.au
+-------------------------------------------------+
"Even in the area of anticompetitive conduct, Microsoft is mainly an
imitator." -- Ralph Nader (1998/11/11)

      reply	other threads:[~1999-03-15  8:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-15  6:15 sound editing tool for split/join/loop Roy-Anders Larsen
1999-03-15  8:10 ` Erik de Castro Lopo [this message]

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

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

  git send-email \
    --in-reply-to=marc-linux-sound-92148613900544@msgid-missing \
    --to=erikd@zip.com.au \
    --cc=linux-sound@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox