[Beginner question] live audiovisualization with particle system
i want to create a live audiovisualization system. The idea is that the parameters of a particle system are controlled by several audiodescriptors. Therefore i need some initial help or a starting point. Are there any good tutorials or references out there.
These are relatively simple things to do in max but they require basic knowledge in a lot of areas.
The built in tutorials are the best you’ll find. Flip through them and you’ll find most of the topics you’re looking for. Honestly, I’d start at the beginning with max, move to MSP and finally to Jitter. They go really quick so don’t be daunted by how many there are.
Finally take a look at jit.p.vishnu.
i went through some jitter example patches and tutorials and finally got something to work, but the problem seems to be that after a certain amount of time the particles vanish from the screen. Is there a possibility to prevent the particles from doing that by giving them some kind of boundary?
Here is the patcher
check out the jit.p.bounds object
i get a "mismatch dim"-error. is it possible that the jit.p.bounds object only works with vishnu and shiva?
the jit.p.* objects pass 2D matrices. the second row of the matrix contains the previous iterations values.
if you are using a homemade particle generator, you *should* still be able to use p.bounds, as long as you provide this second row to your particle matrix. "jit.concat @concatdim 1" can help you to join two 1D matrices into a single 2D matrix.
check out the "Discussion" section of the jit.p.shiva reference file for an in-depth description of the jitter particle objects.
Thanks for your help.
I changed the dimensions of the matrix to 2. now the error is gone, but the particles seem to ignore the boundaries.
This whole thing is really getting frustrating.
post what you’ve got so far. make it as simple as possible showing what you’re trying to do,.
Has someone any idea. I’m so desperate right now. ;(
Few will deal with a messy patch. Fewer will deal with a patch that hasn’t been whittled down to *just the part that malfunctions.*
the process goes like this:
1:delete a few object s
2:make sure that something is malfunctioning
3: IF something is malfunctioning THEN go to one. ELSE post patch.
You can take a ton out of this patch and I assume it will still malfunction. do that and see what happens.
you’re not going to be able to use the p.bounds object with your particle generator unless your matrices are formatted correctly for the jit.p.* objects. as mentioned, take a look at the reference page to learn this formatting.
it expects 2D matrices, of size nX2, of at least 5 planes. the size of the first dim is the number of particles. the second row is the previous iteration values. the first plane is the particle id, and the second plane is the particle lifetime. the next 3 are position, xyz values.
all those things are needed if you want to use p.bounds.
alternatively, you could create your own bounds logic simply by testing if the position is outside a certain range, and if so, reversing it’s direction. this can be done with simple jit.op operators, or probably a better option, jit.gen.