Polyphony example?


#21

superficially this may be true, but in practice false.

there are two approaches
a) simple ... get your sequencer to generate midi thats put on the internal midi bus, then let the poly patcher do its voice allocation

b) dont use voice allocation at all... instead, put your sequencing table in the parent patch, then index this with the voice index. I showed this in one of the first challenges.

you should even be able to use my polyseq objects for this, where the trkId is fed by the voice idx of the poly patch I didnt do this in the help file for clarity sake, but no reason for it not too work.
(note: you can dont need these objects you can do this with simple tables, as per my challenge patch, but the objects cover quite a few things I wanted to do with sequencers, e.g. polyrhythm/polymeter)

(b) is a typical example of Axoloti, where it pays to think laterally (in this case, 'what is a voice' yields the answer)
this is something I like about axoloti, at first you might think something cant be done, but usually with a little reflection, and some creative thinking, you can come up with a solution.


#22

Indeed, I had overlooked the internal midi option (posting here, might be useful to someone).
And I will look into your "challenge patch"!
Thanks.
-poly-in-axoloti.axp (7.0 KB)


#23

Very cool, I found your example:


In attachment, a much simpler patch, just to show the functionality.
Things are very clear now. Thanks!
J-F
polyphony-no-midi.axp (3.7 KB)


#24

yeah, this use of voice idx is pretty common. (many use it to create a bit of 'variety' between the voices)
I think what many are not familiar with is using voiceIdx with tables in the parent patch (which is what creates some of the complexity in my what if patch) . the trick is using offsets allow you to use tables as multi dimensional arrays.
anyway, as i said, I think you dont even need to worry about that now, as my polyseq objects can be used to take care of these implementational details.


#26

For me, Axoloti app quits unexpectedly as soon as I execute step 4.
I click View --> Settings, and the app terminates immediately.
I am using Axolotio app version 1.0.12 (1.0.12-1-0-g4de2b632)
on Mac OS High Sierra.
Any suggestions?


#27

Thanks, this is great, I've been struggling as there are no obvious tutorials on how to organise things like this.