#77

Nice one! I am rebuilding all my main scenes so far (and much more), and will post some there as soon as we have a stable common release of Bees, including all the bug corrections. I’ll try your patches the 3 coming days and will get back at you - also, I am in the middle of collecting all we have about the Bees Operators so far, as the info from the website is rather outdated). I don’t fully understand them all, so I might ask around soon.

1 Like
#78

Awesome

Those scenes might have been broken with skektek no-release…doing investigatingmyself and will try to rebuild any that I have to.

#79

Another ‘nonrelease’ might be pretty imminent I think! Just been on a coding binge - several really important enhancements on last skektek zipfile…

Potentially scene-breaking changes to slew parameters on fmsynth, acid - the lines-style slews are just much better to work with for responsive DSP tuning. Also there’s the issue with varispeed/classic lines with skektek version. Skektek zipfile introduced a (potentially) scene-breaking change to lines.

I’m thinking ‘classic lines’ should continue to be called ‘lines’ for backwards compatibility with 0.7.1 module, whereas varispeed lines should become it’s own thing, potentially optimising the module params for the musically useful things one might want to do with continuous varispeed (e.g ‘playable’ sampler duties). Gonna make it so in my branch.

EDIT:

Also there was an important feature added in skektek zip which changed grains’ param list - namely the textual labelling of ‘named patch points’ - if rebuilding grains scenes I’d recommend the skektek version

3 Likes
#80

OK, I was wondering whether your work was a different tributary. This is great news!

#81

are some people working outside of branches in the github repo?

#82

apparently not

@skektek had an update hosted on a personal site months ago but i guess the changes have been folded back into git by other devs

#83

yes there is an extensive set of changes outside of GH that needs to be brought in

[ed] probably see https://github.com/boqs/aleph for latest and greatest at the moment

#84

they havent actually… working on it!

1 Like
#85

oi, I can help with release management, merging, branching. I do some of that professionally. I have a better feel for the codebase this week :slight_smile:

3 Likes
#86

the big PR is open here if you wanna check it out

2 Likes
#87

Oh, that’s quite a diff. I’m scared now. At the least I can run this on my unit.

#88

Since my recent grid 128 kit assembly, I’ve been using my Aleph a little more every day. I was reminded today that there are White Whale and Meadowphysics operators.

I don’t really understand how these work. Before trying every combination of inputs and outputs as a last resort, where would I find a way to get the Aleph MP operator to give the same kind of demo like in the video on monome.org?

#89

which video?

and at risk of sounding patronising…do you have a grasp of how they worked in the standalone eurorack modules?

#90

I do not know how they work as eurorack modules.

The video at https://monome.org/docs/modular/meadowphysics/

“Circular resets are possible”

#91

Ah ok

i’ll investigate tomorrow but iirc that vid is for “mp2” which hasn’t yet been ported to aleph yet
some features not included in the version we have (i think)

WW might be the same

#92

Bfff… I’m so out of it since getting back to UK, we are moving house for 3rd time in under a year so can’t fish out aleph and answer properly.

But the info is definitely lurking around on this site and/or monome.org. iirc yes the aleph op is mp1, and definitely very simple to understand once you find the right material. Also iirc my conclusion was the improvements in mp2 were more relevant to eurorack than bees.

#93

Definitly still wishing cv output was working on the aleph, using meadowphysics one on my modular would be very cool.

#94

CV output doesn’t work? I have an analog modular rig now and this would make me sad.

#95
#96

That looks like a complicated bug. It also appears it was fixed but the fix had a regression for some modules (that I don’t use).

I’m working with a bunch of Mobenthy modules that do unpredictable things, so the CV output of Aleph works for that. It seems like the bug is for situations where predictable, precise output is required.