Using the 'MapButtonLFO' bpatcher faulty unless an LFO is present

Nov 6, 2013 at 8:15pm

Using the 'MapButtonLFO' bpatcher faulty unless an LFO is present

Hi all

I’ve taken the ‘MapButtonLFO.maxpat’ bpatcher from the LFO device in M4L9 and used it in my own patch, but it acts quite weirdly. Sometimes the ‘Map’ button won’t stop flashing despite it successfully mapping to a parameter, sometimes the X will not delete the mapping, or will require two clicks, and importantly the ‘Map’ button doesn’t change its name when it successfully maps to a parameter.

These problems go away when I actually have an LFO device somewhere in the Live set, my patch with its ‘MapButtonLFO’ bpatchers will work exactly as expected (though I have to reload it once I load the LFO device in). I can’t work out why this is… anyone got any ideas?

Thank you kindly

#270379
Nov 7, 2013 at 12:58am

Sounds like a problem with your file path.
I recommend to save your patch as project and add the map bpatcher to it.

#270394
Nov 7, 2013 at 1:30am

Awesome, thank you for pointing that out. Turns out the ‘stringFormat.js’ wasn’t copying properly when I was copying the bpatcher around.

Cheers!

#270396
Nov 7, 2013 at 2:47pm

I actually failed to copy the map patcher from the LFO as well. Care to share what clipboard of what worked for you?

#270475
Nov 7, 2013 at 3:07pm

Here’s what I did:

Open up the M4L patch
‘Show Containing Project’ (along the bottom toolbar)
‘Add File to Project’, searched for MapButtonLFO.maxpat, then did the same for ‘stringFormat.js’
Freeze device when you’re done editing

#270476

You must be logged in to reply to this topic.