Here’s a really useful formula for calculating where your cue marker is. After writing some music 2 days ago, and leaving the play button on, I wondered just how far to the right my cue marker was… so:
speed = 145 bpm
145 bpm / 4 beats/bar = 36.25 bars/min
1 bar = 58 pixels (at current zoom level)
58 px/bar * 36.25 bars/min= 2102.5 px/min
screen resolution = 72 dpi
2102.5 px/min / 72 dpi = 29.2 inch/min
inch to cm convertion = 2.54 cm/inch
29.2 inch/min * 2.54 cm/inch = 74.17 cm/min
time = 2 days = 2880 min
distance = speed * time = 74.17 * 2880 = 213,609.6 cm = 2.13 km
My cue point is 2.13 km off to the right… hope no one runs into it.
So here’s a handy formula for when you need to work this out
distance in km = bpm / (beats/bar) * (pixels/bar) / dpi * (cm/inch) * time / (cm/km)
If someone feels like it, I would like to know the formula for the following situation: If a Vinyl record is infinitely large, and you are playing it backwards from the end of the record on a turntable with a infinitely long telescopic arm, how far from the centre is the needle at time x. That would be a very useful formula too!
Clever. Wasn’t surprised to see this guy is a regular at flash conferences, and other similar presentations of high geek value.
Synthesizing in flash? Eqing in flash? The sound byte gets closer to the visual byte. I have been dreaming of this… let alone the bitmap transitions…
Bouncing balls dropping from the ceiling create an audio experience when you place reflectors in their way. Pitch is relative to ball speed. You can tweak a few of the environment variables, and mess around.
