On Fri, 27 Feb 2015, R.L. Horn wrote:
> It's something of a PITA, but it's better than a stab in the dark
ahahaha, it is really hard for an Italian like me understand your slang...
fortunately there is http://www.urbandictionary.com that help me in such
situations :)
Anyway all is clear.For n
On Fri, 27 Feb 2015, Gino Latino wrote:
On the roof I'm thinking that using the port names implies that you must
know the devices name, but what if i want to connect an unknown device?
You have to muck about in /proc/asound a bit.
For example, assuming you know that card 1 has MIDI devices as
Thanks to R.L.Horn, i will take time to think about your good idea.
On the roof I'm thinking that using the port names implies that you must know
the devices name, but what if i want to connect an unknown device?
thanks again
Max
ginola...@gmail.com
Il giorno 27/feb/2015, alle o
First of all thanks to you all for the interest.
At this point I think I need to explain my project.
I'm working on a live and mobile midi expander using raspberry PI as hardware
and linux as SO.
I thought that fluidsynth could be a fast and good engine due to low latency
and the use of soundfon
On Thu, 26 Feb 2015, Peter Billam wrote:
I agree with that. Except I'd write it in Lua:
Oh, you kids and your crazy languages. :)
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
R.L. Horn wrote:
> gino latino wrote:
> > does someone know any "advanced" command line midi router?
> but the ALSA sequencer API is so straightforward that I
> quickly concluded that it's easier to write one-offs in C.
> especially for unusual and/or complex event mangling
I agree with that. Exc
