#39

What I think/hope these temporary, fleeting barriers will create is unexpected, trill-like ornamental moments in the composition. Difficult to know without actually implementing the concept into a live app, but that’s what my imagination tells me.

1 Like
#40

awesome idea!

it would be neat if you could also have the option to place objects.

like some geometric shapes or some blocks that would create a playfield of sorts like on an Atari 2600.

2 Likes
#41

Sooooooooo, who wants a slot in Matt’s Hall of Fame? All it’ll cost is crow 1+2 out in rebound. :grimacing:

Edit: also, while I’m here, has rebound been updated to work with the new norns clock? Seemed like the clock devision wasn’t doing anything last night, but, also, it was late…

#42

what would you like them to do? just pitch and gate?

1 Like
#43

Honestly, Just pitch from Out 1 and Gates from Out2 would be super cool.

My use case here involves triggering slices on the Er-301*, but it would also be fun to sequence an oscillator with rebound.

*I know, I know, I should do it over i2c. I have a rev7 301, and haven’t shorted that diode on the back yet. All in good time :grin:

#44

This kind of thing is usually very simple to add to any existing script. If you scroll all the way to the bottom of rebound in the maiden editor, you can see that there is a play_notes function which sends notes out in various ways:

    engine.hz(MusicUtil.note_num_to_freq(n))
    m:send({type='note_on', note=n})
    if params:get("ii") == 2 then
      crow.ii.jf.play_note((n - 60) / 12, 5)
    end

You could add crow CV / trigger output here:

crow.output[1].volts = (n - 60) / 12
crow.output[2](pulse(0.02, 5))

If you want gate output instead of a 20ms trigger, you could modify this to just set crow.output[2].volts = 5 here (at the spot where the midi note_on is sent) and also modify the spot a few lines up where midi note_off is sent to set crow.output[2].volts = 0. This general pattern should be possible to adapt to pretty much any other script you come across that is sending midi note on/off messages.

To me this is a massive strength of Norns: the ability to tweak a script to do what you want like this, even making temporary changes to suit a particular patch or get the behavior you want, rather than thinking of any given change to a script as a permanent feature. Maybe tomorrow you want to use an AD envelope instead of a square pulse, or send x and y position of the selected ball out of crow as voltage outputs, or pretty much anything you can imagine the script doing – lots of interesting possibilities are achievable with only very small modifications to scripts.

It would seem so, yes: https://github.com/nf/rebound/pull/3

10 Likes
#45

Thank you for this response. I knew there’d be a time that I would need to slow down and complete the studies. Seems like scratching my own itch here is the best reason to do so. Everything you’re saying makes sense, I just don’t know enough about Lua syntax to implement the code in a way that will (likely) work.

But I will dig in and, if I’m successful, also learn how to file a pull request. :+1:

3 Likes
#46

dive in! and feel free to ask questions :slight_smile: norns is a wonderful platform for collaboration!

2 Likes
#47

I’m bad at this stuff and just added CV/JF combo output mode to Awake this week. Im sure you’ll find your way, especially with the folks of this forum at your back. And once you make a change, it’s addictive! I’m now thinking of ways to play with this and Foulplay

3 Likes
#48

@csboling @Justmat @kasselvania

Totally worked! Next on my list will be actually unquantizing the note events. Thank you all for your help! Will have more questions soon.

10 Likes
#49

awesome! would love to see this as a feature in the main script

1 Like
#50

So, I’ve been playing around with Rebound a little and I’m having some issues with the Midi_off function, basically in that even if the note is off, there is a single note that hangs. So, in essence, the first triggered note never turns off, and the subsequent notes have short hits.

Any thoughts on how to fix this in the code (I actually found this while digging around in the code to practice Lua)

#51

Hello, thanks for your awesome Script! One Question about the Midi routing. Is it possible, to send midi to more than Channel 1 at same time? Or is it possible to change midi channel? Thanks

1 Like
#52

Matt, would you mind sharing your changes to support crow? I’d like to incorporate these into the main script.

1 Like
#53

It is indeed possible to send midi to different channels, or multiple channels.

Take a look at the play notes function. It has a couple of function calls like this:

m:send({type=..., note=...})

(The ellipises are different things in each call, for note on and note off.)

If you update those lines to say something like

m:send({type=..., note=..., channel=X})

it should send the notes to channel X (change to suit whatever channel you want).

Let me know if this works or doesn’t work for you! <3

1 Like
#54

I don’t see an obvious cause for this. Are you able to reproduce it reliably? If it’s still a problem for you I can dig into it and see what I can find.

#55

You bet! I just dm’ed you. Be warned- I know just enough to be dangerous. I walked away as soon as it worked, so it’s extremely likely that there’s some cleanup needed.

1 Like
#56

hi, thanks for your help.
so it is possible to change “m:send({type=‘note_on’, note=n})” this part to send different notes to different midi channel?

for example, i want to trigger the model:samples on channel 10-16 to get some cool sequenced beats

#57

Sure, just a bit of simple programming. It’s not something I’d want to put into the script because it seems pretty specific to your use case. Have you done any norns programming before? The stuff covered in the introductory materials should teach you enough to make this kind of change.

#58

thank you sir for your answer. i dont think i can programm that, but its ok. with ur instruction i can change the midi channel for the whole thing. thanks!