Unwanted midi data, can someone help?

[monks1975]

Hi,

I've made a template for Operator and I'm executing this randomise Osc script when I press a button in the template:

Code: Select all

// set random values for all the osc parameters

decl r1 = rand()*22;
decl r2 = rand()*30/100;
decl r3 = rand();
decl r4 = rand();
decl r5 = rand();
decl r6 = rand();
decl r7 = rand();
decl r8 = rand();
decl r9 = rand();
decl r10 = rand();
decl r11 = rand();
decl r12 = 0.25+rand()*75/100;

oscatype = round(r1);
osc_coarse.x = r2;
osc_fine.x = r3;
osc_freq.x = r4;
osc_multi.x = r5;
osc_feedback.x = r6;
osc_phase.x = r7;
osc_atk.x = r8;
osc_dec.x = r9;
osc_sus.x = r10;
osc_rel.x = r11;
osc_lvl.x = r12;

The template and all the controls to Operator which the script alters are hardcoded to midi channel 2 but I am getting a bug/unwanted side effect where midi control messages on channel 1 are coming through when I tap the button, controller numbers 6 & 7 (checked with Midi Monitor). This is then messing with Ableton Analog on another track in Ableton. Are these being added by iConnect Midi 4+ (my Midi Controller) or is this standard behaviour? If no-one can help, I guess I should just change the mapping I've set up for Analog but hope I don't have to.

[Softcore]

Are you sure that some of your Lemur objects arent midi mapped by accident? Make sure your MIDI targets are all set to none.

Possible suspects are the "z" variables which we usually do not map and escape our "attention".

[monks1975]

I've check for unwanted Z variables, couldn't see any yet. There is no Z variable under that button, only x, there are some in the knob controls but they are unmapped to midi via target, but still mapped to object target.

I've attached what I see in Midi Monitor when I press the button, I've filtered all the wanted channel 2 messages that occur, leaving the channel 1 ones. Can't figure this out at all..

[Softcore]

can you attach your template here?

[monks1975]

Looks like it was two extra lines in the code in the first post, that changed x on non existent objects.

osc_freq.x = r4;
osc_multi.x = r5;

Don't quite understand why it would generate MIDI data though

[monks1975]

To conclude.. Midi Monitor is an invaluable tool! Saved lots of time.

[monks1975]

Actually, now I've really figured it out- freq and multi were hidden knobs behind the coarse and fine knobs, I had not changed them to channel 2 when I remapped the template in Ableton. DoH.

[Softcore]

Told ya! its always user error when "ghost" midi appears!