#113

cool to see a different approach to patching, I’m totally in on the module “patchability” idea.

on a side note I recently got hung up on a possibly silly idea to use the bfin for graphics/video. notably I have yet to find out if this is something worth pursuing considering that it would “divert” from the original idea/design etc, but I would be up to discuss possibilities.

3 Likes
#114

[quote=“skektek, post:97, topic:177”]
With no grid, this should work:

  • first set SIZE to 6
  • then set 2 encoder ranges both 0-6
  • connect those to X & Y
  • connect sw1 to BONK
  • hook up Hz to a Hz input on, e.g waves.
  • set play screen visibility on X & Y to see where you are on the square
  • tap SW1 to emit a Hz value

with a grid, create a GRIDRAW & a HARRY:
X -> X
Y -> Y
BUT -> BONK
[/quote]Searching here on the forum aint bad but I’d like a hub for referencing all updated features/ops/etc

It would be awesome if the docs were refined to include updated “studies” (and more generally reflect the staggering progress in development since the last update)

#115

btw…@skektek thank you for the incredible work recently

not sure if the ops for grid patching were inspired by @rick_monster @Yann_Coppier ideas from last yr

1 Like
#116

Hello hello… Just saying, but I have been using Grains a lot more in the past months. I can honestly say I have enough good material to make a record now, and a lot of it comes from that sweet module! An incredible lot can be done, and I have made some scenes to make things easier to control. Will be back shortly to explain what I did and share. In the meantime, I’ll have to ckeck all the new stuff that has come for the Aleph recently, which seems rather crazy! By the way I was wondering if, for instance, the MEM0D and such (from @stektek) were the same as yours, of some new versions?

3 Likes
#117

Diving back into this update again tonight and will post a scene. Really been pleasantly surprised by the drum sounds aleph is capable of by tweaking the acid app. Scary good and definitely grittier than most would expect from pure dsp.

Finally put down acid long enough to test my old scenes this week and none are working :frowning:

Don’t really mind rebuilding em but…is anybody else having the same issue?

#118

@skektek @tehn its long overdue but i think we should just roll these changes into the upstream.

the main thing the aleph needs is still a better UI / patching language for constructing scenes offline / over socket. it should not be hard, we just need to get it done…

1 Like
Aleph wobbliness (and emulation)
#119

maybe we could write a script to parse pd scenes containing the BEES_PD objects into working BEES patches? This might still be quite a bit of work!

With the arbitrary op insertion/deletion & properly working preset system I’ve found building scenes on the device to be satisfying & productive (though definitely still somewhat ‘write-only’). Think there’s a PD scene for the ‘marimba’ patch in the snapshot I released. I find it nearly equally fiendish to construct brain-melting tangle of PD wires on computer screen as a huge BEES netlist constructed piecemeal on the aleph.

‘patch language’ as in text/code representation of BEES netlist? cool!

2 Likes
#120

I thought this would interesting the more I looked at pd but figured everybody would ridicule the idea…wasn’t smart enough to implement it myself last year

#121

that would be cool, similar to shlisp. there is already the JSON serializer, which really does kinda work

simplest step i had in mind was just a command syntax for live-patching over socket, commands corresponding to patching actions on the aleph UI. would have terminal feedback too

(i dunno, just making this up)

NEW DIVR - replies with 14.DIVR or something
INS 14 replies A B B_TRIG ?
OUTS 14 replies VAL R ?
SHOW OP 13 replies (say) 13.FADE [A B X] [VAL] ?
CONNECT 13.VAL 14.B
SET 13.B_TRIG 1 ?
INC 13.A 1- include input node in preset 1?
INC 13.VAL 2 - include output target in preset 2?
SHOW PRESET 1 - ARGLBARG [13.DIVR/A:0xFFF]

i mean this is all pretty doable given that everything is bees functions plus a simple parser.

3 Likes
#122

That would be really sick

Now that I’m used to teletype I might actually prefer that over anything else

This system (or the pd-wrapper mentioned above) would be really fun tools when away from the aleph itself

#123

I really like the grid focus-swapping paradigm on most recent firmware & this also works in the pd wrapper. Think the way this now hangs together is true to brian/ezra’s original vision for aleph as grid host.

Would be cool to make that focus-swapping somehow work outside of the pd BEES wrapper - standalone PD grid apps as C language PD externals which nonetheless can grid-swap between one another by ‘stealing focus’.

1 Like
#124

Ok now I am in there, and I must say this is absolutely brilliant!
Now I have so many questions I’ll have to try it all first, spend some time and find out about the obvious first.
Just to know, there is no documentation whatsoever about the new modules (fmsynth, acid) or the new ops, right? Wouldn’t it make sense to build some and integrate them in the existing?
Again, the Aleph’s potential just exploded and I am ever so grateful for it!

2 Likes
#125

Very interesting, man I missed all of what happened within a year, or so it seems! Still, I have been making a lot of music but I only tried the fmsynth module 10 minutes ago. Lots of potential, although it gets messy super fast! I of course noticed that the lfo wasn’t implemented yet, but I suppose you’d use it as an extra source of modulation, right? Or maybe just on the filtering part? It’s crazy with the Aleph, that so few people have it but still it remains such a great source of inspiration. I did play a gig last week in Norway, at Punkt Festival, live remixing a rather free jazz band with the Grains module. And it worked wonders!

1 Like
#126

grains is still a challenge for me to understand cause it can do so much!

I need to sit down and patiently tackle each section to properly utilize it

1 Like
#127

Yes I know, but once you figure out how to use your grid as a matrix it becomes easier. Without this it might feel like a mess I suppose, I am quite used to it now. But true, some things remain challenging. If you get into it as well we might be able to discuss more (along with @rick_monster), but maybe I should send some of my sessions first?

Unfortunately I have made those with a custom version of Bees, in which I have added a couple of modified operators in order to use less memory on some patches (HIST2, ROUTE2 mostly now). Maybe we could have them added as well in the version of Bees @skektek put out, so I could share more stuff? Otherwise I keep making my own compiled versions, which makes them difficult to share… What do you guys think?

Oh and I have to get back to the Loom stuff by the way, now that we have extra elements to work on the Grid!

1 Like
#128

you on git?

I’d be willing to compile your modified BEES to try some of your scenes (if/when they get folded into the non-release skektek put out…great!)

#129

Hello again,

So I am actually looking into fmsynth, with one year of delay I know!
Very interesting but still, I have found a few bugs - unless they are intended, you will tell me.

  • There seem to be quite some entanglement between Op2 and Op3. Basically I think they are addressed as one and only operator, with op2 not working at all (no pan, no envelope, no tuning, no modulations). Only its volume, which logically conflicts with op3Vol. On the other hand, op2’s envelope works when op1 is modulated by it.
  • The waveshape parameters don’t seem to work.
  • Not a bug in itself, but the envelope parameters go from 1 (long) to 150 (short), which is a bit strange. Furthermore, the long ones are still pretty short considering we are doing FM synthesis. Maybe they could be extended quite a lot?
  • Finally for now, the intermodulations are great but they tend to jump at some undefinite points, where the sound disappears (not always at the same point) or jumps suddenly to seemingly different values. Without getting into the jumping and all (it is difficult to quantify at this stage, as I just tried it), some Slew parameters in there, although that might bring quite a few, would be great. At least for the tuning. Also, and even though it is surely not the point of FM synthesis, a filter (or 4) could make the sound more flexible… but that’s mainly my point of view, and you are welcome to disagree.

Alright, time to sleep. Again, thanks for this great job!

1 Like
#130

Hello there, is it just me or the Alt button (last one on the last row of my 128) gets stuck as soon as you press it, using the KRIA operator (which is extremely cool, by the way)? As soon as I touch it there is no way for me to remove it, and on the tutorial video it seems like this specific button is temporary… Any clue?

In all cases, thank you so much for this. It is already more than I could hope for!

#131

wow, kind of a lot going on in here! Many interesting ideas, few tricky questions etc… the fmsynth was pretty much a 1 day hack, haven’t played with it much or given it much thought. Very probable your bug reports are accurate - linux-hosted dev tools have improved again. Straightening this module out should be pretty straightforward…

1 Like
#132

Nice to hear! Also, I noticed that in the Bees version @skektek there are two Grid operators now. Would it be fair to say Grid is the old one and Gridraw is the one you made?

1 Like