Help with connecting Monome 128 and Windows 10.

[kirkwoodwest]

I’ve been reading and reading… Trying a bunch of stuff lots of reboots for a couple hours now. And still cannot get the walnut 128 running.

So far this is where I’m at:

Power sequencer turns on near the usb cable and a little flash somewhere the bottom left corner on the 128.

I’ve installed serialosc 1.4.3

I’ve run serialosc-detector.exe

when i unplug and replug the monome i get another message saying com3 is connected. (that seems good!)

The device is here in the device panel:

Then I tried some of the apps.

Bonjour Print Service installed.
Uninstalled touch osc, touch osc bridge.
Manually installed the FTDI VCP driver.
I’ve disable the local firewall.

The service is running…

What else can I try here? Anything else that I could possibly report?

Thanks in advance!

[nax]

also having trouble, i have a walnut monome 64 from the 2010s. i’m trying to get it to work with pure data. also on a windows 10 machine.

trying to work through grid studies: pure data
i’ve installed serialosc, i’ve found it in Services and it says its runing

running serialosc-detector.exe looks like this

looks like mine prints ‘COM4 connected’ when i unplug and replug

also installed the vcp drivers. Troubleshooting said this might help.

The device shows up in the device panel, interesting looks like my compter says its a mouse

also installed the extrenals ‘osc’ and ‘cyclone’ for puredata, and set them up in the prefrances

the grid studies say to do this

and pushing buttons does not print nothin’

