Rotary Encoders

[Gavin]

Not sick of you, are you sure your not sick of my incomplete objects !!
The object you are using are unipolar, there is a bipolar version I created, but it doesn't have a value select. In the next day or two I will mod this one to be bipolar.
In the mean time, the math solution you have should work fine.

[spacelordmother]

Not quite sick yet.

Ahhhhhh yes! I remember that object now, just got confused since I was able to set the value negative.

Thanks!

[Gavin]

@spacelordmother, sorry for the delay getting it updated, I was having power and conection issues with my Axo setup, so I pulled everything apart, and while it was appart I made a few changes, but haven't forgotten what I said I would do.

As it was quite some time ago when I did the Rot Enc objects, I had completely forgotten why I did them in the first place and the related goals. In fact the "Rot Enc Value" object was originaly designed to go into the negatives as well, the reason why it didn't was because I forgot to compare the rotary value and the minimum value in the code correctly, and instead was comparing to zero which I gues was a setup in a previous object.

Any how, I have replaced a "0" with "param_min" and all works perfectly now.
Enjoy. Every thing has been updated to the community library.

[spacelordmother]

No problem! Life has a way of slowing us down, for better or worse.

Thanks for the object update!

[spacelordmother]

Hello again @gavin

First of all - thank you so much for these objects. They are amazing, and work wonderfully now that you got me all straightened out.

I have another question (which perhaps becomes a request) related to the "value" parameter --

I currently have 4 encoders set up with your objects -- 16 total Rot Env Value objects. When I press the button on an encoder it fires out a number, which activates a group of 4 objects per the setting in the value box. Essentially, I've created 4 pages of 4 parameters each. If I am correct, then the value box is essentially just a logic statement: "if value input = value, then true"

What I am wondering is it it's possible to add a second value input so that the logic would be: "if value input_A = value_A AND value input_B = value_B, then true"

What this would do (if my thinking is sound) is allow the 3 buttons on my hardware to choose between 3 groups of 4 pages for a total of 48 controls. The main goal I am driving at is to have a combo patch that contains a simple synth, a master effects (for the internal synth and external input) and a 16 parameter cc controller to send midi to another device.

Hopefully I am explaining this well enough! My controller patch is attached in hopes that it clears up anything I failed to convey. Hope all is well in your world, wherever that might be!

Encoder control patch.axp (28.4 KB)

[spacelordmother]

As an update: from my totally unqualified perspective, it seems like this is possible:

I'm getting an error that 'param_valueB' was not declared in this scope. When I added the inlet for valueB (I renamed "value" to "valueA" to differentiate) I copied the type and attributes from the stock value param. I've looked through all the tabs and don't see anywhere that value is declared, but obviously it is somewhere and I'm missing it.

[spacelordmother]

I got it! It was as simple as the valueB attribute being incorrectly capitalized. Tested and working.

Many thanks to @nosnibor for the heads up in my PMs.