Wishlist of objects

#67

I'm sure a lot of changes would need to be made, but it would be a good start, in terms of raw DSP code, already optimised for the ARM Cortex M4.

The other issue of course, is that Olivier at MI is pretty good at squeezing the last drop of performance from an MCU. It could be that some of the oscillator types from Braids, for example, wouldn't leave much in the way of processor resources left for anything else, if ported to Axo objects.

I'd still love to see some Braids oscillators, particularly, appearing in Axoloti. If I had the first idea how to start, I'd probably attempt to port the vocal-synthesis ones, and the 'supersaw' unison oscillators, the phase-distortion ones.. actually, just all of them.. :stuck_out_tongue:

a|x

#68

No idea if it's possible, but how about a speech-synth object, based on Flite?

I'd envisage the ability to enter a plain-text string or list of phonemes, and have it step through the phonemes on note-on trigger, with control of pitch in realtime. There would also be some mechanism to reset to the start of the sequence, and perhaps to jump straight to individual phonemes in the list.

Some kind of re-creation of the vocal synth machine from the Monomachine would be great, too, but maybe based on a different synthesis engine, as I never found Monomachine speech/singing very comprehensible.

a|x

#69

Thru boxes are great unless your trying to use axo to poly chain.

#70

a through 0 oscillator would be cool for some different side bands with FM. might be hard to code I have no idea.

#71

i also apply for a midi thru/ merge object

#72

A scope object with 2 inlets would be handy to compare signals.

Unipolar and Bipolar: What does it mean?
#73

Maybe also an option to sync a scope to an oscillators period, so you can view a single waveform cycle.

a|x

#74

+1

yeah, I think the scopes are really useful, I think a bit of time on these could be valuable.
my two 'wishes' I think would be:
- x/y scope
- variable time base

oh, and id really like some bigger (horizontal) ones. often i don't care how much space they take, as they are for debugging. hmmm, perhaps I should consider this more as a new debugging tool for wires :wink:
(@johannes raises an interesting question of introspection... I guess given its native code, we'd potentially have to consider compiling with debugging, and then use debugging hooks... unless 'potential' inspection/watch points, can only be set before you go live)

#76

Emulating an x/y scope is pretty hard to do. If the bitmap is generated in the GUI, it needs a continuous data stream. Displays are polled by the GUI, avoiding a significant performance impact, but no stream continuity.
Generating the bitmap on the target would cause a significant dsp load.
Even low-end digital oscilloscopes based around fpga tech suck in emulating x/y mode.
Even without connecting the dots, every sample is a scattered read+write (unpredictable address).

A two-channel scope 'd be much easier.

Debugging: one approach 'd be importing the linker map file, and perhaps even add some gdb-server functionality. In my development plan this comes after investigating a switch to (lib)Clang (replacing Gcc), to avoid a double effort.

#77

I'd love a PWM Osc with sync input - I've tried cutting/pasting code from both the PWM & Squ Sync oscs (and associated help files) but I'm not getting anywhere with it :frowning:

#78

Generally, Sync and Phase inlets for all the osc types would be cool, I think.

a|x

#79

I would like to have chebyshev waveshaper object. Or maybe some hints or tutorials how one could convert this to axoloti object.

Plus hints for this also.

#80

Please understand that my current development focus is on framework rather than adding more objects.

waveshaper.
"dist/soft" is one particular case of a chebyshev

#81

That's understood.

a|x

#82

I'ld love to see a larger rfft module, the screen on the original module is just too small to be really useful. Doesn't necessarily need to have more sample, but a wider screen would be really nice..
Or is this possible by only adjusting some internal values?

#83

Scopes that shows more than 128 samples. For example 256, 512, 1024, etc.

An idea for bigger scopes could be:
The scope could have a drop down menu like the tables have, where you chose tablesize. The scope then display the amount of samples that is set in the drop down menu. This wold be really awesome, cause if you set the scope display size to the same size as the table you are using, you would then be able to see the whole content of a table.

#84

on my wishlist : xy pad , minmax fader , and a single fader (vertical and horizontal).....

#85

ctrl/toggle and button should have an input to switch on/off,.

#86

This would actually be very useful. I wouldn't suggest it be bigger on the patcher UI, just take every other sample or 1 in 4, 1 in 8, etc.

#87

Like a sort of passthrough? Well the button is easy to do, just run it into an OR gate. The other input on the OR is your passthrough.