#263

Ok, so where you’re going to potentially run into issues is with device management. I’ve not specifically tried this yet, but doing Serial+MIDI on teensy may throw some curve balls at how the devices are recognized/managed on norns.

FWIW - As it stands, teensy devices (emulating monome serial communication) are not officially supported in norns and won’t work out of the box. I have a workaround/hack (the diy_device_fix) for that, but it’s a use at your own risk sorta thing.

#264

pls clarify - so you’re working from szymon’s code? Unfortunately I’m not sure that’s 100% monome serial compatible. I know I made a number of changes in my version past when the thread first started to get compatibility for various grid sizes, rotation, etc.

Some key/button stuff may be slightly different and that’s throwing off the keypress registration.

#265

No, it’s a soft fork of your code, with some of the palette stuff from oldmanfury. As I said, keys are fine in other scripts.

#266

New version of grid test script (fixed up the problem with grid not initializing on start)

grid-test.lua (7.4 KB)

Quick demo on insta

10 Likes
#267

Many thanks for grid_test.lua.
Not kidding at all, but I was totally planning to sit down and write something like this tonight for midigrid. I’ve already managed to modify it to work with midigrid, would you have any problems with me distributing my modified version with midigrid?

As an aside, do you understand vports?

#268

Let’s chat about it and see… maybe a way to integrate your changes.

Kinda understand vports, but let’s take that to DM

#269

Have you an idea of the final price?

#270

I made a thread in the “Trade” category to discuss/gauge interest in these cases. Here’s the link: https://llllllll.co/t/fs-ww-neotrellis-128-grid-case

#271

I tried doing this in the gamma table, still acted really weird. Will need to do some more testing. Or do I need to declare the BRIGHTNESS variable to 128?

#272

The BRIGHTNESS variable. I did it in the latest github version uploaded too.

2 Likes
#273

Inspired by @Lemmy I’m having a go at doing up some bamboo

This is fresh off the laser cutter…

Gotta do some tests to see what the surface looks like with some mineral oil rubbed in. :grin:

21 Likes
#274

Feather M4 update

I can’t remember who was asking about this but I’ve got a complied firmware up on github for the Adafruit 8x8 NeoTrellis Feather M4 Kit Pack or anyone using a Feather M4 for the neogrid.

Addresses DO need to be setup as follows for it to work tho.

{ Adafruit_NeoTrellis(0x2E), Adafruit_NeoTrellis(0x30) },
{ Adafruit_NeoTrellis(0x32), Adafruit_NeoTrellis(0x36) }

So that’s this pattern looking at the back:

0x30, 0x2E
0x36, 0x32

Compiling the source for this requires a hacked version of the TinyUSB libs and I’ve not had a chance to try and upstream those changes yet.

1 Like
#275

Has anyone tried using the Neotrellis DIY grid with the Node library?

I can get a test script to work, but I find that if you disconnect the grid after using it (the disconnection happening after quitting the Node app), after reconnecting the grid, subsequent runs of the Node app fail to connect to the grid. I’m plugging directly into my MacBook Air USB port, not a hub, and attempting to plug it into another port after failure doesn’t work either. I’ve tried it with Node 8, 10, & 12 and all have issues. The only way I’ve found to get it to connect again is to restart my computer.

I wasn’t sure if this belonged here or in the Node library thread, but I figured since there’s no complaints over there seems like it might a DIY grid issue? (Unless it’s a Me issue…)

#276

Hey Gerald,
When it starts up I have to do the following:

  1. Connect the grid diy before starting the fates
  2. Choose brightness in the left most column
  3. Push 2 colours and keep pushed
  4. Sequence appear on the grid
  5. Release the 2 colours I choose

Is that also with yours?

#277

@okyeron do you think this would fix the problems with my 64? It was with a teensy and we tried everything :frowning:

#278

Hi @okyeron, I was asking for this. Thanks. I can’t test it right now as I not have jet have this 8x8 version.

1 Like
#279

I don’t think so (?), this specific code is for using a Feather M4 microcontoller instead of a Teensy.

I thought you got your setup working properly and the problems were more with specific norns scripts. I really don’t remember specifics at the moment.

#280

@okyeron yes you are right, it is not a hardware problem but more of a norns fault (or better said the norns script) since we tried with your grid test script and the grid worked perfectly :frowning:

#281

Close. When it starts up do the following:

  1. Connect the grid diy after starting fates so that fates recognizes it
  2. Choose brightness in the left most column
  3. Push and release any color within a row you like
  4. That selected palette / row appears across the grid for 1 second.
  5. Select a patch in fates/norns and press play

To bring up the selection menu again, press the 3 lower right hand corner buttons at once.

2 Likes
#282

Hmm… I seem to be having more general problems than just Node. I’m also experiencing extreme flakiness with Max as well. Sometimes it will connect, but sometime it just won’t see it, even after a reboot of the computer. Unlike with my experience with Node, which consistently connects at first then fails if you unplug and plug the grid, I see no pattern to my failures with Max. Sometime it will decide to connect, but usually the grid select menu stays stubbornly stuck on “none.” No errors in the Max window.

macOS 10.14.5, Max 8.1.2.

Note that I am able to hot swap my grid with impunity on my DIY Norns.