#2

Ack engine has been moved from we repo to: https://github.com/antonhornquist/ack

I’ve updated the Step script which now assumes Ack engine is installed in ~/dust/code/ack folder

2 Likes
#3

Nice script!

A small question/suggestion: “stop” pauses when pressed once, when pressing again it stops/resets.
Would it make sense to make “play” pause (and continue playing when pressing “play” again) and “stop” would stop/reset?
Although that doesn’t leave room for a “start from the beginning” action which would also be nice.

What do you think?

#4

Hm. I’m rather opinionated when it comes to UI and prefer buttons/gestures that do one thing (stop does two things, probably one thing too much :)). That said, it would be easy to introduce an option and make your suggestion possible.

#5

OK, no problem, opinionated is good, I like the UI a lot :slight_smile:

I guess this is MPC like behavior? I’m totally not used to that, so maybe the question makes no sense.
Potentially you could switch the “stop” label to “reset” or something like that when it’s stopped?

#6

Have you looked further into the slowing down of the tempo when swing is set?

#7

It’s a bit like MPC behavior. Stop after stopping the sequencer on an MPC (at least on the ones I have), however, will also mute all running sounds. Now that I think of it, this might actually be something I’d like to introduce on reset for Step (https://github.com/antonhornquist/step/issues/4 created)

That’s a really good idea, I’ll consider it.

FYI: I’m also planning to implement pattern queuing via grid / arc / encoders and for that I likely will use play as a shift key of sorts.

I’m actively trying to avoid having too many modes as much as possible in my scripts, and trying to be consistent. This is of course a challenge given that there aren’t a lot of buttons and encoders on the norns. :slight_smile:

#8

Note yet, sorry. I will try to look into this more soon - strangely, I am not sure I experience this on my device, or the samples I’m currently using are so messed up I’m not hearing it.

BTW. Didn’t you mention that this also occured when not using swing?

@simonvanderveldt have you experienced tempo / BPM slowing down in Step after a few measures?

EDIT: created this https://github.com/antonhornquist/step/issues/5

#9

No, not so far, but I’ve had swing off till now. Can try it later.

1 Like
#10

@carvingcode found a bug causing Step tempo to be lower than presented. This is now fixed in v1.1.2, which also persists grid width changes.

2 Likes
#11

This is definitely more of an Ack question than a Step question, :sweat_smile: apologies. Is there a way/command to unload samples?

#12

Hi @Justmat. There’s no such command, no. Is there any particular use case where you find this useful?

It would be pretty easy to implement.

#13

Not really a use case, but… in foulplay, I would like ack to unload the sample if the track is changed to a midi track.

#14

I created a github issue for this: https://github.com/antonhornquist/ack/issues/5

My norns time is currently limited, though, since I’ve been snowed under at work recently, so don’t expect it to happen any time soon (PRs are welcome! :slight_smile: ).

1 Like
#15

I just see the letters screen but how is this connected to samples? Cant see a way to use any, sorry if utterly noobish

#16

samples can be loaded in the parameters screen (at main menu turn enc1 right).

1 Like
#17

It took me a little while to get my head into this too. I now find it frustrating that to ‘audition’ the samples, it appears you have to repeat the entire process. Full disclosure: I am very very new to all things Monome.

#18

I am having trouble getting Step to just play at 90bpm .This is also the speed i have my internal clock set at. The value on screen jumps to wierd decimal point values either side… and i suspect its playing even slower than that.

I love the simple interface of this script and its absolute playability- no tricks to remember, just the right number of parameters.

I wonder if one of the recent updates has affected something.

#19

Hm. I need to update and check do some testing.

1 Like
#20

Now I got my norns updated after a long hiatus. Can you please elaborate on how to recreate your issue? How are you changin the tempo parameter? Thanks

#21

I just started up norns to have another look at this. Im still getting some odd behaviour but im not sure if its the same as before. On the main control screen the BPM counter moves up and down at odd increments (86,89,92,95,98,100,103 etc).
Under paramteres /clock source set to 'Interna’l the temp setting works fine for dialing values but i dont think these are being used by step.
beneath CLOCK> in the parameter view (not in the clock submenu) are another 7 paramerters starting with pattern length.Tempo is listed here as well and increses in odd increments again(83.6, 86.4, 89.2, 92.0, 94.8)

This is my only issue with the script -I guess i havent got something set right and dont really understand why there are 3 differnt places to adjust tempo.Ideally the main screen would allow me to adjust the tempo in increments of 1 bpm.

Does this make sense? Any pointers would be appreciated.

thanks