Help, monome devices not recognized in max 7

[tehn]

wow, ftdi. wow.

use the one on the right.

[laborcamp]

ok, ran the installer, then did the Terminal commands, though one said that “operation was not permitted”… not sure why.

[laborcamp]

OMG! @tehn, this did the trick!
I rebooted the mac, and Max found the arc on the first try!

[tehn]

well, you failed to disable your appleFTDI driver, but it is broken anyway, so, glad it’s working. despite not being able to explain. it’s like the apple driver is just locked.

[laborcamp]

However…

It only happened once.

Still high on the headrush of the arc being recognized, I disconnected the arc, and tried the grid: no luck.

Then re-connected the arc: no luck.

Tried this with re-starting Max: no luck.

So, am back to no devices recognized, but feel slightly encouraged by that glimmer of success…

FURTHER TESTS:

After doing the above, I plugged the arc into the other USB port on the other side of the mac, which worked instantly: Max recognizing the arc.

So, again I tried the grid, which it failed to recognize.

After that arc was not recognized again, neither was the grid.

It seems that the arc was recognized only once, in each of the wt USB ports, and either trying the grid on the ports somehow “corrupted” the port or something else leaves some sort of “trace” that prevents subsequent connections.

Rebooting the laptop cleared things up again.
So I did many tests plugging and re-plugging the grid and arc into the two ports.
Sometimes Max will remember the devices, sometimes they need to be re-plugged into the opposite ports. I was able to have both of them connected and communicating, yet at another time only one of them would be recognized.

I also noticed that arc test app would show 3 instances of arc!?

AND I tried the USB hub, which, when hub was connected to laptop, crashed Max on startup each time.

I am not sure if any of the above information sheds any further light on what might be causing this odd behavior, but I wanted to share in case this might help you diagnose further.

Thank you for all the help.
It seems that some progress was made: feeling optimistic!

Both devices running:

Three arcs, but lost grid:

[ioflow]

i have a couple of datapoints on your troubles. you mentioned that you’ve been doing upgrades from old OSes and specific school-loaded profiles. assuming the school didn’t lock out certain functions (i’ve worked with school-issued macs; they always have weird lockdowns for various reasons), your permissions issues look like things i’ve faced ever since 10.8.

i’ve seen the nonworking sudo commands in 10.8, 10.11, and 10.12. i’ve had to run “su admin” (or administrator account name), punch in that password, and then as admin/root i can finally run tasks via “sudo whatever”. never without those steps. your inability to anything besides .pkg/.dmg installs may be related to those permission issues.

also, your devices may be getting locked or grabbed by the networking/serial subsystem of the OS, as i mentioned in another thread. if they’re getting incorrectly/inconsistently detected, there is a workaround you can investigate.

semi-related: USB hubs are generally troublesome unless they’re powered. also, update to the latest max version to be sure you’re getting all the runtime bug fixes.

[laborcamp]

Very interesting and potentially super-useful info!

What you describe sounds very familiar in terms of both:

_ school related permission locks etc.
_ the inconsistent detection scenarios you describe

I will definitely try the workaround you suggest and report back.

Thank you for chiming in!

[dolza]

The ftdi install seems to not be taking so I’ll try upgrading. As always, thanks so much for all the help!

[lloydcole]

I’m afraid I’ve just read all this as today, for the first time, I tried to use Ableton with Terms and my grid.
MacBook Pro running 10.9.5. System report is seeing Monome device, activity monitor is showing serialosc-detector and serialoscd as running with me as the user, grid is flashing briefly at connection, but pull down menu is showing ‘none’.
It’s not the end of the world, but I was hoping to investigate Terms, with Madrona sounds. I’m travelling and the rest of my system has been shipped home but I’m not home for another month…

[lloydcole]

Any news on this? Anything I can try with Mac OS 10.9.5 on macbookpro?

[laborcamp]

I feel your pain @lloydcole!
I got distracted from trying to resolve this problem. But I did try a lot of suggested spapproaches, and while I made some progress, I never got to a fully stabile solution.

[tehn]

this thread is long, with lots of suggestions on how to fight/fix the apple+ftdi problem. you’re on an in-between version of the OS where it’s difficult to know exactly what will work and what won’t.

so, what have you tried so far?

[lloydcole]

Nothing tried other than init set up. No consensus here as far as I could see… so no idea what to do. I may be able to change OS as my ties to 10.9.5 date back to FireWire which I no longer need, so if you can tell me which nearest OS I should try I can try…

[lloydcole]

It seems my 10.9.5 OS had none of the extensions needed. I installed FTDI VCP driver and now Terms is seeing the Grid. Restarted and tried again and it worked again. I have a hobby for my tour, now. Flin looks fun. Can Terms modules be linked, so that the clock from the one of the left feeds the one one to the right? It might be nice to clock Flin from something other than a perfect clock…
To be clear and if anyone else is still using 10.9.5 (the last OS to support Firewire) I installed this - FTDIUSBSerialDriver_v2_3.dmg and serialOSC and it seems to be working, so far…

[soren]

Hello,

I know this thread is horribly long - but it seemed an appropriate place to fit this:

My grid is not seen in max 7 either, and after reading this thread through several times and making sure I have no third party ftdi drivers, and that the apple ftdi driver is recognized - I’m still out of luck.

I noticed that I get a “-11” error when I run the “launchctl list | grep serialosc” command. This was @ngwese who mentioned trying this command, and that “-11” would be some kind of error. I have not been able to search my way through what that error means.

Does anyone know?

Best,
Søren

EDIT: so it seems that Max detects the monome occasionally, but it’s not very reliable.
Also, the “-11” sometimes is “0” instead but that doesn’t make a difference.

OSX 10.12.4, Max 7.3.4

[bluedonkey]

Hi, So I had the exact same problem as other people, Hunting around i think I found a solution.

1 Download the 2.4.2 drivers from FTDI’s website http://www.ftdichip.com/Drivers/VCP.htm and install. The install will succeed, BUT due to Apples built-in FTDI drivers they will not work.

2 Reboot computer and enter recovery mode Via powering down and holding down CMD + R on reboot.

3. In recovery mode open terminal from utilities at the top of the screen and type the following to tempraily disable System Integrity Protection:

csrutil disable

The computer will prompt you to reboot to make changes take effect.

4. On reboot we now need to disable the Apple FTDI drivers (NOTE: this can be reversed at any time so do not worry). - open Terminal and type the following.

cd /system/library/extensions

sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled

sudo touch /System/Library/Extensions

5. Restart your computer in recovery mode. Shutdown, hold Command + R and open terminal in the Utilities tab. Enter the following to reenable Apple’s System Integrity Protection

csrutil enable

My old walnut 64 now works … yeah!

[tehn]

i must point out that once we got to MacOS 10.10, each version update seems to have a different potential issue with the OEM FTDI vs. AppleFTDI driver. solutions change per version, quite frustratingly.

@bluedonkey what version were you having trouble with, which this process fixed?

[bluedonkey]

Hi Tehn, 10.11

It was pretty much the same workflow as your suggestion , it was just getting osx to allow the disabling of AppleFTDI. Seems to be stable. If not I’ll report here.

All the best

[tehn]

got it. FYI 10.12 and 10.13 the AppleFTDI driver works. we’ll see when they break it next

[dlf]

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)

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 ?