jitter versus msp for audio data arrays?
If I am interested in processing real-time audio only (no video displays), are there advantages to putting the data in jitter arrays, as opposed to MSP objects?
I suppose jitter is not as flexible as MSP to manipulate samples.
But it seems interesting for things.
Can’t help further.
There are some examples in jitter-examples folder > audio.
Seems useful for display.
As a new creastor, Im a little surprised, I had thought from the wording of the overviews it was good for all kinds of array processing, but at least for audio, it seems intended for visualization only. I had wondered about building sequencers and filters in jitter, but it doesn’t seem a good idea.
In the meantime, I remember an example with filters jitter-based somewhere …
Jitter is really good at dealing with any kind of data that will fit into an n-dimensional grid. If you are interested in working with Jitter for sound, I recommend checking out the help/reference for the following objects: jit.catch~/release~,jit.peek~/poke~,jit.buffer~. Also, read the article "A Noisy Matrix" here:
…and check out the the Jitter Recipes as well.
The most important thing is to spend some time getting to know what a matrix is and how to use it and operate on it in different ways. Once you get that far, ideas will present themselves.
As always, if you have a specific idea or problem that you would like to solve with Jitter, we will be happy to offer advice.
MSP buffers are designed to handle audio vectors: mono-dimensional, or
stereo / multichannel.
Jitter matrices come handy when you want to manipulate more dimensions. For
instance, sonograms are great candidates to be processed with Jitter.
If you are into spectral domain processing, you may be interested in this
article of mine:
> If I am interested in processing real-time audio only (no video displays), are
> there advantages to putting the data in jitter arrays, as opposed to MSP