darn >:(

@kirkwoodwest did you ever get yours to work?

[McNUG]

I’m having the same problems with a walnut 64, the latest serialosc, and the latest windows 11.

[elquinto]

serialosc 1.4.3 isn’t compatible with certain grid editions (on windows). i think it’s a known issue- SerialOSC 1.4.3 on windows not compatible with monome 64 walnut edition · Issue #60 · monome/serialosc (github.com)

[McNUG]

@nax @kirkwoodwest

Update:
I uninstalled 1.4.3 and then I downloaded serialosc 1.4.2pre from the gtihub and m4l apps are now working smoothly on windows 11. For older grids on windows, version 1.4.2pre should work.
I did not have to download any additional drivers or programs.

[nax]

yay! this is gloryus! @elquinto @McNUG thank you both
uninstalled 1.4.3 with power shell, (Remove-Service -Name “serialosc”)
and installed 1.4.2pre, worked like a charm, pure data is getting things from the monome

[Coyyo937te]

Im having the same issue, is the latest grid tho the 2021 edition. uninstalled the latest serialosc driver through powershell and installed the 1.4.2pre, uninstalled my wacom drivers from a small tablet as per recommended from the troubleshooting guide.

I also installed the FTDI VCP driver manually.
installed the boinjour print service
and touch osc bridge

checked serial osc service is running.

the grid is being detected as COM6

but is not showing in max

I was trying to get the Using a Grid as Linnstrument device, and was not able to get it working either. Just tried to see if it was recognized in max,never tried to use the grid w the computer until yesterday, I just normally use it with the norns w no issues at all.

EDIT : uninstalled and reinstalled serialosc to the newest version and now is working. no idea what it was but glad is working now

[nax]

well gosh dang it, it stopped working at least i can’t get pure data to receive messages.
no clue what changed. i’ve reinstalled serialosc 1.4.2pre a couple times now, and restarted the computer each time with no success.
serialosc-detector.exe says that COM4 connected and the grid shows up in the devices. oogy boogie i guess.

[elquinto]

I’m not sure but it sounds like serialosc is probably working, maybe just the monome PD externals are out of place?

I was experiencing different issues with serialosc 1.4pre so I reverted back to version 1.2a. It works fine, although it seems to have some conflict with my midi controller (Music Thing 8mu) and I have to restart serialosc whenever I plug it in, otherwise it won’t detect my grid. Besides that I haven’t had any real problems with it.

[nax]

well, lets see.
so if i’m not mistaken this should work right?

Protokol can’t seam to see anything. Port 12002 should be receiving things from serialosc right?
from the serialosc docs`

the grid still shows up in devices.

this is with serialosc 1.4.2pre. i guess i could try with 1.2a. hmm

EDIT

also won’t connect in Bespoke synth

EDIT2

when Bespoke trys to connect looks like somethings picked up on port 12002

strange, serialosc-detector.exe still picks up the conection of the grid.

am i listening to the right port?

[elquinto]

The docs here are a little confusing because these terminal commands don’t work on windows. I’m not sure how to set up an osc monitor with command prompt or protokol, and not sure if the correct port would be 12002. In Bespoke Synth, can you select your grid in the monome dropdown?

edit- Just an idea. Have you installed bonjour print services from apple? I noticed in the past that the bonjour installation distributed by Hexler didn’t work with serialosc. I still had to install bonjour print services from apple for it to work.

[nax]

yeah i get nothing for that drop down unfortunately.

also installed bonjour and restarted the computer, that didn’t seam to help.
one weird thing happened though, no idea what caused it, i had protokol and bespoke synth open, and the grid lit up three buttons. this happened twice, with the same buttons, can’t get it to do it again somehow.

[elquinto]

Weird. It really should be working if you’ve done all those things. You mentioned earlier your monome appears as a mouse. I’m not sure why but mine appears as something else. Might be a clue? Have you tried any max patches or the monome modules in vcv rack? They don’t see the grid either?

[nax]

mabye? thanks for sugestion, i’ll check it out and see if i can get it to work in vc rack or max. i’ll also try switching over to serialosc 1.2a see if that helps. i just find it so strange that it was working and then stopped :\

EDIT

looks like a nah on max
vcv rack wouldn’t work either, but it looks like the earthsea module can’t detect serialosc? perhapes thats my problem.

interesting, this is new to me, looks like serialosc is having trouble starting. i’ll try a reinstall.

aight so in the installing and reinstalling of serialosc, looks like at some point i forgot to reinstall it again XD
we working now
vcv rack

bespoke synth

so as a suggestion to anyone reading through this later with simular problems i guess, have services open the whole time to make sure that serialosc is running. i pretty sure serialosc was installed and running when the grid stoped working… but who knows

@elquinto a supa epic big thank you for giving me suggestions X)

EDIT2

aight, so a couple things i’ve figured out to get my grid working consistently.

• if i unplug and reconnect the grid it will not be recognized by anything, a computer restart is required. restarting serialosc does not help.
• need to keep the grid connected to the computer during restart.
• after restarting the computer, serialosc is always turned off and it needs to be started, via the services app.

just happy its workin though XD

[elquinto]

Just to completely rule out the ftdi driver as being the culprit, you might want to try manually uninstalling it (you need to use the CDM Uninstaller https://ftdichip.com/utilities/#cdm-uninstaller) and install the latest version (https://ftdichip.com/wp-content/uploads/2021/08/CDM212364_Setup.zip).

[kirkwoodwest]

nope but i’m glad to see some more deep work done on this. I talked to @dani_derks the other day he convinced me to try it again… so i will have to give whatever you guys found another go. thanks!

[alancodger]

Experiencing the same issue and tried all I could ( several srialosc version ect. ) I did noticed the missing of the USb serial Converter in the device manager on my WIn 10 although I did install the FTDI drivers. For once I wanted to click on the Serial COM assigned on the device connected and manually install from the driver properties the FTDI drivers and it create 2 instances of the same ( with different Port Number ) and the Grid appeared in my M4L grid test… it worked for some minutes and when I changed the M4L to test the Re:Mix mlr it simply disconnect and so the second instance disappeared. Were I can fix for a steady WIN 10 USB Serial Converter driver? it simply not showing up

[elquinto]

What edition is your grid? It’s worth mentioning that the newer grids from 2021 onwards don’t use the ftdi chip, and only work with serialosc 1.4.3 or later. Serialosc 1.4.4 has an issue where the grid frequently becomes disconnected during use, at least that was my experience.

[alancodger]

Thanks for your reply. I completely forgot to mention I’m on the OXI One in Grid mode ( which thread has been also discussed in this forum. Followed all I could in installation and tried all possible situation avail. Worth to mention that the GRID mode work just fine on a old macbook of mine and Norns Shield, so eventually I will use my old Macbook as a spare performance grid with your M4L app ( that I wish was avail on a Norns ) is just I do not want to bring 2 laptop ( one WIN 10 and the IOS ) were I could simply switch between software instead. Thanks for yout time
P.s. the Treeview USB software is indicating the grid to connect as GIga USB Serial Device, don’t know how helpful could be