Yea I mean it takes some max knowledge to fix these things. I can probably test it out later today if that script ends up working for you

1 Like

no need to uninstall serialosc. might want to first ensure the arc is working and recognized by MacOS. they have created all sorts of trouble with each version.

check if your FTDI driver is working by opening a terminal and typing:

ls -l /dev/tty.usb*

if it is working your should see a listing when arc is plugged in.

will follow up with a few more ideas.

2 Likes

Typo there I think. Should be tty.usb*, no?

2 Likes

Hi Andrew. So I tried out that script and opened it up in Max 8 and it looks like it connected as you can see from the screen grabs. What is frustrating of course is that just now I opened up Ableton Live, dragged one of these Arclab ArcControl.amxd devices into it and it worked immediately. Then I’ll quit and try again later on and it won’t work! That’s the most frustrating thing of all!

So the Arc is being recognised by the MacOS but it feels potentially like there’s something quirky going on there. Not sure what!

well I’ve probably isolated that it’s not a problem in the script, Macbook pro / 10.14.5 / Live 9 and the script is working just fine for me : / follow @tehn’s advice to check for a driver issue

do you have access to another mac? if so, going through the install process on another computer might clear up the issue, which would be a pointer for troubleshooting.

I also think @chapelierfou may be on to something above. maybe do a bit of basic research on m4l dev so you can investigate. your max for live license should allow you to save, something might be messed up there.

The ArcControl patches are not broken, the js is unlikely to be missing.

What seems likely to me is that either there’s an FTDI issue (which issue depends on which version of macOS) or there’s an issue with Max/Max for Live/Ableton versions and linking between them (possibly having to do with 32 bit/64 bit mode of Ableton and/or Max/Max For Live).

But I can’t really write a step by step method for diagnosing the above for a couple reasons 1) there are a lot of moving parts I just described, and the combo between them matters, and 2) it’s always been hit or miss for me as well, until somehow magically I get everything working reliably. Which usually lasts until Apple screws around with their USB subsystem once again.

@tehn has debugged more of these issues than any other human alive, and I’d recommend trying everything he suggests.

1 Like

looks like you’re right here, those errors made it look like a js missing thing but they show up for me as well, so they likely don’t mean anything. definitely drivers / weirdness, which yea, I’ve never run into myself despite lots of use and multiple OS updates >:(

sorry for the red herring !

looks like the FTDI driver is fine, provided it’s detecting.

prior to moving on to the max for live patches, can you confirm that returns.maxpat (etc) work consistently? or do they also work only occasionally?

trying to identify where the connectivity issues lies.

2 Likes

So here’s why I am confused (and rather frustrated) - I tested it out last night using returns.maxpat and Monome Home.maxpat and included the screen grabs where it was suddenly working perfectly. Now this morning I’ve opened up my laptop, connected up the Arc again, opened up the very same patches and nothing shows as connected. When I return to Ableton Live and import any of the patches such as ARC4 Mapper or Arclab ArcControl, they also show no connections, nothing can be mapped. etc.

This is what is rather defeating. When you feel like something is working, then isn’t, and literally nothing has changed (apart from me going to bed, waking up again, and opening up the laptop). It’s so weird!

I used ls -l /dev/tty.usb* in Terminal and it reports ls: /dev/tty.usb*: No such file or directory :frowning:

I don’t think it’s an Ableton 32/64 bit issue as it only runs in 64 bit now, it’s the latest version and even if I’m not using Ableton Max is unable to recognise Arc as I’ve just shown with Terminal. I’ve also unplugged Arc, replugged it, restarted, etc.

Thanks so much for trying to help out here. I can connect the Arc to Ansible and have it working immediately and perfectly so the Arc doesn’t itself doesn’t have any issues either. Hmm…

So, just restarted the laptop again. Yet again :slight_smile:
All lights switch on on Arc, but now when I try to open up anything in Ableton it crashes immediately as soon as I drag any amxd patches across. And if I try to open returns.maxpat in Max it also crashes immediately.

So I unplugged the Arc from the computer, plugged it in again and now it connects!! Arghh :smiley:

I know there are much bigger challenges in life, but after three days I was hoping I could get to rely on this. Several folks suggest ā€˜js’ issues sorry I honestly don’t know how what to do regarding that.

I did manage to open up Terminal and it recognised Arc now though

Quick question :
Are you able to load and use a M4L LFO, or anything with a ā€œMapā€ function ?

this is an incredibly uncommon problem you’re having, so it’s time to check hardware. i didn’t see a recent order from you, so perhaps you picked this up used? in which case, there is a change that it’s one of a handful of arcs with a tiny circuit flaw (easily fixable) which makes the FTDI chip unreliable. (all original owners were notified and most had them fixed… this was years ago… but some problem units may be out there still). the only counter-indicator to this is that you mentioned it worked fine consistently with the ansible.

another frustrating check to eliminate the possibility of an arc hardware problem is to see if you can get reliable connections on another computer. i’m very sorry about all the MacOS trouble, it’s a very opaque system to troubleshoot.

thanks Brian. Yes, I picked up off a guy here on this forum but it looked like it was barely used, mint condition in original box. Immaculate. Somehow I doubt it’s the Arc and indeed since it’s working well with Ansible, as far as I can tell, it does indeed seem odd!

I’ll experiment with my iMac in the studio today if time permits and see what emerges then too. Sorry to be writing such very dull updates here but it’s so silly. I like to feel that I understand things quite intuitively and quickly so this has been a little defeating so far!

Thanks again!!

Yes, sometimes I can. Sometimes I can’t. This morning I restarted the laptop and lights came on Arc immediately, opened up Live and every instance of trying to connect Arc crashed Ableton. Unplugged Arc, plugged it back in again, restarted Live and it worked immediately. So yes I can map to an LFO for example sometimes, at other times no response at all.

Does the arc ever flash full of random lights on startup?

Do you mean start up as when connected to the computer when it starts up or when I connect it when the computer is already switched on?

For example I just plugged it after I wrote that sentence, with no software open for it, and it the lights closest to the plug end flashed briefly, but nowhere else. And then I left it plugged into Live and opened up a patch and it immediately worked. Oh, it only it were dependable like this :slight_smile:

As other suggested what’s the behavior outside Live, can you test just with Max ?

Yes, as I wrote to Brian I used that patch suggested to open in Max and it recognises the Arc. But, not always. Sometimes it will recognise every time, sometimes every 3 times. Strange indeed!

very curious to hear if your other computer is consistent, just to rule out hardware. I apologize for the convoluted process!

No apologies need. I like a challenge (I always like a reward of course). As it’s the evening here I won’t be returning to the studio until the morning but will try it out then and let you know. Thanks for your support here too, it’s very much appreciated, as are the suggestions of everyone else!

Have a lovely day!

2 Likes