DSP Robotics Support

I confess the penny has only recently dropped ...

When using the Analyser prim for non-analysis things ( - personally I regularly employ the Analyser to create wave arrays, interpolations, control scales etc etc), you can write entirely normal-looking DSP code with stage(0) & stage(2) sections, the same as we can do when using DSP for stream purposes.

When DSP (or ASM) code is used normally in poly stream it is 'clocked' at your sample rate; stage(0) things are executed just once - at any Note_On - and then the stage(2) section is executed repeatedly, once per sample, at sample rate.

However, when you use such code with the Analyser it just goes for it all, flat out. See the attached - clearly if this was running at sample rate it would take the best part of 1 second to complete, whereas .... ah.


Bit of a clue here, actually, that you don't need to pull in an ASIO_out or DS_out to make this work - hence there IS NO sample rate. Doh!

This will be the reason that trying to connect any Analyser's code to a regular stream is prohibited. Obvious once the penny drops!

Anyway - probably the fastest single item we have in Flowstone

H

Very useful insight Hugh, many thanks.

ooh ty Hugh- will try to understand
-just playing with analyzer now for rendering
..do you want to help- the project is open source

it's for rendering a recorder/renderer in stereo with float array conversion

-do you think float arrays could be processed more quickly using 'analyzer'?

bahaha- it's soo darn fast at making arrays
- how can I make the .wav stereo though?

omg omg- this is such a quick toy

here r some edits- making it longer and using a simpler and complexer counter==>


-can this be bent into the mythical green samplerate timing?

-omg-this is working wicked to render stereo fx

here's the tidied stereo normalizer,
which u can do any float array operations on,
then it renders as fast as cpu,
so vastly beyond realtime==>

What FS version Nix ??

the latest 64 bit Alpha,
RJ mate