|
yes, I saw this message pop up with MIDI realtime
events when using
Mike Gogin's midi compatibility flags (when they
should not really
have been there). I agree p3 should raise such
warnings, but not p7!
Victor
----- Original Message -----
Sent: Wednesday, March 19, 2008 9:09
PM
Subject: [Csnd] Re: Re: MIDI/Score
Question
I modified it to us a k-var (and tried with an i-var) but I
still get the same warning.
kfreq init 0
kvelocity init 0
midinoteoncps kfreq,
kvelocity
mididefault 0dbfs, p4
mididefault 1, p5
mididefault 1, p6
mididefault kfreq, p7
kenv linenr p4, p5, p6,
.01
asig oscil kenv, kfreq, gitab
outs asig,asig
On Wed, Mar 19, 2008 at 1:15 PM, victor < Victor.Lazzarini@nuim.ie>
wrote:
I don't think you can assign to p7. You
probably want
an i-variable (say ifreq cpsmidi
)
Victor
-----
Original Message -----
Sent:
Wednesday, March 19, 2008 7:41 PM
Subject:
[Csnd] MIDI/Score Question
Hi all,
I'm currently trying to learn how to use blue
and I'm starting to port some of my instruments to be MIDI/Score inter
operable.
I have a question though, when I run the following
instrument.
I get a warning when using the real time virtual keyboard
saying:
"WARNING: instr 1 p7 illegal for MIDI"
Can some one tell me
how to get rid of this warning, and how I should properly set up
this instrument.
Thanks,
Miguel Morales
gitab ftgen
1,0,1024,10,1
instr
1
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;all instruments MUST be
score/midi interoperable!
;1xOsc Argument
Description
;p1 = instrument id
; ;p2 = start
time
;
;p3 = end time
;
;p4 = amperage (0dbfs?)
;
;p5 = Rise Time
(secs)
;
;p6 = Decay Time (secs)
;
;p7 = Oscil Frequency
;define some defaults in case
it is midi activated
kcps init 0
kvelocity init 0
mididefault 0dbfs, p4
mididefault 1, p5
mididefault 1, p6
p7 cpsmidi
kenv linen
p4,p5,p6,p7
asig oscil kenv, p7,
gitab
outs
asig,asig
endin
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|