correct. arcologies uses clock.sync(1) in counters.lua
you can experiment with changing this to say, .25 or rely on outboard gear to get down to (and make noise with) eight, sixteenth, etc. notes.
rambling history and philosophy...
back in the day - three months ago - i made the design decision that all signals/bangs would move at the same speed. i wanted all signals to be equal - no fast ones and slow ones etc.
since they all moved at the same speed, it got rid of the problem of note sizes as you could simply increase the bpm and then use things like solariums and gates to slow down if a metabolism of 1 wasn’t enough.
when arcologies came out, mlogger immediately changed the max bpm value from 240 to 480 because he wanted faster notes. i thought this was rad and put it back into arcologies.
then just a couple weeks ago i took out my arbitrary bpm attribute and implemented the internal norns clock.
the internal norns clock maxes out at 300.
while i could introduce a parameter that allows the user to control the clock.sync() value, this would require some more work for me to be happy with it. i’ll add this to the backlog.