2 posts were merged into an existing topic: (Internally) outputting polyphonic aftertouch supported?
Wishlist of objects
Sounds like next release is going to be a game changer. A lot of new functions.
Looking much forward
More div obejcts. A math/div object that divides two inputs. Also a math/divc that divides input by a constant.
table/read i , table/write i.
(Reason: I want to store numbers which are indexes to other tables.)
A midi assignable version of ctrl/i. This object is really simple, small and uber awesome. I use a lot of them in all my patches and would definatly LOVE a version of it that is midi assignable. As it is now, you can only control it using presets.
I think this might have been mentioned before, but colours for objects would be awesome
Windows functions:
Would be really awesome with some extra windows functions for granular stuff:
Suggestions:
Hamming
Blackman
Blackman-Harris
Gaussian
Chebyshev
I guess we have Hanning already as plain math/window object
edit: oops i mixed up Hann and Hamming
Yes Hanning is pretty nice. I would really like to try the others to see what they offer. I looked in the code of the object to see if it was something that would be easy to code yourself. But I am not sure that it can be done by editing the object alone. Probably some java editing needs to be done too.
@johannes can for a hamming window be implemented into an object by editing the objects code alone or is java coding also necessary for this? Just want to know if it is something that I could do on my own, like basic object editing or if it is more complicated. When it comes to Java i am off. Yet too much noob for that. But masic object editing I can do
Hamming versus Hanning, it's just a bit more "raised", Hamming can be transformed into Hanning with offset and scaling, and I don't think it will make a huge difference for granular. Window functions can be fully implemented in an object, but I suggest not to underestimate the complexity, it's not because it is not java that it's going to be any easier!
Ooooh, oooh, a pitch detection pretty please... Though I'm afraid the STM won't be able to handle that...
Sure it will, but there are many different pitch detection algo's.
@Joren did some work on the Yin algo, but I don't know how "ready for consumption" it is: https://sebiik.github.io/community.axoloti.com.backup/t/creating-new-objects-guidlines-for-operations-on-large-buffers/192/8
yeah, after experimenting a bit with it, I think I could make a hamming with objects we have.
Still have some experimenting to do on the hanning. Can be used in many ways
+1 for FFT/iFFT for frequency-domain effects.
Some modules for doing interesting things with the FFT data before resynthesis would be good too.
Recreations of some or all the spectral FX here would be great (though I don't know how realistic that would be using the Axoloti's MCU).
http://www.michaelnorris.info/software/soundmagic-spectral
a|x
I write a lot of JavaScript, so I'd love to see a JavaScript script object. It would be useful for working out simple logic and routing ideas while keeping clutter to a minimum. It wouldn't have to run at audio rates, but could have arbitrary in and out ports, like the JS objects in Quartz Composer, or Max.
I don't know if this would be of any value to anyone else, though. I should probably just learn to use the existing Axoloti C object.
a|x
Developing a JavaScript script object would be a lot of work. All the JS code would have to be converted to C code to run on the device. Guess the easiest way is to learn C and the available functions for Axoloti.
@janvantomme true. As long as there's a simple API to access the guts of the Axoloti in C, that's fine.
a|x