#16

the problem is simply keeping up with OS updates and that are imposed upon us all.

the much more real problem is that OS updates that break everything are happening much more frequently.

monome is hardly alone with these issues.

given we’re an incredibly small operation (it’s just me here, and you, the community) the best way forward is thorough detailed bug reports, and being very very skeptical of operating system updates. because honestly, Apple hasn’t done much for me since 10.6.8-- when everything ran perfectly.

i was just forced to buy a new computer after this one wouldn’t upgrade to the newest broken thing, so i’ll be testing the new broken thing now. thank you for your patience-- we’ll work it out.

3 Likes
#17

@tehn, I hear you. I was fighting upgrading from snow leopard forever. I’m going back to my mountain lion back up for now and not worrying about the newest thing.

#18

fwiw i just installed El Cap today. i had to reinstall serialosc 1.4, reinstall Java SE (for max/m4l), and everything is working fine now.

#19

@abozzelli
i’ve only had this issue with serialosc versions prior to 1.4. it happened all the time, but not once since i upgraded to 1.4. when u unplug, replug and it won’t connect, go to activity monitor and check the cpu usage for the serialosc processes. is it at 100%?

#20

serialosc it’s at 0% all the time.
I’ve tried to upgrade to 10.11.2, java from the link you have provided, max 7.1 and serialosc 1.4 with no luck.

#21

crap, well that’s my exact setup except i’m using a 2012/13 model 256. i’d be curious if @jasper_ryder is using a 2015 model as well? could be related.

#22

grid models are not going to make much of a difference-- they all have exactly the same FTDI chip.

on this new 2015 mac the usb ports randomly fail to detect various usb flash drives. ie, one side doesn’t work, flip to the other and it works, etc. without repeatability. this isn’t great news for apple inc.

#23

Well - apologies if I came across as a dick. Does it all work better on Windows?

I was really expecting the mac experience to be a big step up from PC - but experience has not borne this out.

#24

2012 grid on a 2012 mbp.

#25

The Sonic State guys have started calling the latest OS release “El Crapitan”. So sad.

I’m starting to come around to the idea of building a Linux box that is basically a USB/MIDI/OSC format jumbler. I need to keep using my Mac because that’s where all my synths and Live/Logic live, but it would be good to get the dodgy USB situation out of the mix.

Actually, I guess it would have to be a Windows box, since Max doesn’t run on Linux. Been a while since I had a non-gaming reason to need a Windows box. Odd.

#26

It’s a serious question though. Does everything work better on windows?

#27

i’d doubt that, slightly. for one thing, i’m not good at supporting windows-- my windows computer is hardly what i’d consider worthy of doing musical things. will, who coded serialosc, is a linux user, mac secondarily, and the windows port was a paid gig.

i’m working on a plan for future OS support. it’s a very nebulous issue.

1 Like
#28

To be fair, I just got a new powered hub and everything now works far far better. Even though the old hub was a powered unit by the same manufacturer (Anker). I upgraded to a more expensive unit on a friend’s recommendation. So I now have my interface and other utilities running off one hub and the controllers off their own separate hub.

#29

I’ve noticed that the plug for my Anker hub’s wall wart has a pretty loose fit, so I need to be careful there’s no tension on the power cable.

#30

i must report that i haven’t had any trouble with grids on el cap. i haven’t seen my weird flashdrive enumeration issue, though a motu soundcard wouldn’t work on one port but was fine on the other.

grid install from scratched worked precisely fine the first time-- to potentially put people at ease. but at the same time, i can’t speak for every hardware/software combination out there.

1 Like
#31

grid/arc detection significantly improved for me under el cap after removing the ftdi driver i had installed when running earlier versions of osx.

i’m also running the version 1.4 of serialosc

tldr;

i’ve been working on an arc app with max and noticed that each time i disconnected the arc a “phantom” monome device was left in the os device tree (open the system information app and look at the usb section). searching the web yielded lots of reported problems around ftdi serial devices under el cap. this one thread in particular suggested removing the 3rd party ftdi driver and just using the driver supplied by apple.

to my surprise i did have an older (version 2.2.18) ftdi driver installed (the system was upgraded to el cap, not a clean install). removing /System/Library/Extensions/FTDIUSBSerialDriver.kext and rebooting did the trick.

now when i plug in my arc i see the apple driver being used:
% kextstat -l | grep -i ftdi 142 0 0xffffff7f83564000 0x7000 0x7000 com.apple.driver.AppleUSBFTDI (5.0.0) 4C5CCB24-156D-31A0-9865-FECAC4AB403E <124 40 5 4 3 1>

4 Likes
Pages with new 128
Monome 256 detected as 128
Monome devices not consistently connecting to serialosc (OSX)
Issue - 64 loosing connectivity / freezing
Help, monome devices not recognized in max 7
Arc4 with Max 7.1 and El Cap
#33

you are right!
removing that file has resolved my problems. thanks a lot!

#34

Yay! fixed mine too!

#35

Great thread! FWIW: this fixed not only my grid detection problem but also issues I was seeing with other USB devices (notably external drives). Double-win!

Kudos and thanks!

#36

Solved it for me! Thanks!

1 Like