Help, monome devices not recognized in max 7

andrew · 2018-12-23T05:11:52.013Z

also if this is an inside scoop of lightbath ableton edition I’m v here for it

fourhexagons · 2018-12-23T16:19:57.407Z

Ah, wait. How’s that?

So, you’re saying that I should restart Max, and that quitting and reopening Ableton doesn’t restart Max for Live?

And what are the steps to restarting Max for Live?

And for the record, I was also testing with Max standalone and quitting and restarting Max hasn’t made the device available in the dropdown.

fourhexagons · 2018-12-23T16:20:46.905Z

Ha! Yes. It is. Thanks for the support

andrew · 2018-12-23T17:46:07.919Z

fourhexagons:

And for the record, I was also testing with Max standalone and quitting and restarting Max hasn’t made the device available in the dropdown.

eep this might prove you’re having a different prob then me, wish I had my grid on me to try n reproduce something.

fourhexagons:

what are the steps to restarting Max for Live

yeah on live9/max7 on mac when you drop a m4l device in you should see max launch and it should pop up in the Mac dock at the bottom, and you can right-click and quit, which closes max

anyone else running grids on current macos this might be beyond me ?

fourhexagons · 2018-12-23T18:12:48.514Z

andrew:

yeah on live9/max7 on mac when you drop a m4l device in you should see max launch and it should pop up in the Mac dock at the bottom, and you can right-click and quit, which closes max

Ah, understood. I had forgotten to mention that I’m running Live 10.0.5, which has Max integrated within the application.

alanza · 2018-12-23T19:09:54.473Z

I did have an issue once which sounds similar to yours… unfortunately restarting Live and/or my computer cleared it up completely.

tehn · 2018-12-23T23:24:35.582Z

that arc photo seems like a hardware bug that slipped out on a very small batch of early units (of which i thought all were fixed). e-mail info@monome.org to follow up-- does this arc work 100% of the time with ansible?

tehn · 2018-12-23T23:27:21.168Z

fourhexagons:

/System/Library/Extensions/FTDIUSBSerialDriver.kext

also seems like you’re still running the OEM FTDI driver. the apple one works.

remove this way:

sudo rm -rf /System/Library/Extensions/FTDIUSBSerialDriver.kext

and for good measure:

sudo rm -rf /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext

might help i hope

fourhexagons · 2018-12-24T00:32:58.203Z

Thank you, @tehn. I know you juggle a lot. I appreciate the attention and care you put toward the community.

So, about the stuff. I ran those two lines in Terminal. The first was successful, and the second returned this:

→ sudo rm -rf /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext
rm: /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/MacOS/FTDIUSBSerialDriver: Operation not permitted
rm: /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/MacOS: Operation not permitted
rm: /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Resources/English.lproj/InfoPlist.strings: Operation not permitted
rm: /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Resources/English.lproj: Operation not permitted
rm: /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Resources: Operation not permitted
rm: /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist: Operation not permitted
rm: /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents: Operation not permitted
rm: /Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext: Operation not permitted

I checked to see what’s where:

→ mdfind -name FTDIUSBSerialDriver
/Users/bryannoll/Downloads/FTDIUSBSerialDriver_v2_2_18.dmg

That’s good, right? Just the installer.

I then reinstalled serialosc. And restarted. And during the restart, the computer shut down entirely. So I started back up and it shut down again. So then I unplugged the Arc and booted up in recovery mode to run some first aid in disk utility. It all checked out fine with no errors, so I restarted.

I then waited until opening Max (arc-test.maxpat) before plugging in the Arc. Still not recognized.

So I ran this again:

→ mdfind -name FTDIUSBSerialDriver
/Users/bryannoll/Downloads/FTDIUSBSerialDriver_v2_2_18.dmg

Is that still the expected result after having installed serialosc? I figured the Apple one would be listed, but I guess it’s named something else… right?

So… any idea of a next step?

fourhexagons · 2018-12-24T00:33:55.197Z

Ah, thanks. I’ll email about it.

The answer to your question is ‘I think so’. I’ll expand more in the email.

FLart · 2018-12-26T11:44:22.000Z

Hi Here!

So long time not being there!
Got a brand new laptop now with max7 and want to reinstall my grid and use my patches…
Got an early 2011 128 walnut (old usb connection and first varilight)…
Installed serial osc, opened patch randomly (meadowphysic), but grid not recognised :-/
Any basic ideas??
Thanx a lot!!!
reno

tehn · 2018-12-26T15:14:13.754Z

@fourhexagons

does the grid work? or are both arc and grid not detected?

@FLart open Activity Monitor, do you see serialosc running? open Terminal, type ls /dev/tty.usb* what do you see?

FLart · 2018-12-26T15:34:48.418Z

tehn:

ls /dev/tty.usb*

Hi Brian…
Thanx for answering so fast…SO:

This is what i see in terminal:

MBP-de-Renaud:~ renaudcarton$ ls /dev/tty.usb*
/dev/tty.usbserial-m0000008

Can’t find serialosc in Activity… :-/
And btw, i’m running High Sierra OS 10.13.3

