@ Ralf,
I have downloaded but not yet installed, so I am only answering
from my experience, and a conversation I had with Alfred.

Seeing a choice of ins or outs when choosing your output port
is a good idea. That allows you to play the output of B&P into the
input of another application.. (MIDI transfer in real-time)

We used to transfer from DeluxeMusic to Bars&Pipes the same way.

If that was enough to answer your question, stop reading now.
If you want to be thoroughly confused by a sleep-deprived
programmer, read on a bit more:

All the input and output names being labeled with .in.xx
and .out.xx is actually nonsense. It helps you to know which
way to think of each cluster (the CAMD name for one of these
"message meeting places"), but in reality, any cluster in use
has both inputs and outputs going on.. One (or more) links are
pushing midi events into the cluster, those are all merged together,
and the results are copied to each link that is reading from that
cluster. If any cluster has only readers or writers, (not both),
then CAMD is smart enough to not bother with it at all.

It is perfectly common and practical to create your own names for
internal "meeting points" within CAMD. There is no need ( or reason)
to include an "in" or an "out" in the name. Sure, it's common
to see drivers name things that way, but that's really only a
convenience for the user. As suggested by the CAMD docs, the CLIST
cluster requester that I have uploaded allows you to create a new
cluster just by typing in a name to call it.

I am considering an update to CAMD beyond it's original spec, that
would allow particular port names to be "aliased" into something
more useful. Now that I have ten MIDI OUT jacks spread across
two devices, as well as nine MIDI IN jacks, and one each that are
assigned permanently to control deck in and out, I'm realizing
that I don't need or want them named by interface, direction and
number. It would be far easier to name them according to whatever
I have connected to those ports. instead of remembering that the
D5 input is connected to "EDIROL UM-880.out.4", I could just label
it "D5" if that's what I want, or even "Horns", since that is what
I use that synth most often for.. or maybe "Gen MIDI".. well, you
get the idea.

CAMD is more than just a bunch of MIDI drivers, it's a patchbay,
MIDI merger, and I hope to soon add tools for event filtering,
transposing, and other utility functions. It's a common language
for Big MIDI apps and little MIDI tools to co-exist..

I'm tired.. need to sleep.

Lyle

_________________
question=(2b||!(2b))

Hi Ralf,

The in and out clusters are visible for the case, you want to connect for example the MIDI-Out to the incluster of another MIDI-program.

Attention! Don't try to connect MIDI-Out to a incluster, which is used by a MIDI-In tool. This would end in a infinite loop.

For multiple Out, you must use the depending MIDI-Out tool.

example:
you have one 3 port USB-MIDI-Interface.

Install in the toolbox from tool/MIDITools/Unit1

MIDI-In1_1 for port1
MIDI-In1_2 for port2
MIDI-In1_3 for port3

MIDI-Out1_1 for port1
MIDI-Out1_2 for port2
MIDI-Out1_3 for port3

and use the depending tool for the depending port.

Choose the connections and have fun. If you want to use the different ports for input simultaneous, you must choose from the Preferences menu "Multiple Inputs", and the depending input MIDI-channel on which the input devices are sending.

This should work (Lyle had confirmed, that it works)

The MIDI-Tools are NOT beta !

Kindly
Alfred

Well, however I configure it, it doesn't work.

1. The name of the USB-interface UNO is so long so I can't see if it's in or out in the MIDI-IN/Out tool requester.
2. If I choose Midi-out 1 for the prokeys and Midi-out 2 for the UNO, one of them recieves but not both.
3. If i choose prokeys in the Midi-in, have UNO as Midi-out, and strike a key on the prokeys, the Reaper appears (that worked with the old version, and the latest camd).


Ralf

_________________
Ralf.
Amigaone G4 XE / AOs4 beta update4
Post+1

Quote:

Hi Xenic, ... I don't know your name I'm very sorry, that you have had such a trouble with BarsnPipes. But you show me, whats going on, if a curious men, who never ever had worked with BarsnPipes before, want to try out BarsnPipes.

My name is Jeff and there is no need to apologize. You are helping the Amiga community by working on Barsnpipes. My criticism is intended to help improve the program and not to offend you. Maybe I should choose my words more carefully.

Quote:

The installer don't check the version of the drivers ... thats correct, but this is not a fault, because the archive contains the latest (most recent - the best) available drivers. It's right ... no manual installation instructions are available ... I'll change this ...

I frequently D/L programs and don't get around to trying them for weeks or months. It's possible, though unlikely, that some other program would install more recent files before I got around to testing Barsnpipes. Version checking for all files would be more "user friendly". Including manual installation instructions will be helpful.

Quote:

BarsnPipes (like you have seen) has many many gadgets. The most of them are rendered with small pics. All these pics are loaded from outside from the GUI-directory, which is (since ver.0.6) a lha-crunched archive. The GUI-dir contains 475(!) small pictures files. The harddisk is working any seconds to load all the files. So I decided (to shorten this loading time dramatically) to make this deal with the lha-archive.

I can believe this would make a significant difference on a classic Amiga but I would think the hard-disk load time would be sasisfactory for OS4/PPC. Maybe the program could check for a gui directory in the Barsnpipes directory before attempted the gui.lha dearchivie method. It's a minor issue. The only reason I don't like it is because I keep all non-system commands on a different partition and don't like being forced to put "lha" in my C: directory. I find it easier to update OS4 when I don't have a lot of external commands and files located on my system partition. Maybe you could change the C:lha command to "lha" so that it will work if lha is located anywhere in the command path.

I suppose my opinions are less important than people who can actually use the program. Maybe I can locate some cheap used MIDI device (keyboard) that I can use with Barsnpipes. For now I'll just encourage you to keep up the good work.

_________________
X1000 with 2GB memory & OS4.1FE