MegaMagic Pads V3 - Pol/Air - Macro Glitch

@nordiclight

What do you mean that it is missing the LFO?  The filter is often considered to be the filter cutoff.

Or do you mean that the macro knob is not assigned to anything?  Sometimes macro knob 1 may not be assigned to anything but internally, in Guru Sampler 2, the mod wheel may be assigned to the filter cutoff.

I am not at my music computer at the moment to verify.  I will try and remember to look, but it may not be until tomorrow.

Yes - these days John is often directly mapping modwheel inside of Gurusampler2 patches to the filter, so that the macro link mapping on macro knob 1 is not required.. but since he expects Macro 1 to be configured to send MIDI cc1 by default then it would also affect the same thing (and so he keeps the macro name for Filter). We've had minor slightly heated discussions 🙂 about assuming macro cc assignments are always set up this way in the past (e.g. on my MIDI controller I always have Macro 1 assigned to cc73.. the first hardware slider, then cc75 etc).
IMO we should not assume the knob has the same CC mappings for everybody.. which is also why I added an option in the settings panel (MIDI tab) to disable the knobs from sending out CC values - in case it interfered with patch/plugin where mod-wheel or other cc is already directly mapped (but if we assumed it was off by default then a parameter mapping should be set up if the knob is called 'filter').

In short.. there is no good answer 🙂 ... tweak your macro knob and modwheel.. if the filter sound changes, then it's mapped as expected and if you want all patches to work as John intended, set macro 1 to cc1 (and make sure sending MIDI cc output on macro knob moves is enabled in the MIDI settings tab).

@wavesequencer

Posted by: @wavesequencer

↑

to disable the knobs from sending out CC values

Could you explain this setting more?  I believe you're referring to the setting "Generate MIDI-CC linked events on Macro knobs mouse control".

I keep running into synths that have their own assignment to CC1.  For instance, vibrato is somewhat common.  However I use Macro25 set for CC1 and I assign it to the synths vst filter cutoff parameter.  But then I find that the Layer is also letting CC1 get thru to the synth, and so then CC1 triggers both vibrato and cutoff.  So then I add midi filter blocking CC1 to layer 1 to stop the vibrato, which solves this dilemma. 

If you have this setting checked off, is it supposed to stop CC1 from getting thru on the Layer?  Or what does the setting do?  Manual didn't help me understand it either.

It's pretty much what it says.. if you move the macro knobs (with the mouse) and the 'Generate...' option is enabled, the macro knobs generate cc data for the cc that is currently assigned to the knob.
In my personal opinion that is bad, so I provided an option to turn it off.
Quite a few patches assume that macro 1 is going to be generating cc1 data when manually moved - it's probably safer to assume that is not the case and just add a macro link to whatever parameter you want it to update. 

MIDI cc data received will go straight to the layer (regardless of that setting for the knobs), but will also update the knob position (without generating extra cc messages).

You can monitor what happens with the built in MIDI Monitor - see attached.

@wavesequencer 

Ok, that's what I thought.  I see it works for all macro knobs.  But for midi coming in from a keyboard controller, which I just tested, it doesn't have any affect.  That's what I was getting tripped up on.  So I will still have to use midi filter to block incoming midi data in some circumstances.  Thanks.