I've been working on my problem trying to use Csound .sco
simultaneously with csoundapi~ input.
It seems like, when I send a message to reset the tempo from Pd,
Csound always starts from 60 (aka istartempo).  I had thought that a
tempo opcode would accept input to set the tempo continuously, rather
than being called again when the tempo changes.
I attempted to use offset messages to move the score around to avoid
the .sco portion until it's needed; but every offset change is
accompanied by either a momentary lapse of the established tempo, or a
rush through all of the notes at once.  I would have thought that, if
the i1 (tempo) statement is at time 0, and the tempo message has been
sent, then setting the offset to point to a later time would NOT
restart the tempo change from 60, but it appears to do so.

I have figured out that all of the messages sent from Pd are
uninterpreted; possibly because of the -t flag.  But it seems to apply
to the offset messages too, which I believe are counted as seconds and
not beats, all while the score beats, when the tempo is 120, are half
as long.  I originally had the i1 note set to duration 3600, and the
second i1 note occurring at 3600; but when I then set the offset to
1800, the score would end almost immediately...

I was hoping to compose the melodies and harmonies using my Pd
sequencer and throw together drum sounds in .sco format; but tempo
changes are a necessary part of the process, so I'd have to be able to
synchronize them.  If anyone can think of another way to do this
(other than the "tempo" opcode), please let me know.

Also, I remember the subject came up before, and I was not the only
one befuddled by the need to include istartempo with the tempo opcode.
 If anyone can shed some light on how it works, I'd appreciate it.


Thanks.
-Chuckk

-- 
http://www.badmuthahubbard.com