Hi All,

I am working on a project which need multiple .wav samples to be played at the same time.
They are activated via buttons, hundred of them.

At the moment I'm working on a solution using Raspberry pi, pduino, arduino and multiplexer, but was wondering if anyone would have a better solution.

Maybe midi would work, but seems quite complicated to setup.

At the moment, I've connected everything without multiplexer and it's working, but I'm a bit afraid of the complexity with multiplexer.

Any advice would be more than welcome.

Best,

Pi.

By the way, When I'm saying everything is connected at the moment, I'm speaking of 4 buttons, an arduino, a raspberry pi. 4 samples are well played.

Now , need to connect 100 buttons ...

I've no idea how to use multiplexers inside Pduino, but having 100 buttons could be a bit of an overkill. Are you gonna build such a controller yourself? This means, programming it, designing the circuit, print the circuit board (unless you use a perforated one), solder it etc.
Why not use a few buttons, say as many as the samples you want to trigger simultaneously (at most 10? you don't have more fingers than that...) and use an extra button or two to change between scenes? More or less like the Korg nanokontrol does. Or you could have ten buttons for simultaneous triggering and another ten for scene change (10 * 10 = 100)...you could do this with one multiplexer with a custom firmware.

Hi Alexandros, I was thinking to use you patch instead of pduino, as it seems to work quite well.
By buttons, i was simply saying activator. In reality, it's not button activated by hand, but moving objects which could simultaneously activate 100 samples.

I am just wondering if pure data on a raspberry pi will handle 100 signals at the same time.

Not sure about RPI's capabilities (I have a beagleboard and it can do quite some stuff, but still limited).
So, if you're gonna trigger everything with one push, you can do that in Pd, no need for multyplexing whatsoever. To check how much CPU you're using, when running your patch execute 'top' in a terminal (just type top and hit return), it will show you how much CPU is being used by which program.

Thanks for your answer. To check how much CPU is being used will be very useful.

Regarding execution of triggers, the thing is they could be activated randomly as well, from one at a time to 100.

Ok , I thnik I am not clear enough , sorry for that : imagine 100 tilt sensors running all at the same time. Depending on how many sensors are hit, similar quantity of samples is activated, one for each sensor.

I will seach on my side and keep you updated. Many thanks for your help.