Hi Ben,
very interesting project, thanks for sharing! I'm also working on a
(commercial) project with Fluidsynth on ARM hardware, but I'm using an
Allwinner A20 SOM board. I'm producing it commercially, because I'm
also developing the controller hardware (the instrument itself, with
all the keys etc). But the whole software stack will be released as
open-source. More details on http://www.midigurdy.com
Amazing that you get a good latency response with a stock raspbian
kernel. I'm using a preempt-rt enabled kernel with hand-optimized IRQ
priorities and that gives me a latency (from key press to start of
sound) of about 12-15ms, which is acceptable. But then again, my
system not only runs FluidSynth to produce the sound but also handles
all the sensor inputs, modellig of sensor values to MIDI events and
other stuff.
Have you made any measurements of the actual latency?
Cheers,
Marcus
2015-10-30 22:00 GMT+01:00 Ben Gonzales <b...@gonzos.net>:
> Hi all.
>
> I'm running my EWI-USB through a Raspberry-Pi 2 using FluidSynth. It was a
> challenging project, and it now works well.
>
> Here's the web page: http://projects.gonzos.net/ewi-pi/
>
> Interesting features:
>
> - I configure the running FluidSynth using a smartphone accessing the R-Pi
> via wifi (no need for a screen/keyboard/buttons)
> - The PHP code talks to FluidSynth using the telnet port 9800
> - The PHP code talks to the EWI using ALSA commands via a bash script
>
> Ben
>
> _______________________________________________
> fluid-dev mailing list
> fluid-dev@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/fluid-dev
_______________________________________________
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
