#60

hi there, I have an even more peculiar niche issue … running a Hackintosh with 10.10.5 installed. Did not even have the AppleFTDI kext installed it seems (or at least sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled did not give any result), does have the OEM FTDI installed now. Seems that this Shuttle SX79R5 might need a particular kext of its own for this to work ?

launchctl list | grep serialosc returns
406 0 org.monome.serialosc

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

ls -lrt /dev | grep usbserial returns nothing, just a new bash line

kextstat -l | grep -i ftdi used to return something like below, but since running the ftdi drivers it no longer returns anything.
131 0 0xffffff7f828a5000 0x7000 0x7000 com.apple.driver.AppleUSBFTDI (1.0.1b16) <110 42 5 4 3>

serialosc and -detector are both running.

Another thing maybe worth mentioning is that the monome does show up fine in the system profiler usb list. (and works without problems on other machines here, just need to get it going on this particular machine which will go on the road for live performances)

Have to say, all other USB devices, soundcards, midi controllers, etc run without any problems. (and I did try moving it from the usb hub to the other usb ports on the machine; no go)

38

Any pointers much appreciated !

(update 1)

indeed, these kexts are loaded

AppleUSBAudio.kext
AppleUSBDisplays.kext
AppleUSBEthernetHost.kext
AppleUSBMultitouch.kext
AppleUSBTopCase.kext
and
FTDIUSBSerialDriver.kext

(update 2)

I downloaded the 2.4.2 FTDI drivers from https://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriver_v2_4_2.dmg
removed the previous FTDI and installed the 2.4.2

kextstat -l | grep -i ftdi now returns
111 0 0xffffff7f818c4000 0x7000 0x7000 com.apple.driver.AppleUSBFTDI (1.0.1b16) <110 42 5 4 3>
122 0 0xffffff7f8283d000 0x7000 0x7000 com.FTDI.driver.FTDIUSBSerialDriver (2.4.2) <110 42 5 4 3 1>

I can’t find the AppleUSBFTDI that seems to be loaded anywhere … ?

kextstat_result.txt (11.8 KB)

(update 3)

mmm, clean installed a new system, 10.12.6 – same issue …

(update 4)

mmm, decided to try it on my mac pro 5,1 - also running 10.12.6 – same issue …
could it have anything to do with my device being a 40h ?

#61

40h should work fine, but when was the last time you knew it to be working? does it give the powerup blink?

#62

good question, there’s no blink, few buttons are green, rest is off

#63

and when was it working last?

#64

before i stored it in a box on the shelf, approx a year ago

#65

tried it on another machine with 10.13 and other usb cable, same problem,
so I can assume it’s broken ?

#66

Happy Solstice weekend :star2:

So, thought I’d try and join the arc + grid computer party, but I’m experiencing similar connectivity issues to the above mentions.

The Issue
My arc and grid aren’t reliably recognized by computer.

What I’m Using

  • I’m using the 2015 grid and 2016 arc on a Mac running 10.14.2 (18C54) with Max 7.3.4 and serialosc 1.4.1
  • I have also tried sudo rm -rf /Library/Extensions/FTDIUSBSerialDriver.kext followed by a reinstall of serialosc
  • FWIW, I say I’m using serialosc 1.4.1, because that’s what I downloaded and installed, but truthfully, I can’t figure out how to use -v in Terminal to confirm that’s what I’m using.

What Happens
Often, when first restarting the computer, the arc will light up like this:

arc-lights-post-reboot
arc-lights-post-reboot.jpg3929×1034 976 KB

Hot-plugging results in the lights briefly flashing upon replug, then staying off. I’ve been unable to determine a pattern of behavior, so I’ll just recount my last experience:

  1. After reboot with arc remaining plugged in, open arc-test.maxpat. It recognizes the arc:
  2. Open Ableton and load ArcLab. Arc is still recognized.
  3. Quit standalone Max. Arc still recognized.
  4. Open ArcControl in Ableton. Arc still recognized.
  5. Hotplug arc. Still recognized.
  6. Hotplug arc again. Still recognized.
  7. Unplug arc and plug in grid. Open Gridlab Alfred. Grid not recognized.
  8. Unplug grid and plug in arc. Arc not recognized.
  9. Hotplug arc. Still not recognized.
  10. Restart computer. Get the ‘there was a problem’ dialog box upon restart. Arc lights up as per above photo.
  11. Open Ableton and load ArcLab. Arc is not recognized.
  12. Unplug arc and plug in grid. Open Gridlab Alfred. Grid recognized.
  13. Hotplug grid. Not recognized.
  14. Unplug grid, plug in arc. Arc recognized.
  15. Hotplug arc. Arc not recognized.
  16. Unplug arc, plug in grid. Grid not recognized.
  17. Use breath to move disappointment through body and into earth.
  18. Go back to lines to ask for help.

Terminal Outputs

→ ls /System/Library/Extensions/ | grep FTDI
AppleUSBFTDI.kext
FTDIUSBSerialDriver.kext

→ kextstat -l | grep -i ftdi
  147    0 0xffffff7f843e0000 0x8000     0x8000     com.FTDI.driver.FTDIUSBSerialDriver (2.2.18) 638ECCC3-375D-CD1A-C2EC-0DC14740FC9C <70 53 6 5 3 1>

→ mdfind -name FTDIUSBSerialDriver          
/Users/bryannoll/Downloads/FTDIUSBSerialDriver_v2_2_18.dmg
/Library/StagedExtensions/System/Library/Extensions/FTDIUSBSerialDriver.kext
/System/Library/Extensions/FTDIUSBSerialDriver.kext

And I’m able to provide any more logs and such, I’m just not sure what to run and what it’s actually doing, so I’ll need some hand-holding.

Thanks ~

#67

by grid not recognized do you mean it’s not showing up in the drop-down bit ? or just no light things happening ?

this might be plenty deep in the dumb & obvious zone but i get stuff not connecting in m4l in current macos occasionally and I quit ableton then quit max7 & that seems to make everything happy again

&& the arc lights flashing when you plug it in is just the fun thing that happens when you plug it in nothing buggy there

1 Like
#68

Ah, good question. By not recognized, I mean not showing up in the dropdown.

#69

ah - yea a restart of max (which doesn’t happen w/ a restart of ableton) has never not fixed that 4 me but ¯\ (ツ)/¯

#70

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

1 Like
#71

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.

#72

Ha! Yes. It is. Thanks for the support :hugs:

1 Like
#73

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

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 ?

#74

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

#75

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

#76

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?

#77

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

#78

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?

#79

Ah, thanks. I’ll email about it.

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