I was attempting to get Awake playing with the Digitone last night and ran into some trouble. I was sending clock and notes, but it seemed like maybe there was a clock issue… though I’m not exactly sure. Digitone would play the sequence, and then intermittently cut out a few notes, then pick back up, and then cut out again, at what seemed to be rhythmic intervals (a few bars), but was also not quite perfectly timed.
I did get it working with Fugu and Kria, so I know the Digitone was receiving midi from Norns properly.
I don’t know why I am sending clock either. Great point.
@beat I will update you if I make any progress on this. I’m only connected to Digitone and the grid, and I am using a factory Norns. I’m pretty determined to get this working, so I will document my attempts well going forward.
I was using usb direct, but I can try a Mio2 as well. I was only having trouble with Awake… I didn’t try playing any sequenced tracks from Digitone simultaneously, but I was able to trigger notes while it was playing (if I understand your question correctly). As far as I can tell, all params were set correctly… but I’m going to be more thorough in documenting exactly what the setup is when I can get back to it tonight.
Hey all! I don’t know if it has already been talked here (remember some clock issue quick fix on maiden…) But as I am running awake-rings under the last firmware on a norns-shield, I can’t find a way to make it respond to start and stop messages as a slave device. It responds great to the incoming clock (tempo match), the device is properly set in midi parameters… But Awake is always running, restless…
Is there something that I missed in the parameters, or is this something which need some code swapping on maiden? Thanks for any info you could give me!!
I’m working on something that tacks on functionality to Awake (and other scripts) and I’m having an issue that’s easily resolved with some minor changes to awake. Before I raise a PR I’d just like to sound it out as I know awake is often the first script people interact with on Norns.
The issue is that edit_ch and edit_pos are declared as locals so an included script is not able to modify them. The easy fix would be to declare them as globals and the alternative option would be to create a change_edit_ch function. The function would be my go to option but it only improves the code for my use case and it would also seem odd because it would need to return the current value of edit_ch.
initially in norns scripts we recommended avoiding globals by default. this is good general advice in lua code that is intended to be resued in any modular fashion.
but as of a a while ago (couple years?), each norns script is run in its own sandboxed global environment. so there is now no possibility of “leftover” globals from earlier scripts causing confusion, and little reason to avoid globals in the top level of a script. (they are even encouraged, since they are accessible from the REPL.)
i know this is an old question, but yes: start, stop and continue act like other incoming MIDI messages, in that scripts can easily add handlers for them.
however: awake and many other sequencing scripts use the main norns clock module, which has the option of being driven by MIDI clock messages (in addition to Link, internal timer, etc.) doing this requires no extra code in the script. but handling start/stop/continuedoes require adding extra code, because there isn’t actually a default meaning for these messages.
awake in particular simply doesn’t define a “stopped” or “running” state, or a “reset” / “continue” behavior. if anyone wants to add those things, it’s trivial to connect them to MIDI.