#7

I haven’t tried recently, but that used to be extremely false.

Like, if I made a patch which used nothing but brightness levels 0 and 15, you’d expect that to be 100% backwards compatible. But, it was only 50% backwards compatible. (Specifically, the “brightness at zero” half worked as expected.)

Again, possible that’s changed in the intervening years.

That was with max/msp, mind you.

The modular stuff, I believe Brian programmed support for older grids.

Norns, nobody has.

1 Like
#8

would be nifty have some clarity on that - I use a 4-level grid from 2011 for all my development but I forgot that there are separate messages in the osc spec for led brightness that I assume were added around then. not really sure how non-vari grids reacted to those.

if they don’t it would be really easy to add backwards compatibility in any software/api. could be a nifty thing for norns

#9

Well, the difficulty is that some apps encode meaning for more than two possibilities per light. Varibright becomes a requirement for these apps. But of course there is nothing about norns that prevents people from designing monobright compatible scripts. It’s just a design choice on the part of the scripter.

#10

There was talk of adding support into serialosc to make led/level messages above a certain threshold translate to old led messages. Not sure if that went through though, I think they are just ignored.

I’d test it, but my 256 is disassembled on my desk. I’m nearing completion of a project that’ll make this thread obsolete. I’ve said too much…

7 Likes
#11

Oooh. Vari right conversion? Will this apply to all non-varibright grid sizes?

2 Likes
#12

It’s always going to be a compromise. 2 values != 4 or 16 values. Some things will auto-translate better than others.

#13

thank you so much for your responses, guys!
will definitely dive into it asap… glad to hear, that there are still so many possibilities :slight_smile: :slight_smile: :slight_smile:

you are good people.

and @declutter: you will never get my grid, hahaha :wink: even if it gets obsolete one day, i love this thing way too much to give it away.

peace to @madeofoak as well for the inspiring video!

2 Likes
#14

thanks! and yes, I’m using the earthsea module in the video (and off camera I recorded the fluttery parts with ansible running kria) but you can totally do the same thing with any grid application that just transmits midi notes which would be even better on a 256 with the extra room.

2 Likes
#15

As a monobright user, I am intrigued.

#16

20 characters of me too

#17

Yes.

I will make a thread about this when I’m ready to.

Essentially a replacement for MAX7219 (led driver in 40h, series, gs grids) and a new firmware for the monome logic board to drive it.

8 Likes
#18

Exciting news. I look forward to further details as and when they are ready!

#19

it did, varibright translation currently happens in serialosc (actually, libmonome) - levels above 7 are converted to 1 :slight_smile:

3 Likes
#20

how you manage to get earthsea controlling the moog?
grid -> modular earthsea -> cv interface -> moog ?

#21

any clarification on this? I’m using /grid/led/level/map in a script which is working for both varibright folks and my 2010-ish walnut mono-bright, but it isn’t lighting up a greyscale 64 grid. I believe I’m sending 15 for on and 0 for off.

(using max and a modded serialosc object)

#22

that moog has cv in.

#23

hmm, what is the version of serialosc installed in the system?

#24

Then this should
Work in norns too.

If it doesn’t, or the default behavior is not ideal, That environment is very easy to customize.

#25

Just wanted to add that Ive had great success with using my 64 walnut with norns. I am not a programmer by far, but have had great results in modding mlr, who is made for a 128 varibright, to fit my use.

1 Like
#26

that might be a good thing to check on (paging @dude )

1 Like