#194

i hope you two get well soon !

#195

It seems like the modification you made somehow effected the cv-slew parameters. I tested with the same cv sequencer as before, amd when you change the cv-slew parameters you get all kinds of weird things happening, either dropping on cv channel or the other. Both on waves and lines.

I went back to the original version, and though it has the big jumps in the cv values, the cv slew seems to work just as you’d expect.:persevere:

#196

yeah still working on it

see PR 296

1 Like
#197

I tested out that version.

It works perfectly except that strangely cv1 and cv3 don’t respond to any input value changes at all! Everything with cv0 and cv2 works great.

1 Like
#198

yea… sorry, we’ll get it sorted.

its a bit of a snafu at the moment - i’m travelling and don’t have access to 10v hardware. rick’s having other hardware woes. realistically there is not anyone else to work on this right now, we’re flying blind

i’m regretting “lending” my gnice+ to The Harvestman two years ago :slight_smile:

2 Likes
#199

So…I finally dug into the parameters in the lines module, figured out how versatile they are and produced Don Cab levels of guitar looping phrases. Then I realized it’s time I stop messing around and get a real Monome grid as a sequencer.

I’m curious how others are using a grid as a sequencer for aleph params. My intuition led me to mapping sequences to change the read_pos param for some zero-time live phrase chopping. I got to the point where I had to stop and sketch out Bees patches to make things more interesting.

Aleph Testers Corner
#200

yo! i have 128 and two 64’s. let me know if you wanna borrow one! i could bring it to noise bridge

#201

Oh, yeah. Let’s. I’ll dm with details.

#202

never tried

yes i lack imagination

#203

the acid module & aceeeed scene from skektek zip is an unimaginative (but technically correct) answer to this question! Basically kria & whitewhale are super-fun step sequencers & there’s a module dedicated to this combo.

It’d be fun & not a crazy amount of work to ‘fork’ that module with more interesting melodic voices - currently it’s just 2 303-alike ‘analog modelling’ synths with adsr envelopes & 4 pretty flexible drum voices. the bfin single-sample processing could probably compute something like a stripped-down ‘waves wave’ or ‘lines line’ in place of the 2 monosynths.

1 Like
#204

So did I until yesterday. It hit me when I connected one of the four switches to multiples of the read_pos param. The loop I just recorded jumped around.

2 Likes
#205

i like two krias controlling lines read_pos, read_mul/div, focus swap between them on m128, use encoders for mix points and filters

2 Likes
#206

what’s a kria do? –

#207

its a grid-sequencing bees operator based on the function of the same name in monome Ansible euro module.

https://monome.org/docs/modular/ansible/

i’m sorry, docs are lacking on the differences. you probably just want to look at the operator source… :grimacing:

1 Like
#208

It’s actually a port of the the alternative whitewhale module firmware https://github.com/monome/kria - so there are some major differences from the ansible kria. tehn’s instructions here I think are consistent with the aleph module features Kria 0.3 initial release.

As an aside, I want to look the ansible kria for a puredata version - from what I gather it seems there were some pretty significant advances for melodic sequencing. It might be even bigger (in terms of code size) than the WW alt firmware, which would make it unsuitable for BEES imo.

Also @Yann_Coppier & I worked a bit on a word doc documenting the updates - we should dump that into plain text & put it in the repo soon…

EDIT:
darn, I was trying not to clutter this thread with dev chatter…

3 Likes
#210

Dont feel bad at all, i’m glad this convo is happening

#211

look - a study! I won’t post the patch (yet) because it’s sitting on top of new/scene-breaking changes to BEES/lines… I want to think really hard about whether it’s possible to do do tap-timing as well as I can on my feature branch (https://github.com/boqs/aleph/tree/lines_timebase) without breaking all ye olde lines scenes…

The patch is basically a taptempo-captured casio loop (no encoder-bothering to set loop start/end points) & a single kria (2 channels) doing some variant on what ezra described above. It uses presets quite a bit for the looper functionality… Source material is like 30 secs of SK1’s stock demo rhythm - kria’s clocked @ 1/128 of the entire capture using a new ckdiv (clock-dividing-metronome) operator

4 Likes
#212

yup.

that.

is.

the.

one.

#213

Another study, riffing on the same theme (SK1 vs aleph). This time I used some bends to generate the source material.
https://soundcloud.com/rick_monster/casiochop-number2
had to rebuild the patch - lines doesn’t appreciate being treated this way, so the chopping line will occasionally get ‘stuck’ in a state you can’t get it to make any noise & require reloading the module. Requires the changes I pull-requested to monome/dev (BEES & lines) in order to run… https://github.com/boqs/aleph/tree/lines_timebase

captcha.scn (256.1 KB) (noone try & run that patch it’s not gonna work)

managed to record something before it blew up on today’s third attempt!

3 Likes
#214

I have a couple other things on my schedule this weekend but I’ll get to installing your branch in the coming week.