Norns: Compilation

jasonw22 · 2018-06-21T00:59:55.504Z

Album art ideas?
Deadline suggestions?

dansimco · 2018-06-21T01:05:26.114Z

On album art, perhaps something drawn within the same limitations of the Norns display?

bobbcorr · 2018-06-21T01:23:44.075Z

h/t to @scanner_darkly:

scanner_darkly · 2018-06-21T01:38:47.530Z

ha! i made that on https://www.designevo.com/apps/logo/ iirc
judging from a quick look on the web-site it can be used with credit specified and resolution limited to 500px, not sure if that would work

jasonw22 · 2018-06-21T01:43:31.057Z

Tempted to use it as a starting point for a 128x64 (norns screen dimensions) composition in 16 levels of brightness.

EDIT:

Here’s Kunaki’s dimensions:
http://kunaki.com/artwork.htm

So, I’d be creating pixel art that is up to 10x enlarged.

jasonw22 · 2018-07-10T18:11:23.516Z

New idea courtesy of @trickyflemming!

Approaching: norns Monome

I was thinking about my experience remixing Glut and Spacetime for the latest Dust release, and that gave me an idea. For a future LCRP or similar, it would be cool to pass around a minimal Lua script. There would be a separate thread specifically with help for implementing code ideas specific to this project. Each person then submits their own remix of the script, all of which would show up in one folder on Dust. I suppose if there’s too much worry about unstable/unrefined/unfinished scripts …

Approaching: norns Monome

I love this idea! Next remix edition of LCRP wouldn’t be until March if we follow the schedule. But there’s the norns compilation that I admit I’ve kind of stalled on organizing. But now I know why, it was so that this idea could bubble up! Let’s do it! I like the idea of submitting scripts to dust after the compilation is complete. gist or a new repo would be a great way to organize WIP. I can create new repos in the monome-community org. What would we call it?

Justmat · 2018-07-10T18:12:42.363Z

This sounds really cool!

emenel · 2018-07-10T18:25:58.320Z

I’d be game for that!

Tyler · 2018-07-10T20:13:02.089Z

Count me in as well.

trickyflemming · 2018-07-10T20:29:47.653Z

I think there could be a few distinct phases:

Find a person willing to contribute the foundation script. We could perhaps do two different script ideas for diversity (i.e. one MIDI generator and one standalone audio generator or one sampler and one synth… no reason a script couldn’t be both but it would encourage beginner programmers to start with a simpler idea and cleaner code).
Start a new Lines thread with a link to the script. Create a new monome-community repo for everybody that signed up. The thread will be a friendly, useful place to ask development questions.
First deadline: Submit your version of the script by the deadline (maybe one month).
Spend a week or two for a public feedback phase. Identify issues that need fixed.
Final deadline: publish “completed” scripts. These scripts could then be merged from the standalone repo into an LCRP folder (maybe volume 1 subfolder) on Dust. Any changes after the deadline would be managed as pull requests on Dust instead of the other repo.

jasonw22 · 2018-07-10T20:40:34.781Z

Brilliant!..

robbbiecloset · 2018-07-10T20:56:55.125Z

Just want to say I’m definitely down for this. Love the idea!

cosmicsoundexplorer · 2018-07-14T23:37:26.217Z

Really fantastic idea!

jasonw22 · 2018-07-14T23:42:06.950Z

trickyflemming:

Find a person willing to contribute the foundation script. We could perhaps do two different script ideas for diversity (i.e. one MIDI generator and one standalone audio generator or one sampler and one synth… no reason a script couldn’t be both but it would encourage beginner programmers to start with a simpler idea and cleaner code).

This bit needs a little more working out. What type of scripts are folks interested in learning more about through experience?

The trouble I’m having is that all of the ideas I’m interested in exploring (synthesis, audio effects) would likely require Supercollider engine work. How would folks feel about including engines in this?

The other observation I’ll make is that this project will be a lot easier after study #4 is available, since that’s when we get to the really interesting i/o stuff (grids. midi. sync. OSC, HID)

Tyler · 2018-07-15T14:15:29.730Z

I personally think an additive synth engine would be fun to work with, and could go in many different directions. I’m hoping to piece together a super collider script, but am mainly having trouble figuring out how to translate that to an engine in norns.

Tyler · 2018-07-15T15:01:47.268Z

How do you guys feel about starting a discord or another live chat to build an engine together? We could then report it back here for anyone interested in the LUA scripting.

jasonw22 · 2018-07-15T15:03:33.075Z

If you’ll set it up I’ll join!

We do have this but it hasn’t really been used yet.
https://gitter.im/monome-community

jasonw22 · 2018-07-15T19:04:09.782Z

And now we have a norns-compilation room:

gitter.im

monome-community/norns-compilation

Where developers come to talk.

and repo:

GitHub

monome-community/norns-compilation

Contribute to monome-community/norns-compilation development by creating an account on GitHub.

cosmicsoundexplorer · 2018-07-15T23:05:10.550Z

I’d love to see what people can come up with when using norms as some type of MIDI sequencer, multiple tracks as a focus. Grind as a controller.
Sound processing sounds great too!