ian
Converser
Posts: 8
|
Post by ian on Jul 22, 2018 7:37:16 GMT
Sorry for such a low level question, but I'm a noob here and can't understand the looping syntax.
I have successfully mapped a button press on a foot controller to the correct output to mute my mixer (volume 0).
B0 11 07 = B0 1F 00
However, instead of a sudden mute I'd like to loop and gradually decrement that final volume value from (say) 64 hex down to 00 hex resulting in a smooth fade.
So I'd need a loop with a decrementing volume value and delay each time through the loop - but I don't know how to do that?
Can anyone assist please?
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jul 22, 2018 9:28:56 GMT
Hi ian , You need a loop with one variable for the CC value (64 down to 0) and another to pace the fade (linearly) by delaying each CC. IF M0 == B0 11 07 # I0 = cc value, I1 = delay in ms ASS I0 = 40 0 IF I0 < FFFF +L # loop while I0 >= 0 SND B0 1F I0 +DI1 # send CC with value + delay MAT I0 = I0 - 1 # decrement CC value (I0) MAT I1 = I1 + A # add 10ms to next CC END XX = XX +B END Regards, Nic.
|
|
ian
Converser
Posts: 8
|
Post by ian on Jul 28, 2018 1:18:07 GMT
That works perfectly once Nic, but then I have to close Midifire and reopen it if I want to fade again for another song - otherwise it will fade until the maximum number of loop iterations is reached and then cease fading.
Is there any way to overcome that?
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jul 28, 2018 6:21:29 GMT
Hi ian, That is a bug, but I did make a fix for it. Are you using most recent version of MidiFire? Open the Setup panel to see version number down the bottom. You need 1.15 or greater. If this is happening on 1.15 I will pull my hair out! Regards, Nic
|
|
ian
Converser
Posts: 8
|
Post by ian on Aug 2, 2018 10:43:15 GMT
Sorry, but yes it's 1.15 - it works fine the first time, and then fades only part way the second time, then nothing until I close and reopen.
My apologies - I must have updated AFTER I last observered this problem. It is working now. Well done Nick!
|
|