1090

Ive tried with max and max for live… max is free to use but you cant save patches! Dont know wich other software would work with grids on windows

Edit:
thats what i get when starting serialosc manually, maybe that helps to identify the problem any further

serialosc
serialosc978×197 4.99 KB

Im thinking of writing to monome directly, but as im only owning the DIY Grids, i dont know if its of any interest for them.

1 Like
1091

While working on recent libmonome, I did some testing on windows with device provided by @okyeron . I didn’t modify the firmware on it at all. That output looks very very weird and unfamiliar to me beginning with the device string that libmonome failed to parse. But that’s about as far as I can go with it for now, sorry.

Happy to make any needed tweaks if I did indeed end up breaking something before release. (I admit that windows support for diy devices was the least prioritized combination of many.) Will probably need a little support from someone with device on hand who can modify/build/run the libmonome test programs.

3 Likes
1092

I gave this a try, and I think I have the same issue as you – serialosc doesn’t automatically detect the neotrellis grid. I tried with the grainfield patch and no device is listed in the OSC dropdown. Serialosc and Bonjour services are running, the grid flashes when plugged in.

However, I’ve never used Max before tonight and could be doing something dumb. Is there a super minimal Max patch that demonstrates grid connectivity?

edit:

Dont know wich other software would work with grids on windows

I just remembered [grid] - Easy grid I/O for vanilla pd, however my five minutes of trying didn’t work ;).

1 Like
1093

I made that pd patch and it’s completely untested on anything except linux.

1094

Hey thanks for trying! I think my fault is also that libmonome wont parse the device intance correctly. I habe both serialosc and serial osc-detector running in task manager, but no serialoscdevice shows up when plugging in the grids…

I also walted to share my build process so far on my neonome, decides to use zevrano woood and aluminium to get the high qualtiy feel when handling it. here are some pictures, im just waiting for the laser cut top panel to be manufactured, cost about 90 euro including shipping but i hope it will be worth the money and the waiting. Its a little downer that i cant use it with windows right now, but i hope there will be a fix sometime when so many people are having the same problem :slight_smile:

image
image1920×2560 388 KB

image
image1920×1440 167 KB

image
image1920×2560 514 KB

image
image1920×2560 291 KB

8 Likes
1095

Did some experimenting tonight trying to get a neo-grid working with some linux software that is expecting serialosc.

serialoscd or I should say serialosc-detector was not seeing the neo-grid.

Poking around in the serialosc code I noticed this

if (udev_device_get_parent_with_subsystem_devtype(ud, "usb-serial", NULL))

link to source

detector is expecting usb-serial and the neo-grid is SUBSYSTEMS=="usb"

I changed that line to “usb”, recompiled and serialoscd now sees the neo-grid. :tada:

Could this be the problem people are seeing on Windows?

@Gerald_Stevens could you check the device info to see what subsystem you get? on linux this is udevadm info -q all -a /dev/ttyACM0 for a full dump. Alternately you could try the same hack and see what happens?

1096

no,

  • windows doesn’t use udev
  • i was responding to the above as a libmonome issue, which is what it looks like. (honestly it just looks to me like the device model string was changed in firmware to some random thing that we can’t recognize)

but that’s good that you fixed the detector on linux

1097

Roger that. Thanks!

Should I post a github issue on that?

1098

i had my neotrellis working on windows w/ (at least) the press cafe m4l device.

maybe does it works w/ some m4l patches / m4l devices and not others. maybe some devices get frozen w/ specific versions of libmonome as a local dep, making things work/break.

EDIT: i did some test, every m4l devices from the gridlab, terms & prosody packages work perfectly for me w/ my home-built neotrellis (teensy 3.2).

my setup:

  • serialosc 1.4.3 (installed manually)
  • bonjour print services v2.0.2
  • i did NOT tweak the registry entry related to serialosc
  • i did NOT install the FTDI driver
1 Like
1099

Thanks. I’ve been having issues with my neotrellis and serialOSC on windows 10 as well. I’ll try.

1100

Yep - I’ll confirm that somehow, miraculously, re-installing serialosc 1.4.3 and bonjour print services seems to have gotten my neo-grid responding to grid-studies 3.1 in max!

Holy sh:t!

2 Likes
1101

uh sorry - i guess so, sure?

2 Likes
1102

Oh good news! Maybe i have to try installing the stuff new until it works somehow😄

1103

Thanks to Okyeron and everyone for making the files available. I was looking at the Github repo to send the case file to Ponoko, but wasn’t really sure which file is correct for 3mm acrylic plates for Teensy 3.2 and the breakout board.

If you look at the dates the latest file appears to be “neotrellis-128-12-cut.ai” however, there is a link above for neotrellis-128-13.ai.

Is it correct to assume the 128-12 file is the most recent for 3mm matt acrylic plates with M3 8mm standoffs?

Thanks again.

1104

I finally finished my build :partying_face:
Now, my macbook doesn’t seem to recognize it.

  • While building i tried the multitrellis-test and it worked fine
  • I now tried 3 different USB cables to no avail
  • Entering ls -lrt /dev/tty.usb* always shows ls: /dev/tty.usb*: No such file or directory
  • Entering ~:$ launchctl load /Library/LaunchAgents/org.monome.serialosc.plist + ~:$ launchctl load /Library/LaunchAgents/org.monome.serialosc.plist didn’t solve my issues
  • Serialosc seems to be running (following these steps)

Any help very appreciated :slight_smile:. Would be a shame to not be able tu use this at all.

1105

What MacOS version?

What serialosc version?

Have you flashed the firmware to the teensy?

Do you get a single pixel blink after a second or two when you plug it in?

1106

Big Sur 11.2.3, serialosc should be v1.4.3, firmware is flashed and i do get the blinking pixel.

However, i just tried to reflash the firmware and the teensy isn’t recognized anymore at all. Maybe something broke while wiring.

1107

When it comes to responsiveness of the keys - Has anyone compared the Neotrellis with the real Grid side by side ?

1 Like
1108

I haven’t compared with a real grid, but just by watching how people use their grid Vs how the neotrellis feels, I would say neotrellis buttons are probably stiffer and a little harder to press. I’ve definitely been tentative to use my neotrellis as any kind of playable keyboard interface because of this. I might just be imagining the grid as being softer and easier to press though!!

1 Like
1109

Right. When programming patterns with the Neotrellis it’s kind of hard to be really precise. So I was wondering if the real Grid might be a better pick.