#42

Is there any difference between what they are selling now and the 128? Is it the same software?

#43

Is this a kit version or is the seller legit?

image
image1242×655 597 KB

#44

100% kit. looks like 40h size keys, mono-bright. mk era.

#45

Does anyone know of any compatibility issues with Norns or Fates and one of these 40h kits?

#46

Biggest issue is mono-brightness. Most norns grid scripts rely on variable brightness

This may be addressed with the varibright upgrade thing @stevieraysean is working on, but not sure for this specific model

#47

Hi!
I have an opportunity to buy a 2011-edition of Arc. But before I do, I’d love some input/advice… I’ve understood from the monome editions web page that the encoders are a big wobbly, and that there are lesser steps per revolution than the newer versions, etc. But is there anything else that is useful to know, when comparing to newer versions? I already have Norns, Grid 128 and Ansible/Switch, which I’m planning to pair it with.

Thanks!

#48

Hi, I am considering to buy a used 128 walnut grid. Is this one the 2011 or the 2012 grid? If it is the 2011 grid with only 4-step led brightness, would that still work with Norns scripts relying on varibright leds? Thanks!

Screen Shot 2020-09-01 at 14.01.16
Screen Shot 2020-09-01 at 14.01.162568×1550 385 KB

#49

it’s a 2011. given there are so few of them, they’re not widely tested on a lot of scripts— though i expect they will intuitively work fine, though with less depth (given 4-step)

1 Like
#50

levels 1-3 dissapearing can be annoying some scripts, but i wrote a small lib to remap brightness levels in 3 lines of code

otherwise i’ve been doing just fine with my 2011 grid on norns ! 4 levels generally seems to be enough resolution to understand an interface

3 Likes
#51

Thanks for the information, and thanks for sharing that code @andrew. Could I bother you to give an example on how to add that code to an existing script? I should be getting my vintage grid soon, can’t wait to start using it with Norns (or Fates, to be more exact).

#52

wrote it the other day so haven’t documented it yet, but here’s the gist:

download that library & unzip, add the ledmap folder to dust/code

at the top of a script or anywhere outside of a function, add lm = include 'ledmap/lib/ledmap'

at the bottom of the init function, add add lm:map(g, '2011') (this is the 2011 grid preset, alternatively you can send a table with 16 ints which remap every input level)

function init()
    ...

    lm:map(g, '2011')
end

(note: by convention the grid variable is named g, but the author could’ve named it something else)

optional: add led:unmap(g) to the cleanup function if you don’t want the mapping to persist between sessions, but usually this is not a big deal

3 Likes
#53

Great, thanks! Should get my grid next week, will try it out then.

#54

Thanks for this. I also have this edition Grid. Going to try this with Cheat Codes, which doesn’t seem to display properly on a 4-stage.

#55

exactly - wrote this after modifying the script too many times after updates. I have a clean fork running that I can git pull for new updates while keeping this mod running + some others I enjoy

feel free to fork this / use as-is
(I might make a study about this process at some point, it’s pretty straight forward but requires some command line git actions)

1 Like
#56

fwiw, i’m adding native 4-step and grayscale support to cheat codes 2 beta today (it’s a nice process to examine grid redraws and make conscious choices for what should be displayed and how :sparkles:)
having a clean lib that folks can just drop into any script would be awesome to formalize!

9 Likes
#57

Ooooo, it’ll be cool to get my grayscale in there just for funsies. I still adore the stark white lighting of that bad boy, and the fact that after 10 years, it still functions exactly like it did on day 1. I don’t know a lot of things I own I can say the same about.

1 Like
#58

Hey Andrew, really cool idea. Am i missing something here, lib/ledmap.lua is empty in your repo?

#59

whoops

away from my computer for a few days but i’ll run a git commit when i’m back

(if there’s a real need for it i can put it in the library too, but it felt pretty niche/specific)

1 Like
#60

no worries, whenever you get a chance :slight_smile:

#61

back from camping !

forgot the ever elusive git add * before pushing all the commits. should be up to date now : )

1 Like