fourhexagons · 2018-12-26T15:36:32.041Z

Grid exhibits same behavior. See numbered list in my original post for more Grid details.

FLart · 2018-12-27T14:16:09.802Z

Oups, sorry… Now i can see serialosc, and everything is running ok!
Thanxx!

dlf · 2019-01-15T09:53:59.771Z

so, finally got to trying the 40h on another machine, working fine
seems to have something to do with the hackintosh i tried using it with, makes sense √
happy it’s still working !

richy486 · 2019-04-13T18:39:07.250Z

Hi, I’m having the same trouble with my 256 walnut.

When pluged into power the game of life demo plays and when I plug it into my macbook USB it doesn’t show up in test-grid.maxpat.

I haven’t used any other Monome devices on this MacBook before, previously I used the 256 on another MacBook but I didn’t clone that one to this one when I changed.

I’ve tried, I think everything in this thread with no luck.

The 256 shows up in System Report

1Eqekunj_cAXKpC3Ddvcddwcc_u983yNszP8bLiU9phmwNA8MK-XM2v5EsnXX-9bICrCToPXwIYxLSHP6tEuRzwgiBdC1ePOY8xiirN1FqOauOQjdDimybwHEJIyolS1chMmRedo1118×1574

And here is System Report with it unplugged

V41NjNT_jQqYODGZyHHut2oTTUVIpoq8OMFpMIHOyhmnxELohxYNGeQ6knd1pPZsLjQs_Z3nvpX04S-dwJJCNf2rIwSTeRkVB7-n2VIXFOU7Kt_mBJuXN-E2YGNu7AByEM6aKxDH856×1320

This is my Mac’s info:

Ey8vlKs6_ADAmkiL1hko4iZEsfzP-cefy9Gydi3ItgOCeyzUIYbd5zp7V0JIU4WkSmqse72AfvG836w-I-_L-fZK-PYiQ12jidT-krrnsPoKs1NDLYuufpKPDCEvyJcEMMmX8rCc1160×728

And test-grid.maxpat:

YWzai4JvGAWT6pLvaXy5dgcVo2uXA_MFoBwt_KZbHQXKWoarnOXSGa_ToJy3-HyAXgAhI7B8hzVJYMhTEfWoSTVp0MN5nRmB4jk1990F2fIUeMZT1hZNEa9rYfmX_tI-vCJeAtHU1048×1232

I’ve tested the USB port with my iPhone being recognised by Xcode.

I tried the FTDI driver install via recovery mode, no difference.
I also tried a random USB hub, not difference either.

Here is some output from terminal with commands mentioned in this thread.

$ launchctl list | grep serialosc
540 0 org.monome.serialosc
$

$ sudo dmesg | grep FTDI
Password:
$ 

$ ls /System/Library/Extensions/ | grep FTDI
AppleUSBFTDI.kext

$ ls -l /dev/tty.usbserial-*
ls: /dev/tty.usbserial-*: No such file or directory

$ ls -lrt /dev | grep usbserial 
$ 

$ kextstat -l | grep -i ftdi
$ 

$ mdfind -name FTDIUSBSerialDriver 
/Users/richy486/Downloads/FTDIUSBSerialDriver_v2_4_2.dmg
/Users/richy486/Downloads/FTDIUSBSerialDriver_v2_2_18.dmg

$ ls /dev/tty.usb*
ls: /dev/tty.usb*: No such file or directory
$

Not sure what to do next, I’m open to sending it in for repair if needed.

tehn · 2019-04-14T12:31:25.439Z

does the game of life stop when you plug it in?

it’s very strange that the FTDI would show up in the system report but not show up as /dev/tty.usb* in the terminal.

when was the last time this was working properly?

richy486 · 2019-04-14T16:43:22.414Z

Yeah the game of life stop when I plug in the USB to the MacBook, it doesn’t start again if I unplug the USB.

Also I installed, tested and removed the FTDI drivers through recovery mode earlier.

Last time it worked properly was on a different MacBook about 5ish years ago. I’ve been traveling and just got it back

richy486 · 2019-04-26T04:21:04.168Z

Small update, not working yet though

I found this site that suggested unloading and reloading the Apple USB driver:

$ sudo kextunload -p -b com.apple.driver.AppleUSBFTDI
Password:
$ sudo kextutil -b com.apple.driver.AppleUSBFTDI -p AppleUSBEFTDI-6010-1

Then I re ran this command and got output which I didn’t previously

$ kextstat -l | grep -i ftdi
  179    0 0xffffff7f840d8000 0x3000     0x3000     com.apple.driver.AppleUSBFTDI (6.0.0) E02B2C48-3077-35EC-A20D-3FADE3593128 <178 81 23 6 5 3 1>

The 256 still isn’t showing up in test-grid.maxpat or mlrv 2.5.app but now when I unplug it from the MacBook the Game of Life starts up again, this didn’t happen before reloading the driver.

This command still shows “No such file or directory”:

$ ls -l /dev/tty.usbserial-*
ls: /dev/tty.usbserial-*: No such file or directory

Not sure what to try next, is there anything I’ve missed that I can try?