This is a thought that keeps occurring to me as well.

Not everything gets slugged though. My ER-301 made it through tax free and it was over $1K.

:crossed_fingers:

1 Like

teletype will live on. it’s a totally different use experience.

20 Likes

It’s not necessarily a bad thing if the Teletype platform were to settle down in terms of development (stability and refinement is valuable). I would imagine though that we’ll still be seeing quite a few updates due to Crow and w/.

Teletype does so much as it is, I doubt many people have explored everything you can do with it yet.

3 Likes

I know it’s a few months away but I’m wondering how these will all chain together with i2c and there being more and more i2c devices. (A la i2c backpack behind the teletype). Will TT act as a hub of sorts? Will the back of the crow have multiple i2c headers?

Really good questions.

1 Like

very excited about this—exactly what i’ve been wanting since i first put hands on a grid!

could you tell us more about the features of mlr-norns? mostly curious if it supports aux grids and if you can overdub loops from live input?

2 Likes

I initially read that as “Norns is waiting, just around the beard.”

4 Likes

im still just so impressed and the smile hasnt left my face z(even after the price which is fine considering)

So @Tehn - this “crow” - is it a collab with Birdkids or a co-incidence with the name?

There’s a little something I want to say, because it’s likely an important thing to be aware of and I might not be the only person in this situation

I’m very excited about this. I do have a teletype and totally love it. I have been thinking about getting a grid for some time and in general I really like monome’s approach to designing an electronic music instrument.
Also sampling and working with recorded sound is what I love to do most, so mlr in a linux-powered box that I can even script… well that sounds really like a dream to me.

Will I jump on the ship and pre-order norns tomorrow? No I won’t.

Please note that I’m not saying this because my ego wants it. Actually I’m always a bit annoyed by people replying to a release post saying: “it’s nice, but I won’t buy it”. Really… who cases if I buy it or not?

But there’s some reasons behind this decision which might be shared by other people and it’s something that isn’t being talked much about (and btw. @tehn is ok with me saying this).

This said, I’m not a coder, I’m not somebody who speaks that language as fluently as others here on lines.
I’ve recently been spending lots of hours messing with a raspberryPI+pisound combo to get some basic pD patches going (and thanks to the great help from the community I got most of it working) and it made me realize that I need time for these things, and I can only accomplish some results thanks to the generosity and openness of the community.
I’ve been working with module makers for years now and I know how much work it is to do all the support… it’s really a lot!
What would happen if I got a first-batch norns unit? I’ll likely pester Brian’s email and the forums with silly beginner-level questions and Issues related to my inexperience (and they will have enough to do anyway). Also, I won’t be able to contribute much to the growth of the platform, because I would be more a “consumer” of other people’s code, as I have been with the teletype so far. Maybe the first 100 will go quickly and I hope that they get bought by people who will build the norns ecosystem and make it just as amazing and varied as the grid ecosystem.
So what’s the plan? I’ll watch it unfold, develop, grow a bit more, and wait (a bit unpatiently I admit it) for the next batch. And when that time comes, I’ll ask myself again: is norns the right instrument for me, and am I the right person for norns now?

42 Likes

It’s a collaboration with Whimsical Raps / Mannequins

thank you thats what i thought, just wanted to clarify

A few more questions :smile:

  • What will the support be like for different size and non-varibright grids out of the box?
  • In terms of creating UI is there some kind UI framework for doing the basics (eg, getting menus/submenus, meters, progress bars etc on screen)
  • Any thoughts yet around how scripts will get shared/forked, just thinking about the ‘numerous customized variations of mlr’ gives me a feeling of both joy and forum-searching anxiety :wink:
3 Likes

I’m OK with the pricing, though it’s too high for me to justify at the moment. I just “rewarded” myself with an Elektron Analog Heat after getting promoted at work. Another $800 will be tough for something that is still a bit of an enigma (in a good way) and will require a lot of dedicated time. Free time is elusive when you have a 1-year-old in the house! If I were in a spot where I had recently sold a bunch of gear, then that’s a different story… I’m excited that production isn’t limited to a single run though, and I’ll keep watching this space to see what the folks do with norns.

i’m adding/changing every day but some highlights:

  • punch in/out recording, overdub
  • pattern record of much more than just cut position (ie speed change, loop points… it’s so good)
  • better quantization interface
  • param recall: like pattern record, but just a “state” of changes recorded. ie, start recall store then: cut a position, tune a speed, stop a channel playback. stop recall. now when you hit this recall key it’ll be the same as all of those events you logged into it. it can be cleared and re-setup. so so good, super performative and helpful for customizing gesture shortcuts that you prefer. (ie toggle recording and cut to start)

several things i haven’t gotten to implementing yet, but lua makes this process so easy. i built most of what i have now in a number of hours. (that said, it took massive time with many people to put together the glue of this system which allowed such a rapid realization of an instrument. most of all a custom sc ugen by @zebra that is unbelievably rad)

so far no aux grid support.

19 Likes

i didn’t know about the birdkids module. trent and i have been working on crow for months— seems like a different thing.

1 Like

Wow this looks promising! Congrats and thank you for the amazing work you’re doing! :slight_smile:
I hope one of the second-batch Norns will be mine.

libmonome is under the hood, yes the same lib from serialosc. @artfwo just added 40h support :slight_smile:

i’ve made modules for file selection and text entry (NES-style) that can be used by scripts. the menu system (script selector, etc) has a bunch of stuff built-in like level control, VU’s, and a full parameter navigation menu with editing (and file read/write).

of course we’ll make more display/UI widget modules. they’re very easy to build. it’s more a matter of seeing what’s needed as we make more script to play with.

working on this. there will be a central git repo that gets sync’d so people can submit PR’s. scripts can be uploaded here of course. “official” updates will basically be a package with the scripts/etc git repo (which is incidentally called dust)

edit, for clarification: the script selector supports subfolders. when it ships it’ll have a collection of “main” scripts in the root but then also a collection of subfolders with scripts created by contributors. or you can sort them differently.

11 Likes

/hops over to https://github.com/monome/dust

awww, not yet. :slight_smile:

3 Likes

I’ve been pondering many of the same questions over the last week (in a kind of agonizing way), and I’m generally in a very similar position to yours (especially in terms of coding experience). That said, I think there’s room for us in the exploration and development of this instrument from the get-go – in fact, I think our perspectives (and especially our challenges) could be important to those doing the coding.

5 Likes