Loving the crow integration. Here’s zellen sequencing rings/plaits (alt CV out) and tempi (clock out). Modulated by quadraturia and wogglebug. Tempi self-modulating and sending clock to marbles triggering pico drums. Field rec on Disting.


7 Likes

Beautiful tracks! Thank you for sharing these!

1 Like

Bug report:

Getting some errors where note_on appears to be nil - seems to be related to using a 256 grid.

Summary
lua: /home/we/dust/code/zellen/zellen.lua:53: attempt to perform arithmetic on a nil value (local 'note')

stack traceback:

/home/we/dust/code/zellen/zellen.lua:53: in upvalue 'note_on'

/home/we/dust/code/zellen/zellen.lua:315: in field 'on_step'

/home/we/norns/lua/lib/beatclock.lua:79: in function 'beatclock.advance_step'

/home/we/norns/lua/lib/beatclock.lua:86: in function 'beatclock.tick'

/home/we/norns/lua/lib/beatclock.lua:28: in field 'event'

/home/we/norns/lua/core/metro.lua:169: in function </home/we/norns/lua/core/metro.lua:166>

does local midi_note = state.scale[(state.seq.position.x - 1) + state.seq.position.y] sometimes get thrown out of range if grid y position is larger than 8?

EDIT: I think (in config) SCALE_LENGTH = 24 is too short with a 16x16 grid?

1 Like

Thanks for catching that! I don’t have a 256 for testing and just assumed that it should work with a 256. SCALE_LENGTH is very likely the culprit. I’ll look into it.

1 Like

Hi! Congrats on your script!
Any ideas where i should look into to adapt it to 64 grid?
Cheers!

1 Like

Thanks!

I think the script should work with a 64 grid without any modifications. The script queries the grid for its size and sizes the board accordingly. I only have a 128 grid so I could never test it with any other sizes.

I just simulated a 64 by setting my grid size to 8 x 8 and it seems to work. As Zellen doesn’t make heavy use of the varibright feature, I think you should be fine with a 64.

I raised SCALE_LENGTH to 32 and tried to simulate a 256 by adding 8 to the Y coordinates and it seems to work – at least for my makeshift lower half of a 256.

I pushed the change to the GitHub master and uploaded release v1.3.3.

Hm, I can’t seem to edit my original post. Could some admin unlock it, so I can add the new release? @dan_derks maybe?

1 Like

Confirmed - no more errors on 256 :+1: :tada:

Curious tho - I had to remove and re-clone the repo to get the changes. (had originally installed from maiden project manager)

1 Like

Awesome! Great that it works now!

Re: maiden project manager: To be honest I haven’t dealt with it so far. Do I need to do something for a new version to appear in it? As far as I can see it links to the github repo but not to a specific version.

You shouldn’t need to do anything other that push changes to the master branch on GitHub. Installing / updating just pulls the master branch of the referenced repository.

Thanks @ngwese!

I just deleted my git installed Zellen and installed it with the project manager. I got the most recent version, so everything seems to be working for me. Maybe it was a caching issue @okyeron?

yeah - not sure what was happening there. Some sorta cache, but not obviously the browser cache (which I had cleared).

@ngwese I’ll keep an eye out for if that happens again and report back.

1 Like

is there a way to define the higher and lower note or octaves’ area?

1 Like

Currently there’s no way to do this, but that’s a great idea! I’ll see if I can implement something like this.

1 Like

Accidental zellen shoe-gaze and I am digging it. Zellen > crow > rings/plaits > clouds > AUM

4 Likes

Lovely sounds! Some MBV/Slowdive-esque vocals would indeed be a perfect fit for this. :blush:

1 Like

is there a way to vary the note length/time/gate?

1 Like

Loving the script!
Just wondering if we have JF support yet?
And if it would be possible to have JF and crow cv operate simultaneously?

1 Like

Thanks! Working on JF support right now, should be ready some time later today. Yes, Crow CV and JF simultaneously will be possible.

2 Likes