thetechnobear / eigenharp Goto Github PK

Not using this is fine for Pico, but for Alpha/Tau setups, placing selector keys at the very top of the keyboard is cumbersome to use.

Recommend placing the statement below in createkeygroupoutput.bc, linkrig.bc, and linkmidirig.bc:

%VAR1% hey keygroup output %VAR2% mode key row end relative to %VAR3% set

The value passed to %VAR3% would be 'on' or 'off'.

There doesn't appear to be a way to isolate this statement and place in conf just for Alpha/Tau.

Hi All...

Still working on Controlling the NEURONVS...
I'm creating a link latch to a rig for this ... stuck on the above (title)

cheers

Basically, there are a number of areas where the only way to select items in a setup, are thru the EigenBrowser.
Some like convolver, can be automatically selected if EigenBrowser is running, so thats 'ok'

But others e.g. AU plugins cannot, or realistically dont have a sensible default.
The 'issue' is that if you have a config that loads 3 AU rigs, and 2 Samplers, each needs to use the EigenBrowser,
so you cannot just 'fire' the belcanto at EigenD, as if you do, you wont have time to select (its not a synchronous call)

proposed solution:
At the end of the setup, have it step thru all required EigenBrowser selections:
saying something like:
Select convolver for rig 1 in EigenBrowser, press enter when done.
Select plugin for AU rig 1 in EigenBrowser, press enter when done.
(etc)

this would make it clear to the user what to do, and mean they dont need to use Workbench or similar.

Factory setups work fine. But running creator, the create device.bc file reports 👍

pico manager create failed: nothing uses verb

Anyone run into this?

MH I dont really use, not sure if anyone else does?
so lower prio

string and wind instruments are mono, this is implemented with stringer

factory usually put this inside rig, but I dont since stringer is incompatible with fingerer
allow adding of stringer, in between rig and key group, use picomix wiring as its proven

the original idea was I was going to add scripts, as modules that could be linked together.

they still are scripts, but the they arent strictly belcanto scripts (because they have invalid template code in them) , so they should be moved to a top level directory

also, whilst it is a modular system, this doesnt really describe what it does, so I think I will rename to 'creator' as its a creator of setups.

from Antonio
how about variations of the same rigs but without the recorder, can I add them ?

control to allow octave up and down

allow more flexible control of bow position/velocity - either keyed, breath or strip
(similar implementation to pico mix i guess)

also try to see if bow pressure can be placed on the keys for Martin

remove player and simple from basic config, and start creation of a 'demo config'
... im thinking that the new one , will be something like pico max, tau max alpha max etc:)

The current file only creates an output. Adding the following will create appropriate column/row settings so output can be selected:

%VAR1% hey keygroup output %VAR2% key column to 1 set
%VAR1% hey keygroup output %VAR2% key row to %VAR2% set

AM - small correction line 48
%VAR1% hey gateway output strip position 1 to scaler inputs global pitch bend input connect
This is not present in factory setup, and doing so will pitch bend at the same time bowing...?!?!
((edit: found a reason; it's because every other rigs use this... delete?))

AM - There should be mention (attention to) that EigenBrowser must be running, or impulse file does not load!

metronome control
drummer control - perhaps, dont really use
instrument control... might think which are useful
mixer control... dont really want, but might consider, as will open up adding controller support to modular structure
octave control - high priority, probably next one to do (easy as well)
stringer support
fingerer support

AM - should there be more basic conf files?? like one for each "sound source";
or will this be clutter mess... more files.
basiccello
basicsampler
basicdoublesampler
basicclarinet
basicpanpipe
basicsynth
basicmidi

This I can do by now (and free you up...)

Here's an illuminator agent for use with the light scroller console. I named it "createlightscroller.bc" so as not to confuse with a generic illuminator agent.

This probably should get housed in the 'alpha' folder.

Look it over.

VAR1=%VAR1% name of illuminator agent, VAR2=%VAR2% parent keygroup, VAR3=%VAR3% parent keygroup output

To use, launch a web browser and enter 'http://localhost:1024'.
Then make appropriate setting changes in console and click 'scroll now'.
NOTE: Best to create a unique keygroup for this."

keygroup create
it to %VAR1% name ify
%VAR2% hey output keygroup %VAR3% to %VAR1% connect
%VAR2% hey output keygroup %VAR3% key output to %VAR1% mode key input connect

quite alot of different aspects to these, and many are rig specific....
need to think which are important

tau folder contains no createdevice.bc

I committed two minor updates and want to document why:

1. Flash persistence - it seems standard behavior to have the metronome light blink if using a Talker to toggle on/off. I added this to the 'createmetronometalker.bc' module.

2. The main 'basicsetup.bc' is creating a metronome and scheduler. But they were not connected anywhere. Connection is necessary to add recorder functionality. (Scheduler is not necessary if not using recorder.) Assumption: As scheduler is included by default, connecting it to metronome by default would meet requirements if recorder functionality in desired. Connection would not interfere with anything if recorder not desired,

MH, I dont really use mixers on the instrument, I find it easer with stage (which you need anyway, for visual feedback)

but perhaps others find useful, also this needs to use controller, which might prove a useful template for other controls

When using the pico to select and scroll in the EigenBrower, the currently highlighted item in the scroll does not show ( highlighting is not working ) so you cannot see what the item currently being selected is.

In the screenshot -- the "Chromatic" scale is currently what should be highlighted, the "diminished" was selected earlier using the mouse, and the cursor started on "natural major"

add support for fingerer control, this needs to be in between rig and key group

• phrase 85 of the createaudiounit script is misplaced, so its early because there is no summer at this point, this prevents the script from running.