Sel B Object - Default Value Inlets

#1

Been meaning to ask this for quite some time now, a question about those Sel B objects.

I understand what the input does, the output does, and the chain does, but I'm buggered if I can figure out how I'm supposed to use the default input inlets. I'm assuming they're used to toggle the boolean status of the currently selected step, but how do you do that?

I've tried toggle and standard buttons, and neither of them will switch the boolean status of any of the steps. Can't find an example making use of the default value inlets either, so in the end I've had to ask.

808 or korg electribe style step sequencer
#2

The default inlets can be used for chaining several sequencers into one long sequencer. Maybe they have other uses too, but I think that is the main usecase:

#3

Cheers Jaffa, doesn't make sense though, cause even without connecting those outlets to the inlets, the chain would still work so I don't see the point in that.

How would you go about toggling the steps by connecting something to the inlets?

#4

Yeah it does make sense. Cause if you only use the green chain inlet, the only thing you do is chain the sequencer, you dont forward the triggers from one sequencer to the next. Which means you have to do all sorts of stunts to combine the trigger outputs:

Screen Shot 2018-01-29 at 19.53.51.png777x370 13.5 KB

Its a mess without using the default value inlet.

#5

Dont understand what you mean. Could you explain in another way?

Do you want to use knob or some buttons to turn on/off the steps/toggles of the sequencer?

#6

I basically thought that whatever position the sequencer is at, if you were to connect a toggle and use it at that position, it would toggle the status of the boolean at that specific step. I don't get how I'm supposed to toggle the steps on/off when using it live, and surely you must be able to do that otherwise what's the point in them being toggleable?

Unless I'm misunderstanding their intended use.

#7

you cannot programatically toggle the steps. (*)

if you want to do that, you need to use a table... but then there is no display/ui which is a bit of a pity.
(you can cobble one together but its not pretty, or particularly effective)
... it might be something SSS has tackled though, I think he has done quite a few objects like this

(*) ok, thats not strictly true, I believe by messing with parameter tables you can fudge it, but its complex and not something im going into or recommend :wink:

#8

You cant do it like that, cause as i described above, the inlets are for chaining, not for turning on/off the steps. I though that first too, but they are not for that.

Its possible to make a sequencer that loads presets that lets you change the steps/toggles and save them using mouse.

But I am not sure how to use external controls, for example a midi controller to turn on/off the different steps/toggles. Cause all 16 steps in a sequencer is basically regarded as ONE parameter.

Anyway, to access parameters and change them, the only way is coding it. You can check ctrl/hook on how to acces the parameters and write to them. The functions is called
"PExParameterChange". And this works 100%, but as technobear says, this is not super easy to do.

#9

ANYWAY, now I got curious about it and added the PExParameterChange function to a sequencer and added an inlet for it.... NOW you can see them change, something happens. If you use Power of 2....... 2,4,8,16, etc(just use the embedded object),you can access each of the steps of the sequencer. But did not try to implement how to edit the values of each toggle. This was just a first try of the top of my mind. And its a start to building a sequener I thought about for a while. Will try and fix that later on.

Anyway:

AxomanParameter test.axp (3.0 KB)

#10

AAAAND problem soved:

Here you go, acces to every single step from an external source, could be a midi controller or whatever. Nice. have been thinking about this for a while. Was much easier than I thought :slight_smile:

You just need to copy the POW3 object 16 times and set them to 0-15 and connect it all to the TEST inlet and then you got acces to all of the steps individually.

AxomanParameter test 2.axp (4.8 KB)

#11

Final version for today:

I have implemented midi cc into it now. So now you set ONE SINGLE MIDI CC number in the attribute box., for example 33. and then from 33 and the next 16 midi cc numbers will select and control each of the steps. The midi value you send from each cc number, should be above 1, so anything should work to turn on each step.

For now its ONLY controlled by midi cc, it would take too many inlets to make it with innlets so its hardcoded. You cannot use a mouse to turn steps on/off as it is now. I used a Launch XL for the testing, but you can use it with any midi controller.

So..
Grab a midi controller, hook it up to Axoloti, set a single midi cc number and the next 15 steps are autoset...... and push some buttons to turn on/off steps.

AxomanParameter test 5.axp (4.6 KB)

#12

That's absolutely what I was getting at, Jaffa, thanks a lot for doing that!

After doing all that, you'll probably hate me for saying this but I actually don't need the object, I was just curious as to how it worked really, have been since I first got the Axoloti. That third version though, that's a real game-changer for this object, puts it's usage on a whole new level, it's what I assumed the default object would be capable of.

I'll play with it tonight, I want to see how it might be used in place of more elaborate setups in order to save CPU on sequencer-based stuff.

Very nice, thank you :wink: