#85

How do you set patchwork to start running using the internal clock (i.e. not clocked by crow)? I tried to use it as a midi sequencer but couldnt get it to start…

1 Like
#86

Patchwork was initially designed as a crow-based sequencer (exclusively), but I’m adding support for internal clocking atm! Hopefully will have an update in the next week.

4 Likes
#87

This is amazing! Most fun session I’ve had in months tonight with this controlling JF and my Hydra synth and Ansible doing other duties in my case. Absolutely wonderful!

3 Likes
#88

Patchwork is so satisfying. I find great pleasure in two independently clocked sequences, stumbling around drunkenly, only to be synced up again by the number “1”.

Thanks!

2 Likes
#89

closing the loop! this session happened! @Olivier, @mattlowery + @encephalitislethargi and i had an early AM meetup, tons of warm energy, we made this *norns walkthrough*: hacking a script to add MIDI output !

Patchwork is such a beautiful, expressive, deep script and it was such a joy to be able to mainline some of its magic with this crew :revolving_hearts:

6 Likes
#90

Noob question here. How do I get the Patchwork sequences to run?

  • Crow is connected to JF via i2c (I just updated both Crow and JF successfully today, so that shouldn’t be the issue).
  • Output (A) and (B) is set to jf.vox 1 and 2 respectively (if I set them to Crow 1+2 and 3+4 JF reacts immediately, meaning the i2c connection to JF should be alright).
  • I’m sending triggers/gates from Ansible into Crow’s inputs (have I misunderstood “To drive the sequences, send triggers into crow’s inputs.” ?)

Thanks! :slight_smile:

#91

Hey! I’ve found that a loaded script on crow can sometimes cause conflicts with Patchwork (among others). Sounds like you’ve got everything connected as it should be, so I’d try the following to start:

  1. In the maiden repl, try sending a crow.clear() command, and then re-loading Patchwork.
  2. If you have another trigger source in your system, try sending it to crow’s input(s)

If you’re still stuck, send me a dm and we’ll take it from there!

1 Like
#92

hey @Olivier have u managed to implement midi clock? Thank you!

1 Like
#93

Got a (relatively) stable release worked out, but got distracted by regular work duties. Will hopefully get back to this soon.

3 Likes
#94

What an amazing script. Finally had time to dig it, and i was only using one of the sequencers with juts friends…just thinking i could usd the other sequencer with midi!
Any thoughts on making compatible with txo?
Congrats on a keeper script!

1 Like
#95

Thanks!! Glad you’re enjoying it :slight_smile: Great call on TXo – I never considered it (and I have no idea how to implement support for it), but I’ll take a :eyes:

3 Likes
#96

Thanks Olivier! Thag would be awesome, cheers!

#97

I actually have some experience and knowledge of TXo functions and abilities. If it’s about putting them in to self oscillating settings, with their envelopes and waveforms, I could give a little input and possible apply code. I’ve come a bit further with my Lua and became familiar with the TXo functions thanks to using the Teletype and some Max patches through crow.

I’d be down to collab and give you some basic functional heads ups. I’m pretty busy with the baby boy, so i might only be able to share info, but I’d be curious to try the code base and point you in the right direction.

4 Likes
#98

That would be great! I actually have a TXo+ in my case (therefore familiar, generally, with its osc + envelope settings), but wasn’t sure if crow → TXo communication was only possible in development builds of the crow firmware. Send over a dm and we’ll take it from there!

1 Like
#99

Hi! I envy you lot knowing how to code with lua and norns. Trying to get my grip with teletype at the moment, your inputs is greatly appreciated! Muchas gracias

#100

2.1 - Clock Update

ezgif.com-gif-maker (1)
ezgif.com-gif-maker (1)1200×639 43.6 KB

Demo notes: two different jams, cross-faded near the 1-minute mark. One sequence is sent to Ableton over midi, and then duplicated across three tracks, each one with a different instrument loaded and pitch offset. The second sequence is played via Just Friends in JF.NOTE mode, coming back into Ableton with a bit delay added.

In 2.1, norns’ global clock is now the default. Dual clocking of both sequences via crow was cool, but perhaps a little too niche (you can still use crow as a clock source with the global clock, it should be noted). Now, both sequences are driven by the global clock, but each one has its own set of additional options (in the params menu):

  • BPM – defaults to 120bpm
  • DIV/MULT – turn encoder to the right for multiplications of global tempo, left for divisions
  • PROBABILITY – sets probability of whether the sequence advances

Take note :pencil2:

When adjusting BPM(A) in params, BPM(B) will be set to the same value, and the global clock will be adjusted accordingly too. This is primarily intended for ease of use. Once BPM(A) is set, though, BPM(B) can be shifted independently for phasing effects.

If you adjust the global tempo from the system CLOCK menu, BPM(A) and BPM(B) will automatically be set to that new value.

Thanks to @zanderraymond @swhic and @perbarfot for testing!

21 Likes
#101

20 characters of awesome!

2 Likes
#102

Exciting update!
Looking forward to trying out some phasing sequences.
I know for sure I’ll miss the classic crow clock options even if was niche it was a fantastic feature and one that more sequencers should implement. It was so so good for sending in rhythmic gates. Just Friends/MP/Kria were perfect. Simple sequences would constantly evolve and it was really playable when changing trigger patterns.
Would it be possible to bring that functionality back?
Maybe with the option for internal/global clock or crow for each sequence?

Thanks!

1 Like
#103

I hear ya – it was a tough call to make, but I found that moving to the global clock would provide more flexibility to a greater number of users. Hopefully rests + commands + probability adjustments will get your sequences into that realm of organic evolution :slight_smile:

I may revisit crow clocking in the future, but for now, feel free to grab and install 2.0 from github:

5 Likes
#104

Definitely would have been a tough call and I totally get that global clock will be best for most users. I am also pretty excited to try it out myself. I think the rests + commands + probability will get me in some great territory. But the playability of the crow inputs sets this apart from most sequencers so I do hope you revisit this.
I already planned to download Patchwork 2.0
If I was to rename it to say, Patchwork Crows via Maiden am I able to install the new Patchwork 2.1 without overwriting version 2.0?

EDIT: I renamed it and saved it then installed the new version. Both are now side by side. This will get me by for now :blush: