Forum

"I meant to respond to this one ---- with systems like MainStage, layering is handled extremely well even if you only send stuff on a single channel. You can even do splits with a single channel as well.....it's very rare that you actually need multiple channels with these environments."

This may be, but just as some wish to use systems like mainstage, some do not. I'm really enjoying building on and around eigend. Yes, I have Logic Studio and have used it for years (since emagic days actually) but I'd like to head in another direction and not need to rely on mainstage and it's ilk.

To be really clear, I'm not arguing against your direction at all. I am suggesting that it is not the only direction and that saying it can be done in mainstage is not a good reason to limit what can be done elsewise. (and vice versa BTW)

m

Don't worry Mike, I'm personally using EigenD like you, but we recognize these different usage patterns. We try very hard to not restrict features either way when evolving EigenD. Granted, it does make some things much more complex to implement, but in the end it's worth it :-)

To be really clear, I'm not arguing against your direction at all. I am suggesting that it is not the only direction and that saying it can be done in mainstage is not a good reason to limit what can be done elsewise. (and vice versa BTW)

Manage to stash my PICO (very difficult) and with it the small AKAI SV01v, for this holidays... installing and running 1.3.8.

Thanks Geert...and everyone at EIGENLABS
Merry Christmas to all!

Keyman

@NothanUmber, feel free to edit the relevant pages on the wiki! :-)

Merry Christmas to everyone and thanks for all the input and interaction!

Take care,

Geert

FYI, in the next version we'll have a GUI setting in the routing matrix to turn off pitch bend entirely, as well as note on/off in case you would want that also :-)

[@mikemilton
We are in violent agreement --- the only reason I mentioned this issue at all is that until the recent changes were made, the kind of thing I wanted to do could NOT be done using apps like MainStage because too much data was getting sent into it.

"I am suggesting that it is not the only direction and that saying it can be done in mainstage is not a good reason to limit what can be done elsewise. (and vice versa BTW) "

one thing you can do with multiple channels (although you need the same synth and sound on each channel), different pitch bend plus different values for whatever you have yaw set to, applied to different notes.

we're taking your suggestions into account, some will however have to wait until the end of the winter holidays to be implemented.

I've been playing around with the new routing dialog in 1.3.8, and I'm having problems getting the same behavior out of it than with the old matrix. I'm not sure if this is a bug or whether my mental model of the new system is no longer correct. Here goes:

Old behaviour:
Strip controller 1 or 2 connected to an audio unit parameter using the routing matrix, with a multiplier of say 3.0. Positioning the dial/fader etc in the AU GUI would set the 'base value', and then placing you finger on the strip controller would not affect the value until you slide up or down, at which point the dial moves in the corresponding direction.

New behaviour:
Setting a multiplier of 3.0 gives the same behaviour, but you are unable to move the parameter below the base value as you could before. I then moved the new 'base value' handle on the bounds slider (the round one between the arrows), and positioned this at 50%. Now if I touch the strip controllers the value jumps to 100% straight away and then you can slide it down. Is this jump to be expected with the controls set as I have described?

The AU routing matrix and the MIDI out CC matrix always were different in behaviour (relative and absolute respectively), so does this change represent a unification of the two routing methods, and a move to making the au parameters absolute? Can we have an option to restore the relative behaviour?

Most of the time I want to position a control in an AU at some starting value (say a pitch for an oscillator or a frequency to tune a comb filter), and then assign a control to prod it in either direction. I want the middle value of the controller (ie no key pressure, no breath, or in the case of the strip controllers the middle should be wherever you first touch it) to cause no change in the parameter value, and to be able to push the value in either direction at a certain speed given by the multiplier. Is there another requirement here to be able to set the bounds of the controls in absolute terms, so that I can set up my relative controls as I please but then have eigenD cap the values to the known range of the target parameter in order not to push it into an invalid range?

Hi 0beron,

Just wanted to tell you that I tracked down the problem and that it will be fixed for the next release. Basically, you had to be able to set the low bound range to 100% independently of where the base offset is located. So I changed the GUI to have totally independent dials for all three values. From my testing this should give you all the control you need and behave the same by default as what you were used to in the 1.2 release.

Best regards,

Geert