I am currently using macro buttons mainly to dip music in the background so I can hear discord and my own mic in a conversation. I have the macro setup so I have one button that acts as a proxy for the music controls. Its fairly simple, is basically the demo on the website:
a push button with button on:
Code: Select all
Strip(6).fadeby = (-15.0,50);
Strip(6).EQGain2 = -5;
and button off:
Code: Select all
Strip(6).fadeby = (15.0,200);
Strip(6).EQGain2 = 0;
So I'm using the relative fadeby rather than the absolute fadeto, and I would like to keep it this way, but there is an issue I keep running into. I have two other buttons, one for discord trigger and one for Mic trigger, and both have the same code:
on:
off:
This way, no matter if im talking, or if discord is receiving audio, they both duck audio but only by the same amount rather than compounding. The issue, is that due to the 200ms fade back to the original level, if the button is triggered again before the fade completes then the on trigger will fade -15db at where ever the fade was interrupted at. So for example, lets say we start at 0db then the button is triggered reducing the level to -15db, the trigger goes away and the fader starts to rise back to 0db. Except if the trigger on happens when the slider is at say -5db, then it will reduce -15 relative to that ending up at -20db. If this happens in quick succession, the fader can end up at -60db quite quick and stay there. The only solution to this problem ive found is to use the absolute fadeto so that even if its interrupted, it stays.
I'm not entirely sure how I can fix this, although I do vaguely remembering something in the manual about controlling an individual application on a strip but i read the manual multiple times again and couldn't find it.