20 characters of correct :slight_smile:

2 Likes

one heads up, if you update norns: the softcut syntax has completely changed and that version of cranes will not work. I am trying to set aside time the next few days to update cranes for 2.0, though!

5 Likes

Can the headphone out be different from the main output, say for the purpose of cueing?
If so i think it would be great fun to make a script for DJing.

2 Likes

I actually had this same thought! It’d be cool if someone could adapt that old DJ64 app for the norns with a UI. I’d take it on but I have a few too many projects right now.

1 Like

no, sorry, same DAC channels

Has there been any thought to adding a loop function to TAPE->PLAY? This would allow playing backing tracks/drones/etc under other script output.

4 Likes

I’d sure love this, and also a speed parameter, and also cc control of reverb parameters would be way cool (and also a way of resetting them to default values) but I thought it might be better to think about it after 2.0 is complete.

3 Likes

On crone side: Tape loop is easy, variable speed less easy

9 Likes

Uh, another thing about Tape, I’d love more meaningful filenames. Like Playfair190319_1 or something.

4 Likes

Hugely agree - the possibility to rename would be amazing!

1 Like

Tape appears to be it’s own app. So building out it features into something more usable would be cool.

It’s not at the moment, it’s a module in crone::MixerClient

1 Like

this has been on my list. actually the main thing i wanted to add is a name auto-generator (define-able) along with an editor/override

this is built-in to a param menu mega redesign that is coming post 2.0. you can manually script reverb params, check out mix.lua in norns/lua/core

5 Likes

sleep brain pre work angl jam has me wanting to jot this down for future me with spare time:

it would be cool to control start/end points of glut voices via grid. basically like how the grid version of glut works, but with the grid setting the circumference of the circle of the arc rather than the playhead. could either be two grid rows of resolution per knob or 15 rows of resolution per knob and one row for tabbing between knobs…

can’t get over how good the knobs feel, i knew it would be somewhat more musical but it was hard to really grasp without trying it

4 Likes

getting a bit sidetracked by softcut on my Smalltalk idea but liking where it is right now. casio mt-40 (the sleng teng one) is going into norns with Smalltalk responding (very basic TestSine at this point) to incoming freq and my WIP softcut script ‘tunnels’ on delay(s).

6 Likes

Yea we’re going to need to see that :grinning:

1 Like

definitely, though I ended up getting crazier with it and am thinking about making a small library of these variations that can be loaded from within this same script. one caveat is that since I’m integrating this with a script that takes an external instrument and only uses 1 encoder on norns, most of the softcut changes are coming from simple key presses (like a pedal)… so it might take a bit of work to integrate it better into existing scripts without messing with other parameters/functionality.

2 Likes

3 posts were merged into an existing topic: Norns: scripting

this weekend i did this

so far, it mostly works… some caveats

  • i only used tweets which consist of a synthdef (not routines / PDefs), so i can easily manage it’s lifecycle - a) send it to a specific Group, b) stop all its processes without bringing down all of SC, c) run multiple sctweets in parallel.

  • i ran into a novel SC error! something about “selector table too big.” ~300 tweets was too many to wrap in functions in one class method. i stripped it down to ~70. something in between would probably work.

next steps:

  • add two modulator parameters, and replace/multiply a couple graph-compile-time constants in each tweet with parameter values. this will take some work.
  • spit out a lua file with all the text so it can be shown on screen. this led me to consider keeping everything in lua, and having an engine “command” that just takes the synthdef code, interprets it, and instances it in a Group. that might be a little too insane…
10 Likes

which teensy microcontroller do you use for this (e4)?