#10

ah my apologies. I confess I skipped over the docs and assumed clock.run just took a function as a single arg.

#11

Thank you both – will experiment later today.

#12

you’re both right! these are different use cases. depends if you want global control: then @crim is correct and that’s how i did it in awake. but the clock study shows a nice way to pass args when making a bunch of static coroutines

3 Likes
#31

ok fantastic - that was easy to add even with ratcheting

HOWEVER

syncing to the bar position is currently doing my head in :slight_smile:

#32

The solution here might help.

Note: it’s a workaround due to a bug that’s been fixed but not released yet.

The simpler code that will work once the bug has been fixed is a few posts further up the same page.

1 Like
#33

thank you!!! saved me a lot of head scratching :slight_smile:

#34

The snippet itself has me scratching my head, to be honest, but glad it works.

I’m really struggling to get my head around how to use the new clock, but once I had bar syncing working, being able to sync my Fates to Samplr on my iPad was something of a revelation.

1 Like
#35

ah nice - all locked in - iPad , kria and modular all locked together!!!

#36

How’re you syncing your modular gear? I made a Spink0 module, but haven’t had much success with syncing it to my iPad.

#37

Crow!

although in the past, before crow, I used to do things like using a track of a sequencer to put out a clock via midi/expert-sleepers fh-1. Crow working nicely though

#38

I have an FH-2, so will try that. It should be able to receiver MIDI clock and reset messages from the new Clock (though obviously that only works with Fates as the clock master).

Having said that, maybe the FH-2 also sends its internal clock to connected MIDI devices. Never thought to try.

Crow seems… dare I say it… a little over-priced for what it does.

#39

If you just use it as a CV/Gate expander for Norns - possibly - but I think it has a huge amount of potential (which I’m not seeing used by current scripts yet). For me it opens up options for making more tools that move easily amongst my various sound making devices. I’ve certainly been having fun driving it via druid and on board scripts directly doing stuff I don’t know how to do any other way

#40

Fair enough.

I’m new to the “Monomeverse” (Norns Shield was my “gateway drug”), so from my outsider’s perspective, it seems there’s quite a lot of overlap between the various Monome products.

Ansible, for example, seems to be very similar to Crow (though with more IO).

Neither seem to appear very often on the 2nd-hand market (I’m a cheapskate, so most of my gear is either DIY or 2nd-hand).

#41

Ansible isn’t programmable though it does do lots of cool things

Crow’s real power comes when you start running code on it (via Norns or directly). For example this week I’ve been playing with chaotic non regular clocks (the jury is still out on if anyone wants to actually listen to me playing with the but that’s another matter - you can look in the latest tracks thread if you are interested :wink: ) - I don’t know any other way of doing that without writing firmware for something like the Ornament and Crime for example.

My ansible is mostly become an output expander for teletype or crow these days - since I run Kria on the Norns more often than not…

#42

Having spent a long time a few years ago coding for the Axoloti platform, I’ve gone off scripting for anything that doesn’t have a screen, to be honest.

That’s why Norns appeals so much to me (though the limited number of buttons and (especially) encoders counts as a negative for me, I’m afraid).

That being the case, the standalone aspect of Crow doesn’t really grab me. I might change my mind when I’ve got round to assembling my DIY Grid.

#43

so that’s the key thing - the crow brings all that power right into the modular! you can also script cv just like you can midi or sound with Norns :slight_smile:

anyway - whatever works for you TBH - different things resonate with different people and no sense working with (or paying) for things that don’t. I had a Waldorf Pulse (the original one) for years - on paper it’s a wicked synth but I never gelled with it - was kind of a relief when I realised that and sold it. But there will be a ton of people who would argue I’m an idiot for that POV :slight_smile:

#44

20 characters of Of course :wink:

1 Like
#45

Ok, I have an excessively naive question about clock in options, stemming mostly from an inability to fully test at the moment. If I switch to any option besides Internal (say, Link or Crow) in the Clock menu, I assume it’s normal for the coroutine in my script to continue running? In my head, I had originally thought that switching to crow, for instance, would temporarily stop the coroutine until a trigger was detected on the crow side, but that seems incorrect. I think I’m just confused as to how external sync works if my script is still somehow listening to (and firing) an internal pulse.

#46

from what i understand, totally normal – the global clock continues to run at the last known tempo, adapting its rate when it receives new timing information from any of the sources (sorta like a tap tempo). in performance, this is handy – the worst case scenario (your modular clock source thru crow wasn’t firing) is less of a showstopper if the global clock continues at its last known tempo until it hears otherwise from your new source.

i’m sure others can add more detail, but hope that helps!

2 Likes
#47

That’s great - thanks again, Dan. I’m in a weird position atm in that my router is giving me IP issues w/ Norns (can’t test link), and my modular is still packed in a box (can’t test crow) :laughing: Looking forward to playing with all of this soon.

1 Like