#101

Changed the way the clock works - took out ratcheting for the moment again.

Seems to work better - more as I expect anyway

I think I need to increase the resolution of the ‘ticks’ from the clock so there are several per step now - too tired to do that tonight been coding for work all day…

2 Likes
#102

If your talking 1/16 notes in the modular world being one pulse in the midi world that is 6 ticks. So a whole 16 modular pulses is equal to 48 clicks for a measure. If this helps at all?

#103

yeah - see the discussion about ‘beatclock’ in another thread.

For Kria it basically has a call back for ‘step’ and it does need to be on one of the divisions you mention - so I can split steps up

However until the recent ‘adjustments’ the internal clock logic was just wrong TBH :slight_smile: going to have a go at it today. (It was wrong because I was short of time when I did that bit and tried to take shortcuts. Doing it properly today)

2 Likes
#104

Thank you so much for your effort! Tried it the other day controlling Aalto on Ableton… lovely.

1 Like
#105

ok:

Timing AND Ratcheting both working as they should be!

13 Likes
#106

Hi Mark,

Quick question: It seems like it’s quiet a lot slower than I’m used to for 110 BPM, seems to be a quarter of the speed I’d expect.
If I set it to 440BPM it matches (±) with 110BPM going into Ansible. BPM is coming from Pamela’s New Workout, so obviously depends on the settings there, but this gives me 1 bar of steps. I’m assuming that’s the normal starting point (which one can then divide down using the divisions)?

[edit] I thought (looking at the code) maybe changing the steplength would help, but that doesn’t seem to work correctly. If I set it to 1 bar and slowly go faster 1/16 is slower than 1/12 for me. It also sometimes stops running when doing this, haven’t been able to pinpoint why this happens but it happens pretty quickly so should be easy to reproduce.

#107

hi - I messed about with that part - I’m obviously off by a factor of 2 one way or the other - I’ll look in a little bit (I should have checked myself - sorry about that)

edit - I don’t know what I’ve done to it! fixing it

1 Like
#108

No problem at all :slight_smile:

I don’t know why there is multiplication with the STEPDIV here, just did a quick comparison between kria_midi and Awake and this is an obvious difference.

FYI, I also get this error in the matron logs (repeated many times)

lua: /home/we/dust/code/kria_midi/kria_midi.lua:228: attempt to index a nil value (upvalue 'k')
stack traceback:
	/home/we/dust/code/kria_midi/kria_midi.lua:228: in global 'gridredraw'
	/home/we/dust/code/kria_midi/kria_midi.lua:154: in field 'event'
	/home/we/norns/lua/core/metro.lua:169: in function </home/we/norns/lua/core/metro.lua:166>
#109

the stepdiv is so I get higher resolution steps to allow for ratcheting

that error should just be at the start - there is a stupid race condition - I just bodged around it for the moment it should go away

#110

try updating

I went back and did it the way I should have done in the first place - my “shortcut” turned out to be a very long way round to breaking it… (I really should know better after all these years)

#111

Just updated, but I’m still seeing the same thing :x
Figured it was easier to just compare against Awake. If I set both Kria MIDI and Awake to 110BPM with step length set to 1/16 Awake is four times as fast as Kria MIDI.
Am I doing something wrong?

I’ll see if can transplant Awake’s clocking logic into Kria MIDI, want to get Crow working as well. So far ever never touched the Lua side of Norns so can’t promise it’ll result in anything useful :stuck_out_tongue:

#112

did you completely restart the Norns? it doesn’t pick up libs unless you do (or mine doesn’t)

I did just test it sync’d with Ableton and vice versa and it all seemed to match up.

You’ll need to change it quite a lot to just put the awake logic in. In order to support ratcheting I’ve let it make note times that are decimal parts of a step - and there is now an ‘on tick’ function that picks these up (again just tested it and it seems to work). You will need to move this back to the step function - ignore ratcheting (that’s in the make note function). obviously this will be a fork.

If it is still not working when you’ve restarted I’ll take another look but like I say - it seems to be in time with ableton when I tested. Check that you are seeing a tick() function in Kria_midi and an on_tick in lib/whateverIcalledtheforkofbeatclock.lua

I’ve ordered a crow and have plans for integrating but who knows how long the post will take in these times.

1 Like
#113

Ah, you’re totally right, I didn’t pay attention and missed that you also updated the library. Seems to be working correctly now.
Thanks for the quick fix/help!

1 Like
#114

crow functionality will be in within a day or two of it arriving at my house :wink: but like I say - who knows in the Time of Corona how long that will be.

#115

forgive me for the stupid post of the day…

I can’t for the life of me remember how to start and stop the sequencer. help?

1 Like
#116

button three should pause it (and restart) - also make sure you have the latest because I broke that in one release - but for once I found it and fixed it before anyone complained :wink:

(or you can turn individual tracks off and on with the loop setting button and pressing the track buttons )

1 Like
#117

Oh! That must be my problem. I’ll update. Thanks so much.

1 Like
#118

er - maybe not - possibly broken it again. Two ticks

Update: fixed again - get latest

2 Likes
#119

Had a first go with Kria yesterday, hooking it up to my Prophet 12 module. Since I’m new to the norns party, the version I’m running is stable, full of awesome features and lovely to work with.

Gonna make a Kria-only demo with the Prophet’s bi-timbral mode, see where it takes me. Lovely work on this @junklight

1 Like
#120

thank you!

I’m also hoping to add the new clock (link support. Yay!) and some crow support this weekend/next few days

4 Likes