
Review the code for walking bass. Right now it looks only at the root of the chord...
I think it should check minor and 7th. Maybe it should create an entire scale based
on the chord?

--> Partially fixed, it checks the root and minor intervals.

---------

Better error messages needed, esp in cases like this:

	Cm
	Goove foobar
	...
	
Here the mispelling of Groove is reported as an unknown chord.

---> Not sure if the parsing routines will permit anything better.

-------

Need to check all functions for debug hooks.

-----------

Multiple filenames so we can run in a batch mode? Esp. when extracting docs...

---> doc extraction is pretty fast now. Don't really think this is an issue now.

----------

A 'note' track? Thinking that it might be nice to be able to include
a user defined solo? OTOH, this might be much better left to other editors
or sequencers!

---------

Look at the fermata code. Right now it just slows down the timer. This is fine
for a held note, but the drum notes really sound goofy.

--------

Look at the cresc code. It changes volume(s) at the end of each bar, and
it would be nice to change this to beats. I think some table driven code
will work here... just a have a list of volumes for each track and pop off
a value after every beat...

---------

Would having "riffs" help anything? I'm thinking that a riff is an sequence
which isn't defined... I'm trying to make short sequences easier to create...
so, if we are playing a certain groove and we just want the bass line to
change for a bar we might do:

	walk riff 1 8 1 90; 1.5 8 1 80; 2 2 3 90
	
which would force the walking bass pattern to whatever. This is just syntatic-sugar
since the same could be done by defining a pattern and setting that in the sequence.

To be truly useful we need a riff-end command as well which restores the old seqence.

When would we use this? Well, 2 simple examples:

1. We have a groove with a nice walking bass. But for a specific bar we want the
bass line to be 2 half notes. With 'riff' we just insert a 'walk riff...' line.

2. We have a goove with a strumming chords, but for an ending/transition we want
a sustained chord. Again, just insert a riff.

All this would be nice with macros... We might need some reworking of macros
to accept multi-word args.





