enzienaudio / heavy

heavy public issue tracker and static dsp code releases
https://enzienaudio.com
ISC License
71 stars 4 forks source link

unresponsive parameters in wwise #234

Open vickim91 opened 6 years ago

vickim91 commented 6 years ago

I have made a very simple synth with adsr in Pd. I have used this method for the adsr http://msp.ucsd.edu/techniques/v0.11/book-html/node69.html . In Pd it works just fine, but when i use the heavy version in wwise some of the parameters are unresponsive and some parameters control things that are unintended. This is the Pd patch:

screen shot 2017-11-08 at 13 31 07

and this is the source generator in wwise:

screen shot 2017-11-08 at 13 24 43

The only parameters that work as intended are : peaklevel, sustain and release. sTime (sustain time) does not work. No matter what value i set in wwise it remains a short blip followed by the release. But if i hardcode a delaytime for the makenote object like so:

screen shot 2017-11-08 at 13 34 46

Then the sustain time in wwise is 500ms but the parameter is still unresponsive. Also the attack parameter does nothing while the decay parameter seems to actually control attack time instead. Anyone who has a solution for these unresponsive parameters?

Pd patch:

N canvas 97 55 1342 715 10;

X obj 110 236 mtof;

X obj 111 277 phasor~;

X obj 169 412 dac~;

X obj 218 323 r gain @hv_param 0 1 0.5;

X obj 141 313 *~;

X obj 170 352 *~ 0.5;

X obj 191 78 * 127;

X floatatom 851 234 5 0 0 0 - - -, f 5;

X floatatom 919 234 5 0 0 0 - - -, f 5;

X floatatom 977 235 5 0 0 0 - - -, f 5;

X floatatom 1029 234 5 0 0 0 - - -, f 5;

X obj 925 115 r decay @hv_param 0 3000 1;

X obj 984 62 r sustain @hv_param 0 100 50;

X obj 1039 11 r release @hv_param 0 5000 150;

X obj 298 260 print x1;

X obj 414 275 print x2;

X obj 278 432 sel 0;

X msg 279 458 stop;

X obj 392 408 moses;

X obj 382 435 t b b;

X obj 423 466 t b;

X obj 350 567 pack 0 \$2;

X msg 290 570 0;

X obj 426 592 f \$4;

X obj 426 614 * 0.01;

X obj 487 613 pack 0 \$3;

X text 431 555 Decay;

X obj 604 603 pack 0 \$5;

X obj 497 670 line~;

X text 265 399 trigger;

X obj 426 570 delay \$2;

X obj 834 138 r attack @hv_param 0 1000 1;

X obj 765 174 r peaklevel @hv_param 0 1 1;

X obj 487 591 * \$1;

X obj 350 545 f \$1;

X floatatom 418 77 5 0 0 0 - - -, f 5;

X obj 447 40 r stime @hv_param 1 1000 300;

X floatatom 780 236 5 0 1 0 - - -, f 5;

N canvas 902 461 450 300 notein 0;

X obj 66 7 r __hv_notein @hv_param;

X obj 191 139 unpack f f f f f;

X obj 191 267 outlet;

X obj 216 221 outlet;

X obj 242 179 outlet;

X msg 208 77 0.3;

X connect 0 0 1 0;

X connect 1 0 2 0;

X connect 1 1 3 0;

X connect 1 2 4 0;

X connect 5 0 1 0;

X restore 237 37 pd notein;

X text 754 208 peak level \, attack \, decay \, sustain \, release

;

X obj 278 171 makenote 1 500;

X connect 0 0 1 0;

X connect 1 0 4 0;

X connect 3 0 5 1;

X connect 4 0 5 0;

X connect 5 0 2 0;

X connect 5 0 2 1;

X connect 6 0 40 0;

X connect 7 0 21 1;

X connect 7 0 30 1;

X connect 8 0 25 1;

X connect 9 0 23 1;

X connect 10 0 27 1;

X connect 11 0 8 0;

X connect 12 0 9 0;

X connect 13 0 10 0;

X connect 16 0 17 0;

X connect 16 0 27 0;

X connect 16 1 18 0;

X connect 17 0 30 0;

X connect 18 0 19 0;

X connect 18 1 20 0;

X connect 19 0 20 0;

X connect 19 1 22 0;

X connect 20 0 30 0;

X connect 20 0 34 0;

X connect 21 0 28 0;

X connect 22 0 28 0;

X connect 23 0 24 0;

X connect 24 0 33 0;

X connect 25 0 28 0;

X connect 27 0 28 0;

X connect 28 0 4 1;

X connect 30 0 23 0;

X connect 31 0 7 0;

X connect 32 0 37 0;

X connect 33 0 25 0;

X connect 34 0 21 0;

X connect 35 0 40 2;

X connect 36 0 35 0;

X connect 37 0 34 1;

X connect 37 0 33 1;

X connect 38 0 6 0;

X connect 40 0 0 0;

X connect 40 0 14 0;

X connect 40 1 15 0;

X connect 40 1 16 0;

diplojocus commented 6 years ago

hi @vickim91 that seems strange! Will take a look