Sponsored Content
Full Discussion: A metronome...
Operating Systems OS X (Apple) A metronome... Post 302947214 by bakunin on Tuesday 16th of June 2015 12:01:21 PM
Old 06-16-2015
You use "tick" and "tock" alternating. My suggestion is to introduce another parameter "bar". It should be able to take values 2-13. Have the "tick" only on beat 1 for every bar, e.g.:

Bar=2 tick tock tick tock ....
Bar=3 tick tock tock tick tock tock ...
Bar=4 tick tock tock tock tick tock tock tock ....

etc..

The rationale is that any "bar" has some "inner structure". For instance a 4/4 bar is not just a sequence of 4 equal beats but in fact the first and third beats are stronger than 2 and 4 and 1 is even stronger than 3. For this reason "3/4" and "6/8" may look like the same fracture but in fact the beats are sounding quite differently (when higher numbers denote more stress on a beat 3/4 is "2 1 1 2 1 1 ..." whereas 6/8 is usually "3 1 1 2 1 1 3 1 1 2 1 1 ...". It makes sense to help the user of the metronome recognize the 1-beat (usually the stroke with the most significance) in every bar by making it sound differently.

Why 2-13: the longest metrum of any significance in practical music is 13/8, used for instance in "Blue Rondo à la Turk" by the Dave Brubeck Quartet (it is sometimes denoted as 9/8 // 4/4 alternating metrum, but i think it is a genuine 13-stroke bar structure). 12/8 is commonly used for slow Blues with the "triplet shuffle" feeling,

I hope this helps.

bakunin
These 3 Users Gave Thanks to bakunin For This Post:
 
machid(1)						      General Commands Manual							 machid(1)

NAME
machid: hp9000s200, hp9000s300, hp9000s400, hp9000s500, hp9000s700, hp9000s800, hp-mc680x0, hp-pa, pdp11, u370, u3b, u3b10, u3b2, u3b5, vax - provide truth value about processor type SYNOPSIS
DESCRIPTION
The following commands return a true value (exit code 0) if the a processor type matches the command name. Otherwise a false value (exit code nonzero) is returned. These commands are commonly used within makefiles and shell procedures to improve portability of applications (see make(1)). +-----------+-------------------------++--------+--------------------------+ |Command | True for ||Command | True for | +-----------+-------------------------++--------+--------------------------+ |hp9000s200 | Series 200 ||pdp11 | PDP-11/45 or PDP-11/70 | |hp9000s300 | Series 300 ||u3b | 3B20 computer | |hp9000s400 | Series 400 ||u3b2 | 3B2 computer | |hp9000s500 | Series 500 ||u3b5 | 3B5 computer | |hp9000s700 | Series 700 ||u3b10 | 3B10 computer | |hp9000s800 | Series 800 or 700 ||u370 | IBM System/370 computer | |hp-mc680x0 | Series 200, 300, or 400 ||vax | VAX-11/750 or VAX-11/780 | |hp-pa | Series 700 or 800 || | | +-----------+-------------------------++--------+--------------------------+ EXAMPLES
Given a shell script that must behave differently when run on an HP 9000 Series 700 or 800 system, select the correct code segment to be executed: WARNINGS
always returns true on both Series 800 and Series 700 systems. Therefore, when using this command in scripts to determine hardware type, always use both and in the appropriate sequence to ensure correct results (see machid(1) will no longer provide support for future machines beyond the Series 800 and Series 700 systems. Decisions should be based on the hardware and software configuration information returned by getconf(1). SEE ALSO
getconf(1), make(1), sh(1), test(1), true(1). machid(1)
All times are GMT -4. The time now is 05:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy