#29

No, but you can run the following commands:

sudo rm -r /Library/Extensions/FTDIUSBSerialDriver.kext
sudo pkgutil --forget com.FTDI.driver.FTDIUSBSerialDriver

Then reboot (and this is important!)

#30

monomebridge doesn’t have midi built-in, and now that you’re asking for that i realize you don’t even need monomebridge.

instead

download max
get the monome package
run grid-midi.maxpat which is included

and you’re good

4 Likes
#31

Righteous, got it working! Thank you so much!!!

#33

I originally posted in the High Sierra thread that my grayscale 128 is not working. It is still not working in Mojave.

When I execute ls -lha /Library/Extensions/ | grep 'FTDI' I only see this FTDI file:

drwxr-xr-x@ 3 root wheel 96B Dec 16 2015 FTDIKext.kext

When I execute: ls /System/Library/Extensions | grep FTDI:

AppleUSBFTDI.kext

Executing serialoscd results in -bash: serialoscd: command not found. However ps -ef | grep 'osc' shows that serialoscd and serialosc-detector is running.

501   585     1   0  9:27AM ??         0:00.01 /Library/Application Support/Monome/serialosc.bundle/Contents/MacOS/serialoscd
501   654   585   0  9:27AM ??         0:00.01 /Library/Application Support/Monome/serialosc.bundle/Contents/MacOS/serialosc-detector

The grayscale 128 is connected to my computer:

29%20AM
Screen Shot 2018-12-16 at 9.43.29 AM.png1018×350 18.3 KB

When I had High Sierra I tried many combinations of the FTDI driver and am not sure if I have properly cleared all the results of those attempts. My computer is a 2015 Macbook Pro Retina, and I have Mojave 10.14.1. Does anyone have any advice?

Thank you.

#34

Ok I’m having a problem I had a couple years ago again.

When I fire up Max and connect to a device the first time, works awesome. If I close that patch, I can’t get anything to connect to any monome device again until I quit out of Max and restart.

#35

delete that file and see if things improve. that’s the OEM driver.

augh. what OS point version are you on?

#36

10.14.1 (though I see a 10.14.2 is out). I’m on Max 8.0.2, but I can also test the problem out on 7.3.5 as well.

edit: did some further testing and it all appeared to work right (in both Max8/Max7) BUT it still did fail to reconnect on one of the tries (maybe like 1 in 10 attempts).

At first it was all perfect, then I realized I was plugged into a different port last time (left side vs right side (which I guess are different on the 2017 MBPs)) and when I switched back to the left side, it failed to reconnect…

But after that it was fine. So not sure what’s going on.

Let me know if you want me test anything or have terminal spit something out.

#37

@tehn - removing /Library/Extensions/FTDIKext.kext did the trick. My grayscale 128 works again. Hooray!

#38

FWIW:

grid/serialosc and Max all seem to be working fine here. All software installed today (012919). Grid reconnects fine when changing Max apps.

MacOS 10.14.2
serials 1.4.1
Max 8.0.3
grid 128 (2018)
MBP 2017 w/SSD

2 Likes
#39

Not a beginner, but have had these similar issues many years ago with my first Monome 40h, rarely with my old walnut non-varibright, and now with my 2018 grid. All my usual fixes aren’t working and I suspect I’m another victim of the fickle Apple audio driver policies.

My grid appears under devices:

29%20PM
Screen Shot 2019-10-20 at 9.00.29 PM.png1504×1046 132 KB

But does not appear in Max 8 under monome grid-test, @neauoire’s fantastic Linn or Rack devices, OR in my old reliable Mark Eats Sequencer app that usually has the best track record of connectivity.

Running the following command:

Yields:

no matches found: /dev/tty.usb*

I’ve deleted FTDIUSBSerialDriver.kext (which is the old fix that usually works), I’ve reinstalled SerialOSC through the monome setup docs and nothing.

SO… help? :grimacing:

For what it’s worth, I was initially attempting to use the grid on the Trilogy VCV rack modules and no dice, but the grid DOES work on my Norns.

MacOS Mojave 10.14.6

Monome Beginner Questions
#40

you restarted your computer as well, right?

#41

did you install the FTDI VCP driver? you need to, if the other one was deleted

in the newest MacOS this is generally not needed (the included driver now pretty much works)

#42

@alanza Always! :wink:

@tehn no dice… installed v2.4.2 (which I believe I have done before) from here https://www.ftdichip.com/Drivers/VCP.htm and no changes in response from the commands above.

I don’t think it work previously and eventually I ended up deleted it to get @neauoire’s rack/linn instruments working previously Pre-Mojave upgrade. Or maybe it was back during early days of norns and I was having trouble connecting to norns through serial before I made the switch to ssh/ftp.

#43

UPDATE: ignore everything I said. On a lark, restarted one last time I ran the command again and got:

> /dev/tty.usbserial-m1000539

… holy cow it works… on everything Rack, Linn, MarkEats, Max and VCV. :exploding_head:

Thank you VERY much for your continued 5 star support and nurturing. I’m thrilled to belong to this community. :heart:

4 Likes
#44

Don’t know if it warrants a bump in this thread, but in downloading the ftdi driver, my MacBook wouldn’t start again and I had to reboot from a time machine backup.

So, as of now, is it recommended to only use apple’s include ftdi driver with serialosc to get a monome working on 10.14?

#45

here’s the basic troubleshooting script I use for FTDI help requests:

  1. On your 10.14 device, open Activity Monitor and search ‘serialosc’ – you should see something like this:

    ?name=inline-772553309.png1600×296
    ​
    If not, then serialosc is not installed: https://monome.org/docs/setup/

  2. Once you confirm serialosc is installed, please connect the device and execute ls -lrt /dev/tty.usb* ​in terminal. You should see something like this:

    ?name=inline2077157953.png1092×146
    ​
    Please share the output you get from that command.

  3. Confirm what FTDI drivers are on your system by executing ls /System/Library/Extensions | grep FTDI ​in terminal.

  4. If you’ve gotten to this point and things are still not working, try this in terminal:
    launchctl unload /Library/LaunchAgents/org.monome.serialosc.plist ​
    and then: launchctl load /Library/LaunchAgents/org.monome.serialosc.plist
    This will kickstart serialosc. Open up [arc-test OR grid-test].maxpat, make sure the Max console is visible (shift+CMD+M) and plug in your device. You should see some messages in the Max console and you should be able to connect.

  5. If things are still wonky, please try installing the OEM FTDI driver. Here’s a link: https://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriver_v2_4_2.dmg

if you get all the way to step 5 and no success, please email help@monome.org <333

3 Likes
#46

A post was merged into an existing topic: Apple/Mac issues: hardware, firmware, interfaces, etc

#47

Thank you so much for responding! Still no luck, up to step 5, and before I install the FTDI Driver here’s what I’ve done:

Here’s my setup:
OSX 10.14.5, Macbook Pro 2012, x1 USB 2.0, x1 USB 3.0, SerialOSC 1.4.1, Max 8, “series” 64 monome

I have serialosc 1.4.1 installed along with Apple’s FTDI drivers after the reboot, and the result from the terminal was this:

crw-rw-rw- 1 root wheel 18, 10 Oct 29 13:06 /dev/tty.usbserial-m64_0525

Serialosc seems to be updating when I plug and unplug the monome64.

Still nothing in the devices dropdown in either apps or Max patches, so onto downloading the FTDIUSBSerialDriver_v2_4_2.dmg.

#49

I got prompt help from the folks here and at Cycling 74’ .

My problem ended up being related to me changing my network settings in order to create an ad-hoc server for touchOSC (in lieu of a monome). After setting the network preferences (under wifi) back to default, serialosc began to work!

I’ve never gotten to use a monome before now so I’m jacked:)

1 Like
#50

so glad it worked out! thanks for closing the loop here :slight_smile: