#17

nothing on the screen. drawing comes later i think.

#18

thank you…

1 Like
#19

If you feel bad you can reach into the SuperCollider demo script and copy the function that paints “Why?” on the screen which I did and it feels soooo much better even though its officially cheating.

3 Likes
#20

thank you sir sir sir

#21

A post was merged into an existing topic: Norns: maiden

#22

absolutely there will be. for now, Engine_TestSine.sc is the highly minimal example used in this first lua study.

8 Likes
#23

Is it wednesday yet? Wednesdays are the new fridays.

3 Likes
#24

https://monome.org/docs/norns/study-2/

14 Likes
#25

Neat. BTW, typo: “appreciate the refence docs”. Are the docs also online, or should I go to github?

#26

thanks for the catch, fixed. do feel free to PR any changes via github if you want

1 Like
#27

I will figure out how to github at some point :slight_smile:

There is another typo.

“screen.move(0,40) moves the current position to (x,y) = (0,40) in pixels. the top right of the screen is (0,0). as you move right x is increasing, and as you move down y is increasing.”

Prolly meant Top Left.

Edit: these studies are amazing, and thank you!!!

2 Likes
Github Basics
#28

fixed! thank you @ppqq for the PR

2 Likes
#29

Perhaps another typo:
“for example, we may want to different modes or pages, such as:”
Shouldn’t this be:
“for example, we may want to have different modes or pages, such as:”
?

Also, as I am not yet familiar with guthub, nor do I have yet a norns:
is there a way to read the he reference docs that live on norns under http://norns.local/doc?

#30

Welcome to github :wink: https://github.com/monome/norns/tree/master/doc

#31

granted they’re in HTML and not rendered…

#32

@tehn tried to jump on that typo from @wolfgangschaltung and got some permission errors from git. Just a heads up

ERROR: Permission to monome/docs.git denied to atomboyd.

#33

Thanks, but as I wrote, I am not familiar at all with github. Which document you pointed to is the reference doc and how do I open it?

1 Like
#34

You could download the zip file folder from Git:

monome_norns__norns_is_many_sound_instruments_
monome_norns__norns_is_many_sound_instruments_.png2114×1458 673 KB


And then open them locally from the unzipped folder in your web browser:

modules
modules.png1654×1198 172 KB


Anything with a .html file ending should auto load in whatever default browser you use.

6 Likes
#35

Got it, thank you very much!

2 Likes
#36

Not sure whether the following should be asked here, or in Norns: help or in Norns: dust, but as I encountered it in both studies (and as I do not yet have a norns):
The engines used in the studies (TestSine and PolyPerc) seem to require their pitches be defined in Hertz values only.

On the danger of coming across as lazy (or showing that I have missed something), I have to admit I assumed that all norns engines also offer a way to define their pitches in note values (be it as e.g. C3 or as e.g. 60). I guess I can write a Lua function that converts e.g. integer numbers into Hz values, but it strikes me as odd having to do that in a musical instrument.

P.S.
Study 2 starts by saying that engine PolySub will be used, but the example actually uses PolyPerc. Is this intentional?

Typo in study 2:
“tables are created with curly brackets. above, nothing is am empty table, drumzzz is a table with 8 elements.”
“…an empty table…”