it may interest you to know that in fact many of us (monome/grid contributing developers) use windows daily and macos infrequently / only as need dictates. (for example in my case, to use UAD stuff.) (it is of course true that macOS is a more popular platform for music applications such as Live and Max. so it inherently receives more real world testing. but many of us (a) harbor substantial antipathy towards the Apple ecosystem, (b) work in one of the many sub-fields of SW development that is windows-focused: science/engineering, gaming, business etc.)
in the particular case of latest grid/serialosc release, certainly some particular time was spent on windows. i even tested with neotrellis alongsde new grid on windows, though these DIY clones are still not officially supported by monome’s tools.
anyways: serialosc is working fine for me on windows 10 (home edition, version 10.0.19042 build 19042), with a latest-edition monome grid connected by USB-C to a thinkpad carbon X1.
unfortunately i don’t own Max for Live, my closest test case is using the built in
serialosc patcher on Max 8.0.3 (about to update to 8.1.11 or something.) this works fine. (by which i mean, i’ve done a reasonable amount of “normal use” with long uptime and e.g. sleep-cycling the laptop. but TBH have not attempted a full stress test of every possible serialosc command.)
since serialosc just an asynchronous UDP interface, as expected it is also “works fine” in supercollider, python, or directly with level tools like
before really digging into anything else, one wild guess is that maybe a firewall configuration is blocking the relevant UDP ports. (which appear to be 12006, 12288, and i think 13288 for some reason.)
all i have done on this machine, is install the latest serialosc from the github release page, and reboot. sorry i can’t offer more steps. but i’d agree (and attn to @tehn / @dan_derks perhaps) that the serialosc setup/troubleshooting pages fr windwos seem a bit lacking [see below on a basic step towards verifying the installation and funcitoning of
serialoscd] and outdated [still referring directly to 1.4 beta.])
you mean the windows OS notification. this doesn’t mean anything
(1). in Task Manager (sort processes by name) you should see two processes before connecting a device,
(2). after connecting a recognized device, you should see a new prcess called
if you don’t see
1, i’m not sure what’s going on but something is up with the installation. ignore anything you might see anywhere that has to do with FTDI drivers; they don’t apply to you (unless you did in fact make an FTDI-based clone, IDK… DIY)
if you don’t see
2, then… i’m not sure, but could suggest further steps, or make a diganostic program if i have time (probably won’t. perhaps a neotrellis-grid-user/developer could step in to help support the device at that point.)