MIDI Setup


    May 03 2006 | 7:29 pm
    ...or upset.;-) I'm new here, but been fooling around with max for a while, so i HAVE tried to solve this - obiviously without sucess. I made a lo-tech user interface for bcf2000 using ctlin/out and with max/msp 4.5.7 my patch can't seem to recognize "bcf2000 out 1" as default. This is very annoying. It seems the AU DLS is first priority. I wonder if there is a way to set "bcf2000 out 1" to default for ALL ctlout objects, without writing, for instance, "ctlout b 1 1", but just "ctlout 1 1" Please help.
    For users of bcf2000, heres my share to this forum: (and thanks!)

    • May 04 2006 | 9:40 am
      Added that functionality..., and to make the spaghetti mangeable, added some sauce...
      The needed info is inside the ctlout.help in a subpatcher called outport.help
      But don't assume a different user is using the same port names as you do... To come around that, look at my St.MidiInport/St.MidiOutport abstractions you could ask for just a part of the name like [St.MidiInport bfc]
      Stefan
      --
      [][] [][][] [][] [][][] [][][][][][][][][][][][][][][]
      Stefan Tiedje Klanggestalter Electronic Composition & Improvisation
      /~~~~~ \ /|() ()| ))))) )| | |( \ /// _/)/ ))))) ___/ ///
      -------------------------x---- --_____-----------|----------- --(_|_ ----|-----|-----()---- -- _|_)----|-----()----------- ----------()------------x-----
      14, Av. Pr. Franklin Roosevelt, 94320 Thiais, France Phone at CCMIX +33-1-57 42 91 09
    • May 04 2006 | 10:44 am
      > > Added that functionality..., and to make the spaghetti mangeable, added > some sauce...
      Is it bolognese sauce?
      > The needed info is inside the ctlout.help in a subpatcher called > outport.help
      Looked in the subpatch, but the specific function i'm looking for isn't described there. If I rephrase the question: Why will not the only one midi-in connection chosen in the midi-setup work as a implicit default? (I have, of course, un-checked the inputs i'm not using, and set the correct input offset to 16) If there is a possibility to rule out the other inputs, and get max to understand that i'm using only one midi input, the spagetti, with the sauce, will be unnecessary. (Even though it's appetizing) The strange thing is that this worked out fine in the trialversions of 4.2 and 4.3. I know it may seem a unnecessary thing, but the patch i'm currently working in is huge and it will take hours or days to fix this - and theres allready plenty of spagetti...
      BUT never the less: THANKS a lot for your help, AND the sauce!
      all the best
      eyvind gulbrandsen
    • May 04 2006 | 11:18 am
      OOPS!!! I mean MIDI out of course!!! Its for making my bcf2000 motorized! I came to write midi in when refering to the midi setup prefs. I want it to understand only one midi OUT... Sorry for this mess...
    • May 08 2006 | 9:45 am
      Eyvind Gulbrandsen wrote: > Is it bolognese sauce?
      No, I am vegetarian, its sauce napoli with a parisienne touch...
      > Why will not the only one midi-in connection chosen in the midi-setup > work as a implicit default?
      Are you refering to the OS X Midisetup or the Max Midisetup? This is not clear, for me the Max Midisetup works, though I never use it. This will only work on your computer. To make the patch more universal and distributable you'd need to specify the outport...
      > If there is a possibility to rule out the other inputs, and get max > to understand that i'm using only one midi input, the spagetti, with > the sauce, will be unnecessary. (Even though it's appetizing)
      The Max Midisetup should be able to do it... (Switch off those you don't want) I didn't use it since OS 9 days though and I would not recommend it. In my setups ports are changing all the time, to adjust each time the Midisetup is not convenient. I prefer to patch solid...
      > I know it may seem a unnecessary thing, but the patch i'm currently > working in is huge and it will take hours or days to fix this - and > theres allready plenty of spagetti...
      You can avoid the pasta meal with send/receives... create your own ctlout abstraction, call it bfcout for example. There you just add a receive object [r bfcport]. Then open your patch in a texteditor (you need to save it in textformat). replace all ctlout by bfcout and place a single [s bfcport] into your main patch, which will set all ctlouts to the correct port. This would work on any other computer setup as well.
      Even the spaghetti solution is done pretty fast with nathanaels MaxToolbox (otherwise I would not have sent the spaghetti with sauce my time is limited as well ;-)
      I've eaten all the spaghetti, bon appetit:
      Stefan
      save as bfcout.pat:
      And the patch without spaghetti:
      --
      [][] [][][] [][] [][][] [][][][][][][][][][][][][][][]
      Stefan Tiedje Klanggestalter Electronic Composition & Improvisation
      /~~~~~ \ /|() ()| ))))) )| | |( \ /// _/)/ ))))) ___/ ///
      -------------------------x---- --_____-----------|----------- --(_|_ ----|-----|-----()---- -- _|_)----|-----()----------- ----------()------------x-----
      14, Av. Pr. Franklin Roosevelt, 94320 Thiais, France Phone at CCMIX +33-1-57 42 91 09
    • May 08 2006 | 9:54 am
      That was both constructive and informative! (even without being patronizing as some here tend to, when it comes to rookie questions...)! Thanks a bunch! And thanks for the maxtool tips - I will check it out.
      Have a grand day!
      all the best eyvind