#94

20 characters of Nailed it!

1 Like
#95

I’m trying to learn more about Crone. How come SC can’t run the CroneEngine? My thinking was I would make a little “bootstrap” environment in SC so my engines could inherit from this. Obviously, SC is clearly stating there is a syntax error. But this < is just a getter, no?

I humbly thank you for your brain cycles.

Screen Shot 2020-07-26 at 09.42.51
Screen Shot 2020-07-26 at 09.42.513258×3058 992 KB

#96

it runs just fine (it is developed on desktop,) but it is class code and not interpreter code. put Crone.sc et al in your supercollider extensions folder. (or symlink from there to norns/sc/classes)

3 Likes
#97

Ok, I need to go back to SC 101. :sweat_smile: Thank you.

#98

@license and I are working on a thing. Is this possible? Our understanding is that there is a hardware constraint that couples the stereo outs with the headphones. We’d like to just monitor and record the inputs.

dronecaster-3
dronecaster-32169×1154 253 KB

1 Like
#99

Nope. 20 characters of reference

2 Likes
#100

Great. Thank you for confirming.

#101

This look interesting.

I think it would be pretty easy to convert the free version of this SuperCollider 808 emulation into a Norns engine.

Whether it’s ethical to do that is another question, I guess.

4 Likes
#102

Hi everyone. I am getting a norns shield soon and quite excited to join it in my portable setup with OP-Z.

I would like to ask if anyone has done SuperCollider livecoding on norns? I guess another, roundabout way to ask the question is what happens on the norns if I modify the SuperCollider engine while it’s is running?

Cheers!

#103

speaking literally, engines are classes and cannot be modified at runtime.

but depending on your familiarity with supercollider, you can pretty easily create livecoding structures around engines or within engines.

for example:

  • you can get the current engine in the SC REPL, and call its methods.
e = Crone.engine
-> a Engine_Dronecaster
e.caster.setHz(...

i’d think this would be the kind of technique one would adopt to easily make a SC livecoding environment on the norns itself, if one were so inclined.

4 Likes
#104

Thanks @zebra, i am encouraged and looking forward to trying this on the device!

1 Like
#105

Side note: thank you for putting Redfrik tweets into an engine!

#106

eh… that was sort of an experiment to see if i could programatically scrape all the tweets that consist of a single synthdef each. they don’t all quite work, so… buyer beware. maybe most interesting as a starting place

2 Likes
#107

I’m patiently awaiting my Norns Sheild from Monome, and as I sit and contemplate creating my own applications I have a basic question about Supercollider.

Looking through the tutorials available, I see that you call out to a SC engine using a “name”. Is there a list somwwhere of available, integrated or prefab engines to me started?

#108

In the DOCS bruh:

"To see a list of all locally installed engines:

tab.print(engine.names)"

The engines you’ll have on your Norns are script dependent so there’s not really a standard list.

1 Like
#109

Thanks! I’ve seen in the studies how to call out to the engine, but I’ve never seen it explicitly described what engines the Norns contains by default. In the session “Many Tomorrows” they call an engine named “TestSine”. I’m assuming that every norns would have that engine by default. I understand that users can install and even design their own engines (I’ve written a few for the MinilogueXD that I’d like to port over), but how do I know which engines every Norns is “born” with?

1 Like
#110

I think these more or less cover it

1 Like
#111

Thanks! I’ll check those out.

#113

is there a limit to the number of parameters you can send via engine into the SuperCollider instance?

e.g. is this okay do (36 parameters):

this.addCommand("play","ifffffffffffffffffffffffffffffffffff", ....
#114

I send 64 floats in my grd lib.
It’s just fine

1 Like