#478

the “about” is at the top of the Library category: About the Library category

#479

Ah ha! That could be helpful if added to the pinned post. It only refers to “the template”, perhaps “the template after clicking new post”?

1 Like
#480

Not sure if this is the place, but how does the clock work vs metro? I’m trying to sync up UI (done with metro) to note playing (done with clock) but even though they both use the same BPM params they refuse to sync.

Does clock basically trigger every n milliseconds based off of params:bpm? Vs metro which needs a frame rate.

#481

which “clock” are you talking about?

midi clock?

the Beatclock lib?

1 Like
#482

I think i saw somewhere that its possible to make screenshots within norns now, could someone point me out pls?

#483

Correct :slight_smile:
You can run the following from the maiden REPL

s_export_png("/home/we/test.png")

Which will create a “screenshot” in that location

we@norns:~$ file /home/we/test.png 
/home/we/test.png: PNG image data, 128 x 64, 8-bit/color RGBA, non-interlaced

I don’t think it’s properly documented anywhere yet.

7 Likes
#484

Apologies. Beatclock.

#485

What is the recommended way of getting paths to audio files and folders with audio files to be recognized by the SC engine? I could do it all on the SC side, but I’d like to include some functionality in the lua script to change the file or folder where the audio files reside.

2 Likes
#486

Beatclock is just metros IIRC

see ~/norns/lua/lib/beatclock.lua

1 Like
#487

Ok. I just rolled my own thing off of metro, it works. I need to take the time to understand all the included scripts.

#488

I’m having trouble figuring out how to develop and explore on the supercollider side of things in an easy way. How do people do that?

It seems like my tweak a line, save and publish to see what happens I do on the lua side isn’t quite as simple for engines.

#489

option 1:
tweak a line, enter ;restart in maiden SC REPL, see what happens

(i’d recommend copying and renaming the engine class to something local to your script, e.g. dust/code/we/lib/Engine_TestSine.sc -> dust/code/zebra/lib/Engine_ZSine.sc - important to change class name as well as filename)

option 2:
develop engine on desktop first. this gives you syntax highlighting, completion, SC help files, &c.

norns core SC classes work fine on macOS and linux. @mimetaur made this nice gist documenting the setup on mac (which we really should link from / add to the official docs):
[ https://gist.github.com/nathankoch/18346a71f1444ec8bea98a0c3c6fa365 ]

6 Likes
#490

I got my own repo up but haven’t tested it on my device yet with the 2.0 release. I’ll do that this weekend and make the post to Library.

3 Likes
#491

what happened with the DX7 script? not updated?

#492

Looks like @lazzarello says this weekend prior to your post.

1 Like
#493

does anyone know where the lua code for the “levels” screen is located? wanna try and steal some code from that for a script I am working on.

#494

All of the menu stuff currently lives in a single file. This should bring you to the mix/levels section https://github.com/monome/norns/blob/954f26da8a0362b5d657df31de26820526fc3bfc/lua/core/menu.lua#L1291

1 Like
#495

i might suggest instead looking at the UI code inside the we folder.

3 Likes
#496

yup, looking at both. just good to know how the levels menu are getting the live feeds from the ins/outs.

1 Like
#497

Updated

4 Likes