Forum

Arrrggg --- you mean I needn't have bothered trying to build my own system and could have just used 1.4.8 all along? Bummer.

I was not able to run from within the app package --- and when I looked inside it, not only was the alias wrong, but the resources subfolder was empty.


So I was running it from the command line (although without the -noauto).


I just looked inside the 1.4.8-testing and I see there is indeed an osc_output plugin.

I would really appreciate it if someone could feed me the exact steps to just create a fresh blank setup that just has the osc in it.

Finally, I noticed as I was looking at the OSC output through Max, nothing seems to get generated if I slide my finger on the ribbon. I didn't try the breath control either. How are those transducers supposed to come through OSC?

By the way, thanks for the continued responses this afternoon, really appreciated them and very pleased to have this up and running....

Thank you ---- I will try this later tonight --- very excited to now be close to having an environment that I can completely control from Max.

Again, I appreciate the help.

@dhjdhj
You're welcome. I'm really happy you've got your setup connected.

Hm, what is this "alpha keyboard 1 hey" good for?
Just tried the following with my Tau, worked out of the box:

osc output create

alpha manager create

plumber hey tau keyboard 1 to osc output 1 connect

Well, I'm still struggling with getting an empty setup to work but I've just left it with my existing setup for now and I have the OSC stuff working well.

The format of the incoming OSC seems a bit funky (there's no key information in the message when you release a note) so I ended up with a bit of a hacks patcher in Max to handle it. I wonder if this is going to be changed.

But at this point I'm able to extract info, use Max to create scale definitions (e.g. I have patchers to setup chromatic scales, major or minor, guitar tuning) and then feed info into my Live Rig toolbox. Works very nicely.

Yeah, I knew the 5 (in your example) was the event stream but I was getting bogged down when trying to track them that way because the [coll] object generates no output if an item is not found, which is a pain....I kept coming up with hacks none of which I liked.

I saw a graphic of your Max patch somewhere but I didn't notice a version I could download. Where did you post it?

Skimming through the latest messages, I just want to clarify something about Belcanto. The commands you give it are based around a conversation model, it might serve you well to read this introduction: http://www.eigenlabs.com/wiki/1.3/The_Belcanto_Introduction/

The following commands are not supposed to work:
alpha keyboard 1 hey
alpha keyboard 1 to osc output 1
connect

Since after 'alpha keyboard 1 hey', the alpha keyboard 1 agent is waiting for a sentence, in which connect will be the verb. However, the alpha keyboard 1 agent doesn't understand that verb, the plumber agent does instead.

So what exactly is the command sequence to send to a blank setup?

I have MaxMSP working beautifully now with the raw OSC but I am still letting the Eigenharp load my default guitar profile although of course that information is just ignored.

I now have some basic Eigenharp control patchers that get loaded along with other keyboard routing patchers and so my Alpha is now integrating nicely with the rest of my environment......very exciting (at least for me).


----------
The following commands are not supposed to work

Perhaps dhjdhj's problem is that the interpreter does not connect to the EigenCommander? (It's easy to overlook, in this case you see a red bulb in the lower right). I always have this behaviour if I choose the blank setup as default - presumably it's so "blank" that it doesn't even contain the interpreter? If you load an arbitrary non-blank setup first and then go to the blank one it usually works.

@barnone I implemented my basic Max patcher a little differently and avoided that problem with empty string. I'm still using a single regexp to detect that empty string but may replace it with a simple max external if efficiency becomes an issue.

Here are some top-down pictures of what I did.

EigenStrings The Eigen.Alpha.In object produces MIDI NoteOn/NoteOff messages (same as midiin) and pitchbend which can be fed into either a VST or an external MIDI instrument. The GenericVST is part of my Live Keyboard Rig Manager (see my blog here for more info on that library)


Eigen.Alpha.In This accepts nicely cleaned up KeyDown/KeyUp events, converts them to Row/Col number format (not sure I'm going to keep that, but it has some uses) and then the row/col info is converted into MIDI note numbers for a guitar-tuning layout.

Eigen.OSCInput Here I extract the raw OSC packets and I'm using a regex to feed me either a valid key number or 0 if the empty string is found.

The data is sent into the Eigen.OSCProcessor

Eigen.OSCProcessor Here, I'm basically keeping track of what keys are currently down by using the coll object using the event stream number as the index and the key number as the value. This patcher ensures that only a single keydown event is generated no matter how long a key is held.

So far, it has been totally glitchless so I'm optimistic about the approach.
My next step will be to properly integrate the continuous data for individual notes. It will be pretty trivial to generate polyphonic aftertouch events by finding the associated note number for the current stream and packing that with the pressure value. I'm not sure yet how I'm going to package the left-right data.