public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: <blinux-list@redhat.com>
Subject: Re: Technical Question (was Digital Talking Book Standard )
Date: Tue, 20 Nov 2001 13:36:49 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0111201328261.22650-100000@xanadu.home> (raw)
In-Reply-To: <200111201616.fAKGGAa95386@dc.cis.okstate.edu>

On Tue, 20 Nov 2001, Martin G. McCormick wrote:

> 	Yes, I am a bit slow, but I am catching on.  I definitely
> need to understand more about time scale shifting methods and how
> to accomplish them without adding distortion.
> 
> 	Each digit represents a moment in time and we can make
> things appear to speed up or slow down by intelligently inserting
> or deleting  information.

Exactly.

> 	If we do it on a sample by sample basis, we can make the
> recording appear to speed up or slow down with the expected pitch
> changes.  If we do it on a wave form by wave form basis, we can
> appear to keep the same pitch, but speed up the tempo or, for
> that matter, we can add extra wave forms and stretch out the
> syllables or whatever and slow them down.

Right.  And therefore you can accurately find out where the waveform 
boundaries are when dealing with digital sound.  The technique consist of 
finding the best correlation between the original signal with a small 
moving window 
of the same signal inside a limitted range.  You then get the exact sample 
position where the current waveform is likely to start and end.  Then you 
only need to duplicate or remove that waveform once in a while with a 
certain ratio to create the desired effect.

> 	The old pitch correcting devices like the one I presently
> use to read magazines butcher the sound because they aren't smart
> enough to make sure the next snippet of sound starts at the same
> place on the wave form that the previous one ended so we get that
> characteristic gravelly sound at high rates.

That's because those devices just don't care about signal periods at all, 
and tend to duplicate or remove an arbitrary fixed duration of signal.  


Nicolas




  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Martin G. McCormick
 ` Nicolas Pitre [this message]
  -- strict thread matches above, loose matches on Subject: below --
 Martin G. McCormick
 ` Nicolas Pitre
   ` Janina Sajka

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=Pine.LNX.4.33.0111201328261.22650-100000@xanadu.home \
    --to=nico@cam.org \
    --cc=blinux-list@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).