#142

Hey there all. Sorry to resurrect an old thread. @ithkaa - Hope you are well. I have moved over to Ableton Live 10 and am having difficulty getting Control to send MIDI. I am using the M4L patch. I am able to create toggles and faders, and when I am in performance mode, I am getting the little light to the right of the Control device, as well is on the bottom of the meter on the track where it resides.

Here are my MIDI settings in Ableton:

Here are my audio / MIDI settings:

Can you see what I am doing wrong? I am on a Mac with 10.12.6 (can’t run Mojave because my startup disk is in RAID - thanks Apple!)

Thanks! You know I am a big fan of this app.

#143

FYI I got the standalone working just fine. Would love to be able to run the M4L version, but the standalone is what I always used with Bitwig, and it is working in Ableton.

#144

@pesky_human you have to select your IAC Driver (Bus 1) as the ‘MIDI-To’ device on the track where you put the control M4L device. Should work then …

#145

hey @ithkaa I thought I might be able to use the m4l device via ‘autofocus: track’ with some terms or gridlab devices but everytime I change from/to another ‘autofocus: track’ device (i.e. flin) and get back to the control m4l device, the grid will be disconnected. Any idea how to solve this?

(Ableton 10.0.6 / Max8.0.2)

#146

I remember having issues with autofocus when I wrote it, but thought they were fixed. I’ll look into it later this week.

1 Like
#147

Thank you so much @ithkaa ! I hoped to use the standalone version but I can’t find a way to split/span the grid between gridlab/terms etc. and the control app.

#148

Dear @ithkaa,
I tried again today but no luck. I focus on ‘track’ but everytime I switch to another m4l (terms) app, the m4l control loses connection to the grid. Any ideas?
Best from Berlin and thanks for the amazing work!
KZA

#149

dear @kza, just checked control + gridlab (polygome and gridcontrol) and control + terms (flin and polygome). autofocus seems to work as expected. I’m on ableton 10.1, Max 8.0.4, running on a MBP 10.14.6.

1 Like
#150

I just realized I used an outdated version of the M4L control. Everything works fine now!!!
Thank you very much!

1 Like
#151

New version up on github (see top post for link). Fixed some issues in regard to automation and preset saving. Also, there’s a windows version available… Hasn’t been tested properly but should work. Let me know if it doesn’t.

1 Like
#152

Super ! will this work for any DAW? does it require M4L? thanks@!

1 Like
#153

there are a few different avenues presented in the github: https://github.com/benjaminvanesser/control

  • M4L devices
  • Max patchers which can be run in Max (for free) and mapped to MIDI through IAC
  • Standalone which has Mac and Windows executables to map Control without Max or M4L

hope this helps!

3 Likes
#154

I should thank you again for how much Control has proved to be useful in my livesetup for years now, it looks simple but it’s a blessing for live improv / automation of electro behaviors.

Incidentally now that I’m writing this, is there a page where we can donate to support your work ?

1 Like
#156

Thank you for your kind words @LLK! There’s a donation button on the software page on my site.

3 Likes
#157

Hi there, is microphone required for this to work?

I’ve setup an IAC Bus in midi devices, and the grid is not lighting up when plugged in.

trying to control REAPER daw.

#158

Do I need serial OSC for this to work??

manyh thanks ! :slight_smile:

#159

No. Make sure to refresh the MIDI devices in Control. Then, make sure your receiving software is able to get MIDI from the IAC device you selected as output in Control. The grid doesn’t light up, you have to create an interface first. Take a look at this intro/tutorial video: https://vimeo.com/174826009.

1 Like
#160

Yes you need serialosc

1 Like
#161

its working now !

what a terrific software!!

is there a way to have it load a default patch every time the control software loads??

#162

I’m afraid that’s not possible…