Hi there.
This seems like a really excellent app but unfortunately I’m having trouble getting it to run reliably. The main issue I’m having is that I’m unable to trigger audio clips using either toggle or momentary buttons. It seems like the clip will start to play but then immediately stop itself and it seems strangely connected to whatever quantize settings I have set for the clip. Any ideas? It’s even crashed Live a few times. The playing clip will freeze, I’ll get a big CPU spike, and then the beachball of death.

I’ve tried all the versions. Thanks for any help!

@lintfresh that’s weird. Just checked and all seems to be working well over here. Are you using the standalone or the M4L device? Could have something to do with your MIDI I/O settings.

-> Set up an IAC bus. Go to MIDI Preferences (in Ableton). When using the M4L device, set both ‘remote’ and ‘track’ to ‘on’ for the input and ‘track’ to ‘on’ for the output of the created IAC bus. Now choose the IAC bus you just set up in the ‘MIDI To’ dropdown on the track the ‘control’ device sits on.

When using the standalone, just put the input’s ‘track’ and ‘remote’ to ‘on’ and you should be good to go.

If it doesn’t work, try disabling MIDI devices that you’re not using.

i did find a bug with autofocus on the m4l device - will fix it later on today, but that shouldn’t influence your MIDI mappings

Thanks so much for the quick response! I’ll double check midi settings tonight and report back. I remember having both ‘remote’ and ‘track’ enabled for both the input and output so maybe that’s what’s causing it. Some sort of quantized midi feedback loop perhaps?

Mkay, now things are working better. I think turning off the ‘remote’ in the IAC bus in Ableton preferences helped. Seems like everything is working as it should except for the following:
I have a few faders mapped to the volume sliders of a few audio tracks. They work great EXCEPT: when I stop the Live transport they fade down all the way. It looks like Live is sending out a MIDI message when I hit stop (or spacebar) that causes the faders to drop to infinity. Any ideas?

Using the control m4l.amxd in this instance.

@lintfresh somehow live’s transport got coupled to the automation function.

updated device on github. let me know how it works

Dang. Still doing it. Any other ideas?

@lintfresh can’t seem to reproduce that behaviour. perhaps you have some other automation set up? try setting up control from scratch (new live set, new instance of control, midi-map some volume sliders to faders, …) and let me know if the problem persists

Hi there, thanks a lot for this amazing app, I was trying to do some recording with notes M4L and I just noticed that if you enable the automation and then hold a note, the audio stops after a second or so, but if you continued holding it, when you replay it, it plays as if there wasn’t any stop. This doesn’t happen if you press a second note. Is this a bug or am I doing something wrong? Thanks!

@angel updated device on github … bug should be fixed now

2 Likes

Thanks, I was adapting the random output and automation to a 64 grid and thought I had broken something. Works like a charm now, you’re the best!

1 Like

hadnt tried till today and must say that this ui is making total sense & i’ve saved a few maps
great instructions too…

1 Like

I recently uploaded an introduction/tutorial on control. the video fearures the standalone version but operation and setup is similar in maxpatch and M4L device:

13 Likes

Hi All,

I’m having a few issues with Control. Looking for a little help if possible.

  1. I get the error - “control” is damaged and can’t be opened. You should move it to the Trash.
  2. Having an issue with Midi Mapping with the M4L control device.

Any help would be great.

Thanks

This little tutorial might help you with your first issue.

thanks. Worked a charm. I also managed to work out how to get midi mapping working too.

Great stuff.

Just downloaded this app yesterday looking to control some simple vst effects in my new live set. a page of faders is working a treat, but I’m unable to use a lot of the functions as I’m on a 64gs.

I don’t currently have a max licence, any chance of someone porting this to 64 as the standalone app?

Thanks!

1 Like

@Simeon been planning to do this for a long time but never got to it. I’ll probably start working on 64 grid support in January as I’m buried in work right now. If somebody else wants to give it a go … the max patch is over at the github repository

2 Likes

just want to say i tested this for the first time and it’s working like a charm! great work @ithkaa!

1 Like

Anyone using this with older grids without varibright? Care to share opinions on this?

Yep use it often with my grayscale128… autofocus is sweet too, I can switch between @elquinto suite and sl sequencer easy peasy