[Fluxus] Fluxus Digest, Vol 84, Issue 5

Arq. Eduardo H. Obieta arquitectura at laad.com.mx
Wed Apr 18 07:44:53 PDT 2012


Thanks to everyone for the help.

Yours,
Eduardo.

El 18 de abril de 2012 09:30, <fluxus-request at lists.pawfal.org> escribió:

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



-- 
Arq. Eduardo H. Obieta

arquitectura at laad.com.mx
www.laad.com.mx
cel. 55 40387218
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pawfal.org/pipermail/fluxus-pawfal.org/attachments/20120418/72fa717f/attachment-0001.htm>


More information about the Fluxus mailing list