#61

Oh that’s amazing! Thanks for giving it a shot. It’s interesting that it eventually zeros out the sequence, hoping that gets changed. Did you try out the randomise for input 2?

#62

Yup! random works too, and if you’re also triggering random the sequence won’t zero out.

2 Likes
#63

Yes!!! :raised_hands::raised_hands::raised_hands:
So keen to try it. Hopefully it gets added to the offical app.

1 Like
#64

I feel like I’m cheating with awake and a Moog
:grin:

6 Likes
#65

Norns: Awake, the Cliff’s Notes of melody generation.

2 Likes
#66

merged!

looks great, curious to hear some sounds being made with this—

4 Likes
#67

Thanks Brian!!! :pray:
Ill be trying this as soon as i get home from work.

#68

So I have been using the new morph controls with the crow inputs and I have to say its unbelievably good, very musical and way too much fun with JF.

But I think I have come across a bug.

My setup is:
Norns connected to crow, crow to JF via i2c.
Awake set to crow clock out, i2c to JF
Crow out 1 (clock) into Pams NW clock input.
Pams NW clocking Ansible running Kria.
Kria channel 2 gate out to crow input 1.
Kria channel 3 gate out to crow input 2.

All was fine but now input 2 on crow isn’t responding or changing the random parameter in awake and if I have both inputs trigger simultaneously the clock out of crow output 1 stops working and stops Pams.

Coming across this issue I though of two changes that would be great to have.
Random isn’t really necessary so how about keeping crow input 1 as morph and crow input 2 as a sync input to slave awake .
or
Replace random with another morph parameter so Notes and Transpose can be morphed independently.

Sync in would be my ideal modification but id be happy to keep clock out if we could move it to out 4 and have an option to have both i2c and crow send out cv/gate simultaneously.

3 Likes
#69

I’m not sure if it’s the same issue, but I experienced something similar where the inputs weren’t responding until I tried this:

Can you see if that helps? It seems like a bug in norns/crow, not awake itself.

This is a pretty simple change if you want to try modifying your own script. Just change this section on line 257

crow.input[1].change = function(s)
    morph(one)
    morph(two)
end
crow.input[2].mode("change", 1, 0.05, "rising")
crow.input[2].change = random

to

crow.input[1].change = function(s) morph(one) end
crow.input[2].mode("change", 1, 0.05, "rising")
crow.input[2].change = function(s) morph(two) end

Clock in would be a bit more work I think.

I could see a few different use cases for the crow inputs. Maybe the ideal would be to make them switchable params, so you could redefine their behavior on the fly?

1 Like
#70

Thanks for all that!
I did think to try the clear command, so ill try that tonight.
And thank you for showing me the part to change in the code. I haven’t tried any coding yet but this seems very doable and great way to get me feet wet.
I did think clock in would be more work, what about adding a play/start button?
Anyway, Ill report back soon.

1 Like
#71

Just chiming in to let you know the clear crow command from maiden stoped the simultaneous trigger input clock out bug I was experiencing as well as the random on crow input 2 started working again.
I also modified the code like you suggested and now it works like I imagined, it’s lots of fun!
Thank you for your help and this was just what I needed to jump into come code.
Lots of ideas flowing now so I hope I can come up with something useful!

2 Likes
#72

Glad you got it working! happy to help.

1 Like
#73

So last night I locked up Crow just by sending a gate from Kria to input 1. I guess I’ll give the crow.clear() in Maiden a shot.

The sequence kept playing via iic with just friends, but clock out froze. Restarting norns, but not crow, would fix the issue. But i never got the morph to work without locking up.

#74

I had that issue and I tried a lot of different things to fix it like Norns restarts, module case Power cycles, loading different Norns apps and uploading different Crow scripts. In the end the crow.clear() in Maiden was the only thing worked for me. Since then it’s been solid and my god is it fun, such a fantastic semi generative sequencer. Good luck!

#75

Loving the probability param on Awake, here’s ii JF via Crow along with some w/

7 Likes
#76

Hi. I have a MIDI-learn question, mostly for @tehn, I imagine. I have no trouble mapping any of the third and fourth sets of parameters, but I can’t seem to assign any of the first or second sets of parameters. Is that the case, or am I having an issue on my end? It’d be nice to be able to adjust, for example, step length and note length, and the BPM. Thanks.

#77

How do you save a sequence for recall?

#78

so far, I havent been able to. Saved state seems to save things like bpm, root note, and scale, but it never recalls the saved sequence. I think it may be a feature thats planned to be added?

1 Like
#79

@tehn mentioned this hasn’t been implemented yet but consider this another +1 from me as someone that would love for this to be added!

1 Like
#80

Yes, it would be most welcome. I am currently taking a photo so I can re-record a patch made the previous day…maybe other coders can help out

2 Likes