im dealing with the exact same problem

1 Like

moving up to 10.13 now

2 Likes

Things definitely didn’t work with the builtin driver on 10.13 for me

1 Like

Im getting the same thing High Sierra, Early 2015 MB, Monome Grayscale, device appears in terminal,
Device not appearing in mark eats sequencer app or any max patches help please :slight_smile:

1 Like

Second this.
I have a fresh install of high sierra on a mid 2014 MBP 13" with an old walnut Monome 128 on which I did the bus power mod. The monome is showing up in terminal (/dev/tty.usbserial-m128_100) but no go in max or Mark eats.

I think it’s a serialosc thing, but not sure how to test:

The 1.4 pkg seemed to install the serialosc binaries here: /Library/Application Support/Monome/serialosc.bundle/Contents/MacOS

And homebrew installs them here: /usr/local/Cellar/serialosc/1.4/bin
Homebrew version just crashes every time I try to run it though, so… no idea. (segfault 11)

I’ve uninstalled and stopped the pkg installed one and am now fiddling with homebrew, but would love advice. Thanks!

I have now uninstalled and reinstalled both ftdi and serial osc, and installed them in multiple combiantions and each one alone without any results, full ssd sytem fyi, is there any possibility of serialosc being updated? Or should we just roll back, My system wasd working with Sierra but high sierra Monome cannot be seen

this is a clue. there didn’t use to be underscores in the device name, which is required for serialosc detection.

this of course makes no sense that some people have things working fine.

i’ll put together a further test for people to try, in about an hour once i grab an older unit

That’s hugely appreciated, thank you.

Not sure if this helps, but here’s what system report gives me:

monome128:

Product ID: 0x6001
Vendor ID: 0x0403 (Future Technology Devices International Limited)
Version: 6.00
Serial Number: m128-100
Speed: Up to 12 Mb/sec
Manufacturer: monome
Location ID: 0x14200000 / 11
Current Available (mA): 500
Current Required (mA): 0
Extra Operating Current (mA): 0

ok, this is indeed the problem. 10.13 is somehow changing the dash to an underscore. thanks apple.

working on a fix now.

3 Likes

Thank you very much for looking into this! We all owe you a beer :smiley: if you fix it of course :wink:

2 Likes

Any progress on this one guys?

waiting on @wrl unless someone else can jump in earlier. give us a few days, send apple kind holiday cards in the meantime.

4 Likes

Following this one.
Mine doesn’t work after I upgraded os to 10,13,1.
my old computer is 10.12 and works fine.

Is there an update? Fiending for some grid time.

It looks like no. There are two issues:

The root cause appears to be serialosc and has been tracked down in theory: https://github.com/monome/serialosc/issues/38

But the fact that serialosc doesn’t compile on 10.13 serves as a blocker: https://github.com/monome/serialosc/issues/39

Anyway, with luck @tehn or @wrl will be able to wrangle it soon, or another good samaritan with knowledge of build scripts.

1 Like

apologies for the delay, it’ll be fixed soon, hoping for the next few days.

2 Likes

Miracle on 128th street?

did you try this?

I should mention if it hasn’t been brought up already that doing even point system updates now will reinstall the Apple ftdi driver. My setup stopped working after update and I had to remove it and also recompile serialosc from git head

3 Likes