All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Davis <pbd@op.net>
To: Tim Goetze <tim@quitte.de>
Cc: Gerald Grabner <gerry@mechanik.tu-graz.ac.at>,
	alsa-devel@alsa-project.org
Subject: Re: Easy question: ppq and tempo
Date: Fri, 24 May 2002 10:37:49 -0400	[thread overview]
Message-ID: <200205241435.QAA00530@alsa.alsa-project.org> (raw)
In-Reply-To: Your message of "Fri, 24 May 2002 16:18:16 +0200." <Pine.LNX.4.21.0205241612070.761-100000@summer.quitte>

>>"ppq" stands for "parts per quarter". as the header file suggests
>>without much explanation, its length of a quarter note expressed in
>>clock ticks. if the meter is 4/4 and the tempo is 120bpm, then a
>>quarter note lasts 0.5 seconds. if the clock used for timing ticks 100
>>times per second, there are 50 clock ticks per quarter note, so
>>ppq=50.
>
>though usually it will be a number divisible by 3 and 4 to make
>triplets and even beats alike coincide with integer ticks. cubase
>on the atari used to set this to 192, though some do prefer 480 or
>even more to allow for minute timing ('groove') adjustments.

where "it" is the clock ticks per second. 

thanks tim, i had always wondered why 192 or 480 etc. was used, and
never knew until now :)

--p

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

  reply	other threads:[~2002-05-24 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200205241400.QAA27210@mailin.webmailer.de>
2002-05-24 14:18 ` Easy question: ppq and tempo Tim Goetze
2002-05-24 14:37   ` Paul Davis [this message]
2002-05-24 17:35     ` Frank van de Pol
2002-05-31 16:44       ` Gerald Grabner
2002-05-24  7:57 Gerald Grabner
2002-05-24 10:48 ` Tim Goetze
2002-05-24 14:03   ` Paul Davis
2002-05-24 14:47     ` Richard Bown

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=200205241435.QAA00530@alsa.alsa-project.org \
    --to=pbd@op.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=gerry@mechanik.tu-graz.ac.at \
    --cc=tim@quitte.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.