1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
These library files are presented as a proof-of-concept. A number
are sounding quite good, but many still need much more work to make
them "musical". Many of them were developed by recording the auto-accomp
on my Casio keyboard and then manually re-creating.
Some initial guidelines....
>> Start each file with a commented filename. Just makes editing easier.
>> Follow the filename with BEGIN DOC/END section. This holds a
descriptive comment, used in the library reference header.
>> Include an "Author" directive line. Currently this is treated as a
comment, but we might use it in the future.
>> Add a DocDefine to the end of each goove definition. Something like:
DefGroove Waltz This is a nice waltz groove.
This is extracted using the -Dx command line option for creation
of the library documentation.
>> Be as descriptive as possible in the pattern and groove names.
Probably not as easy as it sounds ... but punct. and digits
are permitted in pattern/groove names. Just remember that
they are case-insensitive.
Also, let's use lots of comments and blank lines.
>> Try not to overwrite common names. There are no warnings for this,
and it could create unwanted results. With auto-loading of grooves,
name duplicates become more problematical!
>> Including voice, volume, random settings in a groove is probably
a good idea. Easy enough for a user to override after he/she
selects.
>> Don't make assumptions. Yes, you can get away without putting a
Time directive at the top of lib file, but don't. Lib files should
have an explicit SeqClear and SeqSize as well.
>> It is probably a bad idea for library files to include other library
files.
>> Do use the standard pattern include files! And don't rename the
patterns defined in them!
>> Create patterns in logical order. The order in which you define them
is also the order in which they'll be listed in the docs.
June/2004, bvdp.
|
