Ok, trying to troubleshoot the issue I was having with my arc not showing up on my mac mini (10.11.2 / 7.3.1). Even with my newer grid connection is always patchy, as it connects the first time, but if I unplug or replug it won’t show up again (until I restart Max), or if I quit a patch and reopen it, the same thing.
I haven’t thought much about it since I don’t really perform with this machine, but as I near getting TPV2 ready for performance, I’ll be switching over to the js version of serialosc as well, and I want to troubleshoot the actual issue.
So I’ve tried running (as explained on the setup page, for former FTDI stuff)
sudo rm -r /System/Library/Extensions/FTDIUSBSerialDriver.kext
And it it just tells me:
rm: /System/Library/Extensions/FTDIUSBSerialDriver.kext: No such file or directory
I also ran this:
ls -lrt /dev
And I get this:
crw-rw-rw- 1 root wheel 31, 3 22 Oct 11:06 cu.usbserial-m0000229 crw-rw-rw- 1 root wheel 31, 5 22 Oct 11:06 cu.usbserial-m0000004 crw-rw-rw- 1 root wheel 31, 4 22 Oct 11:10 tty.usbserial-m0000004 crw-rw-rw- 1 root wheel 31, 2 22 Oct 11:11 tty.usbserial-m0000229 crw-rw-rw- 1 root wheel 11, 0 22 Oct 11:18 random crw-rw-rw- 1 root wheel 3, 2 22 Oct 11:18 null crw-rw-rw- 1 root wheel 14, 18 22 Oct 11:18 io8logtemp crw-rw-rw- 1 root tty 15, 1 22 Oct 11:18 ptmx crw--w---- 1 Rodrigo tty 16, 0 22 Oct 11:18 ttys000
(I cropped a ton of entries off the start)
Now just to be thorough I loaded up TPV1 in Max6 (which uses the May-14 version of serialosc) and that works just fine. In fact, if I opened up a patch that uses the js version of serialosc in Max7 and then open up the May-14 serialosc in Max7 as well, the js version works fine too (auto-populating the umenu).
So the serialosc server/FTDI stuff appears to be working fine, which leaves just the js version being the only difference.
Is there something else I should be doing? (I did a forum search but nothing concrete to do)
There’s also the option of just using the May-14 serialosc instead of the native one, but that’s a bit lame.