Yes it’s working for me.

5 Likes
5 Likes

this needs a bump to the top. visited @stretta earlier this week and gridlab continues to evolve wonderfully. if you’re using grids or arcs with max or m4l these are essential.

9 Likes

Wish he’d drop by and say hi!

1 Like

I sat down to play with these today and I can’t seem to get LED feedback on any of the arc or grid devices.

I can communicate to the devices fine, so it’s connecting to serialosc no problem.

On the github README it says:

And I’ve done that, and still nothing. Again on both grid and arc apps.

Anyone run into anything similar?

2 Likes

@Rodrigo yes I ran into the same problem last week. You simply gotta hit the “focus” button and the the lights come to life :slight_smile:

2 Likes

Sometimes I have to select a different track and come back too, to make the lights appear.

I wish I had a better understanding of what “focus” means. I know the intention is to make it possible to use multiple max for live devices with one grid, and switch between them, but I don’t have a good mental model for what events are actually getting passed around.

For me that behavior is actually true for all apps, including terms. Switching from one track to another can help make the lights appear. A little annoying but so easily managable I stopped thinking about it. Would be nice to effectively get rid of that someday though !

yeah i have this problem quite a bit with the arc. i was using it for a live tour a while back and experienced many an anxious soundcheck - restarting ableton repeatedly, toggling tracks, plugging/unplugging, etc.

i wish it were more reliable.

This one goes back a ways, but here you go:
http://archive.monome.org/community/discussion/6428/maxforlive-autofocus/p1.html

1 Like

Thanks @greaterthanzero!

So now I wonder what is sending and receiving the “when a track is selected in live” event, and I wonder if there are other moments when we could fire that event such as when the device is done loading, or similar?

[live.thisdevice] is where that comes from.

I don’t remember offhand which outlet is which, but one of them gives you state info (“this track is selected” vs “this max for live device is selected” vs “neither of those are selected”). I’m sure he’s using that.

I think the left outlet is your “ready to execute” message. (the max for live version of “loadbang”) Which is what you’re looking for.

The problem is this:
If you tie into that event, and your setup has 20 autofocus devices, which one gets control when you open your scene?

The answer is each of them, very briefly, in the order that they finish loading.

That’s not a great answer.

2 Likes

Good point, and also a great explanation for why the device doesn’t feel fully loaded until you’ve triggered autofocus.

I’m getting my Arc4 soon-ish (already got a Grid 256) and ideally want to do drum step sequencing like in the original Plane video (https://youtu.be/OfFyvh_BGN8 ), is there a M4L device for that? I tried plane v mi p etc, but couldn’t find out how to achieve what I want.
I’m still fairly new to the whole Monome universe, so please bear with me if my questions sound redundant (I did search) or stupid :slight_smile:

Thanks so much in advance and cheers from Cologne, Markus

1 Like

Thanks, I was aware of gridlab and am using some stuff already, but which of the devices does what is shown in the video?

Here’s Plane-V

4 Likes

Hi! I just got the newest edition Arc, and the knobs and lights are amazing. I was hoping though that someone could point me to the root of a problem. I have Arc newest edition, windows 10, ableton live 10 and max 7. I have Serial OSC 1.4.1a and the FTDI drivers installed. I have been trying to use Arc with the Stretta made M4L devices for the past 2 days, and on all of them, functionality is compromised. In Quad LFO, (my favorite way to use arc), the Arc lights will spin for a few seconds, then stop. Sometimes the knob turns still register in the device, other times the arc will suddenly be gone and when I go to focus device, there is no option for it. I found a workaround by hitting enable debug and activating debug. The lights and everything then become fully functional, but usually after 30 minutes they freeze again. I also see this error in the debug screen that I will attach. Some devices work longer before freezing like Electric Dharma wheels, but others like Arc Rhythm generator do not function at all. Its quite a mix of issues with the Max for live devices. I do plan on getting ansible, but I love some of these M4L devices and want to use them! I was wondering if anyone might have insight on this issue thumbnail_Image

Same issue here though with 1.4.1b. @tehn and @artfwo are aware and working on it (hopefully :wink:).
Btw strum is the worst (happens fastest) in my case