Hello everyone, recently just got a new Windows 10 computer and I’ve been trying to set up my monome on it. It doesn’t seem to be working and I don’t know why though.

I tried using the win_MonomeDevice1.1 file to install everything. I also tried installing the FTDI VCP driver seperately, as well as serialOSC seperately. Not sure what’s going on.

I did install the max 7 monome package and I’ve been using the grid test max patch to check if it works. The patch says SerialOSC is running but there is no device to be found.

Any ideas?

I thought I’d add that I am using a 128, which I believe is the 2013 edition

1 Like

I’m not very knowledgeable about Windows but I do happen to have a Windows 10 VM setup at the moment. I’ll give the install process a test later today to see if I run into any problems.

Thank you, I just updated my Max 7 to see if that was the issue but it unfortunately didn’t help. I never had problems on Windows 7, just Windows 10 :confused: Not sure if that has anything to do with it though.

I just went through the same process as you - installing everything via the win_MonomeDevice1.1 installer up on Github. When I ran monome_sum my grid didn’t show up.

Poking around just briefly on my VM it seems that serialosc doesn’t want to start. I tried starting it manually via the Services application and got a weird error:

…are you seeing a similar error?

I was able to get things working by tweaking the registry.

I looked up that “Error 1075” and based on what I found I started to wonder if the service description for serialosc listed another service that needed to exist/be running before it would start.

Using regedit I navigated to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\serialosc - note the “DependsOnService” key? Guessing that “Bonjour Service” was something which no longer exists I figured that might be the problem so I deleted that key.

Before:

…the selected “DependsOnService”, right-clicked and chose delete.

After:

I then rebooted the machine and serialosc started automatically and monome_sum worked.

I have no idea if this is the correct fix but it works. Maybe @tehn is already aware of this. At a minimum preparing a newer installer which configures things correctly for Window 10 is probably needed.

2 Likes

Thank you! I’ll take a look and see if it works when I get the chance and report back.

windows support has fallen behind in the last year. keeping up with OS updates is predicated by user demand, so thank you for voicing your need.

Unfortunately, the registry tactic didn’t fix Arc on Windows for me (W10, 64-bit). My Grid connects fine, though.

Interesting. I hadn’t tried an arc. I’ll give it a test later.

IIRC the first time I plugged the grid in, Windows went through its let me find a driver for that dance.

Thanks! Arc does the driver thing too, but it fails to be recognized by Max 100% of the time, while Grid seems to work just fine.

I just did a quick test with the following devices:

  • walnut 128 (2012 edition)
  • arc 2 (2012 edition)
  • arc 4 (2016 edition)

The 128 and arc 2 work fine under Win 10 for me (with the registry hack). Unplug / replug doesn’t seem to be a problem. Interestingly I can’t get the arc 4 to work…

Now in my case this isn’t a perfect test since the Windows machine is running under VMware on a macOS 10.12 machine. Out of curiosity I disconnected everything, shutdown the VM, and tested again under macOS. Each device worked fine (in Max), any combination of two devices worked as well but strangely three devices at the same time didn’t work. Which ever device was plugged in last wasn’t recognized…?

@tehn, is an updated Windows driver being worked on?

Any news on this? I really want to use Arc with my primary machine.

@wrl is working on a new serialosc release which includes windows.

1 Like

That’s great news. Thanks!

I was having the same trouble, tried deleting the Depend On Service entry, worked a treat! Thanks so much!

Any updates on the serialosc version for windows? I’ve had luck with the regedit fix but it would be good to see some windows support.

i’ll check in on it, apologies for the delay.