Approaching: norns

autreland · 2018-06-13T00:28:57.394Z

so . . . anyone made a script that spreads one sample out across the grid/keyboard yet?

greaterthanzero · 2018-06-13T03:12:35.335Z

Like a 64 subdivsion mlr?

Or do you envision the one sample repitching across the grid/keyboard?

dansimco · 2018-06-13T03:24:50.362Z

glut can kind of do this, one row per sample at 0% speed

autreland · 2018-06-13T03:34:20.285Z

one sample pitching across the keys/buttons, ableton-style—i have some bells, pianos, pizzicato strings, and so on that i’d love to play live on the grid!

plus now that you mention mlr, much as i love the new version, i’d also be very into a port of the classic one too . . .

Plym · 2018-06-13T06:30:23.358Z

It would be cool to have Earthsea able to load samples for pitching across the Grid. For all I know this should be easy to do? Shouldn’t there be a sample player like that in SC one could load up as engine?

glia · 2018-06-13T16:17:59.988Z

might be overkill for your needs but since it already exists i’d recommend…

github.com

monome/dust/blob/master/lib/sc/Engine_SoftCut.sc

// a sample capture / playback matrix
Engine_SoftCut : CroneEngine {
	classvar nvoices = 4; // total number of voices
	classvar bufDur = 480; // 8 minutes +clear
	
	classvar commands;

	var <bus; // busses
	var <buf; // buffer
	var <gr; // groups
	var <pm; // patch matrix

	var <voices; // array of voices (r/w heads)
	var <trig_s; // array of trigger synths
	var <adc_s;
	var <dac_s;
	var <phase_quant_poll;
	var <buf_dur_poll;

	*new { arg context, doneCallback;

This file has been truncated. show original

Mattb · 2018-06-13T22:21:22.810Z

I think (hope) so

Heath · 2018-06-14T00:59:28.840Z

D71FBA81-DF52-4E91-9D6A-62D15B1BE752.jpeg4032×3024 2.67 MB

karst · 2018-06-14T05:38:21.302Z

a not great recording, but I’m starting to get more comfortable with mlr

instagram.com

Sam Tellman

22 Likes, 0 Comments - Sam Tellman (@samtellman) on Instagram: “norns apocopations #monome #norns”

Heath · 2018-06-14T13:13:01.688Z

I have a question – Is there going to be a place on the main monome norns dust page where users will have their scripts? I’m not a good coder (yet) and have seen some good user scripts already here in various threads (that’s another issue, they seem spread out across various threads) and also they seem to be spread out on other people’s github pages and it becomes hard to keep up with where you found what (and also any dependent files and then updates to the scripts).

I’ve seen lots that I would like to try, just don’t have a good grasp as to how to get them up and running.

It seems a good centralized place to house user scripts/files would be very useful. Perhaps something similar to the Critter and Guitari Forum’s “patches” section could be useful? Maybe if something like that could be done on lines, or on the dust github page?

glia · 2018-06-14T13:54:21.777Z

Might be a matter of housekeeping but at this stage it seems the hope is that we all make pull requests on github with our new engines and lua scripts

That will be the central location

Until we are all up to speed (and using gh) I’d check the threads tagged norns for “.lua” files to find the scripts scattered across them

edit: or just check this one , only two users have shared here on lines…

bobbcorr · 2018-06-14T14:18:16.692Z

Question: Will there be a list of “Monome Tested and Approved” user-provided scripts? My understanding is that those scripts that make their way into dust will magically get synchronized to my norns, but I also anticipate there will be a portfolio of other scripts that aren’t part of the core distro but which are available for use. These are the ones that I’m hoping will pass through some sort of QA gauntlet.

glia · 2018-06-14T14:24:22.499Z

i sympathize with your fear but two points

little if anything we do at user-script level will bust your norns (lol…the english language)
pull requests on github are approved by those with write access like @tehn

also it’s unlikely that a member of our community would share a broken script OR that you download and run it w/o seeing evidence that it works, right?

Jonathan_Riley · 2018-06-14T14:24:53.716Z

Seconded. I’m writing some scripts right now and wish we had a “Testing/testers” group of some sort. Could served as the “Tested” part of “Monome Tested and Approved.”

glia · 2018-06-14T14:26:31.078Z

i would be happy to test!

dm me or post in the scripting thread with some sort of beta warning for other adventurers

bobbcorr · 2018-06-14T14:28:40.635Z

glia:

also it’s unlikely that a member of our community would share a broken script OR that you download and run it w/o seeing evidence that it works, right?

Not every member of this community pays close attention to the daily ins-and-outs of script performance, and while I know no member would share something broken, Mistakes Do Happen. Reducing the frequency and severity of errors - which leads to a reduction in support contacts - is the magic that even a di minimis QA process brings.

I am completely confident something like this will come out in the wash, but it would be helpful to be transparent in the docs about the process for how scripts move from concept to release candidate, especially as the Nornish Tribes increase both in number and ranges of technical capability.

(I thank you)

greaterthanzero · 2018-06-14T14:30:30.536Z

Added that concern to this thread, where it probably makes more sense to discuss:

Norns: ecosystem Development

I don’t know how scripts are added and organized on the device itself yet, so this may not be a real concern, but… It may be wise to create separate folders for scripts that are performance-ready vs those still in active development, seeking collaborative input before they can be completed, etc. (a user seeking one might not be interested in wading through the other)

GoneCaving · 2018-06-14T15:10:57.710Z

Jonathan_Riley:

Seconded. I’m writing some scripts right now and wish we had a “Testing/testers” group of some sort. Could served as the “Tested” part of “Monome Tested and Approved.”

No reason that that couldn’t be done as part of the pull request. It might be useful to have some community members who were willing to take that on monitor the pull requests and comment that things were working to take some of the workload off the core developers. I’d certainly offer to help in that regard, but need to get my hands on a Norns first!

zebra · 2018-06-14T16:18:34.380Z

Yah this is what PRs and approval are about. We’re hashing out contribution guide

jasonw22 · 2018-06-14T16:29:17.007Z

zebra:

We’re hashing out contribution guide

Yay! Much needed. …