***************************************************************************

    MIDI-Tools (MIDI-In** and MIDI-Out**) for
    BarsnPipes MOS version 1.3 an higher

    by © 2023 Alfred Faust

    ***************************************************************************

    
    Version 1.4 (02.03.2023)
    ------------------------

    The installation of the new MIDI-Tools is a bit  more  extensive,  but  only
    needs to be done once.

    First :

    These tools expecting a directory:

    BarsnPipes:support/toolenv

    Please create it, before you install these MIDI-Tools.

    A common way:

    - open a new CLI-window
    - give in:

      makedir BarsnPipes:support/toolenv

	Second:

    These tools require the new camdusbmidi.class, which comes with this archive.
    This  camdusbmidi.class  has  Antoine Dubourg (alias tcheko) in the meanwhile
    further  developed,   so   it   can   handle   the   so   called   Multiport-
    USB-MIDI-Interfaces without any restrictions.

    Please copy it to MOSSYS:Classes/USB.
    (I recommend, to make a backup of the previous camdusbmidi.class before.)

    A overall recomentation:

    After you have connected the USB-MIDI-Interface, look in

    Prefs->USB->Devices

    if your MIDI-Interface is bound correct to your computer. You should see a
    entry similar like this:


    Name			Speed 	State  		Class	Bindings

    USB MIDI 4i4o   Full	Running     Audio   camdusbmidi.class

    ############################################################################

    The **  above  in  the  title  is  the  number  for  the  USB-MIDI-line  (or
    USB-MIDI-port).

    These are found in the so called Multiport-USB-MIDI-Interfaces.

    For example:
    MIDIBOX 4x4 	(four MIDI-lines, each with IN and OUT)
    Ploytec 2x2 	(two MIDI-lines, each with IN and OUT)
    MIDIFACE 8x8    (eight MIDI-lines, each with IN and OUT)

    These Interfaces combine multiple USB-MIDI-Interfaces in one device.

    For each MIDI-line a separate MIDI-Tool is used.

    Like you may  know  already,  each  MIDI-Interface  has  it's  own  name  in
    BarsnPipes.

    Example for MIDIBOX 4x4:  (name in BarsnPipes: "USB MIDI 4i4o")
    ------------------------

    used MIDI-Tools:

    MIDI-In1  <--->  MIDI-Out1
    MIDI-In2  <--->  MIDI-Out2
    MIDI-In3  <--->  MIDI-Out3
    MIDI-In3  <--->  MIDI-Out3

    The  connection  you  choose  in  the  tools  by   clicking   on   the   "Set
    Connection"-gadget and choose from the PopUp-Menu:

    MIDI-In1 -> "USB MIDI 4i4o.01.in"          MIDI-Out1 -> "USB MIDI 4i4o.01.out"
    MIDI-In2 -> "USB MIDI 4i4o.02.in"          MIDI-Out2 -> "USB MIDI 4i4o.02.out"
    MIDI-In3 -> "USB MIDI 4i4o.03.in"          MIDI-Out3 -> "USB MIDI 4i4o.03.out"
    MIDI-In3 -> "USB MIDI 4i4o.04.in"          MIDI-Out3 -> "USB MIDI 4i4o.04.out"


    Immediately after you have choosen the connection, the tool saves the name in
    a toolenv-file, which is named smilar like the tool.

    MIDI-In1  -> toolenv/midi_in1
    MIDI-In2  -> toolenv/midi_in2
    MIDI-Out1 -> toolenv/midi_out1
    MIDI-Out2 -> toolenv/midi_out2

    ... and so on

    After you have set everything up, it is always good to save it as a song,  or
    if  you  want,  that  BarsnPipes starts evertime with this setup, as "Default
    Song".

    Each time a MIDI-Tool is loaded:

    - at startup (Default song is loaded)
    - when a stored song is loaded
    - when it is installed in the toolbox

    it looks in toolenv for a file with its name, load it - if  it  is  present,
    and trys to create the connection.

    If this doesn't work, the tool will try again when a MIDI-event reaches  the
    tool.

    If  this  fails  again,   the   USB-MIDI-interface   is   unfortunately   not
    USB-MIDI-standard  conform,  and doesn't work with the new camdusbmidi.class.
    That is not a failure of the camdusbmidi.class

    Have a lot of fun!

    Alfred Faust
    12.03.2023