MacOS 10.13 (High Sierra) and serialosc

[wader]

Thanks for your response. I’ve been following that thread for a while. I hope there will be a nice solution at some point!

[stevieraysean]

After some more tinkering tonight, I’m pretty sure my system is completely reliable.

The only thing I’ve done further to installing the FTDI driver and disabling apples one as per my post above (post 195) is:

The chgrp -R wheel FTDI… command listed in that post. I don’t think this did anything though.

The other thing I did which I think may be the fix is delete the monome devices that showed up in device list in network preferences. When the system asks if you would like them added next time the device is plugged in select no. This was triggered by reading some FTDI docs where they mentioned that Apple asked them not to add their device into there anymore. For some reason they were still being added…perhaps being in this list causes some conflict when the device is plugged in and serialosc can’t get control of it

[california2022]

This command chgrp -R wheel FTDI shouldn’t do anything. You’re just telling the computer that the group of users called wheel now own the directory called FTDI and all of its contents. That seems like a misinterpretation of installing a python wheel or something.

I’ll have to give your method a try and update here if it works.

[stevieraysean]

I think wheel is a group of users who have access to super user. Something left over from Unix. If you ls -l in /Library/Extensions you see the files already have wheel associated with them.

I think getting rid of the devices from the system preferences / network is of more importance to getting serialosc going well. That and disabling the Apple driver.

[wader]

I went through the steps, but my 40h still doesn’t show up in any max patch. I also removed it from the network devices. It’s visible in About this Mac > System Report > Hardware > USB > … I even tried it directly in a USB port on the machine, instead of through a hub … nothing.

[hyena]

i’m on a macbook pro early 2011 (i7), 10.13.6, latest sc and serialosc.
i have no problem with it if i start SC with the grid already attached.
so no hotswap but the rest is working properly

EDIT: no, i can unplug it and plug it back IF it was plugged the first time SC is run. then i can remove it and plug it back with no problem.

[tehn]

@artfwo recently did some fixes to get 10.13 working well, but then apple hit 10.13.6 and it seems they changed something minor again

i’ll get mine upgraded to 10.13.6 and see what happens. thanks everyone for the suggestions here.

[wader]

Cheers Tehn… I switched back to MonomeSerial again, but it’s fussy and doesn’t like the device being unplugged.

Actually I really like the functionality of MonomeSerial and would be super-interested if it were possible to assign every button with a MIDI note or CC event with specific value. I can’t imagine needing anything else for basic switching purposes.

[jessemiller]

Connection with monome and SerialOSC is very inconsistent. I’ve read a number of threads about FTDI drivers and tried various combinations, but it still the same. Sometimes monome shows up in serialOSC, sometimes it doesn’t until I restart CPU. If I unplug and re-plug monome, sometimes it flashes LEDs, but often it doesn’t.

Is there a set of steps to trouble shoot? Running this on a mid-2012 macbook pro, OSX 10.13.6

Part of the issue seems to be that the USB connection to the monome itself is touchy. Is there any type of cleaning that might be helpful?

[tehn]

Part of the issue seems to be that the USB connection to the monome itself is touchy. Is there any type of cleaning that might be helpful?

that’s actually probably the main problem unfortunately. not likely something that can be cleaned, but the USB port should probably be replaced because the contacts are bad (ie, the plastic housing internally is broken). e-mail info@monome.org if you want to send it in

or, have you tried another usb cable?

[alanza]

So far mine works as expected in 10.13.6, but I’ve really only opened a Max patch or two, so I’ve hardly stress-tested it. (edit – my mistake, I thought sum was M4L, but that’s terms or something)

When I have time I’ll try to give some of the M4L stuff a whirl and see if that is also working for me.

[MASHtheCTRLR]

Thank you so much. It has worked fine for me in the past but just recently I can’t seem to get it connected. Are there any simple troubleshooting steps I can take to find where the issue may be occurring? Thank you for your help. I really appreciate it!

[alanza]

if you haven’t yet, I’d take a look over at the getting started page—it mentions something about removing a driver? that wasn’t relevant to me since I … just got my grid, but maybe that might help you?

it probably wouldn’t hurt to reinstall the serialosc daemon as well

[tehn]

reinstalling serialosc is a good first step. it’s also helpful to know what version of os x you last had it working, or if this is a new install?

please test using Max, and the monome max package. it has a simple testing patch inside. sum has possibly not kept up with os updates. and just a warning that 7up hasn’t been actively developed for a very long time. just a general warning: since so many monome apps are community contributed and often not maintained, if you want to keep something running indefinitely it’s sadly the case that you’ll need to freeze a computer at a particular os update known to work.

10.13.6 has created problems for some people. i’m more focussed now on fixing whatever might be wrong with 10.14 since i’m sure everyone is about to upgrade to that-- i’m actually hoping apple fixed whatever FTDI problem is present in 10.13.6.

[MASHtheCTRLR]

@tehn So… I was able to use the monome max package and have successfully used terms after reinstalling serialosc. I can’t tell you how good it feels to see those beautiful orange lights working their magic again. I guess 7up (and maybe sum) got left in the dust. Time to explore new programs. Thanks again tehn. You’re so kind to devote your awesome brain power to such a simple misunderstanding. I really appreciate it.

[steinbruchel]

Hello
I’m completely new to the Monome world. I purchased a grid about a month ago and am trying to set it up, but it doesn’t get recognised in Max 7 or Max 8 at all.

I’ve installed serialosc (at least I think I did), because I have no clue how to check this. I’ve also downloaded some of the FTDI Drivers, but also there have no clue which one is the correct one and how I can check this. As you probably all notice from my post I am completely lost. I’ve checked through lot’s of the posts in this forum, but actually understand only very little of all the advices given. Maybe this whole Monome approach is a step to difficult for me?

Anyway, I apologise beforehand for such basic questions but if I could get some support and at least be pointed in the right direction I’d be very happy.

Here are some of my specs:

• Monome grid (assembled around october 2018)
• MacOS High Sierra, Version 10.13.6
• MacBook Pro, 13inch (2016)
• Connected with a USB adapter to USB-C

Thanks a bunch and sorry again for the waste of your precious time!
Cheers, Ralph

[steinbruchel]

Hello there
It’s me again, but it seems that my post has been moved to another post entitled «Monome and Max 8»? Not sure if this is the right place for my query? Hope I still get some answers…

Cheers, Ralph

[alanza]

have you installed “serialoscd”? also, you should NOT need to download any separate FTDI drivers—the standard ones on Mac will suffice.

[tehn]

I might suggest upgrading to Mojave if you can.

open Activity Monitor and you should see some serialosc processes, yes?

[steinbruchel]

I have installed serialoscd and upgraded to Mojave. Below are screenshots of the Max console and also a screenshot of the Activity Monitor (serialoscd seems to be installed). Any clues please?