#113

So I’m trying to fix this but think I’m missing the very first steps here. When you say ‘open the device’ - do you mean within Ableton and right click on it to reveal the Max window. If so there’s no ‘box’ called “P Mapping” to double click on. If I open it within Max it reports that I don’t have a registered version to save as it’s included within Live itself.

Sorry to sound stupid here but if I can work out this first step then I follow the rest I hope!

Thanks

Robin

#114

Hey Robin,

I often had the same issues. You’ll get used to it :slight_smile:
Try the Monome Home App to see if your devices are connected:

Reinstall SerialOsc:
https://monome.org/docs/setup/

Check threads like:
https://llllllll.co/search?expanded=true&q=ftdi

Tag @tehn :slight_smile:

Good luck!

#115

Thanks for your support there, though admittedly after 24 hours I feel the blood draining from my body and my enthusiasm with it. I want to create, and not struggle to even open the door to things! For one brief moment today I connected it to Ableton, the lights all lit up and it was instantly able to be mapped to parameters. But just once. Not sure what this even suggests - the settings are okay or not? Hmm…

I’ve been over and over the forum but no joy as yet in resolving what I sense should be a familiar and basic question too. Followed threads but nothing points towards a solution! :frowning:

I’ve installed serialosc at least three times. There’s no uninstaller and no clear instructions on what I should be removing to uninstall it. I see countless remarks from people on the same issues but never a solution sadly.

Not sure where to go here. I’d like to think the only way is up as that classic pop tune once said but at present I’m going down, down, down a dark and miserable rabbit hole.

Luck might be the only solution, ha ha!!

1 Like
#116

Sorry not to contribute useful info but I hope someone can help @robinrimbaud fix this. Robin your music is amazing and I’d love to see what you can do with the monome instrument/controller set!

/end cheerleading

3 Likes
#117

@robinrimbaud Try writing info@monome.org to get @tehn’s attention.

It’s a busy forum and nobody has time to read every post.

1 Like
#118

You are not alone. If you want to go the grid/arc way be patient, it can be very frustrating but also very rewarding. If not just buy a plug and play device.

1 Like
#119

Oh I completely understand. I never expected to hit gold immediately. But if only you felt the sense that you were actually getting somewhere it would feel more rewarding. On the other hand connecting Arc to Ansible is immediately rewarding and currently manipulating the modular system in a beautiful manner, so I remain optimistic :smiley:

Thanks for the mail suggestion!

1 Like
#120

Thank you. I’ll send the money to the usual place for you :rofl:

I’ve got the Arc working reasonably well with Ansible in the modular set up so that’s positive at least so let’s hope I can get the other basics sorted out.

Kind words though, thank you!!

1 Like
#121

the error codes in the top post seem to suggest that yea the js script might be missing. we should probably isolate whether the issue has to do with this specific app or any arc applications running on your computer @robinrimbaud - try this one out (incidentally it’s kind of similar or ArcControl).

my guess: there’s an issue with this app, I don’t think gridlab has been touched in a little while, inevitably max applications fall apart with versioning and all kinds of inherent issues with max/msp which is sad. but any of that can be fixed.

1 Like
#122

I’ve downloaded and will try this out tomorrow. Thanks Andrew!
I only wish I understood where, as I wrote earlier, I’m meant to be finding this ‘box’ when I open it. No idea how I ‘open’ it either. Oh dear, how embarrassing :smiley:

#123

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
#124

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
#125

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

2 Likes
#126

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!

39
Screenshot 2019-08-06 at 21.57.39.png2541×697 92.4 KB
09
Screenshot 2019-08-06 at 22.02.09.png1108×867 61.5 KB

#127

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.

#128

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
#129

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 !

#130

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
#131

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…

21
Screenshot 2019-08-07 at 07.22.21.png772×266 42.4 KB

#132

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

00
Screenshot 2019-08-07 at 08.03.00.png1148×170 31.7 KB