Syncing Norns / Fates to External Clock - Midi - Crow? Scripts?

Questions
#1

Hi!
Im trying to sync my fates to the outside world.

So far i have managed to have tempo sync but have not managed to find a way to reset the script to step 1 on clock stop /start (midi or analog).

So I have tried:

Sync with midi:

Only managed to get stop/start and tempo successfully with midi din and a um one by Roland.

Midi usb has been a fail in start /stop messages.

Sync with crow.
Im feeding pamelas work out euro module into Crow inputs.

The scripts i have trying so far (awake and kria midi) respond to clock input from crow BUT i dont know what signal i should feed into input two of crow to make a reset / start from the beginning.

I have tried a pulse on start, a pulse on stop.

I have tried feeding a clock divider of 1 every 16 beats so it resets to step number 1.

So far its been a fail.

What kind of signal is crow expecting for an analog reset? Is it a crow issue or a script issue!

Ill keep on trying different approaches!

I have also tried link with ethernet. Tempo is spot on, but even though ableton i sending start /stop messages with link, the scripts dont react to it :frowning:

Any ideas? Or working methods?

Thanks :slight_smile:

1 Like
#2

Replying to my own post in frustration, apologies.

I give up for today.

I literally have tried everything that came to my mind.

I tried converting Expert Sleepers es5 to midi, sending midi clock into fates. No luck; it does reset though which is good but i cannot get tight sync.

Tried sending midi clock sync from Ableton into fates trough a iconnect interface and then into roland um-one that goes into fates. Nope

I think the problem comes down to the sum of the jitter produced by:

Syncing fates to midi clock—>converting midi notes to cv-----(via fh1)-------> sending cv to the eurorack and then sending this audio back to the main sync computer.

I can do this with the erm multiclock (in another setup i have) but i think i got too many devices in the chain in this situatuiton.

So last (note to myself) way to try:

Sync with midi in (the most stable i can find) (probably Expert sleepers Es5 or with Erm multiclock) and try:

a) Convert midi to cv with yarns.

b) Send midi with sevilla midi host straight back from fates to the computer and sequence midi instruments there (thats the setup i used in the past that worked good) and avoid all the midi to cv deal.

Just grab my trusty ansible and teletype and use that.

Sucks because there are so many great scripts on Norns/Fates :frowning:

Nigh night

#3

sorry to hear about the troubles – i believe that this comes down to a scripting issue, but i want to verify that i understand what you’re looking to do, if that’s alright (in the morning, don’t worry about this any more today!):

  • you’re using awake and kria
  • you want a MIDI “start” message to reset the positions of these scripts to their starting points
  • you’d like if one of the crow inputs could reset the position, as well

does this summarize things?

the most important thing here might be that neither script seems to implement crow inputs, so the cv signals you were sending aren’t coded to trigger any events.

if it helps: the reason why tempo syncing works (midi or crow) is that these scripts rely on the clock library module, which standardizes what to do with a clock signal. it’s up to individual scripts to extend MIDI further, though.

taking a look at awake’s code, it doesn’t have any handlers for clock start messages, so it doesn’t know what to do with them when received.

kria does have a defined clock.transport.start() function, which does reset position – you can manually trigger this in PARAMS > CLOCK > reset. i was able to sync clock start to the reset using Ableton > external interface like iConnect > um-one > norns, but it sounds like you had trouble with this? is both your fates + kria up to date?

can you describe this setup a bit more? norns doesn’t have built-in MIDI USB – it requires a dongle like the um-one.

hope the rest of the night is smooth!

1 Like
#4

Thank you for your reply @dan_derks !

I really appreciate you detailed reply.

Yes thats right.

Im using awake and Kria. Both and fates are up to date.

Is good to know awake does not have a function of knowing what to do with a reset signal, so ill focus on kria from now on.

I have tried your exact same approach. Ableton- iconnect midi - um one- norns.

I think the problem is the path back. Norns-midi to cv (i have tried fh1 and going to try yarns)- trigger eurorack module- audio back to computer.

If i do the same route avoiding the cv to midi conversion, by sending midi back to the computer and sequencing some midi instruments the delay is not that bad.

When i was talking about norns usb midi, i did not clarify that i was using on the way back a sevilla usb host to midi converter. Maybe i should just use the other um one port and send the midi back from —> fates ---->um one----->i connectivity ------> computer. And not get mixed up with usb host devices.

Im goping to try out a few different things and see what i come up with. Really appreciate your feedback!

Cheers

Edited:

Ok so i have made some discoveries.

On Kria midi the reset on the clock subpage doesnt seem to do anything.

I have downloaded less concepts and when you press the reset button, well it resets.

Clocking crow directly from an analog clock and sequencing an analog voice from crow has MUCH less latency as expected since there is no conversion to do an ill all stays analog.

Might need a second crow after all…

Still digging the setup, thanks a bunch :slight_smile: