Two layers Arpeggiator


#1

Hi Everyone,

Haven't yet found an exact answer as browsing the posts in the forum, but do guys feel free to delete this if inappropriate.

I'm looking for a way to use an Oxaloti board to make a double layer arppegiator that could generate midi from played notes as well as patterns, either calculated or from SMF, on different midi out channels.
Let's say the Axoloti would have to :slight_smile:
- add 3 fixed midi notes to 3 played midi notes,
- process the result given different programmed patterns
- to the first midi channel ;
as well as :slight_smile:slight_smile:
- extract the fondamental midi note from the 3 played and
- apply a different programmed pattern to the fondamental and
- midi out it on another channel.

My question as a newbie and a futur user is :
can Axoloti do this in a simple way?

As I prefer picturing the process rather than trying to make a bad explanation :

Thank you by advance for any comment and help about this project.


#2

Hi Cedric,

Welcome to the Axoloti world!!!
I don't know if I understand you completely,
but I think it should be doable.

What do you mean with the fundamental? The lowest note played, or a calculation that extracts the fundamental even if it's an inversion? Both are possible but the latter might be a little more difficult I guess.
Also what are the fixed notes, always the same notes or fixed intervals?
Triggering the patterns wouldn't be too difficult.

I think with some clever patching this is definitely possible with the built in modules, without having to program your own!
I suggest you take a look to the midi/in/keyb object, the math objects (+) and the mux and demux objects first? Also the AND OR ... modules are great to patch a logical 'conditional' data flow.
There are also midi out objects with selectable midi channels so yeah, sounds cool!

I don't know how much patching experience you already have on other platforms like Reaktor, Pure Data or Max and such, but the concept is ofcourse fairly similar.
For me personally, Jan Vantomme's book 'Getting started with Axoloti' was a great great help to, well ... getting started, without too much of a headache :slight_smile:


#3

hi Andrew,

Tx for the welcoming and this quick answer :slight_smile:

Fundamental : calculation if calculatable, otherwise lowest, you're right.

Fixed notes : always the same notes, like open chords triplet on guitar. Ideal would be that these fixed notes wouldn't be noticed if the midi played chord went more than 3 different notes ( why not adding this option ). Option : Why not being able to choose the fixed notes from a list set by the user? ( different base tuning for these open chords )

Midi Patterns : I'm a bit lost with the options of the gear, as its said that Axoloti cannot host midi files, but I've seen on demos that it was possible to patch some seq patterns that can, if I'm not wrong, logicaly loop....

I'm a fast learner when it comes to fiddling with modules rather than learning to code :wink: As far as the concept is easy as : enter/exit, values/ON/OFF/step seq/IF/etc. Color system seems to be of a great help for people to patch the Axoloti.
As the manual of Jan, you're right :slight_smile:

"Hold note" option seems to be easy to achieve, if I understand first chapter of Jan's manual :slight_smile: But I'm curious it could be triggered by a pad or button, like on the Arturia Keystep, for instance?

Two last questions, for know :
- Is it possible and easy to attribute a knob to a patch to modify its values? ( I was thinking about a knob to navigate the menu of each seq to determine which midi pattern was to be used )
- Is it possible to use either a screen being able to display to columns or to plug two displays on one Axoloti ( shared or separate menus for each seq as the Axoloti will have to seq playing at the same time with differnt patterns and midi channels )?

I guess I merely can contact Johannes to be put on the list for next units fab :wink:

Thanks again for your help, Andrew :slight_smile:

Best Regards,
Ced.


#4

Hi Cedrick,

I'm more of a patcher than a programmer too, but programming a lot of conditions is probably easier to code. Something like case 0, case 1, ... would prove very handy.
The patching route would involve a lot of = AND and OR modules together with MUX and DEMUX objects.
I still think it is doable.

So fundamental: I would start with the standard chord position for starters and implement the inversion calculator later

fixed notes: this is easy! Take the midi/out/note object, get the right note in there with a const/i object and give it the trig out from your keyb object. repeat 3 times et voila :wink:
If you want to choose the notes live, just use a dial in stead of the const/i

Patterns: you should look at logic/counter. You can drive it with a square wave LFO. Again with a const/i you can set the maximum steps by putting your maxnumber to the reset inlet of the counter.

For the HOLD, you can attach any button or knob to a MIDIcontroller by rightclicking on it and selecting the corresponding MIDI note or cc.
Just think about what parts of your patch you want to be polyphonic. If you want to hold multiple notes, you have to make a subpatch and set it to polyphonic. It is pretty well explained in Jan his book too!

So for your last 2 questions:
Making a bank of patterns and selecting them could be achieved with MUX objects. Depends on how many patterns I guess. I would say between 4 and 8 you can patch this easily but for a long list of choices you should look at implementing tables, so you can load a lot of patterns from the SD card or from a longer table in the RAM.

For adding a display or 2: yes you can. Check https://sebiik.github.io/community.axoloti.com.backup/t/spi-i2c-oled-display/638
but expect to be ready to solder at least some pin headers for some breadboard fun to start with.
But yeah.. technically it is possible! (thanks to the incredible work of some skilled coders in the community)

Happy patching :slight_smile:


#5

Whao!

Andrew, your positive answers are... Let's say that most of the forums I've been on these years are, most of the time, more of some " well, no... Maybe, but, you know, it's not done for it, so... But it's gonna be difficult I guess... " or places when the asker ends on more time spent to explain the why of the project than to get practical and clear answers.
Well, these have been really productive and clear answers in a short time! I'm impressed :+1:
I think this gear could the answer to put on hardware what I like on plug-ins and vst as well as focus on the main features I like using arps like Podolsky, BlueArp and Bitsonic WT-01 without re inventing the wheel...
Ok, you've convinced me to join the community, I guess :grin:
Thanks again for your time, Andrew!
I'll post here the result ( and buy Jan's book before everything to learn things while waiting for new boards to be produced. Great thing is that platform patching is available even if the board isn't connected to test the results).

Best Regards,
Ced.