#7

Same for me. Iā€™m running a 40h kit under win 10 64bit. Only way for me to see it connected is the old monome serial where it appears. Suggestion: I tried to install ftdi drivers and realized, that win10 obviously does have a sort of ftdi drivers already on board. Tried to manually override them, but iā€™m not sure if it worked. However, serialoscd.exe says: [!] running in debug mode, hotplugging disabled
serialosc [m40h1230]: connected, server running on port 17714. Hope youā€™re able to fix this ā€¦ ;). Greetings

#8

+1

Iā€™d like to have a Windows serialoscd binary that is not in debug mode and that has hotplugging enabled, if possible.

My C skills are limited but I have Visual Studio at work. If someone could give me some pointers perhaps I can help out in some wayā€¦

#9

After some investigation: found out, that the serialosc service isnā€™t running. If i try to start it manually, it ā€œsaysā€, it isnā€™t possible cause the required dependent service isnā€™t running, but win10 didnā€™t mentioned which one this could be ā€¦ any suggestions? THX!

#10

For me serialoscd works on Windows 10, but hotplugging is disabled (so all devices needs to be attached prior to launching serialoscd.exe) and it is in debug mode. Iā€™m getting the same output in the console as you:

[!] running in debug mode, hotplugging disabled
serialosc [m40h1230]: connected, server running on port 17714

For me itā€™s not a big deal to start serialoscd.exe manually (as opposed to have it automatically started / as a daemon of sorts), but Iā€™d like hotplugging so that I donā€™t have to have all devices plugged in before starting serialoscd.exe.

DIY monome compatible grid w/ Adafruit NeoTrellis
#11

hey, the main issue here is that the serialoscd service isnā€™t starting correctly. ā€œdebug modeā€ is just the message you get when running the executable directly (rather than as a service), and hotplugging is disabled because in earlier versions of serialoscd I hadnā€™t figured out how to make a non-service receive device arrival notifications. Iā€™ve since figured out how to do so, but again the primary issue here is that itā€™s not running as a service.

I think the root cause here is that Iā€™ve got something wrong in the service dependencies thatā€™s preventing it from starting. Iā€™ll find some time later this week to investigate.

2 Likes
#12

Great News! Looking forward to it ā€¦ :wink: .

#13

Any news about that? Greetings ;).

#14

For everyone who is looking for a solution to get the monome 40 (kit) working on Windows10: Here is my little solution that worked for me -> How to install Monome 40 (kit) on Windows 10 64bit

#15

Just wanted to give an update. Everythings working fine with hotplugging!

Im not sure if it was a new Bonjour installation or not, but after uninstalling all traces of monome related applications, it looks like weā€™re up and running again.

Not sure what has changed since my original attempt to get my MK working happily :smiley:

#16

Iā€™ve been having issues with hotplugging on Windows 10 too. I just did a clean install a couple weeks ago and itā€™s still not working. Whatā€™s most frustrating is for some reason i lose connection sometimes when going from M4L edit mode back to Live so Iā€™m having to restart the service a lot. :confused:

#17

Yeah I do have the same issues, weirdly enough hotplugging seems to work more regularly on my tower computer than on my laptop so I really donā€™t know where it comes from. Very strange.

#18

Do you start serialoscd.exe yourself or run it as a service/daemon?

#19

Was there ever any solution found to this problem? While preparing a live set I went back to my laptop, tried to solve it by reinstalling everything, with absolutely no luck. The problem seems to be that no matter if I check the ā€œstart serialosc serviceā€ box, it doesnā€™t run as service (it actually shows the service is not running when I check in msconfig), and itā€™s not starting automatically when I launch windows which means I have to run it manually using the exe. Which means hotplugging doesnā€™t work. Other than that, still absolutely 0 issue on my tower computer, hotplugging works like a charm, serialosc running as service as expected, itā€™s realllly confusing.

#20

it was weird, i was on my windows 10 system yesterday to test something, and the monome worked fineā€¦ it showed up in the serialosc box like it should and i never had to start the service manually. i unplugged/ re-plugged the device several times and it re-connected perfectly.

maybe a windows update fixed it? i have no ideaā€¦

1 Like
#21

Yeah itā€™s rather puzzling that all the people who were able to solve the problem donā€™t seem to have any idea how they did it! It doesnā€™t help much as to what I can try to do. Could it have something to do with Windows UAC? I know itā€™s disabled on my main computer for plugin wrapper issues, and thatā€™s the only difference I can think of that would make a difference but it seems unlikelyā€¦

#22

Any solution to this? Iā€™m having the same issue on my win 7 64, any idea how to sort this out?

#23

OK So what I found out is that some installers (canā€™t remember which because Iā€™ve tried so many combinationsā€¦) install useless files, probably obsolete, in the ā€œProgramFiles/monome/serialoscā€ folder, and after theyā€™re installed, even if you just uninstall serial osc and other monome applications, they stick in that folder, so you have to uninstall everything AND delete the monome folder. Once thatā€™s done, just install bonjour and serialosc manually, check the monome/serialosc folder and make sure all you see there is ā€œlibmonome.dllā€ ā€œserialoscdā€ ā€œuninstallā€ and a folder called monome with 3 protocoles.dll in it. I donā€™t know if itā€™s making a lot of sense and it sure was a very unacademic way to correct the problem, but after hours of trying, I found it was the only solution to get serialosc to automatically run as a service at the start of Windows and detect my monome easily. Hope it helps.

1 Like
#24

This is what I have, considering my installation fresh as just received my monome 64 and still suffer of the serialOSC driver stop working for uknown reason, there must be a sort of conflict surely, I must see If there any software to monitor dll in memory and behaviour, maybe is just port assignā€¦ throwing my cent really.

#25

Just want to give another trace. Win 10 is installing a ftdi driver on its own. Maybe this Win Uac Version is causing troubles. :wink:

#26

Adding this link here since the solution seems directly related to the problems reported in this thread.