#7

just to confirm-- do the keypads work even when it’s reported as a 128? (they should)

#8

no, they dont /: well – the last 8 columns seem to receive osc, but don’t output anything.

#9

ah, maybe i got that backwards. do you mean the LEDs still work?

#10

yes tehn, that’s it (:

#11

i’m sorry to ask this-- but is there a chance you have another machine that has a version of os x lower than 10.11.3 ? or do you have a sense that this cropped up after you upgraded?

#12

no worries – obviously i’d like to help! (: i have a macbook running i think 10.11.1 … i can’t say for sure that this bug came up after the upgrade, although i never had it earlier so it may very well be linked to most recent OS. i’ll do a test on the 10.11.1 and let you know.

anything else i could try?

#13

try deleting your serialosc prefs:

~/Library/Preferences/org.monome.serialosc
#14

no /: … and it’s getting worse and worse. now the monome additionally locks up completely after pushing several buttons. i’m totally lost. after it crashes, nothing goes in or out (of the serialosc bpatcher) anymore.

#15

did you get a chance to try a different computer?

#16

ok, ran a test now. weird:

  1. hooked up the 256 to my 10.11.4. iMac (formerly 10.11.3.) » monome recognised as 128
  2. hooked it up to my 10.11.1. macbook » monome recognised as 256
  3. hooked it back up to my 10.11.4. iMac, but connected it to a different USB port » monome recognised as 256

how ever, i had tried ( 3.) multiple times in the past, unplugging and replugging to different ports, restarting, deleting preferences – solving the problem remained to appear random. i therefore assume that this is no long-term solution.

can you make any sense of this, brian?

#17

Completely random suggestion: have you tried removing /System/Library/Extensions/FTDIUSBSerialDriver.kext and rebooting?

#18

hello @abozzelli – for some reason i don’t have this file :? any clue?

yeee, this problem is really annoying. connecting my monome currently works like 1 in 15 times – the other times it involves various restarts, reconnections and whatnot :frowning: furthermore, it seems to be getting more and more labile.

#19

and another observation – it’s getting weirder:

most of the time, when my 256 is detected as a 128 and i unplug it and plug it back in (while max is running) – the serialosc bpatcher’s umenu doesn’t show any device (only choice in the dropdown is “none”). ocasionally how ever, this does work (how ever the selection remains 128, not 256). if i repeat the step, i’ll at some point have a whole list of 128’s in my dropdown

#20

the grid has no “memory” so plugging it into other machines won’t affect behavior.

however, you mention that 10.11.1 works? so we can narrow this down to a 10.11.4 issue?

#21

just an idea, u might want to open up the case and verify all the ribbon cables are secure. maybe some loose cables are causing the problem?

#22

update: it’s NOT working on my 10.11.1 machine, anymore. it’s now also detected as a 128, there. seems to have been a coincidence :frowning:

#23

ok-- sadly it’s possibly time to open up the hardware and ensure all of the cables are firmly attached to each board.

#24

no problem – i’m happy to try anything! … have just unscrewed the 4 screws on the back. it doesn’t “come out” (: any quick help?

#25

i had a 2011 256 so i have some experience with this. what i’d do is back out all the screws just a bit, then tap them gently with a hammer or something and usually the faceplate would start to give. (rotate between all 4 screws so you’re pushing the faceplate out evenly on all sides.) make sure u do this over a bed or something soft… u have to be really careful you don’t damage the enclosure.

if the enclosure is super tight on the faceplate like this, once u get it out, u might not be able to get it back in without some sanding. just a warning, u might want to wait and see what @tehn says.

#26

working on this via e-mail. will get it fixed!