Hey. Not sure I understand. Are you saying you’re trying to clock Circles via an external clock and it’s not working? Any specifics about what your trying, what you expect to happen and what actually happened are helpful for diagnosing bugs. More details the better. 
@jakecarter iam sorry. i ll try 
actualy the script works like it should.
i can trigger notes from circles and op-z recieve.
if i switch circles to external clock - the circles animation stops.
on op-z midi clock out and midi clock in is activated.
sorry for bad communication 
edit: if i change the bpm on opz, norns also adjust them
Ah! Ok thanks. I’ll look into it when I have some free time. Maybe this weekend. 
Can’t open the script on the latest norns version, I get the Error: Init message
no problems for me on latest. (CM3 factory norns, clean install)
so we would probably need to see your actual error message from the REPL to offer further insights.
Oh wow. I’m surprised people are still using my script. I’m sorry you’re having issues. I haven’t had time to update my Norns, but it sounds like @zebra has gotten it working. If you’re still having issues, please post the full error message from the REPL and I’ll see what I can do. I’m extremely busy these days with work and a move, but I’ll try to fix it as soon as I can.
Of course, it’s a fantastic script! I get this:
WARNING: Could not open directory: '/home/we/norns/sc/ugens'
To resolve this, either create the directory or remove it from your compilation paths.
that’s not actually an error, and shouldnt pose a problem. (though it is sort of weird… i posted about this warning on the forum very recently… was that you also? basically, i would only expect to see this after some unusual reconfiguration, not after a clean install of the most recent image.)
the relevant error preventing the script from launching will be under the matron REPL tab.
I did a fresh installation with the newest norns version just about a week ago.
# script clear
# script load: /home/we/dust/code/circles/circles.lua
including /home/we/dust/code/circles/lib/math_helpers.lua
including /home/we/dust/code/circles/lib/libCircles.lua
including /home/we/dust/code/circles/lib/math_helpers.lua
# script run
loading engine: PolyPerc
>> reading PMAP /home/we/dust/data/circles/circles.pmap
m.read: /home/we/dust/data/circles/circles.pmap not read.
Engine.register_commands; count: 7
___ engine commands ___
amp f
cutoff f
gain f
hz f
pan f
pw f
release f
___ polls ___
amp_in_l
amp_in_r
amp_out_l
amp_out_r
cpu_avg
cpu_peak
pitch_in_l
pitch_in_r
# script init
### SCRIPT ERROR: init
/home/we/norns/lua/core/paramset.lua:122: paramset.add() error: id 'clock_source' is already used by another parameter
stack traceback:
/home/we/norns/lua/core/norns.lua:145: in function </home/we/norns/lua/core/norns.lua:145>
[C]: in function 'error'
/home/we/norns/lua/core/paramset.lua:122: in function 'core/paramset.add'
/home/we/dust/code/circles/circles.lua:66: in global 'setupParams'
/home/we/dust/code/circles/circles.lua:140: in global 'init'
/home/we/norns/lua/core/script.lua:126: in function 'core/script.init'
[C]: in function 'xpcall'
/home/we/norns/lua/core/norns.lua:146: in field 'try'
/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>
something is weird with your system. it seems you are running parts of our lua stack from norns 2.6.1 (before the recent image-based update), and parts of our supercollider stack from the latest main branch. (2.7.0)
(did you try and update to latest without reflashing the disk? or something? anyways maybe @dan_derks or someone can help with that on another channel.)
anyways, the error message is pointing out the problem: the script is attemPting to declaire a parameter with the clock_source Id, which is already used by a system parameter. this error condition was introduced in 2.6.1 because that anti-pattern was causing bugs. in the latest norns version we downgraded the error to a warning, but it’s still something that @jakecarter shoudl be aware of and hopefully fix (its trivial, just remame the parameter ID, the label can even stay the same.)
1 Like
Ah. Didn’t know that. I should be able to make that change pretty quickly. I’ll try to get that done this weekend.
Hey @St0rMl0rD, I just pushed a 1.5.1 update to fix the broken clock. Not sure how long it takes to show up in the Maiden library, but here’s a direct link: Release circles 1.5.1 · JakeCarter/circles · GitHub
Enjoy!
Hello, sorry to bump but I am having some issue with using external midi to control bpm/start/stop on this script (which I love by the way). I have the clock source set to midi, clock option set to external, but I am not seeing bpm changes or seeing the script run when I start/stop on my omx-27. I do see this working on the awake script, so I’m wondering if there’s something I can fiddle with in the code to get this working. Thanks!
Oh wow. So cool people are still using this. I’m actually off work for a week so I’ll try to look into this soon and let you know.
1 Like
Hot off the presses!
Read the release notes before updating please. I had to change some of the param IDs which means any saved PSETs will not work as expected.
MIDI support should be much better. circles will now respect incoming BPM and transport controls now, if setup via the CLOCK param menu. Just as before, you can still output note values to the internal audio engine, MIDI, crow, or crow + jf. I didn’t test any of the crow/crow+jf functionality since I didn’t change any of it. Hopefully it’s still working. 
Also added in a new “step divisions” param. Default is 1/4 notes, which is what is used to be hardcoded to.
This was a lot of fun update, so thanks for the push. Let me know if something doesn’t work as expected or if you have any requests.
6 Likes
Awesome update, thanks for taking the time! It works great =]
[is self promo allowed? here’s a quick stream I did using circles Grids mode on omx-27 with dirtywave m8 and norns shield (circles) - YouTube]
That’s awesome! Thanks for sharing. Is circles midi going out to the M8? I’ve never seen the omx-27 before. Is that acting as the drum sequencer or are the drums a pattern on the M8?
It’s fun seeing circles being used. I honestly had no idea anyone used it. 
Yep, circles midi goes through omx-27 to m8 and controls a synth. omx has a drum mode (grids) that’s also going to m8.
And Circles is great! Kinda chaotic, but keeps a pattern going over time, easy to understand the visual/audio connection, sounds pretty flawless no matter where you drop spawns…
//edit (another request…)
Hi @jakecarter, me again =]
I was wondering if it’s possible to get Circles to start playing again when a ‘midi continue’ message is received by norns. I’m looking at other sequencer modes on my omx-27, and it seems that resuming a pattern there sends continue, not start. If I reset the sequencer, then start, it sends the right message and Circles starts moving again. So I have a solution, but was wondering if that’s possible in your script (rather than trying to recompile omx firmware to send ‘start’…which would probably mess other things up…)
I poked around, found some start/stop sections in the script, but I’m pretty new to scripting so thought I’d ask. Please don’t spend energy on this unless it’s a 1-2 line fix, not worth it if it’ll need big rewrites. Thanks!
Sorry I missed this. Was able to work on this today and got it working. I used my OP-1 as the midi device. It sends midi “continue” unless I reset playback to the beginning of the tape. Seems to be working for me. Let me know if you have any issues.
1 Like