Thanks to everyone for the help.<br><br>Yours, <br>Eduardo.<br><br><div class="gmail_quote">El 18 de abril de 2012 09:30, <span dir="ltr"><<a href="mailto:fluxus-request@lists.pawfal.org">fluxus-request@lists.pawfal.org</a>></span> escribió:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Fluxus mailing list submissions to<br>
<a href="mailto:fluxus@lists.pawfal.org">fluxus@lists.pawfal.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.pawfal.org/listinfo.cgi/fluxus-pawfal.org" target="_blank">http://lists.pawfal.org/listinfo.cgi/fluxus-pawfal.org</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:fluxus-request@lists.pawfal.org">fluxus-request@lists.pawfal.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:fluxus-owner@lists.pawfal.org">fluxus-owner@lists.pawfal.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Fluxus digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Help to connect two MIDI sources into FLUXUS (Eduardo Obieta)<br>
2. Re: Help to connect two MIDI sources into FLUXUS (gabor papp)<br>
3. Re: Help to connect two MIDI sources into FLUXUS (Kassen)<br>
4. Re: Help to connect two MIDI sources into FLUXUS (Jon Stutters)<br>
5. Re: connecting to Jack (David Griffiths)<br>
6. Re: Help to connect two MIDI sources into FLUXUS (Ted)<br>
7. Re: connecting to Jack (Kassen)<br>
8. Re: Help to connect two MIDI sources into FLUXUS<br>
(Arq. Eduardo H. Obieta)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 18 Apr 2012 01:59:16 -0500<br>
From: Eduardo Obieta <<a href="mailto:eduardobieta@gmail.com">eduardobieta@gmail.com</a>><br>
To: <a href="mailto:fluxus@lists.pawfal.org">fluxus@lists.pawfal.org</a><br>
Subject: [Fluxus] Help to connect two MIDI sources into FLUXUS<br>
Message-ID:<br>
<CADDcuCm11g5w+TpKquompSaFCT7h3RvNZoUJgXMg7qdyAA=<a href="mailto:yPw@mail.gmail.com">yPw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hi everyone<br>
<br>
Today I try to connect two midi controllers to fluxus, when I put<br>
<br>
----------------------------------------------<br>
;CODE<br>
(clear)<br>
(display (midi-info))<br>
;the post prints the two controllers I have connected<br>
"((0. LAUNCHPAD) (1. KNOB/SLIDER))"<br>
<br>
;after this I put<br>
(midi-init 0)<br>
(midi-init 1) ; to initialize the ports<br>
<br>
;and try to take the MIDI values and print<br>
(define (midimsg)<br>
(display (midi-peek))(newline)<br>
)<br>
(every-frame (midimsg))<br>
----------------------------------------------<br>
<br>
When I move the faders of controller in port 1 nothing happens, but the<br>
controller in port 0 prints me all the values...<br>
<br>
Now, when I connect first the KORG NANO (1. KNOB/SLIDER) and after that I<br>
connect the LAUNCHPAD, the values of the launchpad do not prints, but the<br>
other ones from the KORG prints OK<br>
<br>
Hope you can help me or tell me where is the error.<br>
<br>
<br>
Best Regards.<br>
_________________________<br>
*Eduardo H Obieta*<br>
<br>
<a href="http://eduardohobieta.mx/" target="_blank">eduardohobieta.mx/</a> <<a href="http://eduardohobieta.mx/eng/index.html" target="_blank">http://eduardohobieta.mx/eng/index.html</a>><br>
<a href="http://laad.com.mx/" target="_blank">http://laad.com.mx/</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.pawfal.org/pipermail/fluxus-pawfal.org/attachments/20120418/f513737a/attachment-0001.htm" target="_blank">http://lists.pawfal.org/pipermail/fluxus-pawfal.org/attachments/20120418/f513737a/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 18 Apr 2012 09:57:07 +0200 (CEST)<br>
From: gabor papp <<a href="mailto:gabor.lists@mndl.hu">gabor.lists@mndl.hu</a>><br>
To: Eduardo Obieta <<a href="mailto:eduardobieta@gmail.com">eduardobieta@gmail.com</a>><br>
Cc: <a href="mailto:fluxus@lists.pawfal.org">fluxus@lists.pawfal.org</a><br>
Subject: Re: [Fluxus] Help to connect two MIDI sources into FLUXUS<br>
Message-ID:<br>
<<a href="mailto:alpine.OSX.2.00.1204180953400.178@catv-80-99-4-46.catv.broadband.hu">alpine.OSX.2.00.1204180953400.178@catv-80-99-4-46.catv.broadband.hu</a>><br>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed<br>
<br>
hi Eduardo,<br>
<br>
> Today I try to connect two midi controllers to fluxus, when I put<br>
the current fluxus-midi module only allows one midi controller<br>
at a time unfortunately.<br>
multiple midi controller support is on the todo list.<br>
<br>
best,<br>
gabor<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 18 Apr 2012 12:53:16 +0200<br>
From: Kassen <<a href="mailto:signal.automatique@gmail.com">signal.automatique@gmail.com</a>><br>
To: gabor papp <<a href="mailto:gabor.lists@mndl.hu">gabor.lists@mndl.hu</a>><br>
Cc: Eduardo Obieta <<a href="mailto:eduardobieta@gmail.com">eduardobieta@gmail.com</a>>, <a href="mailto:fluxus@lists.pawfal.org">fluxus@lists.pawfal.org</a><br>
Subject: Re: [Fluxus] Help to connect two MIDI sources into FLUXUS<br>
Message-ID: <<a href="mailto:20120418105313.GA1704@gmail.com">20120418105313.GA1704@gmail.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On Wed, Apr 18, 2012 at 09:57:07AM +0200, gabor papp wrote:<br>
> hi Eduardo,<br>
><br>
> >Today I try to connect two midi controllers to fluxus, when I put<br>
> the current fluxus-midi module only allows one midi controller at a<br>
> time unfortunately.<br>
> multiple midi controller support is on the todo list.<br>
<br>
In the meantime; I think many modern controlers with USB plugs will<br>
act as both a interface to the computer (featuring din plugs) and as a<br>
controller themselves. With some luck yours will be able to merge the<br>
two, pluging controler A's din output into controller's B's MIDI-in<br>
and B's usb into the computer.<br>
<br>
I don't know the exact models used here but consult your manual.<br>
<br>
Hope you're in luck, if that fails you can run a software-based merger<br>
that would present a single virtual device to Fluxus for you to open;<br>
I don't have much experience with that personally, somebody else might<br>
have a pointer or you could consult your favourite search engine.<br>
<br>
Yours,<br>
Kas.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 18 Apr 2012 12:23:24 +0100<br>
From: Jon Stutters <<a href="mailto:jstutters@jeremah.co.uk">jstutters@jeremah.co.uk</a>><br>
To: <a href="mailto:fluxus@lists.pawfal.org">fluxus@lists.pawfal.org</a><br>
Subject: Re: [Fluxus] Help to connect two MIDI sources into FLUXUS<br>
Message-ID: <<a href="mailto:14993206-1427-4CAA-BD1E-81795A210D76@jeremah.co.uk">14993206-1427-4CAA-BD1E-81795A210D76@jeremah.co.uk</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On 18 Apr 2012, at 11:53, Kassen wrote:<br>
> In the meantime; I think many modern controlers with USB plugs will<br>
> act as both a interface to the computer (featuring din plugs) and as a<br>
> controller themselves. With some luck yours will be able to merge the<br>
> two, pluging controler A's din output into controller's B's MIDI-in<br>
> and B's usb into the computer.<br>
><br>
> I don't know the exact models used here but consult your manual.<br>
><br>
> Hope you're in luck, if that fails you can run a software-based merger<br>
> that would present a single virtual device to Fluxus for you to open;<br>
> I don't have much experience with that personally, somebody else might<br>
> have a pointer or you could consult your favourite search engine.<br>
<br>
I wrote a small utility a while ago that takes the input from multiple MIDI devices and converts it to OSC messages (it will do output as well). Might be useful as a temporary fix until fluxus gets multiple MIDI device support.<br>
<br>
<a href="https://github.com/jstutters/MidiOSC" target="_blank">https://github.com/jstutters/MidiOSC</a><br>
<br>
Cheers,<br>
Jonny<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 18 Apr 2012 12:35:42 +0100<br>
From: David Griffiths <<a href="mailto:dave@pawfal.org">dave@pawfal.org</a>><br>
To: Kassen <<a href="mailto:signal.automatique@gmail.com">signal.automatique@gmail.com</a>><br>
Cc: Fluxus <<a href="mailto:fluxus@lists.pawfal.org">fluxus@lists.pawfal.org</a>><br>
Subject: Re: [Fluxus] connecting to Jack<br>
Message-ID: <<a href="mailto:4F8EA70E.1050402@pawfal.org">4F8EA70E.1050402@pawfal.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Hi Kassen,<br>
<br>
Make it work for jackd2 I reckon... you can always pass the ports on<br>
commandline if you want to still use jack1.<br>
<br>
cheers,<br>
<br>
dave<br>
<br>
On 04/17/2012 03:31 PM, Kassen wrote:<br>
> Dear list,<br>
><br>
> I'm trying to fix Fluxa in that I want Fluxa to connect automatically<br>
> to Jackd on a new-ish Ubuntu install like it does on my 10:10 install.<br>
> For this I already updated the depreciated jack_client_new to<br>
> jack_client_open but that didn't help.<br>
><br>
> Then I noticed that the actual error in connecting refered to a<br>
> unknown port. I traced what I believe is the core of the matter to<br>
> this part of the code in (fluxa's) main.cpp;<br>
><br>
> ----------------------8<-------------------<br>
> #ifdef __APPLE__<br>
> string leftport("system:playback_1");<br>
> string rightport("system:playback_2");<br>
> #else<br>
> string leftport("alsa_pcm:playback_1");<br>
> string rightport("alsa_pcm:playback_2");<br>
> #endif<br>
><br>
> ----------------------8<-------------------<br>
><br>
> As I understand the info I was able to find online this isn't a<br>
> difference between Apple and Linux as much as it is a difference<br>
> between Jackd1 (using alsa_pcm) and Jackd2 (using system). Even that<br>
> isn't entirely correct; on my own Linux computer (using jackd2) the<br>
> alsa_pcm parameter is accepted (I get sound) even though jack_lsp<br>
> lists the ports in question as being called "system....".<br>
><br>
> Clearly the above condition doesn't completely reflect reality and the<br>
> check may need to be for the presence of Jackd1 or 2, unless jackd1 is<br>
> also switching to calling it "system". I think it might, because jack<br>
> can also connect to cards through means other than alsa, for example<br>
> the firewire series of drivers.<br>
><br>
> Personally, BTW, I prefer jackd2 because unlike 1 jackd2 won't<br>
> disconnect clients over a few missed deadlines. I think that makes it<br>
> a more pleasant pick for experimental live performances where things<br>
> can and will occasionally go wrong.<br>
><br>
> I think this will affect Fluxus too, not just Fluxa, so we should<br>
> probably talk about what would be the best sollution here.<br>
> Particularly I'm curious whether anything would go wrong if we'd<br>
> simply just refer to "system".<br>
><br>
> Yours,<br>
> Kas.<br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 18 Apr 2012 13:38:48 +0200<br>
From: Ted <<a href="mailto:tedr56@gmail.com">tedr56@gmail.com</a>><br>
To: Jon Stutters <<a href="mailto:jstutters@jeremah.co.uk">jstutters@jeremah.co.uk</a>><br>
Cc: <a href="mailto:fluxus@lists.pawfal.org">fluxus@lists.pawfal.org</a><br>
Subject: Re: [Fluxus] Help to connect two MIDI sources into FLUXUS<br>
Message-ID: <1334749128.3044.2.camel@VJ-Workstation3><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Le mercredi 18 avril 2012 ? 12:23 +0100, Jon Stutters a ?crit :<br>
<br>
> On 18 Apr 2012, at 11:53, Kassen wrote:<br>
> > In the meantime; I think many modern controlers with USB plugs will<br>
> > act as both a interface to the computer (featuring din plugs) and as a<br>
> > controller themselves. With some luck yours will be able to merge the<br>
> > two, pluging controler A's din output into controller's B's MIDI-in<br>
> > and B's usb into the computer.<br>
> ><br>
> > I don't know the exact models used here but consult your manual.<br>
> ><br>
> > Hope you're in luck, if that fails you can run a software-based merger<br>
> > that would present a single virtual device to Fluxus for you to open;<br>
> > I don't have much experience with that personally, somebody else might<br>
> > have a pointer or you could consult your favourite search engine.<br>
<br>
<br>
For my part, on linux, I connect Fluxus to one midi device, then use<br>
Jack Connection panel (or Patchage) to connect (or de-connect) the<br>
others to the fluxus port.<br>
I don't know any equivalent for OSX users, sorry.<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.pawfal.org/pipermail/fluxus-pawfal.org/attachments/20120418/04f63890/attachment-0001.htm" target="_blank">http://lists.pawfal.org/pipermail/fluxus-pawfal.org/attachments/20120418/04f63890/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Wed, 18 Apr 2012 13:48:09 +0200<br>
From: Kassen <<a href="mailto:signal.automatique@gmail.com">signal.automatique@gmail.com</a>><br>
To: David Griffiths <<a href="mailto:dave@pawfal.org">dave@pawfal.org</a>><br>
Cc: Fluxus <<a href="mailto:fluxus@lists.pawfal.org">fluxus@lists.pawfal.org</a>><br>
Subject: Re: [Fluxus] connecting to Jack<br>
Message-ID: <<a href="mailto:20120418114806.GC1704@gmail.com">20120418114806.GC1704@gmail.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On Wed, Apr 18, 2012 at 12:35:42PM +0100, David Griffiths wrote:<br>
> Hi Kassen,<br>
><br>
> Make it work for jackd2 I reckon... you can always pass the ports on<br>
> commandline if you want to still use jack1.<br>
><br>
<br>
Agreed. Then the whole ifdef thing can go out, I think.<br>
The other spot would be in the FLuxus example for the audio-in<br>
connection, I think.<br>
<br>
If I understand it all correctly then jackd2 gave the alsa_pcm name<br>
some grace period, but unlike the function for creating ports didn't<br>
note that there was a actual error, not sure I find that correct,<br>
though I do agree with the more general "system" name.<br>
<br>
Yours,<br>
Kas.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Wed, 18 Apr 2012 09:30:19 -0500<br>
From: "Arq. Eduardo H. Obieta" <<a href="mailto:arquitectura@laad.com.mx">arquitectura@laad.com.mx</a>><br>
To: Kassen <<a href="mailto:signal.automatique@gmail.com">signal.automatique@gmail.com</a>><br>
Cc: <a href="mailto:fluxus@lists.pawfal.org">fluxus@lists.pawfal.org</a><br>
Subject: Re: [Fluxus] Help to connect two MIDI sources into FLUXUS<br>
Message-ID:<br>
<CADDcuC=<a href="mailto:onCoVYwUm7pFnxE8zvKXGo1WVckRM8VbWN8tzsJLing@mail.gmail.com">onCoVYwUm7pFnxE8zvKXGo1WVckRM8VbWN8tzsJLing@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
El 18 de abril de 2012 05:53, Kassen <<a href="mailto:signal.automatique@gmail.com">signal.automatique@gmail.com</a>>escribi?:<br>
<br>
> On Wed, Apr 18, 2012 at 09:57:07AM +0200, gabor papp wrote:<br>
> > hi Eduardo,<br>
> ><br>
> > >Today I try to connect two midi controllers to fluxus, when I put<br>
> > the current fluxus-midi module only allows one midi controller at a<br>
> > time unfortunately.<br>
> > multiple midi controller support is on the todo list.<br>
><br>
> In the meantime; I think many modern controlers with USB plugs will<br>
> act as both a interface to the computer (featuring din plugs) and as a<br>
> controller themselves. With some luck yours will be able to merge the<br>
> two, pluging controler A's din output into controller's B's MIDI-in<br>
> and B's usb into the computer.<br>
><br>
> I don't know the exact models used here but consult your manual.<br>
><br>
> Hope you're in luck, if that fails you can run a software-based merger<br>
> that would present a single virtual device to Fluxus for you to open;<br>
> I don't have much experience with that personally, somebody else might<br>
> have a pointer or you could consult your favourite search engine.<br>
><br>
> Yours,<br>
> Kas.<br>
><br>
><br>
Thanks to both,<br>
<br>
I will try to merge both controllers.<br>
<br>
Best wishes,<br>
Eduardo.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.pawfal.org/pipermail/fluxus-pawfal.org/attachments/20120418/119dfcdc/attachment.htm" target="_blank">http://lists.pawfal.org/pipermail/fluxus-pawfal.org/attachments/20120418/119dfcdc/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Fluxus mailing list<br>
<a href="mailto:Fluxus@lists.pawfal.org">Fluxus@lists.pawfal.org</a><br>
<a href="http://lists.pawfal.org/listinfo.cgi/fluxus-pawfal.org" target="_blank">http://lists.pawfal.org/listinfo.cgi/fluxus-pawfal.org</a><br>
<br>
<br>
End of Fluxus Digest, Vol 84, Issue 5<br>
*************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br>Arq. Eduardo H. Obieta<br><br><a href="mailto:arquitectura@laad.com.mx">arquitectura@laad.com.mx</a><br><a href="http://www.laad.com.mx">www.laad.com.mx</a><br>cel. 55 40387218<br>