katheryn.swynford at gmail.com
Sun Feb 15 18:21:03 CST 2009
While looking for info on HC's old way of doing scripted musical generation,
I came across this page:
Apparently, it's some sort of Rev port of an earlier HC work.
>From the parent page:
*String Quartet Pi / Kenji Kojima*
* The music was created from the constant π (Pi*) to 3,000 decimal places. I
believed many artists and scientists have tried same idea before. I should
rather say "String Quartet Pi" was one of interpretations of Pi music. The
constant was always same, however as the result of each music by an
interpretation was accompany sense of beauty of composers.
One of purposes of this creation was beyond human being performance. I hope
you can enjoy the music and the reading process of the data. 2004, Kenji
* Click on the top-left of QuickTime controller and listen it.
*A SEED OF THE MUSIC <http://www.kenjikojima.com/pi/htmlFiles/seed.html>:*
* The constant Pi is used from the first number 3 to until under the point
3,000 decimal places.
*MUSICAL NOTATION /
* The score adopted with same musical notation that was play command of
HyperTalk a script language of Apple's HyperCard. And it was extended to
other MIDI functions that was PMD (Play Midi Data). A number plus one is a
step of chromatic scale is upped. For Ex. If the number 3 is C, 4 is C#. The
center C is set to the absolute pitch 60 for the application player* which
plays MIDI instruments by numeric steps. C# that is next of center C is
absolute pitch 61. Next D is 62.
On Thu, Feb 12, 2009 at 1:13 AM, René Micout <rmicout at online.fr> wrote:
> Thank you VERY much Kurt !!!
> I will look it (that ?) this week-end. If there are still "dark" ("obscur"
> in french), I will ask you some explanation.
> Le 12 févr. 09 à 01:02, Kurt Kaufman a écrit :
> "...I know your work and I appreciate it, but.... but...
>> It is a little bit complex for me :-(
>> I dont understand binaryEncode(etc...)
>> and also the bridge between Revolution (code) and Midi..."
>> I know it looks complicated. I think it would take me a while to figure
>> it out again, even though I commented the scripts fairly heavily!
>> But once you understand what makes up a MIDI file, which parts are
>> constant (always the same in every MIDI file of that type), and which parts
>> are variable (different in each music track), you see that it is not that
>> complex. If you look at the MIDI format document, you'll see the various
>> parts described in the order in which they appear.
>> At least MIDI files are generally not very big, so if you want to open
>> them up using a Hex editor, you're not scanning a tremendous amount of data.
>> To that end I would use MIDI Builder to create a MIDI file with a single
>> note, and then take a look using HexEdit:
>> (there's a French version, too)
>> Now compare what's in the MIDI format document with what you see in the
>> Rev's binaryEncode function is called after all of the various parts of
>> the data have been set up, as most of the MIDI data cannot be represented by
>> ascii (it's not printable, for the most part). But the binaryEncode
>> function is automatic; you just have to give the function its data and the
>> proper parameters, and Rev does the rest. Rev makes it easy: You can simply
>> add the successive bytes of encoded data "after" what's already there. The
>> file can be created in a fraction of a second and played almost immediately.
>> Rev's QT player object handles most of the work, you just have to send it
>> data that it understands.
>> Hope this helps,
>> further info:
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode