#62

as a note for anyone diving in to that scene… i realise that if you don’t have a foot pedal (and don’t mind it continuously recording) you could just set run_write to 1.0 on both del0 and del1 by hand… as far as I remember that shouldn’t be affected by any presets.

1 Like
#63

ok… here’s the current version of the scene i posted recently.
Video demo here Latest tracks + videos
There’s a few new functions but the docs I posted before are still mainly correct. New things include different pitch scaling options. If you scroll through the preset list you’ll see STANDARD, TONAL, LOFI, REV. recall any of these then the pitch control of del0 (usually encoder 0 in most of the modes) will have quite a different impact. Usefully they don’t have any effect until you turn the encoder (e.g. you can recall them without affecting what’s currently going on.
The two new modes are STOC and READER. I’m hestitant to make proper docs for them unless anyone actually wants to use them. If you do and don’t understand them buzz me and I’ll give notes.
Download the scene here- _stereo3.scn (256.1 KB)

Docs of previous version here alephTune.pdf (102.2 KB)

6 Likes
New ALEPH scenes
#64

Thanks for sharing… please, tell me, do you use beekeep as editor?
I tried to build an OSX version (homebrew) but despite I’ve followed the instructions a lib is missing…

#65

thanks for sharing the revision

hey by the way
I used this scene to scatter my synth into something sundanese (for the mitamine project mentioned elsewhere)

#66

No, always seemed a bit too much effort
Very happy just patching on the device itself
Good for making quick changes to interface too

1 Like
#67

Oooe great!
Where do I hear that?

#68

i’ll post longer excerpt of the session eventually or record a fleshed out track but
the first ~30 seconds of the new mixes here

the rhythm and bells are just a short volca fm sequence passed thru tune.scn
(vocals were processed thru organelle)

#69

Hello people. I have been out for quite a while I must say, but will be back on the Aleph very soon, hopefully with some new scenes and stuff I have been willing to develop in a long time. Thanks for keeping this forum alive, and thanks to those who keep sharing their work!

3 Likes
#70

This is a waves scene made on bees 0.7.1 (actually the whole card image is copied to the desktop)
Very cool, I am using the SD card my recent one came with.

_.scn (256.1 KB)

GNU X Font bitmap support / Tracker modules?

Probably a good idea to lower volume settings.

1 Like
#71

Oh waow a LOT has been happening here! I am very much back on track after having worked a lot more with the Grains module - besides my research and the production of about 4 albums (3 of them using the Aleph extensively). I will try all the new stuff that is up there now, so much looking forward… Damn this community is fantastic!

3 Likes
#72

Heya, found your video, chased down the scene file to this forum post and loaded it into my Aleph. It’s my first try with the lines module. Thanks for wiring up all the parameters. I made a variation on the classic Link Ray song Rumble as a way to discover the beauty of the low pass filter resonance into positive feedback on delay1. If you’re curious

I figured out how to get analog I/O to delay1. I could not figure out how to get the same source to delay0. Probably just needs more hacking but I gave up after the third or fourth try.

My question is based on the PDF you posted. Reading the doc, it looks like there is a pre-feedback send which could come back into the DSP chain. This is relevant to my interests. Is it possible to send the del1 => del1 parameter to a DAC, effect it with another unit and bring it back into a ADC to be fed back?

1 Like
#73

in lines and waves there are 16 parameters controlling ADC->DAC routing.
adcN_dacN with N in [0, 3] = 16 patch points.
(well, in waves they are patch points and in lines they are slewed multipliers.)

in lines there’s also adcN_delM and delM_dacN, with M in [0, 1], so 16 more.

if you set adc0_dac0 and then physically connect dac0 to adc1, then adc1 will be adc0 delayed by one sample at 48k. (which is the only SR the aleph will feasibly run at without hardware hacking.)

adc0, adc1 and dac0, dac1 have analog boost/cut knobs. (the dacs share one knob.)
adc2, adc3, dac2, dac3 have no analog volume controls! they are just there for weird routing/mixing ideas.

and that’s about all there is to know about the routing i think!

so in a word: yes (it is)

and in short: yes, if you mean what i think. the paths del1_del1 and del1_dacN have identical sources.

2 Likes
#74

that settles it. this does what I expect and that’s pretty rad. thanks for the tips.

#75

Hi,
i’ve actually got a better version of the patch now with more flexible routing… away from studio this week though, can post it at the weekend.
d

3 Likes
#76

a central space to share and archive scenes

you can upload zip files right now
but if others wanna use it I can ask them to allow .scn and other formats we use

probably not worth the effort

4 Likes
#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?