Originally reported by Sourceforge User: menno0
perhaps this is a bug: p4 doesn't always seem to kick in using the harmon234 opcode. It has an effect typing in the p4 value directly but when using the score below, the result is okay when the p4 change is from a higher to a lower value, while in the next section where values of p4 change from low to high, the result stays frozen at the first p4, ie. 5
<CsoundSynthesizer> <CsOptions> ; Select audio/midi flags here according to platform -odac ;;;realtime audio out ;-iadc ;;;uncomment -iadc if realtime audio input is needed too ; For Non-realtime ouput leave only the line below: ; -o harmon2.wav -W ;;; for file output any platform </CsOptions> <CsInstruments>
sr = 44100 ksmps = 32 nchnls = 2 0dbfs = 1
instr 1
aout diskin2 "fox.wav", 1, 0, 1 kmaxvar = 0.1 imode = 1 iminfrq = 100 iprd = 0.02 koct, kamp pitch aout, .01, 6, 10, 10 ilow = p4
asig harmon3 aout, koct, .9, 1.5, 0.7, 0, p4 ;asig harmon3 aout, koct, 300, 800, 2000, 1, 9 print p4 ; outs (asig + aout).5, (asig + aout).5 ;mix dry&wet signal outs asig.5, asig.5
endin </CsInstruments> <CsScore> s i1 0 2.7 8.8 i1 3 2.7 8.0 i1 6 2.7 5 s i1 0 2.7 5 i1 3 2.7 8.0 i1 6 2.7 8.8 e </CsScore> </CsoundSynthesizer>
该提问来源于开源项目：csound/csound
